Website Redesign SEO: The Freeze Addendum to Hand Your Designer First

Website redesign SEO usually fails in the contract, long before anyone writes code. Your designer is paid to make the site look better, and nothing in a typical web design agreement says the new site has to keep the pages, words and URLs that Google already ranks. So the fix is simple: before the designer touches anything, attach a one-page SEO freeze addendum (a short list of things that can't change without a plan) and tie the final payment to it.

I've written that addendum below. Copy it, adjust the names, and send it with your signed proposal. Your designer keeps full creative control. The addendum only protects the parts of your site that earn traffic.

Why website redesign SEO breaks

A redesign feels like a visual project. To Google, it's often a site move in disguise. Here's what tends to change without anyone deciding it should:

• URLs. The new theme or platform uses a different structure, so /services/roof-repair/ becomes /roof-repair-services/.
• Words. Long service pages get trimmed into tidy cards with 60 words each. The text that ranked is gone.
• Titles and headings. The page title (the blue link in Google) gets reset to the theme's default.
• Internal links. Menu and footer links shrink, so deep pages lose the links that told Google they mattered.
• Tracking. Analytics, call tracking and ad conversion tags quietly vanish with the old theme.
• Staging leaks. The test site gets indexed, and Google meets a duplicate of your business at staging.yoursite.com.

None of this is the designer being careless. It's just outside the brief. Google's site-move guide warns to expect temporary fluctuation in site ranking during the move, even when everything is done right. A lasting drop is a different story, and it usually traces back to one of the items above.

If you'd rather have someone run the SEO side of your redesign for you, describe the project in my short questionnaire. I reply with a plan and a fixed quote within one business day.

The SEO freeze addendum (copy and paste)

Paste this into a document, fill in the brackets, and attach it to your design agreement. Plain language is deliberate. Your designer doesn't need to be an SEO to follow it.

SEO Freeze Addendum to the agreement between [Owner] and [Designer], dated [date]

1. URL inventory first. Before design work begins, the Owner provides a list of every current URL that received search clicks, links or visits in the last 16 months. The Designer confirms receipt.
2. URLs stay the same where possible. Any URL on the inventory that changes gets a one-to-one 301 redirect to its closest new page. No mass redirects to the homepage.
3. Top pages keep their substance. The 20 pages with the most search clicks keep their main heading, title tag and body copy, or get an improved version approved by the Owner. Copy is not cut to fit a layout.
4. Staging stays private. The staging site is protected by a password at the server level. A robots.txt rule or a "discourage search engines" checkbox alone does not count.
5. Tracking moves with the site. Analytics, Tag Manager, call tracking and ad conversion tags are reinstalled and tested on staging. A test conversion is recorded before launch.
6. Speed doesn't get worse. Core Web Vitals on the five most visited templates are no worse than on the old site, measured with the same tool before and after.
7. Redirect test report. Before launch, every URL on the inventory is requested and the result (status code and final URL) is delivered to the Owner as a spreadsheet.
8. Launch timing. Launch happens early in a working week, never on a Friday or before a holiday, with the Designer available for 48 hours after.
9. Final payment. The final [X]% is paid when items 5 and 7 are delivered and the live site matches the redirect test report.

Signed: ____________ (Owner) ____________ (Designer)

That's it. Nine clauses, one page. A good designer will sign it without fuss, because it protects their launch as much as your traffic.

Why each clause is there

Here's the reasoning, so you can defend each line if someone pushes back.

Clauses 1 and 2: the URL inventory and redirects

The inventory comes from your data, not from the menu. Search Console's Performance report covers the last 16 months, so export the Pages tab for the full range. Add your old XML sitemap, the URLs other sites link to, and your analytics landing pages. My website migration checklist walks through each source step by step.

Every changed URL then needs a permanent redirect. Google treats redirects as a strong signal that the target of the redirect should become canonical (the version Google indexes). That's why the clause says 301, not just "redirect." Many redirect tools and code snippets default to a temporary 302, and my comparison of 301 and 302 redirects explains what that costs you.

Clause 3: the words that rank

This is the clause designers push back on most, because long copy fights clean layouts. But Google ranks text, not mockups. If your roof repair page ranks for 40 different searches, it's because of the specific words on it: the materials, the neighborhoods, the questions it answers. Swap 900 words for a three-line card and those rankings have nothing to stand on.

The fix is easy. The designer designs around the existing copy, or the owner approves a rewrite that keeps the same topics.

Clause 4: staging that stays private

Robots.txt (a file that asks crawlers not to visit certain pages) is not a lock. Google's own documentation says robots.txt is not a mechanism for keeping a web page out of Google, and a blocked URL can still be indexed if something links to it. Worse, a robots.txt block stops Google from seeing a noindex tag, so the page can still appear in search results.

A password is a lock. On Apache hosting, basic authentication takes a few lines in the staging site's .htaccess:

## Staging site's .htaccess only. Asks for a username and password before showing anything.
## Could break: uptime monitors and payment webhooks on staging. Never copy this file to the live site.
AuthType Basic
AuthName "Staging"
AuthUserFile /home/youraccount/.htpasswd-staging
Require valid-user
Header set X-Robots-Tag "noindex, nofollow"

On cPanel, the Directory Privacy tool does the same without editing files. Plesk calls it Password-Protected Directories. That extra X-Robots-Tag header is a second lock in case the password ever gets removed early.

The real danger comes at launch. Somebody copies the staging site to production, and the "noindex" setting or the WordPress "Discourage search engines" box comes along for the ride. Your brand new site then politely asks Google to forget it. Check this first on launch day.

Clause 5: tracking that survives

When tracking breaks, a redesign can look like a disaster that never happened. If the analytics tag is missing, your reports show a cliff while real visitors keep arriving. So the clause asks for a test conversion on staging, and another one on the live site after launch.

Google Ads deserves its own check. Auto-tagging adds a click ID called GCLID to your ad URLs, and Google says the GCLID must reach the final landing page for conversions to track. If your ads point at old URLs that now redirect, test that the parameter survives the hop. If tracking is already shaky, a GA4 and conversion tracking rebuild is worth doing before launch, not after.

Clause 6: speed that doesn't slip

New themes often ship with sliders, video backgrounds and a dozen fonts. Google's Core Web Vitals (its page experience measurements) set clear targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less. "Not worse than before" is a fair bar for any designer, and easy to measure with the same tool on both versions.

Clauses 7 to 9: proof, timing and payment

The redirect test report is how you check clauses 1 and 2 without learning regex. One command can produce it from your URL list:

## Read-only: request every old URL and print status code, final destination and the original URL.
## Safe to run. Replace old-urls.txt with your inventory (one full URL per line).
while read -r url; do
  curl -s -o /dev/null -L -w "%{http_code} %{num_redirects} %{url_effective} $url\n" "$url"
done < old-urls.txt > redirect-report.txt

Every line should show a 200, one redirect, and the right destination. A 404 means a missing redirect. Two or more redirects means a chain to flatten.

Friday launches are banned because problems surface over the weekend, when nobody is around to fix them. And the payment clause is what turns the addendum from a polite request into a deliverable.

Vlad's take: when to delay the launch

I'd rather see a launch slip a week than go live with a gap. Three findings should stop the clock: a redirect report with 404s on pages that earned clicks, a missing analytics or conversion tag, or a staging copy that's already indexed. Each one costs a day to fix before launch and weeks to untangle after.

A redesign that also changes the domain or the platform is a full migration, and it deserves the full process. If that's your situation, look at a migration with an evidence-built redirect map rather than treating the SEO as an afterthought. If you haven't picked a designer yet, my web design service has redirects from the old site built into the scope from day one.

Final Thoughts

Website redesign SEO is mostly about deciding, in writing, what can't change by accident. The addendum costs you an hour and costs your designer nothing if they were planning to do it right anyway. Send it with the contract, keep the redirect report, and pay the last invoice when the proof arrives. If your site has years of history, or you'd like a second pair of eyes on the plan, a pre-redesign technical audit before kickoff will find the pages most worth protecting.

Website Redesign SEO FAQs

Will a website redesign hurt my SEO?

It doesn't have to. Rankings usually drop after a redesign for specific, fixable reasons: URLs changed without redirects, ranking copy was cut, titles were reset, or a staging noindex setting reached the live site. Google expects some temporary movement during big changes. If you keep URLs or redirect them one-to-one, preserve your best content and test before launch, most sites settle within a few weeks.

How do I redesign my website without losing SEO?

Start with a URL inventory from Search Console, analytics and your sitemap. Keep URLs where you can and set up 301 redirects where you can't. Preserve the copy on your top pages, password-protect the staging site, and reinstall tracking before launch. Then test every old URL and fix 404s and chains. Putting those rules in writing for your designer is the easiest way to make them stick.

How long does it take for SEO to recover after a redesign?

When the redirects and content are handled well, many sites see rankings settle within a few weeks as Google recrawls. Larger sites take longer. If traffic is still well down after a month, look for a cause rather than waiting: missing redirects, deleted content, noindex tags, or broken tracking making the drop look worse than it is.

Should I hire an SEO before or after a website redesign?

Before. Most of the damage happens in planning, when URLs, page structure and copy get decided. An SEO brought in after launch can only find and repair what already broke. Even a few hours before kickoff, to build the URL inventory and the freeze addendum, costs far less than recovering lost traffic later.

Is blocking staging with robots.txt enough?

No. Google says robots.txt doesn't keep a page out of its index, and a blocked page can still show up if something links to it. Robots.txt also hides any noindex tag from Google. Use a server-level password on staging instead, add a noindex header as a backup, and remove both when the site goes live.