Thanks,

Joel

<meta http-equiv="content-language" content="lv">

And likewise one for "en" on your translated page. This will help Google know what it's looking at.

Stephan. Good idea. A "sitemap" is always a good way to get Google about your whole site.

I provide on every page a link on the bottom of the page:

<div id="searchenginestarthere"><a href="fullurl/siteoverview">List of all pages</a></div>. With css I hide it: div#searchenginestarthere { display : none }.

siteoverview is a PAGE (passthrou html) with an embedded view that lists the first 1000 documents. Nicely done with link & description so the spider has something to read. This way no page is further that 2 clicks away from the homepage (at least for the spider). If u like I can email the template.

:-) stw

One thing that made me chuckle, though, was the search facility. You can easily prove you built the site as searching for 'Jake Howlett' returns every page within the database! Good old Lotus, nice of them to give us an 'Exclude field from FT search' option!!!

All the best!

Until recently, like you, I had mainly been concerned with Intranets but now I'm working on public web sites that are concerned about accessibility. Such JavaScript links will not pass accessiblity tests.

There are ways round it - see {Link}

As with most things in life - it pays to keep things simple. The trouble with relying on the 'easy' option of Domino-supplied functionality is that you'll usually pay for it in the long run.

As with most things Domino, there's many ways of doing it. Which is best? Who knows!

I guess it depends on the kind of website you're working on and how many document you expect it to hold. In my case the site I am working on will probably never have 1000s and performance should be ok.

Oh Lord of the CodeStore.... You may smite me down after this reply, but have you ever done/thought of this!!!

With regards to Domino and counting of documents in a View. Whenever i need to do this, i create a computed field called "Total" that extracts the "&total=" value from the Query String.

If the query string does not contain this value, then i perform an "@DbColumn" or "@DbLookup" to return the list of the documents in the View. From this i use the "@Elements" to extract my view total.

--- Total Field Value ---

t1 := @Middle(Query_String; "&total="; "&");

@If(t1 <> ""; @Return(t1); @Success);

t2 := @DbColumn(""; ""; "View"; 1);

@If(@IsError(t1); 0; @Elements(t1))

--- Total Field Value ---

Although this will fail for HUGE views, it works for most. Also, because the Total calculation is done once and then passed to the "Next" & "Prev" pages, it processes pretty quickly.

--- Next Link ---

View?OpenView&Start=21&Count=20&Total=100

--- Next Link ---

Using the Total field i can then calculate when to Show/Hide the "Previous" and "Next" links.

--- Hide Previous Link ---

Start = 0 | Start = ""

--- Hide Previous Link ---

--- Hide Next Link ---

Start + Count >= Total

--- Hide Next Link ---

The Exact coding above may not be 100%, but the logic is sound!

Anyway, just thought i'd throw my oar in!

Later

Patrick