Practical digital skills

Document a website domain change without losing references

Follow the real destination, compare content and publisher, and update links, citations and bookmarks with a migration record.

Step-by-step guideUpdated
Follow the method ↓
Two document versions examined on a desk — AI-generated illustration
AI-generated illustration: fictional scene, no real scientific document.

The answer in 30 seconds

An old link may redirect to a new address, a homepage or different content. Replacing a domain everywhere without reading the pages can damage a bibliography or directory. This method concerns public links; never send private URLs to third-party checkers.

Open the old address, record the destination and compare the expected content. HTTP 301 indicates a permanent technical move, not proof of publisher continuity. Confirm the current name through the site’s introduction and publisher information, then link to the equivalent page.

Examples to adapt

An old network record

Fictional example: a subdomain redirects to a standalone domain. Update the address and confirmed current name while retaining the record’s stable internal ID.

A homepage redirect

Fictional example: a cited report now opens a homepage. Find the exact report before considering the citation repaired.

Follow the method

  1. 1
    Preserve the original reference

    Record old URL, cited title, author or publisher and original access date. Remove parameters containing personal information before sharing a log.

  2. 2
    Observe the destination

    Open the link and record the final address. Technical checks should record HTTP status, redirect steps and check date separately. HTTP 200 only records a response.

  3. 3
    Compare document and identity

    Find the useful page and matching subject rather than accepting a homepage. Check publisher information for the current name. If the document disappeared, seek an archive and identify it as historical.

  4. 4
    Update and test

    Change address, label and cited name according to confirmed observations. Test destination and language. Keep old link, new address and the reason in your log.

A checklist to keep

Use these checks to record your observations. They are a reading aid, not an automatic assessment.

Document a website domain change without losing references: checklist
CheckWhat to examineAction
OriginalURL, title, publisherPreserve context
ObservationDestination, HTTP, dateSeparate response and content
EquivalenceSubject, language, identityConfirm before replacement
UpdateCurrent URL and nameTest and keep the record

Download the CSV checklist

Free, no sign-up. UTF-8 text with semicolon-separated columns.

What to check

Do not infer new email addresses from website domain changes.

Do not give a historical source a title it never had.

403 responses and timeouts need investigation, not closure assumptions.

Common questions

Should the record ID change?

Retain a stable ID when the subject remains the same. Address and display name are separate fields.

Does a 301 prove the same owner?

No. Check publisher information separately.

How should I cite an archive?

Retain historical title and date, identify capture provenance and distinguish it from the current page.

Sources and documentation

Documentation consulted on . Examples are illustrative; interfaces and results may change.

Reference record for this resource

Identify the publisher, official destination and practical checks before using the service.

Read the MDN Web Docs record →

Continue exploring

All English guides →