Compare staging with production

Fetches the same paths on two origins — staging (a) and production (b), say — and lists every difference in what they tell search engines: status, robots, canonical (read on each side's own host), hreflang, title, H1 and structured data, with critical ones first and a Markdown summary. Paths default to the client's latest crawl (its shallowest pages, spread across templates) or, without a crawl, the links on b's home page; paths narrows it. sendCrawlAuthTo sends the client's set_crawl_auth credentials (basic auth, headers, cookies) to that side only, for a password-protected staging site. When one side's home redirects to the other's host (www to the apex), redirect names the status and target and nothing is diffed, since that side has no pages of its own; single paths that redirect across are listed in redirected. followRedirect: true follows that redirect instead of stopping: each path on the redirecting side is fetched to where it lands and compared with the same path on the other side (the redirect's destination), redirectMap lists where each landed, and a path the redirect sends elsewhere (the home page, a 404) or a temporary redirect shows as a change; redirect stays reported and followedRedirect says it was followed. Answers 'is staging ready to go live', 'what will the migration change' and 'does www still redirect every page to the same path'. No vendor charge; it fetches pages on the client's behalf, so it needs project:manage.