Forum Moderators: Robert Charlton & goodroi
I've read the threads about canonical root issues
[webmasterworld.com...]
And here:
[webmasterworld.com...]
and I think I understand the reasons why.
Recently I've observed websites that are redirecting with a 301 from example.com/ -> example.com/index.htm
They have all of there internal links pointing to the /index.htm page on the site so for me this is the same as redirecting from /index.htm to / so why is Google indexing the root / URI and not the full path /index.htm .
Would this cause an issue for Google and slow the indexing of the site, I just don't understand if the 301 is pointing to the index.htm why Google needs to index the example.com/ as the homepage of the site.
Is there any real difference as long as there's only one root or does Google's Algorithm insist that I use example.com/ as my root URI now.
Any advice greatly appreciated.
Vimes.
[edited by: tedster at 5:17 am (utc) on Mar. 8, 2007]
[edited by: Vimes at 5:25 am (utc) on Mar. 8, 2007]
You may in the future change to php driven pages or shtml if you need server side data, then you would have to 301 ALL htm documents to their php new version, save the hassle and work on /
Yes it would appear that’s what Google’s saying as its displaying the example.com/ in the SERP’s I think I’ll run a test on two separate new domains and see which gets fully indexed first.
Vimes.
I dont think it will help in speeding up indexing, not so you would notice anyway, its just the best route that this forum has come up with, I built a site a month ago, within 4 days it was ALL in the index, no PR obviousley and I linked to it from a PR6 page.
Bad move.
Google prefers to index the shorter version of the URL.
The redirect should point the other way, and the internal links should also all point at the shorter version too.
