SEO Migration Audit — URL and Page Evidence

SEO MIGRATION AUDIT · OBSERVED EVIDENCE

Compare an old URL with its intended destination

Check up to 5 explicit URL moves with bounded GET requests. Review redirect behavior, the destination’s initial HTML signals, and an optional earlier metadata snapshot.

Free · no API requiredGET only · explicit pairsNo redirects or SEO settings changed

Match old and expected URLs line by line

Line 1 on the left pairs with line 1 on the right. Keep both lists the same length; blank values are never shifted or guessed.

Old URLsOne public HTTP(S) URL per line, up to 1,000 bytes each. Query strings and credentials are not accepted. Expected destinationsUsed as the comparison target only; it is not requested separately.

Optional: supply an earlier metadata baseline

Paste one JSON object if you have a snapshot from before the move. It is user-supplied and unverified; this tool does not invent historical data. Each row must identify a submitted old URL and include at least one of title, description, or h1.

{"source":"your-export","captured_at":"2026-01-15","rows":[{"old_url":"https://example.com/old-page","title":"Old title","description":"Old description","h1":"Old heading"}]}

Baseline JSONValidated again on the server. Maximum complete request size is 32 KiB.

This is a bounded migration subset: supplied old URLs are traced, and only a reached final HTML response is inspected. It cannot verify a full-site move, content equivalence, rankings, indexing, rendered JavaScript, hreflang, or Search Console processing.

Submitted URLs and optional baseline are sent to this site for one server-side check. The tool does not save reports or raw page bodies; requested websites and ordinary infrastructure may log requests. Human verification and shared Site Audit limits apply.

Human verification

The code expires after ten minutes and works once.

Check URL moves with evidence you can review

Enter explicit old-to-expected URL pairs to observe redirect behavior and the reached page’s initial HTML signals. The report keeps destination agreement, redirect type, HTTP status, canonical declarations, robots noindex evidence, and metadata separate so an incomplete check is not mistaken for a migration pass.

If you have a snapshot from before the move, you may supply its title, description, or H1 values with a date and source label. The baseline is user-supplied and unverified; this tool does not invent historical content or fetch the expected URL separately.

A bounded migration evidence check

No paid API is required. The audit does not verify Google indexing, Search Console processing, rankings, traffic, content equivalence, hreflang, full-site coverage, or migration completion. It does not create redirects or change your website. For broader page sampling, use the Website SEO Analyzer; for a single canonical declaration, use the Canonical Tag Checker.

Questions about migration evidence

Does a matching redirect prove migration success?

No. Destination agreement, redirect type, response status and initial-HTML evidence are separate observations. This tool cannot confirm Google has processed a move or that traffic, rankings and content relevance were preserved.

Is the old page fetched as historical content?

No. Old URLs are requested as they exist now. Optional baseline values are supplied by you with a date and source label; their historical authenticity is not independently verified. Missing baseline fields are not guessed.

Does the tool fetch the expected URL if the mapping fails?

No. It follows the old URL within the pair’s two supplied origins. The expected destination is a comparison target only. Blocked or incomplete chains can leave destination and page evidence unknown.

What can the page evidence show?

Bounded initial HTML and HTTP canonical declarations, general/Googlebot noindex evidence, title, description and H1 values. No JavaScript rendering or canonical-target request is performed. No noindex observed does not mean indexable, and a declared canonical is not Google’s selection.

Does it need APIs or change my redirects?

No paid API is required. It does not create redirects, save reports or change website content. Shared CAPTCHA and usage protections apply. Requested websites and ordinary infrastructure may log requests.