The short answer
Before launch, the new site must match the old one on everything that earns: the words, the titles and meta, the schema, the internal links, the forms and the tracking. Then prove it, with a crawl comparison and real test submissions. "It looks right" is not a test. The problems that hurt after launch are usually small and invisible: a form that sends to an old inbox, a noindex left on a template, an event that never reaches analytics.
Content: move it, do not rewrite it
Keep tier A copy word for word through the move. If rankings shift, you want to know the move caused it, not a new headline. Improve the copy after things settle.
- Every page in the inventory that is staying has a home on the new site.
- Body copy, headings and link text came across whole, including hidden tabs and accordions.
- Images came across with their alt text, and are sized and compressed.
- Downloads and PDFs were moved, and links to them still work.
- CMS items were imported in full, with dates and authors kept, and rich text checked for broken formatting.
- Words like "lorem ipsum", "test" and "sample" are gone, including from hidden panels and mobile-only blocks.
That last one is real. In the check before launching our own new site, we scanned every built page for test wording, and found some in a hidden panel left over from a prototype. A search over the built HTML takes minutes.
SEO parity, page by page
Crawl the staging site and compare it with your inventory crawl, by URL. Keep the same URLs, titles, meta, schema and internal links wherever a page is staying. That is the standard to aim for.
| Check | On the new site | How to check |
|---|---|---|
| Title and meta | Same as before, unless you chose to change one | Crawl comparison |
| H1 and headings | Same message and order | Crawl comparison |
| Canonical | Points at itself, using the new URL | Crawl: canonical equals URL |
| Robots | No stray noindex at launch. Keep a list of what to remove. | Crawl, then search the HTML |
| Internal links | Point at new URLs, not through redirects | Crawl: no internal 301s |
| Schema | Same types, valid, with new URLs | Rich Results Test on each template |
| Hreflang | Updated to new URLs, on every version | Crawl comparison |
| Sitemap | New URLs only, matching the canonicals | Open it and compare |
| robots.txt | Blocks only what you mean to block | Read the file |
| Social images | Exist, and open without errors | Open each image URL |
The canonical, hreflang, internal link and robots points all come from Google's site move guide. Two more checks that catch real problems: when we audited our own new build, 16 pages pointed at social images that did not exist, and sitemap URLs did not match our canonical URLs until we fixed the trailing slash. Neither showed up on screen.
Decision rule A row in the comparison can differ only if someone chose the change and wrote down why. Any other difference is a bug.
Hide staging, and plan how to unhide it
You do not want staging in search results, and you do not want the launch to carry over the block. Protect staging with a password if your host allows it, or use noindex.
Google suggests preparing the list of URLs where you will remove noindex, and getting the final robots.txt ready, before launch. Write down the exact steps, and put them on your launch sheet in chapter 5.
Carry over your Search Console verification too, whether it is a file, a meta tag or a DNS record. Verify the new property before launch if the address is changing.
Forms: send a real one
Forms are where a move can cost you the most and show it the least. List every form, on every page, and test each one all the way to where the message lands.
| For each form | Check |
|---|---|
| Where it sends | The right inbox, CRM or sheet, and a person confirms it arrived |
| Every field | All values arrive in the right column, including dropdowns and hidden fields |
| Campaign data | UTM tags and the page it was sent from are kept, if you used them |
| After sending | The success message or thank-you page shows |
| Spam guard | A honeypot or similar is working, and real messages still get through |
| Bookings and embeds | Calendars and third-party forms load, and are allowed by your security policy |
| Privacy | The policy names any new tool that now handles this data |
On our own new site we submitted each kind of form and confirmed that a lead came through. Do this on staging, then again on the live site on launch day. A form that works on staging can fail on the live domain, because of a domain allow list or a security rule.
Tracking: see the hit arrive
Set up tracking on the new site to match what you measure today, then check that the data actually arrives. A tag being present proves very little.
- List the events and goals you report on today, and rebuild each. Our post on tracking setup has a starting list.
- Open the real-time or debug view and do each action: send a form, click to book a call.
- Check any thank-you page that a goal or ad conversion depends on.
- Cookie consent works: nothing fires before the visitor agrees, where your rules require that.
- Ads, heatmaps, chat and other scripts are added on purpose, not copied across out of habit.
- Note in analytics the date of the move, so later readers can see it.
A real example from our own build: our custom events looked fine on the page, but they were missing a send_to setting, and without it they never left the page. We only caught that by watching what was actually sent. So capture the hits, and look at them.
Speed, mobile and the rest
You moved partly to be better, so check that you are. Run Lighthouse on your top templates on mobile, and compare with your before picture. Check your main pages on a real phone. Then go through the rest of the things the old site quietly did:
- The 404 page is designed, and links to useful pages.
- Search, login, gated content and members areas all work.
- Connected tools, such as your CRM and email, are connected to the new forms.
- Legal pages are up to date, and name your new host and tools.
- Editors can publish a page on their own. Try it, with a real editor.
Our website launch checklist and Webflow SEO checklist go deeper on each area. If you would rather hand this part over, it is the core of our migration work, and SEO and analytics services cover the specialist parts.
Done when The comparison crawl has no unexplained differences, every form has landed in the right place, and every event has been seen arriving.


