Google Search Console Errors: Meanings & Fixes
Google Search Console shows errors that directly explain why pages are not ranking. Each status in the Pages report maps to a specific technical cause — understanding what Google is actually telling you is the first step to resolving it quickly. This guide covers every major GSC error, what it means, and the exact steps to fix it so your pages can get indexed and rank.
Your sitemap contains a URL that robots.txt prevents Googlebot from crawling. Either remove the URL from your sitemap (if the block is intentional) or update robots.txt to allow the URL (if it should be indexed). Check your robots.txt at yoursite.com/robots.txt and look for Disallow rules matching the affected URLs.
Your sitemap includes a URL with a noindex meta tag on the page. These directly contradict each other - your sitemap says index this, the tag says do not. Either remove the URL from your sitemap or remove the noindex tag from the page. Check the page source for meta name=robots content=noindex.
A URL in your sitemap does not exist - it returns a 404 error. Either restore the page, create a 301 redirect to the current URL, or remove it from your sitemap. Sitemaps should only contain URLs that return 200 status codes.
A URL in your sitemap redirects to a different URL. Update your sitemap to contain the final destination URL directly. Sitemaps should never contain redirecting URLs - only the canonical final destinations.
Google crawled the page but decided not to index it. Common reasons: content is too thin or too similar to other indexed pages, the page has no meaningful unique content, or Google chose a different canonical URL. Improve the content quality and depth, add internal links pointing to the page, and verify canonical tags are set correctly.
Google knows the page exists but has not crawled it yet. This usually resolves on its own within a few weeks. Speed it up by: submitting the URL via URL Inspection and clicking Request Indexing, adding internal links from well-linked pages, and ensuring the page is in your sitemap with an accurate lastmod date.
This URL in your Coverage report redirects to another page. This is usually informational, not an error. However, if these are URLs you submitted in your sitemap, remove them and replace with the final destination URLs.
Google found duplicate content and chose its own canonical - not necessarily the one you prefer. Explicitly add a canonical tag to the page pointing to your preferred URL: link rel=canonical href=https://yoursite.com/preferred-url.
Google got a 5xx server error when crawling the page. Check your server logs for the specific error. Common causes: server overload during crawl, PHP errors, database timeouts. Fix the underlying server issue, then use URL Inspection to request re-crawling.
A soft 404 occurs when a page returns a 200 status code but contains content indicating the resource doesn't exist - for example, 'No results found' on a search page, or a deleted product page that renders a blank template. Google sees the 200 and knows something is wrong. Fix by returning an actual 404 or 410 status for truly gone content, or improve the page content so it provides genuine value. Soft 404s waste crawl budget and signal poor content quality to Google.
Googlebot cannot access a page protected by HTTP authentication (a username/password prompt). This is expected for private areas but a problem if the page is in your sitemap. Remove these URLs from your sitemap and add a Disallow rule in robots.txt for the protected path. If the page should be public, check your server configuration - authentication headers or .htaccess rules may be applying incorrectly to URLs that should be open.
Google has indexed a URL that is not in your sitemap. This is often not a problem - it means Googlebot discovered the page via internal links. However, review these URLs: some may be parameter variants or session ID URLs that you don't want indexed. For any unintentionally indexed URLs, add a canonical pointing to the correct version or add noindex if the page has no search value. For important pages you missed in your sitemap, add them to ensure they receive the crawl priority sitemap URLs get.
This is informational, not an error. Google has found a page and correctly followed the canonical tag to index the preferred version instead. This status appears for pages that are intentionally canonicalized to another URL. No action needed unless you see a page here that should be the canonical itself - in that case, check whether the canonical tag is pointing in the wrong direction and correct it to a self-referencing canonical on the intended preferred page.
Google crawled and indexed the URL but found no content - the page likely rendered empty due to a JavaScript error, failed API call, or server-side rendering issue. Use URL Inspection, click Test Live URL, and check the rendered screenshot. A blank or near-blank rendering confirms a JavaScript rendering problem. Check your browser console for errors on the live page and ensure the content is available in the initial HTML or server-side rendered output before JavaScript executes.