When an organisation changes domains, the redirect plan is the document that holds the whole move together, recording what will redirect, who owns each decision, and how success will be proven. Who needs this document? The project lead, developers, content owners, and anyone whose campaigns, emails, or printed materials point at the old domain. What is it for? Turning a risky, one-off event into a reviewed, testable commitment that the whole team can work from.
Where does the plan sit? At the centre of the project, agreed before implementation begins and referenced at every check afterwards. Why write it down instead of relying on stand-up conversations? Because a domain change touches search visibility, analytics, advertising, and customer trust at once, and memory is not a control system. How detailed should it be? Detailed enough that a colleague could audit the move from the document alone.
Note what this guide is and is not. It is about the planning document itself, its sections, tables, and governance. It is deliberately not a day-by-day execution diary, because teams first need a plan solid enough to execute against.
Open the plan with scope, stated plainly. List the old and new domains, any subdomains and language versions in or out of scope, and anything explicitly excluded, such as a microsite staying behind. Ambiguity here becomes an argument later, usually at the worst possible moment.
Follow scope with objectives and success criteria. Define what a good outcome looks like in measurable terms, such as no mapped URL returning an error, agreed traffic tolerance in the weeks after launch, and enquiry or sales tracking verified on the new domain. Criteria written in advance prevent the post-launch debate about whether the move went well.
The plan should also name its assumptions and dependencies. Examples include registrar and DNS access, certificate provisioning, and freeze periods for content changes. Recording a dependency, along with the tool you will use to verify the current setup, such as checking where the domain is registered and hosted, stops small access problems from becoming launch blockers. Background reading on related technical writing, including how search features present results, can be found in Google material on featured snippets and search presentation, and further planning articles live on the Seovaro blog.
Every redirect plan stands or falls on its mapping table. Specify the format in the plan itself, even if the full table lives in an attached spreadsheet, so reviewers know exactly what a complete entry looks like and can challenge incomplete rows.
The plan should state coverage rules as well as columns. Confirm that the table includes non-page assets people forget, such as PDFs, images referenced externally, feed addresses, and campaign landing pages with tracking parameters. It should also state how late discoveries are added, who approves them, and how version changes are logged, because a mapping table without version control quietly becomes several conflicting tables.
Finally, describe the pattern rules. Where the new structure is regular, the plan can define rule patterns with worked examples instead of listing every generated row, but exceptions and high-value pages must always appear individually.
A plan without named roles is a wish list. Assign a single accountable owner for the document, a technical owner for implementation, content owners for destination approvals, and a communications owner for stakeholders and support teams. Include an escalation route for launch-day disagreements, decided while everyone is still calm.
The timeline section should work at milestone level rather than minute level: mapping complete, plan approved, staging test passed, go or no-go decision, launch window, and review points afterwards. Note the constraints that shape those milestones, such as avoiding peak trading periods and allowing DNS propagation time, without turning the plan into a minute-by-minute runbook.
The rollback section deserves special honesty. Describe the conditions that would justify reversing the change, how long rollback remains possible, and what reversing would and would not restore. A rollback paragraph written to make everyone feel better, but impossible to execute, is worse than none at all.
Testing belongs in the plan as commitments, not hopes. State that every mapped row will be verified on staging and again live, that internal links and sitemaps on the new domain will be checked, and that forms, logins, and payments will be exercised end to end. Name the evidence, such as test exports attached to the plan, so completion can be audited later.
Before your next planning review, verify the current registration and hosting facts your document depends on: try the Domain Hosting Checker to confirm domain and hosting details for both the old and new domains, so your scope and dependency sections rest on checked facts.
As long as it needs to be to cover scope, mapping format, roles, timeline, testing, monitoring, and rollback without ambiguity. For most domain changes that means a concise main document plus the full mapping table as an attachment, rather than one enormous file.
The project owner should approve the whole document, with technical sign-off on feasibility and rollback, and content sign-off on mapping decisions. Record names and dates in the plan itself, so approval is auditable after launch.
The plan defines what will happen, who owns it, and how success is judged, at milestone level. A runbook is the chronological, step-by-step execution script used during the launch window. Most well-run domain changes need both, written in that order.
Before implementation starts, ideally as soon as the domain change is approved in principle. Writing the plan early surfaces access problems, missing content decisions, and timeline conflicts while there is still time to resolve them calmly.