Use the Rich Results Test URL parameter interface: construct a GET request to 'https://search.google.com/test/rich-results?url={encoded-url}' to manually verify a staging URL
For automated CI use, call the Google Search Console Rich Results API endpoint (under the Search Console API) or use the unofficial URL-based approach with a headless browser to parse the result page
Alternatively, run the 'schema-dts' or 'schema-org-validator' npm packages locally in CI to lint JSON-LD before the page is deployed
Add a CI step that crawls a sample of newly generated pages and POSTs their HTML to Google's Structured Data Testing endpoint to check for critical errors
Fail the build if any 'errors' are returned; treat 'warnings' as non-blocking but log them for review
Maintain a list of URL templates that correspond to each structured data type deployed on the site and test one representative URL per type on each deploy
Known gotchas
There is no stable, documented public REST API for the Rich Results Test — the tool is a web interface; CI integrations relying on scraping its output are fragile and may break without notice
As of mid-2026, FAQ rich results are deprecated (Google stopped showing them in Search on 7 May 2026); continuing to include FAQPage markup will not cause errors but will not generate rich results
Testing with a staging URL only works if the URL is publicly accessible; localhost or VPN-only URLs will return a 'URL not reachable' error
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp