Adjust fact-checking SEO strategy after Google's 2025 removal of ClaimReview from Search Console reporting and the Rich Results Test
domain: developers.google.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Understand that Google removed ClaimReview from Search Console's rich-result reporting, the Rich Results Test, and Search-appearance filters starting September 2025
Stop treating ClaimReview markup as a way to earn a visible fact-check rich-result snippet in mainstream Google Search, since that surface has been discontinued
Keep existing ClaimReview markup in place for machine-readability, since some reporting indicates Google's AI Mode still treats ClaimReview-marked pages as higher-trust sources for verification-style queries
Redirect reporting/monitoring workflows away from the retired Search Console fields for this type, since the Search Console API also stopped returning ClaimReview-specific data
For organizations whose core business is fact-checking, evaluate Google's separate Fact Check Tools API / Fact Check Explorer, which is a distinct product unaffected by this removal
Known gotchas
ClaimReview no longer produces any visible rich-result treatment in standard Google Search — don't scope new SEO work around achieving that snippet
The removal was staged (Search Console UI/reporting first, then the Search Console API), so API-fed dashboards may have kept returning data after the front-end feature disappeared
The Fact Check Tools API/Explorer is a separate Google product for fact-checking organizations and shouldn't be confused with the retired Search rich-result feature
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?