Forum Moderators: Robert Charlton & goodroi
I have run Xenu on both my sitemap and site. And both my site and sitemap include target urls only, not one redirects. What's more, the above url appears in neither. Apart from the homepage, my urls end in /index.html.
I have not made any changes to my sitemap or structure of the urls in months. On 9 Jan, however, I changed the preferred domain setting in Webmaster Tools from don't set a preferred domain to display urls as www.example.com. (A 301 redirect from non-www to www in .htaccess has been in place for some time and our urls are indexed correctly.) Could this be our problem?
Another thought. I manage the 301 redirect from non-index.html to index.html (example http://www.example.com/<category>/<page>/ to
http://www.example.com/<category>/<page>/index.html
in realurl (TYPO3 module). Is it possible that google is now considering non-www to www in .htaccess and / to index.html in realurl as a multiple redirect? (Of note the 301 redirect from / to /index.html was implemented nearly 2 years ago.) Is there a better way to accomplish the above? I can't drop /index.html as I have too many external links to my internal pages. Is it possible to manage the 301 from / to /index.html, on internal pages only, in .htaccess? If so, what is the correct htaccess code for manage the following kind of redirect?
http://example.com redirect to http://www.example.com/ (homepage non-www to www)
"http://example.com/../<page>/index.html", "http://example.com/../<page>/" and "http://example.com/../<page>" (without slash) all redirect to "http://www.example.com/../<page>/index.html" (non-www internal pages, with or without index.html, redirect all to www with index.html)
[edited by: tedster at 7:49 pm (utc) on Jan. 22, 2009]
[edit reason] switch to example.com - it can never be owned [/edit]
Is it possible that google is now considering non-www to www in .htaccess and / to index.html in realurl as a multiple redirect?
If it happens in two steps, it is a multiple or chain redirect - so it's best to avoid it, even though 2 redirects of this kind is often not a problem.
what is the correct htaccess code for manage the following kind of redirect?
For handling all manner of complex canonical redirects on an Apache server, I'd recommend this post in our Apache forum:
A guide to fixing duplicate content & URL issues on Apache [webmasterworld.com]
