Skip to content
regensbot
DEV-CAN-10Must10 of 11 in CAN

Redirect an old URL only to a page with the same intent, and return 404 or 410 when there is none

Level
Must

Required: the site is not ready to launch without it.

Documentation

Documented

At least one cited Google document states or supports it.

Covered

Assisted

Proposed with the evidence. A person confirms it.

Why it matters

Google's site move guide warns against redirecting many old URLs to one irrelevant destination such as the home page, which can confuse users and might be treated as a soft 404, and says to return 404 or 410 for content that is not moved. Community speakers who ran migrations at the event built them around one redirect map that gives every old URL an approved destination, redirected only where a new page served the same intent and never sent removed URLs to the home page, even those still bringing traffic. A 200 on every new URL proves only that the URLs work, not that the content users came for is still there.

How to meet it

Before launch, freeze the inventory (CMS export, crawl, sitemaps, search data and logs) and approve a redirect map with one row per old URL: a same-intent target, or 404 or 410. Where two language or market versions duplicate each other, redirect both old URLs to one shared target. After launch, test the live site against the map.

How to test it

A script requests every old URL in the map and checks it returns one 301 to the mapped target, or the mapped 404 or 410; no old URL other than the old home page redirects to the new home page; the Page indexing report shows no rise in soft 404s on redirect targets.

How Regensbot covers it

AssistedNeedsYour verified site

Regensbot proposes a verdict with the evidence; a person on your team confirms it.

The evidence comes from your verified site: its pages, its profile and the files you upload.

You verify the site by a DNS TXT record, a meta tag or a file. Regensbot then keeps a checklist item for this requirement, with a state, a guide, an evidence upload and reminders.

How verdicts workWhat you connect

Sources

Google documents02

  1. 01How to move a siteGoogle Search Central (opens in a new tab)
  2. 02How HTTP status codes affect Google's crawlersGoogle (opens in a new tab)

Claims in the knowledge base07

  1. D2-C911SourceLightning session E: Managing Duplicates and Site MovesGoogle's documentation
  2. D2-C882ConsistentLightning session E: Managing Duplicates and Site MovesSaid on stage
  3. D2-C883ConsistentLightning session E: Managing Duplicates and Site MovesSaid on stage
  4. D2-C895ConsistentLightning session E: Managing Duplicates and Site MovesSaid on stage
  5. D2-C902ConsistentLightning session E: Managing Duplicates and Site MovesSaid on stage
  6. D2-C903ConsistentLightning session E: Managing Duplicates and Site MovesSaid on stage
  7. D1-C479ConsistentQ&ASaid on stage

Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)

Consistent
Google's documentation supports it without stating it.
Source
The claim is the cited document itself.

Audit

Check it on your site.

One audit checks a URL against all 138 requirements and returns one finding for each, with its source. One URL decides 66; for each of the others, the finding says which source to connect.