Compare migration redirects with canonical targets

Compare a small set of old URLs, their planned or observed redirect destinations, and the canonical targets you recorded from the corresponding new pages. This worksheet checks only the values you paste; it does not request pages, follow redirects, or read canonical tags.

Use one URL mapping per line and exactly two tabs between the three columns. Each value must be an absolute HTTP or HTTPS URL. Blank lines and lines beginning with # are ignored. Paste a small review sample; the worksheet accepts up to 200 rows.

Compare URLs Copy report

Paste URL rows, then compare them.

What the flags mean

• Redirect and canonical differ: the normalized destination you entered does not exactly match the canonical target you entered. Review whether this is intentional and whether both URLs represent the same content.
• Old URL is its own destination: the row describes a self-redirect and needs review.
• Canonical still points to the old URL: the entered canonical target is the old URL, even though the row lists a different redirect destination.

URL comparison uses the browser URL parser, ignores fragments, and keeps scheme, hostname, port, path, and query. These are exact consistency flags, not a judgment about which URL Google should select. Redirect responses and page canonical elements must be checked separately.

Migration review context

Google's site-move guidance recommends mapping old URLs to corresponding new URLs and testing redirects. Google also describes canonical signals as a way to indicate a preferred URL. This worksheet makes no network requests, and its pasted values cannot establish what a live server returns or which canonical a crawler sees.

• Google Search Central: site moves with URL changes — URL mapping and redirect testing.
• Google Search Central: canonicalization — canonical signals and preferred URL guidance.
• Redirect-map coverage checker — find missing, duplicate, or unused source rows in pasted lists.
• Redirect response log reader — summarize status and Location lines you already collected.
• Website migration checklist — record per-URL migration validation evidence.

Your input stays in this browser page and is not uploaded. A complete migration review may also need to test response codes, redirect chains, page content, internal links, and canonical tags on the actual destination.