What to check when moving a site that gets search traffic
A new site can look finished while an old search result sends a visitor to an error. Before launch, ask your agency for an inventory of pages and files, an old-address map and staging results. Have it rerun the map at cutover, then compare search visits by page as Google recrawls the new addresses.
Francisco Contreras · Founder, Machina
5 min read

Decide where every old address should lead
When we moved the Veterans Transition Center off Wix, 51 old addresses needed a destination before launch. If one of your pages brings a call, an order or a donation, an old search result or link to that page cannot simply end at an error. We believe the address map belongs in the redesign. We keep an address when its page still answers the same question and give every changed address a deliberate destination before launch.
We start with the current sitemap, a crawl of the site, search visits by page, and links from other sites. We also list PDFs, images and other files people reach directly. Save a dated report of clicks and impressions by page and search query before the move so the team has a baseline.
For each old address, record the new destination, why it fits and who approved it. When several old pages become one fuller page, each can lead to that page. If a page has no similar replacement, we would get the content owner’s approval to retire it and return a 404 or 410, which means the page is gone. We would not send unrelated pages to the home page just to make the map look complete. Google warns that irrelevant mass redirects can be treated as missing pages.
| Old address | Purpose and evidence | Intended destination or decision | Observed final address and status | Owner and fix |
|---|---|---|---|---|
| /housing | Current housing page still answers the same question | Keep /housing | /housing, 200 | Web lead, no fix |
| /benefits and /housing-help | Two overlapping guides are combined | Move both to /veteran-housing | Each returns 301 (permanent redirect), then /veteran-housing returns 200 | Search lead, retest both |
| /events/2022 | Old event with no similar replacement | Retire, approved by content owner | /events/2022, 410 | Content owner, removal approved |
Illustrative addresses and test results, not a client record. A 200 means the server returned a successful response. Check the page itself. Enter and test each old address separately in a working map.
For the Veterans Transition Center move, we ran the full audit and built a redirect map from 51 old Wix addresses to 26 new pages. That meant some new pages received more than one old address. The center’s team reviewed and revised every redirect, and we checked every target before launch. We also re-hosted files from a newsletter archive to more than 250 event photos. Where does your current platform store those files, and will the old links still open them after you close the account? On July 27, 2026, we verified Search Console and submitted the sitemap as the site launched. The case records later search growth alongside new content and other search work. It does not isolate the move as the cause.
What should the agency show before launch?
Ask for the map while the new pages can still change. It should show pages that earn search visits or have outside links, a relevant destination for every changed address, and any choice that needs your approval. Name who controls the old hosting, who can set redirects and who can repair a failed path on release day. If the domain changes, the old domain must stay in place to serve redirects.
For a permanent move, we ask for server-side permanent redirects where possible. The 301 and 308 codes in the test report tell browsers and Google that a page has moved for good. Google recommends this type of redirect. The report should start at each old address and show where it finally lands. We want one direct route to the relevant page. A loop, error or unrelated destination on a priority address is a reason to stop the cutover.
The pre-launch report should also show that menus and other internal links point to the new addresses, the sitemap lists them, and each page names its preferred address through a canonical tag. Pages intended for search must have no leftover development instruction that blocks indexing. For a domain or subdomain move, the agency should have access to both sites in Search Console and a plan to use Change of Address. That tool does not apply when only paths change on one domain.
Who checks the live site, and what happens if a path fails?
We test the full map on staging before cutover. A failed priority address is fixed and retested before the new site replaces the old one. Agree in advance who has authority to delay the release, who can change a redirect, and whether the release can be rolled back. We rerun the map against the live site as soon as cutover happens. If a priority address fails, the named owner repairs it that day, or the team uses a planned rollback if it remains possible.
- Have the release owner open priority old addresses and every exception in the map. Record the final page, response code and whether it answers the old question.
- Open new pages and files on a phone. Test the forms and the actions that bring a visitor closer to a call, order or donation.
- Confirm that pages meant for search can be reached and no development block on indexing remains.
- For a domain move, confirm that the old domain serves its redirects. Verify both sites in Search Console, submit the new sitemap and use Change of Address where it applies.
- Hand over the remaining faults with each old address, expected destination, observed result, owner and retest time.
What should the agency watch after the move?
For a domain move, review both sites in Search Console. For a move within one domain, compare the old and new page addresses within that site’s reports. Review indexing, crawl errors, and clicks and impressions by page and query. Ask the hosting team which old addresses people or search engines still request. If a page that brought search visitors loses traffic, test its old address, its new destination and whether the new page is indexed. Once that route works, inspect the content and other changes.
Search visibility can move while Google recrawls a site. Google says a medium-sized site may take a few weeks or more to start showing new addresses in results, with the pace depending largely on the number of addresses and server speed. That is not a deadline for traffic to recover. Compare like periods and individual pages before blaming a redirect, new content or another change for a rising or falling graph.
The same guidance recommends keeping redirects as long as possible, generally at least a year. Keeping them longer also lets someone using an old link reach the right page. Put redirect ownership and a retention plan in the handoff, so a hosting change does not quietly remove them.
We join a move before the new addresses are final, map the pages that earn search visits, test on staging and check the live site on launch day. We keep watching landing pages and indexing after the release. That is the work behind our SEO website migrations service, alongside broader technical SEO. When you compare proposals, ask each team how it would test one of your busiest old pages and who would fix a failed redirect. In your application, tell us when the site moves and which pages already bring calls, orders or donations. Reach out to Machina.
Explore related work
Next steps
Let's talk about your project
Tell us what you're working on. We'll tell you if we can help — and exactly what we'd do.
