Google Search Console errors, and how to fix each one.
Search Console uses short messages, such as "Crawled - currently not indexed" or "URL is not on Google". Find yours below.
Page indexing report
Pages Google chose to leave out
- Crawled - currently not indexedGoogle visited the page and chose not to show it in search, usually because the page added too little.
- Discovered - currently not indexedGoogle knows the page exists but has not visited it yet.
- Duplicate without user-selected canonicalGoogle sees the page as a copy of another page, and the page doesn't say which one is the main page.
- Duplicate, Google chose different canonical than userYour page says it is the main page, but Google picked a different page.
- URL is unknown to GoogleGoogle has not found this page anywhere yet.
- Soft 404The page loads, but Google thinks it looks like an error or an empty page.
Blocked by a setting on your site
- Page indexed without contentGoogle added the page to search but could not read what is on it.
- Excluded by 'noindex' tagA noindex rule on the page tells Google to leave it out.
- Blocked by robots.txtYour robots.txt file stops Google from visiting the page.
- Indexed, though blocked by robots.txtGoogle lists the page because of links, but robots.txt stops Google from reading it.
- Not found (404)The page shows a 404 Not Found error.
- Server error (5xx)Your server showed an error when Google asked for the page.
- Redirect errorThe redirects for this page are broken, too long, or go in a circle.
- Blocked due to unauthorized request (401)The page needs a login, so Google can't read it.
- Blocked due to access forbidden (403)The server turned Google away with 403 Forbidden.
- Blocked due to other 4xx issueThe server showed a 4xx error other than 401, 403, or 404, such as 400 or 410.
Often fine
On Google
URL Inspection results
- How to read a URL Inspection result
- URL is on GoogleGoogle has the page in its index, and it can show it in search. That does not promise it shows up for the words you search.
- URL is on Google, but has issuesThe page is in Google's index. Something extra on it, such as structured data, has a problem. The page itself can still show in search.
- URL is not on GoogleGoogle did not add the page to its index, so it can't appear in search. The reason is in the Page indexing section, right below the verdict.
- No referring sitemaps detectedGoogle did not match this page to a sitemap you submitted. It found the page another way, or not yet at all.
- Referring page: None detectedThe tool can't show a page that links here. That does not prove no page does. It often means the page needs more links.
- Last crawl: N/AGoogle has no successful visit to this page on record. So it has nothing indexed to show yet.
- Crawled as: Googlebot smartphoneGoogle visited the page with its mobile crawler. That is normal. For most sites, Google indexes the mobile version of each page.
- Crawl allowed? No: blocked by robots.txtA rule in your robots.txt file tells Google not to visit this page. Google follows it, so it can't read the page.
- Page fetch: FailedGoogle tried to get the page from your server and could not. The words after "Failed:" say why.
- Page fetch: Failed: Redirect errorGoogle followed the page's redirects and gave up. The redirects go in a circle, run too long, or lead to a bad address.
- Server connection errorGoogle could not connect to your server at all. That is a problem for the whole site, not just this page.
- Page fetch: Successful, but not indexedGoogle got the page without trouble and still left it out. The reason is about the page or a duplicate, not your server.
- Indexing allowed? No: 'noindex' detectedYour page tells Google not to index it, with a noindex rule in a meta tag or an HTTP header. Google follows it.
- User-declared canonical: NoneYour page does not name a main address. For a page with no copies, that is fine.
- Google-selected canonicalThis is the address Google treats as the main version of the page. Inspected URL means this page. Another address means Google sees this page as a copy.
- URL is available to GoogleThe live test found nothing that blocks Google. That is not the same as being indexed. The live test skips several checks.
- Indexing requestedGoogle added the page to its crawl queue. It will visit, then decide whether to index it. The request does not promise indexing.
- Quota exceededYou hit Search Console's daily limit for Request indexing. Google does not publish the number. Try again the next day, and let your sitemap handle the rest.
- Indexing request rejectedTo fix "Indexing request rejected", click Test live URL, fix the problem it names, such as a noindex rule or a page that doesn't load, and click Request indexing again.
Validate fix
Sitemaps report errors
- Every sitemap message, and the guide for it
- Couldn't fetchCouldn't fetch means Google could not download your sitemap file at all. Open the address yourself, run a live test in URL Inspection, fix what blocks it, and resubmit.
- Sitemap could not be readSitemap could not be read means Google's download failed. The details below it, such as General HTTP error or an HTTP error with a code, tell you why.
- Sitemap is HTMLSitemap is HTML means the address you submitted returns a web page, not a sitemap file. Submit the XML file instead, or find what replaces it with a page.
- Temporary processing errorTemporary processing error is a problem on Google's side, not in your sitemap. Run the inspection again later. In the Sitemaps report, resubmit only if Temporary error lasts for hours.
- Has errorsHas errors means Google downloaded your sitemap but found problems in it. Google still uses the addresses it could read. Click the sitemap to see each error, then fix them in the file.
- URL errorsThese errors mean some addresses in your sitemap don't match where the sitemap lives, can't be read, or can't be crawled. Make every address a full URL on the same host and protocol as the sitemap.
- XML and format errorsThese errors mean the sitemap file is not valid XML, or not in the sitemap format Google expects. Most come from a plugin or theme printing extra text, or from an unescaped &.
- Invalid dateInvalid date means a <lastmod> date in your sitemap is in the wrong format, or is not a real date. Use 2026-10-08, or a full time with a time zone.
- Too large or emptyOne sitemap can hold up to 50,000 URLs and 50MB uncompressed. Split a larger one into several files and list them in a sitemap index.
- Sitemap index errorsA sitemap index can list sitemaps, but not other sitemap indexes. Every listed sitemap needs its full address.
- 0 discovered pagesSuccess with 0 Discovered pages means Google read the file but found no page addresses in it. Check what the file lists, and where it lives.
- Old Last read or pendingGoogle re-reads a sitemap on its own schedule. A Last read date that does not move after you change pages, or a sitemap with no Last read date, needs a check.
- Success, but pages not indexedSuccess means Google read your sitemap. It does not mean Google indexed the pages in it. Filter the Page indexing report by your sitemap to see why each page is left out.
Structured data errors
- Find your structured data message
- Merchant listings: missing fieldsA missing name, image, or offer price is critical: those products can't show as merchant listings until you fix it. A missing description, shippingDetails, hasMerchantReturnPolicy, or GTIN is non-critical and can wait.
- Missing field "shippingDetails"This is a non-critical issue in the Merchant listings report, so your products can still show with their prices. Add shipping details if you want Google to show your shipping cost and delivery time too.
- Missing field "hasMerchantReturnPolicy"Google wants your return policy, and your product markup doesn't include it. It's a non-critical issue, so your products still qualify for merchant listings. Adding the policy lets Google show your return window and cost next to them.
- No global identifier providedGoogle wants a product ID that is the same everywhere the product is sold, such as the barcode number. It's a non-critical issue: add the GTIN if your products have one, and leave the warning if they don't.
- Either "offers", "review", or "aggregateRating"Google found Product markup with no price, no review, and no rating, so that product can't get a rich result. Give the markup an offer, or remove the stray Product block that shouldn't be there.
- Product snippets: missing fieldsMost Product snippets warnings are non-critical. Missing field "review" or "aggregateRating" usually means the page has a price but no ratings, and Google's own docs say that can trigger a warning you can leave.
- Missing field "priceValidUntil"Yes, unless the product is on sale with an end date. The warning is non-critical. Watch for the opposite problem: a priceValidUntil date in the past can stop your product's rich result from showing.
- Invalid object type for field "brand"Your product markup gives brand the wrong type, often Thing. Change it to Brand with a name. It's a non-critical issue, so it doesn't block your product's rich result while you fix it.
- Review snippets errorsA Review snippets error means Google won't show stars for that item. Each one has a small fix: a supported type, a rating count, a name for the reviewed item, or the rating scale.
- Invalid object type for field "<parent_node>"Google's help doesn't explain <parent_node>. Reports from site owners point to one pattern: the wrong type is on the object the markup hangs from, not on a named field. Test the live page first, then check the types below.
- Breadcrumbs: missing fieldsEach Breadcrumbs "Missing field" error is a gap in your BreadcrumbList: an empty list, a crumb with no address, or a crumb with no name. It stops the breadcrumb trail from showing, not the page.
- Unparsable structured dataGoogle found structured data with a syntax error, so it couldn't read that markup at all. Every item in this report is critical. When many pages share an error, a template is usually the cause.
Bing Webmaster Tools statuses
- Why Bing is not indexing your site
- Discovered but not crawledBing knows the page exists but has not crawled it yet, so it can't appear on Bing. Here is why it happens and what to do.
- URL cannot appear on BingURL Inspection says the page is not on Bing. The line above it tells you why. Here is how to read it and fix each case.
- URLs with guideline issuesBing crawled the page and chose not to show it. In Site Explorer it sits under Excluded or "URLs with guideline issues". Here is what to change.
- URLs that are robots.txt disallowedA robots.txt rule tells Bingbot not to crawl these pages. Find the line that matches, check whether you meant it, and fix it if not.
- URLs with NOINDEX tagThese pages ask Bing not to show them, and Bing follows the rule. Remove the tag from pages you want on Bing. Keep it on the rest.
- URLs that are redirectingThese addresses send Bingbot to another page. That is fine for old addresses. It is a problem when your sitemap or links still point to them.
- URLs with crawling issues (deadlinks)Bingbot asked for these pages and got a 404 or 410. Fix the ones that should exist, redirect moved pages, and let deleted pages go.
- URLs with crawling issues (server errors)Bingbot got a 403 or a 5xx from your server. Often a firewall blocks Bingbot. Sometimes the server is too slow. Here is how to tell and fix it.
- Bing blockers people missYour site is on Google but not on Bing. These Bing-only blockers are the usual reason: firewalls, crawl-delay, a missing sitemap, and more.
More ways to get pages on Google
- The best Google index checker toolsSix tools ranked by who each one fits, from free Search Console to sites with a million URLs.
- Is Search Console enough, or do you need an SEO audit tool?What Screaming Frog, Ahrefs, and Semrush add, what they cost, and when they are worth it.
- Is there a Google Search Console alternative?Nothing replaces it, but other tools fill its gaps. Here is which tool fills each one.
- Google Indexing API vs sitemapsThe Indexing API is only for job posts and livestreams. Every other page needs a sitemap and links.
- Pages not indexed on your platformFixes for Shopify, WordPress, Webflow, Wix, Lovable, and more.
- Add a site from another Google account
- Tell Bing when your pages changeSet up IndexNow on your platform, so Bing and Copilot see new pages sooner.
- Let your AI agent fix your pagesYour agent makes the changes and asks CrawlCoach to check them with Google.
Which of these affect your site?
Get my free reportFree for up to 500 pages. No card needed. Sign in with the Google account you use for Search Console.