Hi Jeremy,
Hi Dan,
for a project long ago I had the trail of making a product-browser SEO
friendly; I used a plain PagingNavigator at first, and then extended it
to have it to use the IndexedUrlPageParameters; this allowed me to put
anything into the path to have a nice URL;
the key here is to look at the URL and treat it as a unique resource
line; so I did it sth like that:
mountName{(/anyparams)}*{/pageNumber}
this gave me the possiblity to have a browsing URL where I could put
anything in while the rest still works; remember also that the URL for
SEO may (!) change in future, so go for maximum flexible designs, up you
see a resource, then any params to feed the spider (there may be 0 to
over 10) and a hook at the end that has to be a number (where 0 is
pretended in case nothing at the end is a number);
so I was able to finally let the spider see things like:
e.g:
product/brand_New/BestItemOfTheWorld
product/specialCategory/moreSpecial/moreInfo/2
product/spcialCategory/moreSpecail/brandName/moreDetails/1
etc.
now, you wonder if I feed the spider with this how do I know where to
end? the key was that the part between got merged internally and was
specified by the application so we overcome the problem of:
a, recreating the view that should be the right one (here: we had a
tree-like behaviour for our products where we could compare to the tree
in database)
b, duplicate content (very bad! - never, ever have a spider find the
same content (or very very similar!) under more than one URL !)
this strategy did very well; Today with wicket 1.3 I would go nearly the
same but stick to the HybridURL scheme, and maybe try to be even more
flexible with URL scheme by having the basic schemes and resources
specified in persistence (URL-hook, initialState); Remember it is
important to feed same resources under same URLs out, else the spider
will think you might try to fake content for him;
The jsessionID is sth. I dont care about anymore - its 2008, spiders
knows it and the usual visitor/ surfer has no clue how to different a
URL from an emailadress; however many people have turned cookies + JS
off because of security fears - in turn the JSessionID will concern only
few people who know about some details but hamper many people that have
no knowledge of the internet and its techniques all over - IMHO.
@Jeremy: your aproach also seems interesting to me, can you give more
details about it?
Best,
Korbinian
Jeremy Thomerson schrieb:
....
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
