For sites that rely on rich results
Read the JSON-LD a page publishes and check it on every deploy
Pull every JSON-LD block from the rendered page and check the fields your rich results depend on, on every deploy.
The problem
Prices, review stars, FAQ answers and breadcrumbs in search results all come from JSON-LD that a template emits. A refactor renames a field, a tag manager injects a second, conflicting Product block, and the rich results quietly disappear while the page itself looks unchanged.
How domscout handles it
An extract field with type html and all: true returns the contents of every script[type='application/ld+json'] on the rendered page, so blocks injected by JavaScript are included. Parse each one and assert what you depend on: that a Product has a price and a currency, that there is only one, that the breadcrumb matches the URL. domscout reads what the page publishes; whether a search engine shows a rich result for it remains the search engine's decision.
Where it shows up
- A CI check that product templates keep their price and availability.
- A sweep for pages that publish two conflicting blocks.
- A comparison of the JSON-LD before and after a template change.
The request
POST /scrape. extract starts at Pro and costs 2 credits a page. Each value is cut at 20,000 characters and marked truncated when it was, so a very large block is never silently incomplete.
Go further
More in SEO and site health: SEO regression checks · Link preview checks · Find every page on a site · Website migration checks · JavaScript SEO checks · Page weight and load metrics · Backlink checks · hreflang checks · Website audits for prospects · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.