Website migration plan, reviewed 28 October 2026

Open website-migration-plan.xlsx in a spreadsheet editor. Save a separate copy of the workbook for each project and fill Plan template and URL template. Retain these tab names so their formulas stay connected. Amber cells are editable inputs. Grey cells contain formulas. The launch decision checks required tasks and gates, owners, evidence references, baseline completion and reviewed URL rows. It is a review aid, not a substitute for inspecting the evidence or owner approval.

Example plan and Example URLs describe the deliberately fictional Birch Studio / Beržo studija, with English and Lithuanian pages. The reserved .example domain is not a live site. Names, dates, HTTP observations and SIMULATED evidence references are teaching data, not real checks or files. Open checks intentionally keep launch on hold. Replace all example values before using this for a real project.

Use example-old-urls.csv and example-new-urls.csv as separate URL inventories in https://webaloha.co/tools/seo-migration-redirect-mapper/ . They have url,title columns. They support importing and reviewing matches, but live validation requires your own public URLs. A retired old URL intentionally has no destination. Review that decision manually. url-map-template.csv is a blank full-register header for your own records; export its url/title columns for the old inventory and the reviewed destination/title columns for the new inventory. Do not treat the register as a deployment-ready redirect file.

Record one row per old URL, including media and downloads. Keep and Redirect require a destination; Retire requires an intentional response and reason. The URL readiness formula checks duplicate IDs/URLs, required fields, an explicit Pass result and matching source HTTP codes. A Reviewed row records your completed checks; it does not fetch a URL or prove a relevant redirect, canonical, language relationship or customer flow. Extend the Excel table, fill the readiness formula, and extend the bounded launch-decision and duplicate-check ranges when adding rows beyond the supplied template.

The plan contains scope and baseline fields, task owners, dependencies, evidence, launch gates, rollback actions and 7/14/28-day reviews. Keep real evidence in your own accessible storage and reference it here. Do not enter passwords or personal customer data. Not applicable needs an explanation and evidence. Do not count an untested function as passed.

Review dates are calculated from the planned launch date. Update that date to the actual launch when it happens. Search clicks, analytics sessions and received enquiries are different measures. Record exact comparison windows, filters, consent changes, incomplete data and other work. The first month is an operating schedule, not a promise that indexing or rankings settle within 28 days.

Before a rollback, identify the action owner and preserve new orders, bookings or enquiries. Restoring an old database can overwrite new writes. Rehearse recovery before launch and test the customer journey after restoring.

website-migration-plan.json contains the same template fields and fictional example in a text format.

Sources checked 28 October 2026:
Google site moves; reviewed 2026-10-28
https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes

Google hosting changes; reviewed 2026-10-28
https://developers.google.com/search/docs/crawling-indexing/site-move-no-url-changes

Google redirects; reviewed 2026-10-28
https://developers.google.com/search/docs/crawling-indexing/301-redirects

Web Aloha redirect mapper
https://webaloha.co/tools/seo-migration-redirect-mapper/

Guide: https://webaloha.co/website-redesign-without-losing-seo/