dave4c03 wrote: > - Common sense would suggest that search engines identify context > from that which people "see and use" which is navigational > menus andlinks to the page (and not by deconstructing the URL).
You might think that, but it does seem documented that engines deconstruct the URLs and use this info. I think it's fair to say that the linking structure of the site IS more important to them, though. > - You do not want to contaminate the URL in any way and that > means you do not want keywords that are not supported by the > page content in your URL. > In particular, you do not automatically want any navigational > context keywords or directory structure keywords in your URL. That really depends on your organization, doesn't it. A well planned website will usually organize parent/children by their topic creating themes. And you DO want this to show up in your URLs. In fact most testing suggests that this strengthens your site from an SEO perspective. Granted, if you arbitrarily create a structure like example.com/bodies-of-water/tulips/neil-armstrong, the URL probably won't help you. > - Furthermore, as the web site content grows and changes, > as they areprone to do, you want to be able to move the > page and change the menu/navigational structures without > breaking internal or external links to a URL resource. Sure, but this is wholly separate from everything else. If you move a page, you must either: change all links to it, have some automatic mechanism for changing all links to it, or else have Radiant do a redirect from the old page to the new one for you. Picking a Radiant tree location and a different URL doesn't solve this problem. There has been discussion about this. > - The Menu1/SubMenu2/keyword1-keyword2-keyword3 and the > Menu3/SubMenu4/keyword1-keyword2-keyword3 menu/navi- > gational structures should both refer to the same page > (http://example.com/keyword1-keyword2-keyword3). After > all, a page should be able to participate in multiple > navigational contexts. You can do this today. Make a page with your content at the desired URL. Make another page at another desired URL and include the following in the body: <r:find url="your/first/url"> <r:content /> </r:find> Or, if you want to be TOTALLY abstract, create your pages in any organizational structure you want (say /repository/your/favorite/structure/here) with NO links to that content (maybe even using 'hidden' page type). Then create all the URLs the way you like them and link to your content in the repository. This solution affords you the benefit of a tree view that shows you the different URL structures that you are using while allowing you to store your content in some other structure. Personally, I'd work on organizing my site based on SEO themes and gain the benefits of simplicity and not having to worry about Google changing their algorithms to penalize people with 10 "different" pages that all have the same content (because this matches spammer behavior). -Chris -- Posted via http://www.ruby-forum.com/. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
