What does this error mean?

Paste the exact error Google gave you: Merchant Center disapproval, Search Console status, structured-data warning. You get what it means, why it happens, and the free check that finds it on your own store.

Every error, in plain words

43 guides, each mapped to the check that detects it. Browse the full list.

What the Google error decoder matches

Paste an exact Merchant Center disapproval, Search Console status or structured-data warning. The page runs matching in your browser against its local list of error guides and aliases. Recognized phrases can lead to a specific fix guide and the related check. For certain topics without a guide, such as GTIN or other identifiers, it can recommend a focused tool instead.

The decoder does not connect to Google, inspect your account or diagnose your store from the pasted words. It classifies the text you provide. Exact wording improves matching because vendor messages often differ from a guide’s title. Your Merchant Center or Search Console account remains the source for the actual status of your items and URLs.

Known Merchant Center disapproval strings and common alternate phrasings.
Search Console page indexing statuses and structured-data warning aliases.
Guide matches with a link to the fix explanation and the detecting tool.
A tool fallback or a clear no-match result when it cannot identify the text confidently.

How to use a decoded error

Copy the complete message as it appears in the product or URL report. The decoder ranks guide matches using explicit aliases and word overlap. When a match is strong enough, it labels the result Recognized and links to the corresponding guide and check. The check does not run automatically; open it and provide the relevant site or URL yourself.

If the text does not match a guide, a few broad fallbacks can point to an appropriate tool. If neither a guide nor fallback fits, the page says it does not recognize the error and links to the guide index or full audit. Do not apply a suggested fix until the exact item, page or account context confirms it is relevant.

Copy the complete error text, including quoted field names or status wording.
Read the matched guide to understand cause and scope.
Run the linked check against the public site to see whether the condition is present.
Use Search Console or Merchant Center diagnostics to confirm Google’s actual status.

Why exact error wording matters

Several messages can share words while describing different causes. For example, a product URL that is missing differs from a page that is blocked, and a Search Console exclusion status differs from an item disapproval. The decoder includes aliases for known platform wording, but it cannot infer every account-specific detail from a phrase alone. Check the match against the URL or item named in the original report.

A guide explains a known failure mode and where to investigate. It is not evidence that the condition exists on your site. If the linked check finds no issue, compare what it inspected with the exact Google record: the crawler may have seen a temporary response or a different variant.

Keep status names, punctuation and field names in the pasted message.
Do not paste sensitive account credentials or private customer information.
If the result seems unrelated, try the full original error or browse the fix guide index.

When to use the decoder

Use it when you have a status or disapproval and want a plain-language explanation plus the next relevant tool. It is especially useful when vendor wording does not resemble the title of the guide you need. If you already know the technical symptom—such as a dead page, noindex tag or canonical mismatch—go straight to that checker for evidence.

Because matching happens in the browser, the pasted text is not sent to the decoder service. The resulting link opens a separate guide or tool; those pages may need the public URL to run their checks. Account-only problems must still be investigated in the account that reported them.

Site audit: broad technical checks when the cause is unclear.
Indexability check: page-level crawl and index signals.
Feed file check: identifiers and other feed attributes.
Search Console checker: connected property information where available.

Questions

Which errors does it understand?

The Merchant Center disapproval strings, Search Console exclusion statuses, and structured-data warnings: the ones merchants actually see and paste into a search box. Paste the text as Merchant Center shows it.

Why not just search for the error?

A search gives you blog posts from 2019 for a different platform. This matches the string against the exact rule we check for, then runs that check on your store.

What if it does not recognise my error?

It says so rather than guessing, and points at the full list of guides. A wrong answer would be worse than no answer.

Does it store what I paste?

No. The matching runs in your browser and nothing is sent anywhere.

How do I find out what a Google Search Console error means?

Copy the status text exactly, including its wording and punctuation, and match it to a reliable explanation. Shipwork’s decoder searches its local guide index and aliases in your browser, then links to a fix guide or related check when it recognizes a phrase. It does not query your Search Console account, so use the Pages report or URL Inspection to confirm the affected URL’s current status.

Can this tool decode any Merchant Center error?

It recognizes a maintained set of Merchant Center, Search Console and structured-data phrases, including known alternate wording. It cannot decode every account-specific message. If it does not find a sufficiently strong match, it says so or offers a relevant broad tool fallback rather than claiming a precise diagnosis. Check the exact item details in Merchant Center before changing data.

Does the error decoder send my message anywhere?

No. The guide index is included in the page and the matching runs in your browser; the pasted error text is not submitted to a decoder API. The guide or checker link opens only after you choose it. Avoid pasting credentials, customer data or other sensitive information into any public tool, even when matching is local.

Why did the error decoder match the wrong guide?

The decoder uses explicit phrases and overlapping words, so short or incomplete messages can resemble more than one known error. Paste the full text from the source report, then compare the recognized description with the product, URL or field Google named. If the match still does not fit, browse the guide list or use the relevant checker to gather evidence before applying a fix.

Does the decoder automatically fix my Merchant Center issue?

No. It explains a recognized message and links to a guide or a check. You make changes in the store, feed, server or account that controls the problem. Afterward, rerun the relevant public check and follow Merchant Center’s own process for requesting a review or waiting for a recrawl. A clean check does not itself change account status.