For teams moving a site
Check every old URL against the new site before search engines do
Capture each old URL and its new counterpart together, and compare where it lands, what it says and what it declares.
The problem
A replatform goes live on a Monday. By Thursday the old blog's traffic has vanished because its redirects point at the home page, product pages have lost their canonical tags, and a section nobody remembered never moved at all. The spreadsheet of URL mappings existed; nobody had a quick way to check it.
How domscout handles it
Start with POST /map on the old site for the list of URLs. Then send each old URL and its new counterpart in one batch. For each, markdownMeta.finalUrl shows where the URL ended up after redirects, metadata.httpStatus what it answered, and the title, word count and Markdown let you compare what the two pages say; an extract field reads the canonical tag on both. Run it against staging before launch and against production after, and the problems arrive as a list of rows rather than a slow decline in search traffic.
Where it shows up
- A pre-launch check of every mapping in the redirect plan.
- A post-launch sweep for redirects that land on the home page.
- A content comparison for pages rewritten in the move.
The request
POST /batch. Batch starts at Business and /map at Pro. Each item here costs 2 credits, and /map 2 a request. A batch takes up to 100 requests, so a large site goes through in several.
Go further
More in SEO and site health: SEO regression checks · Link preview checks · Find every page on a site · JavaScript SEO checks · Page weight and load metrics · Backlink checks · JSON-LD structured data 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.