Find Duplicate Schema Errors Killing Rich Results
Scan a page for the #1 cause of Rich Results validation failures: the same data expressed in BOTH visible microdata (itemscope/itemtype/itemprop) AND JSON-LD. Returns a clear list of which microdata attributes to remove from the visible HTML so JSON-LD can stand alone, plus a check for orphaned aggregateRating, broken @id references, and 5 other common Rich Results killers.
schema · validation · rich-results · duplicate · aeo · debug
When duplicate FAQ data appears in both microdata and JSON-LD on the same page, Google's Rich Results Test rejects the entire FAQPage. We've hit this twice on AlignAI's own properties. The pattern: visible <details> blocks marked up with itemtype="https://schema.org/FAQPage" while the same Q&A pairs also live in JSON-LD. Pick JSON-LD, strip the microdata.
How to use this prompt
- Pick your AI model. Choose the tab for Claude, ChatGPT, Gemini or Copilot. Each variant is tuned for that model.
- Copy the full prompt. Click Copy Full Prompt to copy the text to your clipboard.
- Paste into your AI tool. Open your chosen model and paste the prompt into a new chat.
- Replace the [placeholders]. Swap any bracketed fields for your company name, audience, product or tone.
- Run and refine. Review the output. If anything is off, ask the AI to tighten tone, length or format.
Prompt Variants by Model
Act as a Rich Results debugger. I'll paste a page's HTML. Find the #1 cause of Rich Results validation failures — the same data in both visible microdata (itemscope/itemtype/itemprop) and JSON-LD — plus 7 other common killers.
Page context: URL [https://YOUR-DOMAIN.COM/...] · Rich Results Test run? [yes — paste errors / no]
Page HTML (full source):
[PASTE]
Check:
- Every JSON-LD block and the @type it declares
- Every itemscope / itemtype / itemprop in the visible HTML, and which JSON-LD block (if any) expresses the same entity — where both exist, JSON-LD wins and the microdata gets stripped
- Killer A — orphaned AggregateRating (no backing Reviews or @id refs)
- Killer B — broken @id references
- Killer C — wrong @type for the content
- Killer D — required fields empty or missing for the @type
- Killer E — placeholder values ("Lorem ipsum", "Your Company Name", "[BRAND]", "example.com", "TODO")
- Killer F — invalid JSON (trailing commas, unescaped quotes, unbalanced braces)
- Killer G — conflicting nested schemas (e.g. Organization name ≠ WebSite publisher name)
Output:
1. JSON-LD inventory table: Block # · @type · Valid JSON? · Required fields complete? · Placeholders? · @id used
2. Microdata vs JSON-LD duplication map: Microdata location · @type · Duplicates which block? · REMOVE / KEEP — with the exact attributes to strip for every REMOVE
3. Other killers found — one section per killer A-G that appears: location, plain-English problem, exact fix
4. Verdict — will it pass Rich Results after the fixes? Yes / Maybe / Unlikely, and why. Re-test URL, Schema.org validator URL, fix order (invalid JSON → missing required → duplication → other)
Success means every finding points to a line or attribute in the pasted HTML. If nothing is wrong, say so — don't invent problems.
Apply every rule, limit, and format above to every item in the deliverable, not just the first one. Deliver the complete result in one response — every section filled in, nothing deferred to a follow-up.
If a required input is missing, ask for it once before starting; otherwise proceed and label any assumption you made.Notes: R40 refresh; tuned to vendor prompting guidance
Frequently Asked Questions
What does the Find Duplicate Schema Errors Killing Rich Results prompt do?
Scan a page for the #1 cause of Rich Results validation failures: the same data expressed in BOTH visible microdata (itemscope/itemtype/itemprop) AND JSON-LD. Returns a clear list of which microdata attributes to remove from the visible HTML so JSON-LD can stand alone, plus a check for orphaned aggregateRating, broken @id references, and 5 other common Rich Results killers.
Which AI models is this prompt written for?
Claude, ChatGPT, Gemini and Copilot. Each one gets its own version up top, written the way that vendor says to prompt its own model. Pick the tab that matches yours.
Do I need a paid AI account to use this prompt?
No. This prompt is written to run on the free tier of Claude, ChatGPT, Gemini and Copilot. Paid tiers simply give you longer context windows and faster responses.
Can I customize this prompt for my business?
Yes. Any text inside square brackets is a placeholder you replace with your own business details, such as company name, audience, product or tone. You can also ask the AI to adjust format, length or style after the first output.
When was this prompt last checked?
The date is on each version up top. We check every prompt in full every month, and when a major new model lands we rewrite the prompt for it. One glance tells you how current it is before you paste.
Works with
More in AI Search & SEO
SEO Content Brief Generator
Generate a structured SEO content brief for a blog post targeting a specific keyword, including…
AI Search Readiness Audit & Fix Plan
Build an agentic workflow that ingests your homepage HTML, scores AI-search readiness on a…
Generate FAQs Your Customers Actually Search For
Generate 10 FAQ Q&A pairs phrased the way real customers type into ChatGPT, Google and voice…