Skip to main content
Completions

schema-audit-remediation agent

How to build per-location rich-result eligibility scoring + revenue-impact estimation

Rich results are won page by page, and nobody can say which location pages are one fix away from earning one. This guide builds eligibility scoring with revenue impact attached, so the fixes queue by what they are worth; the substrate below is what it scores.

Schema App + Yoast SEO Premium + RankMath Pro + Schema Pro + Schema Ninja + Google Rich Results Test + Schema.org Validator + Sitebulb + Screaming Frog + OnCrawl ship per-account flat schema-validation primitives. The Catalog + Score + Estimate + Audit skill bundle on the schema-audit-remediation agent sits above 50+ rich-result classes and writes a per-page canonical record with named regulatory anchors covering Google Rich Results Spam Policy + FTC Fake Review Rule 16 CFR Part 465 + HIPAA Safe Harbor + FINRA 2210 + state bar advertising + FDD Item 12 + EU AI Act Article 50 + WCAG 2.2 AA.

Published August 14, 2026 · 3,200 words

The 4-skill bundle on the schema-audit-remediation agent

One agent. Four coordinated skills. The Catalog + Score + Estimate + Audit bundle runs above the schema-audit surface (Schema App + Yoast + RankMath + Google Rich Results Test + Sitebulb + Screaming Frog + OnCrawl + DeepCrawl + Botify + Conductor) and writes one canonical per-page record.

Catalog

Per-portfolio per-banner per-location per-page snapshot of eligible rich-result classes across the 50+ Google-documented taxonomy. Quarterly schema.org draft absorption tracks new types + properties + deprecations + supersessions. Google policy update tracking watches the structured-data documentation for new constraints (FAQ deprecation 2023 + HowTo mobile-only 2023 + Speakable beta + future deprecations). Per-vertical schema-pack catalogs the LocalBusiness subtype required.

Score

15-dimension scoring per page per class: required-field presence + recommended-field presence + field-value compliance + JSON-LD syntax + type-hierarchy alignment + property domain-range + image URL accessibility + Restaurant servesCuisine + LocalBusiness geo coordinates + mobile-friendly + CLS impact + spam detection + per-Google-policy guardrails + per-vertical schema-pack + render-mode.

Estimate

Bayesian + causal + counterfactual revenue-impact estimation. Inputs: baseline organic traffic from Search Console Performance API + CTR uplift by feature + RPV + conversion rate + seasonal adjustment. Outputs: per-page Bayesian revenue impact (PyMC + Stan + NumPyro + bambi + brms + 95-percent credible interval) + synthetic control + DiD + regression discontinuity at Google update cutoff + Monte Carlo distribution + sensitivity analysis + loss-if-drop per page per month.

Audit

Per-page WORM canonical record covering every dimension above + audit trail of which dimension drove each routing decision + FBC feedback loop (realized vs predicted rich-result presence + realized vs predicted CTR uplift + realized vs predicted revenue uplift + multi-arm-bandit regret + recalibration). Retention stacks: 7-year FTC + 7-year IRS + 7-year HIPAA + 6-year SEC + 3-year FINRA + GDPR Article 30 + EU AI Act Article 12 + SOC 2 CC7/CC8.

The real ecosystem this sits above

Catalog + Score + Estimate + Audit does not replace the audit tools. It sits above them, coordinates them, and writes one canonical per-page record with named regulatory anchors.

Schema-validation surface

  • Schema App + Yoast SEO Premium + RankMath Pro
  • Schema Pro + Schema Ninja + JSON-LD Playground
  • Google Rich Results Test + Schema.org Validator
  • Bing Markup Validator + Yandex + Naver Search Advisor
  • Search Console URL Inspection + Bing Webmaster

Crawl + audit surface

  • Sitebulb + Screaming Frog + OnCrawl
  • DeepCrawl Lumar + Botify + JetOctopus
  • ContentKing Conductor + Sistrix
  • Ahrefs Site Audit + SEMrush Site Audit + Moz Pro
  • PageSpeed Insights + Lighthouse + WebPageTest

Revenue-attribution + causal stack

  • Search Console Performance API + BigQuery export
  • GA4 BigQuery + Adobe CJA + Tableau + Looker + Sigma
  • PyMC + Stan + NumPyro + bambi + brms + RStan
  • CausalML + DoubleML + EconML + scikit-learn + statsmodels
  • GeoLift + CausalImpact + Synth + propensity-score + RDD

Compliance overlay

Five anchors run before any per-page eligibility-score commits or any rich-result publish decision routes. The first anchor is operationally distinctive to rich-result schema: Google Rich Results Spam Policy retroactive enforcement intersects FTC Fake Review Rule per-violation civil penalty exposure on AggregateRating nodes.

Anchor 1: Google Rich Results policy + FTC Fake Review Rule (operationally distinctive)

Google Search Essentials + Google Structured Data Policy + Google Rich Results Spam Policy (Q1 2024 fake-review policy with retroactive 24-month enforcement against AggregateRating that cannot tie to verified individual Review nodes + no rating gaming + no auto-generated content claiming human + no misrepresentation + no marked-up content not visible to users + no hidden pricing or availability). FTC Fake Review Rule 16 CFR Part 465 (effective October 2024 + $53,088 per-violation civil penalty + AggregateRating-must-tie-to-real-individual- Review-node + Review-must-tie-to-real-reviewer + no-incentivized-without-disclosure + no-suppression-of-negative + no-AI-generated-fake-reviews). FTC Endorsement Guides 16 CFR Part 255 material-connection disclosure. FTC Act Section 5 + Pfizer 1972 substantiation when Offer/Product schema asserts price/availability/features that cannot be backed up. FTC MARS Made-in-USA / origin claims in schema. Bing Markup Guidelines + Yandex schema policy.

Anchor 2: Per-vertical schema constraint (HIPAA + FINRA + state bar + state licensing)

HIPAA 45 CFR 164.514 Safe Harbor de-identification when MedicalBusiness/Physician/Dentist/Pharmacy/Hospital schema (no-PHI-in-JSON-LD + no-patient-name + no-condition + no-treatment + no-appointment-ID). FINRA Rule 2210 communications with the public when FinancialService schema. SEC Regulation S-K when public-company FinancialService schema. State bar advertising rules when LegalService schema (50-state matrix + ABA Model Rule 7.1-7.5). State professional licensing schema constraints (Plumber + Electrician + Locksmith + RoofingContractor + GeneralContractor + MovingCompany + Notary + Physician + Dentist + Pharmacy + per-state-board). FDA DSHEA when MedicalBusiness promotes supplement. FTC Health Products Compliance Guide when MedicalBusiness/Drug schema asserts therapeutic claims. state-board (39 medical + 24 adult-use). Alcohol TABC + CalABC + per-state- SLA when Restaurant/FoodEstablishment schema includes alcohol.

Anchor 3: Franchise territorial + UDTPA + Lanham

FDD Item 12 territorial-protection per FTC Franchise Rule 16 CFR 436 when franchise LocalBusiness schema crosses ADI/protected-territory boundaries. 15-state franchise registration (CA + HI + IL + IN + MD + MI + MN + NY + ND + RI + SD + VA + WA + WI). 30-state Franchise Relationship Rule. State UDTPA enforcement. Lanham Act false-advertising. Robinson-Patman per-location-pricing-discrimination when Offer schema reveals territorial pricing variance. FDD Item 17 + Item 19 financial-performance representation substantiation when Offer schema price/availability claims.

Anchor 4: Accessibility + AI governance

WCAG 2.2 AA + ARIA + EAA EN 301 549 + Section 508 + ADA Title III when schema-driven rich-result rendering must remain accessible. EU AI Act Article 50 transparency + EU AI Act Article 13 + 14 + 15 + Annex III high-risk when AI-ML scoring drives publish/block routing. Digital Services Act Article 30 + Digital Markets Act. NIST AI Risk Management Framework. ISO 42001 AI Management System. ISO 27001. SOC 2 Type II.

Anchor 5: Privacy + crawl-budget honoring

GDPR Article 6 + 7 + 17 + 22 + LGPD + DPDP + PIPEDA + Quebec Law 25 + CCPA + CPRA + COPPA + 18-state comprehensive privacy + per-vendor LLM zero-retention verified per call. Sitebulb + Screaming Frog + OnCrawl crawl-budget honoring + per-source Data Processing Addendum + per-API rate-limit. Policy-as-code via OPA Rego + AWS Cedar + Casbin + Cerbos + Oso + Styra DAS + Permit.io. Storage: AWS S3 Object Lock + Azure Blob immutable + Google Cloud Storage Bucket Lock + Wasabi WORM.

6-workstream reporting cycle

Every two weeks during a Tier 3 Fractional Digital Marketing Lead engagement, six workstreams report against the pre-engagement baseline. No forecast accuracy claims. Process commitments only.

  1. 1. Rich-result-class catalog coverage. Eligible vs gated vs blocked per page taxonomy + delta from prior cycle.
  2. 2. Eligibility-scoring distribution. Per-page eligibility-confidence-tier distribution + dimensions driving block decisions + per-vertical patterns.
  3. 3. Revenue-impact-estimation distribution. Per-page Bayesian 95-percent credible interval distribution + per-vertical loss-if-drop estimation + realized-vs-predicted reconciliation.
  4. 4. Routing-tier flow distribution. Per-tier volume + latency + sampled routed decisions.
  5. 5. Regulatory-defense audit coverage. FTC Fake Review Rule + Google Spam Policy + HIPAA Safe Harbor + FINRA 2210 + state bar + FDD Item 12 + EU AI Act Article 50 + WCAG 2.2 AA.
  6. 6. FBC feedback-loop pattern-learning. Multi-arm-bandit regret + recalibration applied + per-vertical pattern shifts + Google-update impact retrospective.

FAQ

What is rich-result eligibility scoring + revenue-impact estimation — and what is the fake-review-retroactive-enforcement problem when 50+ rich-result classes are in play?
A multi-location retail operator with 80 stores depends on 50+ Google-documented rich-result classes — LocalBusiness + 20+ LocalBusiness subtypes (Restaurant + MedicalBusiness + LegalService + FinancialService + AutoDealer + Plumber + Electrician + Locksmith + RoofingContractor + GeneralContractor + MovingCompany + ChildCare + Notary + Physician + Dentist + Pharmacy + Hospital + RealEstateAgent + ProfessionalService + HealthAndBeautyBusiness) + Product + Offer + AggregateRating + Review + Recipe + Event + FAQ (deprecated except medical/government 2023) + HowTo (mobile-only as of 2023) + Article + NewsArticle + BlogPosting + VideoObject + JobPosting + Course + Dataset + Podcast + SoftwareApplication + Book + Movie + TVSeries + Restaurant-Menu + Sitelinks-search-box + Carousel + QAPage + Speakable + Math-solver + Practice-problems + Vehicle + Estimated-salary + Education-QA + ImageObject-with-License + Subscription-paywall + Discussion-forum + Profile-page + Vacation-rental + Loyalty-program + Breadcrumb. The four-skill bundle on the schema-audit-remediation agent — Catalog, Score, Estimate, Audit — sits above the 50+-class surface and writes a per-page canonical record. The operationally distinctive anchor: Google Rich Results Spam Policy (Q1 2024 fake-review policy with retroactive 24-month enforcement against AggregateRating nodes that cannot tie to verified individual Review nodes) and FTC Fake Review Rule 16 CFR Part 465 (effective October 2024 + $53,088 per-violation civil penalty for fake reviews, undisclosed material connections, review suppression, AI-generated reviews). Per-location AggregateRating with 4.8 stars and 247 reviews is a per-location compliance liability if those individual Review nodes cannot be produced on demand.
Why do Schema App + Yoast SEO Premium + RankMath Pro + Google Rich Results Test + Sitebulb + Screaming Frog + OnCrawl break at multi-location 50+-class scale?
Each schema-audit vendor ships a per-account flat schema-validation primitive — an SEO plugs a URL into Google Rich Results Test, gets a green/yellow/red report on whether the page is eligible for one or two features, and re-pastes JSON-LD into a Yoast or RankMath panel. None catalogs the 50+ Google-documented rich-result classes against the per-location page taxonomy. None scores eligibility across 15 dimensions (required-field presence + recommended-field presence + field-value compliance + JSON-LD syntax + type-hierarchy alignment + property domain-range + image URL accessibility + Restaurant-servesCuisine + LocalBusiness geo-coordinates + mobile-friendly + CLS impact + spam detection + per-Google-policy guardrails + per-vertical schema-pack + render-mode). None estimates revenue impact through a coordinated Bayesian + causal + counterfactual stack (PyMC + Stan + NumPyro + bambi + brms + CausalML + DoubleML + EconML + synthetic control + difference-in-differences + regression discontinuity at Google update + Monte Carlo + sensitivity analysis). None enforces the per-vertical compliance overlay covering Google Rich Results Spam Policy + FTC Fake Review Rule + HIPAA Safe Harbor + FINRA 2210 + state bar advertising + FDD Item 12 + EU AI Act Article 50. None writes a per-page audit trail with regulatory-defense retention. The four-skill bundle Catalog + Score + Estimate + Audit sits above the audit-tool surface — it does not replace it.
How does Catalog + Score work across 50+ rich-result classes?
Catalog maintains a per-portfolio per-banner per-location per-page snapshot of which rich-result classes the page is currently eligible for. Quarterly schema.org draft absorption tracks new types + new properties + deprecations + supersessions. Google policy update tracking watches the structured-data documentation for new constraints (FAQ deprecation 2023 + HowTo mobile-only 2023 + Speakable beta + future deprecations). Per-vertical schema-pack catalogs the LocalBusiness subtype required (Plumber + Electrician + Locksmith + RoofingContractor + GeneralContractor + MovingCompany + Notary need state-professional-licensing schema beyond base LocalBusiness; Physician + Dentist + Pharmacy + Hospital need MedicalBusiness with HIPAA-Safe-Harbor constraint; LegalService needs state bar advertising compliance; FinancialService needs FINRA 2210 + SEC Regulation S-K when public-company). Score evaluates 15 dimensions per page per class: required-field presence + recommended-field presence + field-value compliance (per-Google-documented constraint + per-schema.org property domain-range + per-schema.org type hierarchy) + JSON-LD syntax + schema.org type-matching no-fake-types + image URL accessibility + image dimensions + image aspect ratio + itemReviewed presence for Review + AggregateRating ratingValue/reviewCount/bestRating/worstRating + Offer price/priceCurrency/availability/url + LocalBusiness address-fields/telephone/openingHours/geo coordinates + Restaurant servesCuisine/priceRange/acceptsReservations/menu + render-mode (server-side prerender vs static generation vs client-side hydration vs rich-result detection impact) + mobile-friendly test + Cumulative Layout Shift impact + spam detection (fake review + rating gaming + keyword stuffing in JSON-LD + hidden pricing) + per-Google-policy guardrail.
What does Estimate + Audit do?
Estimate runs a per-portfolio per-banner per-location per-page revenue-impact estimation through a coordinated Bayesian + causal + counterfactual stack. Inputs: baseline organic traffic from Search Console Performance API (last 90 days + last 365 days + 2-year trailing) + CTR uplift by feature (Google published benchmark + internal benchmark from historical deploy + vertical benchmark from Searchmetrics/Sistrix/SEMrush + causal uplift CATE via T/S/X/DR learners on CausalML + DoubleML + EconML) + revenue-per-visit + conversion rate + seasonal adjustment. Outputs: per-page Bayesian revenue impact (PyMC + Stan + NumPyro + bambi + brms + 95-percent credible interval + posterior predictive check) + synthetic control + difference-in-differences + regression discontinuity at Google update cutoff + Monte Carlo distribution + sensitivity analysis + loss-if-drop per page per month + loss-if-drop per vertical per quarter. Routing: 5 tiers (eligible-to-publish-and-monitor + drop-detected-to-CMO-Slack plus revenue-impact plus remediation-queue + borderline-to-governance-decision-router-five-destination + policy-violation-to-block-and-flag-and-remediation + Google-policy-violation-to-block-and-flag). Audit writes a per-page WORM canonical record covering every dimension above + audit trail of which dimension drove each routing decision + FBC feedback loop (realized vs predicted rich-result presence + realized vs predicted CTR uplift + realized vs predicted revenue uplift + pattern learning + multi-arm-bandit regret + recalibration). Storage: AWS S3 Object Lock + Azure Blob immutable + Google Cloud Storage Bucket Lock + Wasabi WORM. Retention stacks (longest applicable): 7-year FTC substantiation + 7-year IRS + 7-year HIPAA + 7-year state bar + 6-year SEC + 3-year FINRA + GDPR Article 30 + EU AI Act Article 12 + SOC 2 CC7/CC8.
What does this skill connect to on the schema-audit-remediation agent and across the swarm?
On the schema-audit-remediation agent: continuous schema audit (sibling skill — recrawl on N-hour, N-day, on-deploy, on-schema.org-quarterly-absorption, on-Google-policy-update) + per-vertical schema validation (sibling skill — per-MedicalBusiness + per-Restaurant + per-LegalService + per-FinancialService per-AutoDealer + per-Plumber + per-Electrician + per-Locksmith + per-RoofingContractor + per-GeneralContractor + per-MovingCompany + per-ChildCare schema pack) + auto-compose schema (sibling skill — JSON-LD generation from master record) + per-vertical catalog schema validation (sibling skill) + JSON-LD generation (sibling skill + sibling build-pillar at how-to-build-17-schema-class-jsonld-generation-from-master-record) + schema coverage scoring + schema conflict detection + quarterly schema.org absorption. Across the swarm: governance-decision-router five-destination routing for borderline cases + local-pack-rank-tracking per-market-competitor rank tracking (sibling agent — pairs as eligibility-to-ranking signal cluster) + multi-location-seo-architecture + franchise-local-seo-orchestration + url-hierarchy-authoring + canonical-tag-management + orphan-page-detection + title-rewrite-tracking + ai-overview-tracking + seo-alerts. Build-pillar siblings: tiered pre-filter deterministic gates for AI content compliance + marketing AI autonomy profile configuration + master record + per-jurisdiction compliance multi-state franchise + per-location per-cohort two-sigma anomaly detection + per-market competitor rank tracking. Commercial-pillar parent: rich-result-eligibility-scoring.
What does the 6-workstream pre-engagement-baseline reporting cycle look like for this skill?
Every two weeks during the Tier 3 Fractional Digital Marketing Lead engagement, six workstreams report against the pre-engagement baseline. Workstream 1: rich-result-class catalog coverage — which classes the page taxonomy is eligible for + which are gated + which are blocked + delta from prior cycle. Workstream 2: eligibility-scoring distribution — per-page eligibility-confidence-tier distribution + dimensions driving block decisions + per-vertical eligibility patterns. Workstream 3: revenue-impact-estimation distribution — per-page Bayesian 95-percent credible interval distribution + per-vertical loss-if-drop estimation + per-page realized-vs-predicted reconciliation. Workstream 4: routing-tier flow distribution — per-tier volume + per-tier latency + per-tier sample of routed decisions. Workstream 5: regulatory-defense audit coverage — FTC Fake Review Rule + Google Rich Results Spam Policy + HIPAA Safe Harbor + FINRA 2210 + state bar advertising + FDD Item 12 + EU AI Act Article 50 + WCAG 2.2 AA. Workstream 6: FBC feedback-loop pattern-learning — multi-arm-bandit regret + recalibration applied + per-vertical pattern shifts + Google-update impact retrospective.

Engage Completions

Two ways to engage. The Tier 1 Marketing Operations Audit maps the schema-audit substrate + rich-result-class taxonomy + per-vertical compliance surface against the Catalog + Score + Estimate + Audit bundle. The Tier 3 Fractional Digital Marketing Lead embeds 1-2 days per week for 6+ months and runs the bundle end-to-end against the schema-audit-remediation agent across the swarm.

Free — for the person who will build it

The Agent Build Spec Pack

Get the working spec behind the architecture on this page — skill decomposition, data contracts, and the acceptance tests that tell you the agent is actually done.

  • The four-skill decomposition applied to a real agent, with the input and output contract for each skill.
  • The data-fabric contract: what the agent reads, what it writes back, and how it stays consistent with every other agent reading the same record.
  • The acceptance tests — the specific assertions that separate a demo from an agent you can leave running.

Opens on this page immediately. No attachment, no waiting on an email.