Lorixen.
EN

Rich Results Test errors and warnings, fixed one by one

Short answer: In Google's Rich Results Test, an error means an item is invalid and cannot earn that rich result; a warning means the item is valid but missing something recommended. Fix errors first: they usually come from a missing required property, broken JSON-LD syntax or a page Google could not crawl. Warnings are optional improvements. And even a fully valid result is no guarantee: Google says correctly marked-up pages may still not show rich results.

You added structured data, ran the Rich Results Test, and got a wall of red and orange. The labels are terse, and the advice online is often tied to one plugin. This guide goes symptom by symptom: what you see in the test, the usual cause on a small-business site, and the fix.

Before you start: how to read the result

According to Google's help page, the test reports a status for the URL such as "N valid items detected", "N valid items detected: Some have warnings", "N items detected: Some are invalid", "No items detected", "URL cannot be crawled" or "Structured data with syntax errors detected". Expanding an item shows its issues, and clicking a description opens the code explorer at the right line. The explorer uses the rendered source code, meaning the page after JavaScript has run, not just the HTML your server sent.

The test supports JSON-LD, RDFa and Microdata. By default it tests as a smartphone; you can switch to desktop.

Symptom: "URL cannot be crawled" or "Crawl failed"

Cause. The tool fetches the page as Google, not as you. If robots.txt blocks the URL, or the page is behind a login, firewall or staging password, the test cannot see it. Google's help page also lists DNS problems, server connection errors, invalid SSL certificates and an unreachable robots.txt among the reasons a page cannot be reached.

Fix. Test the live public URL. For a staging site, paste the code into the test's Code option instead. If the live URL fails, check that robots.txt allows the page, that the certificate is valid and that a security plugin is not blocking Google's tools.

Symptom: "Structured data with syntax errors detected"

Cause. The JSON-LD is not valid JSON. Common culprits are a missing comma between properties, a trailing comma after the last one, straight quotes replaced by curly quotes when someone pasted from a word processor, or an unescaped quote inside a business name or description.

Fix. Open the code explorer at the flagged line. Look for the character just before the highlight. Also note a quirk Google documents: the test ignores comments inside JSON-LD, but comments are not supported by the JSON-LD standard and might cause errors in real use, so remove them before publishing.

Symptom: "Missing field" shown as an error

Cause. A required property for that rich result type is absent. Google's structured data policies are direct about this: items missing required properties are not eligible for rich results. Each type has its own list. For product snippets, for example, name is required, plus at least one of review, aggregateRating or offers.

Fix. Open Google's documentation page for the exact type you are using and compare its required list with your markup. If a plugin generates the markup, look for the setting that feeds that field. A product without any price, rating or review data cannot satisfy the product snippet requirement, however the plugin is configured.

Symptom: "Missing field" shown as a warning

Cause. A recommended, not required, property is absent. Google's policies say the more recommended properties you provide, the higher quality the result is to users.

Fix. Add recommended fields when you genuinely have the data. Do not invent it. A useful example from the product snippet docs: the test may warn if you provide offers without review or aggregateRating. If you have no real reviews, the warning is simply telling you a fact; leave it.

Symptom: "Invalid value" in a field

Cause. The property exists, but the value is the wrong type or format: a price with a currency symbol inside the number, a date in a local format instead of ISO 8601, a URL that is relative when an absolute one is expected, or a text value where a nested object is required (for example, offers as a plain price string instead of an Offer).

Fix. Check the type listed beside each property in Google's documentation (Text, URL, Number, a nested type) and match it exactly. Use dates like 2026-11-05 and plain numbers for prices, with the currency in its own property.

Symptom: The test finds items you didn't add, or duplicates

Cause. Two sources output the same markup: the theme and an SEO plugin, or an SEO plugin and a reviews plugin. You end up with two Product or two LocalBusiness items, sometimes with conflicting values.

Fix. Pick one source per type. Disable schema output in the other tool. Retest and confirm one clean item per type.

Symptom: Markup appears in your source but the test sees nothing

Cause. The markup is injected by JavaScript that fails, runs late or depends on a cookie banner choice. Or it is only on one version of the page (desktop vs mobile template).

Fix. Use the code explorer to view the rendered source. Test with the smartphone user agent, which is the default. If markup depends on JavaScript, make sure it does not wait for a user interaction.

Symptom: Everything is valid, but no rich result appears in Google

Cause. Validity is necessary, not sufficient. Google's policies state that it does not guarantee structured data will show in results even if it is correct according to the test; the algorithm decides what to display. Markup must also be a true representation of the visible page content; marking up content that is not shown, or labeling the wrong kind of content, breaks the guidelines. A manual action for structured data removes rich-result eligibility without affecting ranking.

Fix. Make sure the marked-up information is visible on the page, wait for the page to be recrawled, and check the Manual Actions report in Search Console if rich results vanished suddenly. Also confirm the feature still exists: Google retires some rich result types over time.

FAQ

Do I need to fix every warning?

No. Warnings are about recommended fields. Add them where you have real data; ignore the rest.

Will structured data errors hurt my rankings?

Errors stop the affected item from being eligible for that rich result. Google says a manual action for structured data affects rich-result eligibility, not how the page ranks.

Can I test a page before it goes live?

Yes. Use the Code option in the Rich Results Test and paste the markup or full HTML.

Is JSON-LD better than Microdata?

The test supports JSON-LD, RDFa and Microdata. JSON-LD is usually easiest to maintain because it sits in one block rather than being woven through the HTML.

If the test keeps flagging markup that a theme or plugin generated, share the URL with us and we will untangle which tool is writing what.

Sources

WhatsAppLet’s talk