To protect your search traffic during a website rebuild, make the agency map every old URL to its new one before launch, redirect each with a permanent server-side redirect, keep those redirects for at least a year, and check Search Console afterwards. Expect some movement in rankings for a few weeks, and plan for it.
By Avi Vatsa, CEO, Exchange Four Agency. Avi leads the team that installs and runs AI-leveraged revenue systems for owner-led companies. His background spans law, technology, and marketing; he also co-founded Dialora, an AI voice-agent platform for automated lead capture and booking. (Marketer of the Day #1411)
Why does a rebuild put search traffic at risk?
Because Google knows your pages by their addresses. Every page that ranks does so under a specific URL, and a rebuild often changes them: a new folder structure, a new platform, a new naming habit. Visitors who followed an old address land on an error page, and Google is left holding links and rankings for pages that no longer exist.
None of this is a secret. Google's guidance on moving a site opens the process with one instruction: "It's important to map your old site's URLs to the URLs for the new site." An agency that rebuilds a site without that map is working without the one document that protects what you have already earned.
What should you ask for before the build starts?
Three things, in writing, before the first design is shown.
| Ask for | Why it matters | What a good answer looks like |
|---|---|---|
| A list of every current URL | The map cannot exist without it | A crawl of the live site, plus the pages Google already shows |
| The pages that earn traffic | These are the ones to protect first | A ranked list from Search Console, by clicks |
| A named owner for redirects | Someone must be accountable on launch day | A person, not "the dev team" |
You can build the second list yourself. In Search Console, the Performance report shows, in Google's words, "the number of times a user clicked your site from Google Search results" and "how many times your site appeared in Search results". Export the pages by clicks and keep the file. It is also your baseline for judging the launch afterwards, and it is the same record you would hand to a new agency, as who owns your marketing assets explains.
How should the redirects be set up?
Google's advice is specific. It recommends "server side permanent redirects from the old URLs to the new URLs as you indicated in your mapping", and warns: "Don't redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site." That second line is the common shortcut. Sending every old page to the home page is quick to set up and tells Google, and your visitors, that the specific page they wanted is gone.
Redirects also have to last. Google suggests keeping them "generally at least 1 year." That belongs in the agreement. If the agency hosts the new site and you later leave, the redirects must come with you, which is one more reason to read the hosting and handover clauses in the contract terms guide before the build, not after.
What should be checked on launch day?
Four checks, none of which needs a developer to read the result.
- Open the old addresses. Take the ten pages that earn the most clicks and type their old URLs. Each should land on the matching new page, not the home page and not an error.
- Look for leftover blocks. Google says: "Don't forget to remove any noindex or robots.txt blocks that were only needed for the migration." A site built on a hidden staging copy often carries a block that nobody remembers to remove. Ask the agency to confirm in writing that none is left.
- Submit the new sitemap. Google lists it as the final step: "Submit the new sitemap in Search Console."
- Keep the old export. You will need it for the comparison.
If the domain or subdomain changes, Google adds one more step: submit a Change of Address in Search Console for the old site.
What should you expect afterwards, and when is it a problem?
Some movement is normal. Google says: "Expect temporary fluctuation in site ranking during the move," and that for medium-sized sites "it can take a few weeks or more for Google to gradually start showing the new URLs." So a dip in the first week is not proof of a mistake, and a calm first week is not proof of success.
Compare, do not guess. After a few weeks, export the same Performance report and set it beside the baseline you kept. Look at clicks for the pages you protected. If those pages are down and the rest of the site is flat, the redirects are the first thing to check. If everything is down by a similar amount, look at the launch checks above. Whichever it is, you now have numbers to put in front of the agency instead of a feeling.
What belongs in the agreement?
Four lines, written before work begins: the agency delivers a URL map before design is signed off; it sets the redirects on launch day; it keeps them for at least a year; and it confirms in writing that no migration block is left on the site. Our guide to leaving an agency covers what must come back to you if the relationship ends after the rebuild.
The simple test: could you, tomorrow, name the ten pages that earn your traffic and show where each one lives on the new site? If you can, the rebuild is protected. If you cannot, it is a bet.