After observing 301, inspect Location, the rest of the chain, the final response, and whether the destination actually replaces the source.
The status has a defined meaning
RFC 9110 defines 301 Moved Permanently as a redirect indicating that the target resource has been assigned a new permanent URI. Google currently describes 301 and 308 as permanent redirect signals for Search.
That is enough to classify the observed response as a stated permanent move. It does not fill in any missing evidence about the destination.
Five questions remain
- Did Location resolve to the intended URL?
- Did another hop change the destination or permanence?
- Did the final URL return a usable response and representation?
- Does the final page satisfy the same user job as the source?
- Do canonical and robots signals agree with the migration intent?
Homepage redirects need the same proof
A blanket redirect can remove 404s from a report while sending visitors to an unrelated page. That is not the same as restoring a resource or consolidating equivalent content.
For retired software downloads or historical pages without a rights-safe successor, an explicit 404 or 410 may describe the state more accurately.
Test the chain as a sequence of separate responses
Record the requested URL, status and Location value at every hop. Resolve relative Location values against the current response URL, not the original URL. Stop on a loop, a missing Location header, an unsafe scheme, or a defined hop limit instead of guessing the final destination.
Then request the final URL independently and capture its status, content type, robots directives and canonical. Browser address bars often hide intermediate hops, so a final-looking page is not evidence of a clean one-hop migration.
Judge equivalence from the user's task
The destination should help the person who requested the old URL complete substantially the same task. A moved product page can usually redirect to its direct successor. A retired download with no rights-safe replacement may be better represented by 410 and a clear explanation than by a generic homepage.
This decision is editorial as well as technical. Matching words in a title are weaker evidence than matching purpose, scope and expected next action.
Migration evidence worth keeping
- A versioned source-to-destination map with an owner for each decision.
- Pre-launch and post-launch captures for representative URLs.
- A check for redirect loops, long chains and mixed host or protocol hops.
- Final-page status, canonical, indexability and internal-link updates.
- A follow-up window in logs and search-platform reporting without a ranking promise.
A lower 404 count is not a success metric when unrelated URLs have merely been hidden behind homepage redirects.