For web agencies handing over a rebuilt site

Website migration checklist

Keep the evidence behind every old URL, and leave the next person a clear account of what still needs work.

This checklist covers the URL comparison and handover. Your launch plan also needs live checks for forms, rendering, analytics and search performance.

  1. Keep the before and after crawl exports.

    Save the original exports with their crawl dates and scope. Use the old crawl to account for the pages you are moving; the current crawl supplies evidence about their destinations. A crawl that missed a section cannot establish that the section is fine.

    Keep: original files, crawl dates, included hosts and known exclusions.

  2. Give each old URL a destination or a recorded reason.

    Work from the old URL list, rather than only the pages found on the new site. Check every destination in the redirect map. Record intentional retirements and consolidations with a reason. A missing mapping still needs an explicit decision, even when removing the page was deliberate.

    Keep: the old URL, its intended destination and the reason for any exception.

  3. Test the live redirect path separately.

    Use your crawler or browser to inspect the old URL and its final destination. Check for loops, unnecessary hops, unexpected hosts and error responses. Where a page has moved permanently, check that the server uses an appropriate permanent redirect. A map is an instruction; it does not prove that the server follows it.

    Keep: the observed redirect path, final response and time checked.

  4. Read the destination beyond its status code.

    Compare the title, H1, canonical and indexability evidence. Investigate a staging address in a canonical, an unintended noindex, a changed title or a blank field. Write down an intended change as intended. An HTTP 200 alone does not establish that the right content can be indexed.

    Keep: the source row, the changed or missing field and your decision.

  5. Put an owner and next action on each open finding.

    Make the handover useful to the person fixing it. Name the affected URL, what the evidence shows, who owns the next step and what they need to do. Keep unresolved gaps visible in the opening summary. Recording a decision does not make a missing destination or canonical disappear.

    Keep: one follow-up list, grouped by owner, with source records attached.

  6. Recheck the corrections and keep the first record.

    After the fixes, export a fresh current crawl and the corrected map. Compare the changed pairs and keep the earlier handover beside the new result. Record which findings are resolved, which remain and which could not be checked. Retain the files behind both versions so your client can trace a decision back to its source.

    Keep: the original handover, corrected files and the outcome of each recheck.

Start with the files

Three CSVs for a traceable comparison

Redirectory reads these headers exactly. Keep the originals; if your export uses different names, make an adapted copy.

Old crawl and current crawl
Address and Status Code are required. Include Indexability, Indexability Status, Title 1, H1-1 and Canonical Link Element 1 when available. A matched current row with a missing indexability, title, H1 or canonical value is flagged. The comparison does not audit every missing field in either file.
Redirect map
Use Old URL and New URL. Each address must be a complete HTTP or HTTPS URL without a fragment or embedded credentials. Resolve duplicate source URLs before import. If several old URLs share a destination, add a Merge rationale column and put the same nonblank explanation on every affected row.

Up to 250 HTML rows per file, 2 MB per file and two origins across all three files. The comparison reads your exports locally and does not fetch any address in them.

See the format in a fictional project: download the old crawl CSV, current crawl CSV and redirect map CSV. These are example records, not a crawl of a real site.

Finish the checks outside the files

Test important forms and customer tasks in a real browser. Verify the new site's sitemap and Search Console property, and watch indexing and traffic after the move. Keep live results with their dates; a clean exported comparison cannot certify a launch or guarantee rankings.

Google's site-move guidance explains URL mapping, redirects and post-move monitoring. Use it alongside your site's own release plan. Guidance checked November 17, 2026.

When you want the handover written for you

A reviewed record of the files you share

For $249 per project, an AI agent operator reads your source pairs, records decisions and follow-up owners, and delivers a portable handover with one correction recheck. Live redirect testing and independent human expert review are outside the service.

Get a $249 reviewed handover