Welcome to WebmasterWorld Guest from 220.127.116.11
[edited by: Robert_Charlton at 11:20 am (utc) on Jan 8, 2013]
[edit reason] examplified domain [/edit]
In GWT, on the "crawl error" page you can select each error and by type of error. When you check the links by clicking them, what additional information does it give you about where the links are "Linked From" (that's the name of the tab)?
It's likely the errors are links created by crawl mistakes but it would be interesting to know if they are all from your site or if there are any external links creating them.
You should do: href="/svenska/"
The leading slash is required.
The link should not mention the index file filename.
Your DirectoryIndex directive should take care of delivering the correct content.
ensures that when a user requests
- the canonical URL for a folder or for the index page in a folder - the server uses the content of the index.htm file in that folder to fulfill that request, without telling the user what that file is actually called.
directive is also relevant. When user requests
for folder name that exists, the server will send a redirect telling the browser to make a new request for
DirectoryIndex index.htm ensures that when a user requests example.com/folder/ - the canonical URL for a folder or for the index page in a folder - the server uses the content of the index.htm file in that folder to fulfill that request, without telling the user what that file is actually called.
The DirectorySlash directive is also relevant. When user requests example.com/folder for folder name that exists, the server will send a redirect telling the browser to make a new request for example.com/folder/ instead.
tag to each index page would be a good idea.
Thats the server already do,Correct - By default a server is usually set up to look for pages named "home", default" and "index" when a user clicks into a directory including your home directory (public_html).
I have tested mysite/espanol
and mysite espanol/
and I get my site with/ at the end and without mentioning index.htm
DirectoryIndex example.htmlin the htaccess file in the folder named "/name/"
So do I understand you right if I add this to htaccssThat is correct but you do not need to do this because your server is already doing it by default... there's no reason for you to go the effort or add new files unless you plan on using something much different for the name of the index page to be served to users. This works per folder as well.
that will take you to the index page on root and on folders index page?
DirectoryIndex widgets.htmlif that were in the htaccess for the folder/directory "mysite.com/swedish/" you are telling the server to show the page named "widgets.html" to users as the default index page even if there is a file in the same directory named "index.html".
That is correct but you do not need to do this because your server is already doing it by default... there's no reason for you to go the effort or add new files unless you plan on using something much different for the name of the index page to be served to users. This works per folder as well.
You'll want to make sure you use the trailing slashes "/" to avoid server redirects; the server will add it anytime you leave it off of a "/folder/directory" link to push the user inside the "/folder/directory/" - then it looks for the default index page to serve content.
DirectoryIndex finds the right internal index file when URL with trailing slash is requested.
When URL with index filename included is requested the server will serve the index file as duplicate
content unless you add a RewriteRule that tells the browser to make a new request for the right URL -
the one ending with a slash.
# REDIRECT ROOT htm INDEX PAGE
Looks like all 404 errors starts with one of these patterns:
links out to
[edited by: Robert_Charlton at 10:03 am (utc) on Jan 10, 2013]
[edit reason] delinked linked example [/edit]
makes space for any and every query string parameter of any length - and it gets stripped in the redirect.
are supposed to redirect, then replace the '
' bit with '
' or whatever you need in both places.
If you have rules for both http and https in the same file that potentially cover the same path requests, you'll need to add extra conditions to both rulesets otherwise one will run for every request and the other will never run.