Search Console indexing errors and how to fix them
What each Search Console "Page indexing" status means, why it happens and how to fix it step by step.
- Crawled - currently not indexedGoogle crawled the page but did not add it to the index. Googlebot visited the page and read its content but decided it was not worth adding to searc…
- Discovered - currently not indexedGoogle knows the URL but has not crawled it yet. The URL was discovered from your sitemap or a link, but Googlebot has not visited it yet. It usually…
- Duplicate without user-selected canonicalGoogle found duplicates of the content and you did not declare a canonical. The same or very similar content sits on several URLs and none of them ha…
- Duplicate, Google chose different canonical than userYou declared a canonical but Google picked another URL. Your page carries a canonical but Google judged another URL more fitting from content and oth…
- Alternate page with proper canonical tagThe page canonicalises to another URL; usually expected. This page declares itself a copy of another URL and Google accepts that. It is normal for…
- Page with redirectThe URL redirects elsewhere, so it is not indexed. The URL returns a redirect; Google indexes the target, not the redirecting URL. Usually healthy, b…
- Soft 404The page looks empty or like an error but returns 200. The server says "success" (200) but the content reads to Google like a missing page: an empty …
- Not found (404)The URL returns 404. Googlebot visited and the server answered "not found". If you removed the page on purpose this is normal and it will drop out ov…
- Blocked by robots.txtrobots.txt stops Googlebot from fetching the URL. A Disallow rule in your robots.txt forbids crawling this URL. Google cannot read the content; if ot…
- Excluded by 'noindex' tagThe page has noindex, so Google deliberately leaves it out. The page says "noindex" through a robots meta tag or an X-Robots-Tag header. Google obeys…
- Server error (5xx)The server returned a 5xx error to Googlebot. The server answered Googlebot with 500, 502, 503 or a similar error. If errors persist Google slows cra…
- Redirect errorThe redirect loops or the chain is too long. Google could not follow the redirect to the end: a loop, a very long chain, or an empty or overly long t…
- Indexed, though blocked by robots.txtThe URL is blocked by robots.txt yet still in the index. Google did not crawl the URL because robots.txt forbids it, but it knows the address from li…
- Blocked due to unauthorized request (401) / access forbidden (403)Googlebot could not read the page because it asked for login or access was denied. The server answered Googlebot with 401 (login required) or 403…
- URL is unknown to GoogleGoogle has never discovered the URL. URL inspection says Google has never seen this address. The page may be new, or no link or sitemap entry leads t…
- Indexed, not submitted in sitemapThe page is indexed but not in your sitemap. Google found the URL through a link and indexed it, but it is not in your sitemap. Usually harmless; it …