New answers tagged crawl-errors
When you have a URL in the page without a nofollow, loaded directly, it is most likely that Google will follow it. In your case, when Google is following it, it is being served with a page by your script, so it is not entirely Google's fault. You have really two options here: Add a canonical link. You mentioned that you have already done that. Add a ...
Finally found the error. The problem was in the canonical link: I had: <link href="http:www.somedomain.com/whateveryouwant.php" rel="canonical"/> It should be <link href="http://www.somedomain.com/whateveryouwant.php" rel="canonical"/> The "//" were missing. The Seo-Spider recommended by @closetnoc did help me to find the problem.
The link you refer to in your example is not absolute, because it does not contain the http://www.mysite.com/ part. However, there is nothing wrong in using relative paths in your link (i.e, starting with '/'). This is authorized and ok. It is not an issue. Browse your page and check the page source for the duplication you are reporting. If you see, then ...
Your sitemap example looks to be correct. I would make sure that your whole sitemap is correct before taking any further steps. Otherwise, it has to be something on your website. But there is not enough information here to determine what exactly is going on. Check your header and footer includes if the pages listed in Google Webmaster Tools appear to be ...
If you are getting crawl errors, then yes it is affecting crawling. I'm guessing how you have your page files and your include files organized on your server is incorrect. Do you have your header.html in a separate directory than the whateveryouwant.php file?
I once had the same problem, which I solved by adding the following lines to my .htaccess file: php_flag display_startup_errors off php_flag display_errors off php_flag html_errors off Also check that your php.ini is fine.
You should check the site to confirm if the errors are happening or not. Also look at the server logs to see if something happened at the time Google was crawling the site and then resolved itself. It could be an intermitted error that resolved itself but might show up again. So steps to take: Confirm if errors exist on the site for the pages reported in ...
Top 50 recent answers are included