FAQ Schema Verification Loop
A structured-data loop that keeps JSON-LD aligned with visible page content.
Use loop copies the kickoff prompt. Copy Markdown and Download loop include the complete Markdown page with context, source attribution, anchors, and guardrails. Cursor / Claude Code buttons prepare the shorter kickoff prompt only.
Supported agents
Goal
Keep FAQ structured data accurate and visible.
Feedback gate
curl -sL $URL | rg "application/ld\+json|FAQPage"Stop condition
FAQ JSON-LD matches visible questions and answers on the page.
Give the agent these inputs before it starts the loop. This keeps discovery bounded and prevents vague retries.
The loop assumes these commands or integrations are available. Missing tools should be reported as blockers, not ignored.
Two separate pieces: the kickoff prompt starts the loop, while the downloaded Markdown carries the complete reference page.
1. Copy or download
Use the kickoff for a fast agent run. Download the full Markdown when you need source, context, and attribution in one file.
2. Paste into the agent
Start a fresh agent session in the target repo and provide the requested project context if the loop asks for it.
3. Let it self-pace
The agent should act, check evidence, retry only when the gate fails, and stop at the stated exit condition.
The diagram shows the order. This checklist keeps only the action, command, and failure handling needed during a real pass.
1. Inspect visible FAQ
Confirm questions and answers are rendered for users.
2. Inspect JSON-LD
Find FAQ structured data in server HTML.
curl -sL $URL | rg "FAQPage"3. Compare content
Ensure JSON-LD uses the same questions and answers as visible content.
4. Fix mismatch
Patch data source or schema generator and re-check.
This is the text copied by Use loop. It is intentionally shorter than the Markdown export.
Verify visible FAQ content and JSON-LD structured data match exactly. Fix mismatches and avoid marking up hidden content.
Goal: Keep FAQ structured data accurate and visible.
Check command: curl -sL $URL | rg "application/ld\+json|FAQPage"
Exit condition: FAQ JSON-LD matches visible questions and answers on the page.
Max iterations: 3
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not mark up hidden, misleading, or unrelated FAQ content.Quality
87/100
Safety
94/100
Expected output
Visible FAQ and matching JSON-LD validation summary.
Related loops
Browse allSEO Metadata Audit Loop
Audit title, description, canonical, Open Graph, headings, and indexability for SEO-critical pages.
Kickoff preview
Audit SEO metadata from server-rendered HTML for the target pages. Verify title, description, canonical, H1, Open Graph, and indexability, then fix and re-check. Goal: Ensure SEO-critical pages have unique, server-rendered metadata and indexable content. Check command: curl -sL $URL | head -80 Exit condition: Each target page has unique title, description, canonical, visible H1, and no accidental noindex. Max iterations: 5 Guardrails: - Do not weaken, skip, delete, or rewrite the validation command to force success. - Do not claim completion until the stated exit condition is actually satisfied. - If blocked, report the blocker, evidence, and next safest action instead of gaming the metric. - Do not rely only on client-rendered metadata for SEO-critical pages. Verify server HTML.
Programmatic SEO Page QA Loop
Review generated SEO pages for thin content, duplicate metadata, broken internal links, and missing structured data.
Kickoff preview
Audit a sample of generated SEO pages for uniqueness, helpfulness, metadata, internal links, and schema. Fix template/data issues before publishing at scale. Goal: Ensure template-generated pages provide distinct value and are safe to index. Check command: curl -sL $URL Exit condition: Sampled generated pages have unique metadata, useful body content, and valid internal links. Max iterations: 5 Guardrails: - Do not weaken, skip, delete, or rewrite the validation command to force success. - Do not claim completion until the stated exit condition is actually satisfied. - If blocked, report the blocker, evidence, and next safest action instead of gaming the metric. - Do not create large numbers of thin pages solely to manipulate search ranking.
AdSense Readiness Audit
Check whether a free content/tool site has enough original value, policy pages, navigation, and ad-safe layout for AdSense review.
Kickoff preview
Audit the site for AdSense readiness: content depth, policy pages, navigation, mobile UX, and ad-safe layout. Return blockers and fixes. Goal: Make the site credible, useful, navigable, and ad-safe before AdSense review. Check command: curl -I $SITE_URL Exit condition: Core content, policy pages, navigation, and ad placement are ready for review. Max iterations: 4 Guardrails: - Do not weaken, skip, delete, or rewrite the validation command to force success. - Do not claim completion until the stated exit condition is actually satisfied. - If blocked, report the blocker, evidence, and next safest action instead of gaming the metric. - Do not place ads next to copy/download/source buttons where users may click accidentally.
Ship PR Until Green
Implement a scoped change, open or update a pull request, inspect CI, and continue until all required PR checks pass.
Kickoff preview
Take this branch to a green pull request. Implement the requested change, run local verification, open or update the PR, run `gh pr checks`, inspect failures, fix root causes, and repeat until every required check passes or you hit the iteration cap. Goal: Open or update a pull request and stop only when all required PR checks are green. Check command: gh pr checks Exit condition: All required pull request checks are successful and the PR is ready for review or merge. Max iterations: 10 Guardrails: - Do not weaken, skip, delete, or rewrite the validation command to force success. - Do not claim completion until the stated exit condition is actually satisfied. - If blocked, report the blocker, evidence, and next safest action instead of gaming the metric. - Do not disable required checks, edit loops to skip jobs, or remove tests to make CI green. - Do not merge the PR unless the user explicitly asked for merge authority.