Search Console and Merchant Center error decoder
Paste a Search Console or Merchant Center message and see what it means.
- Paste and test
- 2 rules
- Last updated
What it checks
- The page indexing statuses: «Crawled – currently not indexed», «Discovered – currently not indexed», the duplicate and canonical messages,
noindex, robots.txt blocks, soft 404, 404, redirects and server errors. - The sitemap messages: an address in the sitemap that is a 404, a
noindexpage or blocked, and a sitemap that cannot be read. - Structured data messages: a missing field or an invalid value, such as a price written with a symbol or Arabic digits.
- Merchant Center messages: price or availability that differs from the page, a missing image, an invalid GTIN, a landing page that does not work.
- Core Web Vitals messages: LCP, CLS and INP.
- It reads Google's wording in English and the stems of the Arabic interface's; a message it does not know gets the list of those it does.
Example
<meta name="robots" content="noindex, follow"> <link rel="canonical" href="https://example.com/">
<meta name="robots" content="index, follow"> <link rel="canonical" href="https://example.com/">
How to fix
Most messages come down to one of a few causes. Read the message, find the cause here, and fix it where the page is made:
- «Excluded by 'noindex' tag»: remove the
noindexfrom the page's robots meta tag and from theX-Robots-Tagheader, then ask Search Console to inspect the address again. - «Duplicate…» and canonical messages: make each page's canonical the address you want in search, and make your links, sitemap and redirects name the same one.
- «Crawled – currently not indexed»: the page is not broken; give it content and links that make it worth indexing.
- Merchant Center price and availability messages: fix them in the feed, where the platform exports the product.
- After a fix, use the “validate fix” button in Search Console, and wait: Google checks again over days, not minutes.
<meta name="robots" content="index, follow">
<link rel="canonical" href="https://example.com/">FAQ
Paste its heading as Search Console shows it. If we do not know it, the tool lists the ones it does. Google's own help page for the report explains the rest.
Not necessarily. It means Google fetched it and did not index it yet. The usual reasons are content that adds little, content close to another page, or too few links to it. Improve the page rather than asking for indexing again.
It removes the reason Google gave. Whether the page is shown, and where, depends on Google's own judgement of the page.
No. The decoder runs in your browser, and nothing you paste leaves it.
What this tool runs
- The page blocks search indexing (noindex)critical
page-noindex - Conflicting canonical URLs on the pageserious
canonical-conflict
How we measure
The decoder runs in your browser. Each message of Search Console's page indexing, sitemap, structured data, Merchant Center and Core Web Vitals reports that we know is a patterns-and-text entry written from Google's help pages for those reports: the English wording and the stems of the Arabic interface's wording (with the marks and the spelling of ة and أ folded). A pasted message gets the entry whose pattern says most about it. The Arabic interface's exact words change between releases, so when nothing matches, we say so and list the messages we know. The two rules the page lists, page-noindex and canonical-conflict, are the checks behind the most common of them.