I think the main search engine problems come up when there are lots of 
parameters in the URL, although Google seems to do pretty well.  One 
solution is to turn what would have been parameter names into 'directory' 
names in the URL.  For example, on my site, rather than have a url like:
http://amnestyusa.org/exe.do?method=countries&value=china&pagetype=index
I have action mappings of the form:
/countries/china/index.do
that all go to the same basic action.  The action then decodes what to do 
from the URL.  In a lot of ways this is similar in effect to what the 
rewrite engine in Apache can do (turning    /x/y/z  into 
/cgi-bin/x.cgi?param1=y&param2=z ).

I'm sure there is a better way, but this has been working pretty well. 
Along with helping some search engines, it gives users  urls that are much 
easier to remember.

Joe Baker
Amnesty International USA





"Brian Styles" <[EMAIL PROTECTED]>
12/19/03 09:56 AM
Please respond to "Struts Users Mailing List"

 
        To:     [EMAIL PROTECTED]
        cc: 
        Subject:        Struts and Google


Hi all,

I've searched the archives on this topic, but would appreciate any up to 
date advice. I have my actions forwarding to my jsps in my WEB-INF folder. 

Thus my jsps are protected from direct access. However I obviously want my 

site to get as high a rating on google and other search engines as 
possible. 
Now I have heard differing reports that google can list dynamic sites and 
also that it cannot. I would very much like to know people's experience 
with 
this.

If the answer is that google cannot crawl a struts site like this, then 
I'd 
very much appreciate user's previous approaches to this problem.

thanks very much,
Brian

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to