How to Redesign a Website Without Losing SEO: Content Audit, Redirect Map and Launch Steps

A redesign changes how a site looks. It should not change what search engines already know about it. When rankings drop after a relaunch, the cause is usually mechanical: pages moved without redirects, content disappeared, titles were rewritten, or the new site was accidentally hidden from crawlers.

All of that is preventable. This guide walks through the work in the order it should happen.

Step 1: Record what you have before you touch anything

You cannot protect what you have not measured. Before design starts, capture a baseline.

• A full list of current URLs. Crawl the site with a crawler such as Screaming Frog, or export from your CMS. Include the sitemap.
• Search performance. Export queries, pages, clicks and impressions from Google Search Console for the last several months.
• Analytics. Export sessions and conversions by landing page from your analytics tool.
• Backlinks. Export the pages that other sites link to, from Search Console's links report or a backlink tool you already use.

Save these in a shared folder with the date. After launch, this is your before picture.

Step 2: Run a content audit

Open the URL list in a spreadsheet and add columns. For every page, decide one of four outcomes.

Decision	When to use it
Keep as is	The page performs, is accurate, and fits the new design.
Keep and improve	The page has traffic or links but the content is thin or dated.
Merge	Two or more pages cover the same topic and compete with each other.
Remove	The page has no traffic, no links and no purpose.

Add columns for: current URL, page type, monthly clicks (from Search Console), inbound links, decision, and new URL.

Two rules make the audit safer.

Do not remove a page just because it is old. Old pages with backlinks or steady search traffic are assets. If you must retire one, redirect it to the closest relevant page.

Do not rewrite everything at once. If a page ranks well, keep its main heading, the topic it covers and the information that made it useful. Improve around it. A full rewrite on launch day makes it impossible to tell what caused any change afterwards.

Step 3: Design the new URL structure on purpose

The cleanest redesign keeps URLs the same. If a page does not need a new address, do not give it one.

When URLs must change (new information architecture, a CMS switch, a removed category), follow these rules.

• Keep URLs short, lowercase and readable, with words instead of IDs.
• Mirror the hierarchy a visitor would expect: /services/web-design, not /page-27.
• Choose one format for trailing slashes and stick to it.
• Do not change a URL unless there is a reason you can write in one sentence.

Step 4: Build the redirect map

The redirect map is the most important document in the project. It lists every old URL and where it goes.

The format is simple:

old_url,new_url,type
/about-us,/company,301
/blog/2019/05/old-post-title,/blog/old-post-title,301
/services/web-design-bd,/services/web-design,301
/old-landing-page,/services,301

Use a 301 (permanent) redirect for pages that have moved for good. Rules to follow:

1. Redirect to the closest relevant page. Sending a retired product page to the homepage is a weak signal and a poor experience. Send it to the matching category or the replacement.
2. Avoid chains. If A redirects to B and B redirects to C, point A directly at C.
3. Cover every old URL that has traffic or links. Start with the top pages from your analytics and backlink exports, then work down.
4. Include variants. Check versions with and without www, with and without trailing slashes, and with common tracking parameters.
5. Test before launch. Run the map against a staging site and confirm each old URL returns a 301 to the intended new URL with a 200 response at the end.

Step 5: Carry over the on-page SEO

For each kept or merged page, check that the new design preserves:

• Title tag and meta description. Keep the ones that perform, or improve them deliberately.
• Headings. One H1 per page, with H2s and H3s in a logical order. A design that turns headings into styled paragraphs removes structure search engines rely on.
• Body content. The text that earned the ranking should still be on the page, in crawlable HTML, not baked into images or hidden behind interactions.
• Image alt text and file names.
• Internal links. Update links within the site to point to new URLs directly, not through redirects.
• Canonical tags. Each page should point to its own preferred URL.
• Structured data. If the old site had schema markup for articles, products or organisation details, rebuild it.
• Hreflang for multilingual sites, if used.

Step 6: The launch checklist

Work through this list on launch day, in order.

1. Remove any noindex tag and any password protection used on staging. This is the most common launch-day mistake, and it is easy to miss.
2. Check robots.txt allows crawling of the live site.
3. Deploy the redirect map and spot-check the top 50 URLs by traffic.
4. Submit the new XML sitemap in Google Search Console.
5. Confirm analytics and conversion tracking fire on the new site.
6. Test forms, checkout or any other conversion path end to end.
7. Crawl the live site and look for 404s, redirect chains and missing titles.
8. If the domain is changing, use the Change of Address tool in Search Console and keep the old domain's redirects in place.

Step 7: Monitor for the first month

Rankings may move for a short period after any large change, because search engines need time to reprocess a site. Do not panic, and do not start changing things daily.

• Week 1: check Search Console for crawl errors and coverage problems every day. Fix 404s that have traffic or links by adding redirects.
• Weeks 2 to 4: compare clicks and impressions for your top pages against the baseline from Step 1. Look at pages, not just totals.
• After a month: investigate pages that fell and did not recover. The cause is usually a missing redirect, removed content or a changed title.

Mistakes and fixes

Launching with staging settings still on. Fix: put "remove noindex" at the top of the checklist and verify it in the live page source.

Redirecting everything to the homepage. Fix: map each old URL to its closest equivalent.

Changing design, content, URLs and platform in one release. Fix: if you can, split the project. Keep URLs stable in the first release and restructure later.

Forgetting non-page files. PDFs, images and downloads that other sites link to also need redirects or a place to live.

FAQ

Will a redesign always cause a traffic drop?

No. A careful redesign with stable URLs, preserved content and complete redirects can launch with little or no visible change. Drops come from missing steps, not from the redesign itself.

How long should I keep redirects?

Keep them for as long as you can, ideally indefinitely. They cost almost nothing, and old links keep arriving for years.

Talk to us

If you are planning a redesign and want a second pair of eyes on the audit, redirect map or launch plan, write to hello@risingstation.com or visit risingstation.com/contact-us.