For teams that ship websites
Catch a noindex or a wrong canonical before search engines do
Read the head tags a search engine reads and fail the build when a deploy ships a noindex or a wrong canonical.
The problem
The worst SEO bugs are silent. A staging flag ships a noindex to production, a canonical keeps pointing at the preview domain, a template change drops the meta description from every product page. The page still renders, still returns 200, still looks right in a browser, and almost nothing in a normal test suite looks inside the head.
How domscout handles it
One request reads the tags you name by CSS selector from the rendered page and reports each as found or missing, so an absent tag cannot pass for an empty one. To see the head as your server sends it, before any JavaScript runs, a renderJs: false request returns the served title, description, Open Graph tags and canonical URL; named fields like robots need the rendered page. Run the check in CI against a preview URL and fail the build on a problem.
Where it shows up
- A post-deploy check on the pages that carry your organic traffic.
- A pre-merge check against preview deployments.
- A scheduled comparison of the served and the rendered title, description and canonical.
The request
POST /scrape. extract starts at Pro and adds 1 credit to the capture, so each page checked costs 2. Monitors can collect these fields on a schedule, but their alerts compare the title, status code, text, links and DOM, not extracted fields.
Go further
Other use cases: Web access for AI agents · Website change monitoring · Web archiving and evidence · Crawling a whole site · Thumbnails and link previews · PDFs from your own HTML · Structured data from web pages · Link preview checks · Responsive layout checks
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.