wowprompt

Rich results errors fixed field by field from a validator report

Reads the errors and warnings from a rich results or schema validator, explains each in plain words, and returns the corrected structured data block with only the broken fields changed. Use it when product, recipe, event, FAQ or review stars stop showing, or Search Console reports invalid items after a theme or plugin update.

A table of validator errors with the cause and fix for each, the corrected JSON-LD block, and a short list of warnings that are safe to leave
The output this prompt produced, unedited.

The prompt

Fill in these first

  • Page URL and what it is: [e.g. a product page for a cotton kurta]
  • Validator output: [paste every error and warning line]
  • Current structured data: [paste the JSON-LD or microdata block]
  • Facts visible on the page: [e.g. price Rs 1,299, in stock, 4.4 from 86 reviews, brand name]
  • How the markup is added: [e.g. theme code, an SEO plugin, a tag manager]

Task

Fix the markup so it validates and still matches what a visitor sees on the page.

Output format

  1. | Error or warning | Field | What it means | Fix | Must fix or safe to leave |
  2. The corrected block, complete, with each changed line marked by a comment above it.
  3. Where to make the change for the method given, in two or three steps.
  4. How to confirm the fix: which test to rerun and what the report should show after recrawl.

Rules

  • Every value in the markup must appear on the page; never add ratings, prices or dates that are not shown.
  • Keep all fields that already validate exactly as they are.
  • Use the types and property names the current schema.org vocabulary defines.
  • If a fix needs data the business does not have, say so instead of inventing it.
rich results errorsschema markup fixstructured data warningssearch console enhancementsjson ld errorsproduct schema fix

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity