In-depth practical guides

Verify a redirect and a domain change

Find a citation’s useful destination, preserve context and distinguish migration, login and error.

Updated :

Ethernet switch and network cables. Illustrative scene.

AI-generated illustration · Ethernet switch and network cables. Illustrative scene.

Does the destination preserve the cited document?

A successful final HTTP response does not prove that the original document still exists. It may lead to a home page, login or bot protection. Verify a domain change through response history and final content. Google’s documentation recommends permanent redirects for permanent moves and updating internal links and language alternatives.

  1. Record the chain

    Keep initial URL, status at each hop, Location header, final URL and check time. Distinguish server redirects from JavaScript navigation. Use GET if HEAD is refused or responds differently.

  2. Verify the cited passage

    Compare title, publisher, identifier, language and relevant passage. A destination on the same domain may be unrelated. Blocked access proves neither disappearance nor ownership change.

  3. Choose the published link

    For a confirmed migration, cite the new public page matching topic and language. Retain a DOI or other persistent identifier when it is the reference point. Do not replace it with a personalised login or session URL.

  4. Check dependencies

    Update affected citations, canonicals, hreflang, sitemap and internal links. Repeat the journey in every language; retain the old address in the migration log and schedule a recheck.

Situations and decisions

Typical situations for preparing a check. They do not describe completed assignments or actual observations.

A profile leads to the home page

Fictional case: a registry profile redirects to the home page. Final status 200 does not validate the profile. Search by identifier and cite the recovered profile or record that it was not consulted.

403 or 429 after a link

An illustrative 403 refuses access; 429 indicates rate limiting. Make a reasonable browser check and consult documentation. Do not rename the service or remove the source on this evidence alone.

Record to retain

  • Old URL and dated response chain
  • New URL, title, language and compared passage
  • Reason for replacement or retention
  • Owner and next check date

Official references

Related source profiles

Related protocols

Checks before reaching a conclusion

  • Does the destination cover the same topic?
  • Is the expected language preserved?
  • Is the final URL public and stable?
  • Can the old citation be recovered from the log?

A register of migrated, retained or unverified citations, with evidence for each decision.

Frequently asked questions

Should every redirected link be replaced?

No. A DOI may be intentionally persistent. A login or consent redirect may be circumstantial. Replace migrated addresses when the new page actually matches the source.

Do 301 and 308 guarantee content continuity?

No. They indicate permanent HTTP movement. Read the destination and check document identifiers and context before concluding editorial continuity.