A website redesign can improve user experience, conversion rates, page speed, and organic visibility, but it can also cause a serious SEO decline when URLs, content, redirects, internal links, indexing, or technical settings change without a migration plan.
The safest approach is to treat SEO as part of the redesign from day one, not as something to check after the new website goes live.
Google’s official site-migration guidance recommends planning URL changes carefully and using permanent redirects when URLs move.
A useful redesign SEO process looks like this:
Before redesign → SEO baseline → URL/content mapping → staging SEO checks → launch → post-launch monitoring → recovery and optimization
The numbers below show exactly what you should compare before and after the redesign.
Website Redesign SEO Checklist
Before the Redesign
| Task | Complete |
| Export Google Search Console data | ☐ |
| Record organic traffic | ☐ |
| Record organic conversions | ☐ |
| Record organic revenue | ☐ |
| Crawl current website | ☐ |
| Export all indexable URLs | ☐ |
| Export title tags | ☐ |
| Export meta descriptions | ☐ |
| Export H1s | ☐ |
| Export internal links | ☐ |
| Record backlinks | ☐ |
| Record Core Web Vitals | ☐ |
| Record indexed pages | ☐ |
| Save robots.txt | ☐ |
| Save XML sitemap | ☐ |
| Identify top 100 organic pages | ☐ |
| Identify pages with backlinks | ☐ |
| Identify high-converting organic pages | ☐ |
During the Redesign
| Task | Complete |
| Preserve valuable content | ☐ |
| Maintain important URLs where possible | ☐ |
| Create URL mapping | ☐ |
| Create 301 redirect mapping | ☐ |
| Preserve internal links | ☐ |
| Maintain structured data | ☐ |
| Optimize headings | ☐ |
| Optimize metadata | ☐ |
| Optimize images | ☐ |
| Test mobile UX | ☐ |
| Test Core Web Vitals | ☐ |
| Test staging crawl | ☐ |
| Remove staging noindex rules before launch | ☐ |
Immediately After Launch
| Task | Complete |
| Test homepage | ☐ |
| Test top landing pages | ☐ |
| Test redirects | ☐ |
| Check 404s | ☐ |
| Check 5xx errors | ☐ |
| Check robots.txt | ☐ |
| Check XML sitemap | ☐ |
| Check canonical tags | ☐ |
| Check noindex tags | ☐ |
| Check analytics | ☐ |
| Check Search Console | ☐ |
| Check internal links | ☐ |
| Check structured data | ☐ |
| Check mobile experience | ☐ |
| Check Core Web Vitals | ☐ |
Website Redesign SEO: Before vs. After
| SEO Metric | Before Redesign | After Redesign | What You Want |
| Organic clicks | Record baseline | Compare weekly | Stable or increasing |
| Organic impressions | Record baseline | Compare weekly | Stable or increasing |
| Average ranking | Record baseline | Monitor changes | Stable or improving |
| Indexed URLs | Record count | Check new count | No unexplained losses |
| 404 pages | Record count | Check after launch | 0 critical URLs |
| Redirects | Record existing redirects | Test all new redirects | 1:1 relevant mapping |
| Organic conversions | Record baseline | Compare | Stable or higher |
| Organic revenue | Record baseline | Compare | Stable or higher |
| Core Web Vitals | Record status | Retest | Good or improved |
| Internal links | Crawl baseline | Crawl new site | Important pages remain connected |
| Title tags | Export all | Crawl new site | No critical duplicates |
| Meta descriptions | Export all | Crawl new site | Important pages optimized |
| H1s | Export all | Crawl new site | Correct hierarchy |
| Backlinks | Export referring URLs | Check after launch | Important links resolve |
| Sitemap URLs | Record | Compare | Important URLs included |
| Robots.txt | Save copy | Test new version | No accidental blocking |
The purpose of this comparison is simple: you need a numerical baseline before changing anything.
Without a baseline, you cannot confidently determine whether the redesign improved SEO or caused traffic loss.
Record Your Organic Traffic Before Redesign
Before the design team changes the website, export your current SEO performance.
Use Google Search Console to record:
- Total clicks
- Total impressions
- Average CTR
- Average position
- Top queries
- Top pages
- Countries
- Devices
Also record organic conversions and revenue from your analytics platform.
Example Baseline
Imagine your website currently generates:
| Metric | 90-Day Baseline |
| Organic clicks | 48,000 |
| Organic impressions | 1,200,000 |
| Average CTR | 4.0% |
| Average position | 12.4 |
| Organic sessions | 52,000 |
| Organic conversions | 1,040 |
| Organic conversion rate | 2.0% |
| Organic revenue | $104,000 |
After the redesign, compare the same metrics.
If organic clicks fall from 48,000 to 28,000, that represents a:
41.7% decline
That is not a small fluctuation. It deserves immediate investigation.
Create a Complete URL Inventory
One of the most important redesign SEO tasks is creating a list of the URLs that currently exist.
Your crawl should identify:
- Homepage
- Service pages
- Product pages
- Category pages
- Blog posts
- Landing pages
- Location pages
- Resources
- PDFs
- Images receiving backlinks
- High-traffic URLs
- URLs ranking in Google
- URLs with external backlinks
URL Inventory Example
| Old URL | Organic Clicks | Backlinks | Ranking Keywords | New URL |
| /seo-services | 2,400 | 85 | 142 | /seo-services |
| /technical-seo | 1,850 | 61 | 98 | /technical-seo |
| /local-seo | 1,420 | 47 | 76 | /local-seo |
| /seo-audit | 980 | 33 | 51 | /seo-audit |
This table tells your development team which pages need special protection.
A page receiving 2,400 organic clicks should never disappear from the new website without a deliberate replacement strategy.
Protect Your Top 10, 50 and 100 SEO Pages
Do not treat every URL equally.
Prioritize pages based on actual SEO value.
Create three groups:
Tier 1: Top 10 URLs
Protect these pages first.
Tier 2: Top 50 URLs
Map these pages carefully and test their redirects.
Tier 3: Top 100–500 URLs
Review them for traffic, backlinks, rankings, conversions, and business value.
Priority Formula
You can score each URL using:
SEO Value = Organic Traffic + Rankings + Backlinks + Conversions + Revenue
For example:
| URL | Traffic | Keywords | Backlinks | Revenue | Priority |
| /service-a | 5,200 | 310 | 120 | $25K | Critical |
| /service-b | 3,100 | 180 | 70 | $16K | High |
| /blog-a | 1,900 | 95 | 35 | $4K | Medium |
| /blog-b | 140 | 8 | 2 | $0 | Low |
This prevents a redesign team from spending equal time on a page generating 5,200 visits and a page generating 140 visits.
Create a 301 Redirect Map Before Launch
If a URL changes, map the old URL to the closest relevant new URL.
Correct Redirect Mapping
Old:
/services/seo-services
New:
/seo-services
Incorrect Redirect Mapping
Old:
/services/seo-services
↓
New:
/
Redirecting hundreds of unrelated URLs to the homepage does not create a meaningful replacement for the original content.
Shopify’s redesign SEO guidance specifically warns that incorrect redirects can create problems, while relevant redirects help search engines understand where content has moved.
Redirect KPI
Aim for:
Old URL → One relevant new URL
Avoid:
Old URL → redirect → redirect → final URL
The cleaner the redirect path, the easier it is to manage the migration.
Compare 404 Errors Before and After
A redesign can accidentally create hundreds or thousands of broken URLs.
Record the number of 404 URLs before launch.
Then crawl the redesigned website.
Example
| Metric | Before | After |
| Total crawled URLs | 2,450 | 2,310 |
| 200 status URLs | 2,280 | 2,250 |
| 301 redirects | 110 | 125 |
| 404 URLs | 60 | 8 |
| 5xx errors | 0 | 0 |
A small number of irrelevant 404s may not be a major problem.
But a 404 on a page generating 5,000 organic visits per month is a very different situation.
Prioritize broken URLs according to traffic, rankings, backlinks, and conversions.
Compare Organic Rankings Before and After
Do not measure only your overall average ranking.
Create a keyword-level comparison.
| Keyword | Before | After | Change |
| SEO services | 4 | 5 | -1 |
| ecommerce SEO | 7 | 6 | +1 |
| technical SEO | 9 | 13 | -4 |
| local SEO services | 11 | 8 | +3 |
| SEO consultant | 14 | 18 | -4 |
Look for patterns.
If hundreds of keywords drop simultaneously, investigate technical or structural changes.
If only one topic declines, investigate its content, internal links, search intent, or competition.
Preserve Existing SEO Content
A redesign often removes content because the new design looks cleaner.
That can create an SEO problem.
For every important page, compare:
Before content vs. After content
Example
| Content Element | Before | After |
| Word count | 1,850 | 620 |
| H2 sections | 9 | 4 |
| FAQs | 8 | 0 |
| Internal links | 14 | 5 |
| Supporting terms | 42 | 18 |
| Images | 7 | 3 |
A lower word count is not automatically bad.
The real question is:
Did the new page still satisfy the search intent better than the old page?
If the old page ranked for 120 keywords and the redesigned version ranks for only 35, investigate what information or relevance the redesign removed.
Preserve Title Tags and Meta Descriptions
Export all existing metadata before redesign.
Then compare it against the new website.
Before vs. After
| SEO Element | Before | After |
| Unique titles | 96% | 91% |
| Duplicate titles | 4 | 18 |
| Missing titles | 2 | 11 |
| Unique descriptions | 89% | 72% |
| Missing descriptions | 14 | 42 |
Do not allow the redesign to replace carefully optimized titles with generic templates such as:
Home | Company Name
Services | Company Name
Product | Company Name
Important landing pages need unique, descriptive titles aligned with their search intent.
Check H1-H6 Structure
A redesign can change heading structure without anyone noticing.
Check:
- H1 count
- H1 text
- H2 hierarchy
- H3 hierarchy
- Missing headings
- Duplicate headings
Example
Before:
H1: Website Redesign SEO Checklist
H2: Before Redesign
H2: URL Migration
H2: Redirects
H2: After Launch
After:
H1: Website Redesign
H2: Our Services
H2: Why Choose Us
H2: Contact
The second structure may look visually attractive, but it may remove important topical context from the page.
Protect Internal Links
A redesigned navigation system can accidentally remove links to important pages.
Compare internal linking before and after.
| Page | Internal Links Before | After | Change |
| /seo-services | 42 | 39 | -3 |
| /technical-seo | 31 | 12 | -19 |
| /local-seo | 28 | 8 | -20 |
| /seo-audit | 25 | 4 | -21 |
A major reduction deserves investigation.
Important commercial pages should remain accessible through navigation, contextual links, breadcrumbs, related content, or other logical pathways.
Check Canonical Tags
Every important indexable page should have an appropriate canonical signal.
Compare:
Before canonical → After canonical
Check for:
- Missing canonicals
- Incorrect canonicals
- Canonicals pointing to old URLs
- Canonicals pointing to unrelated pages
- Canonical conflicts with redirects
- Canonical pages blocked by robots.txt
A common redesign error is leaving staging or development URLs inside canonical tags.
For example:
https://staging.example.com/page
instead of:
https://www.example.com/page
That can send confusing signals to search engines.
Check Robots.txt Before Going Live
One of the most dangerous redesign mistakes is accidentally blocking the new website.
Compare:
| Robots.txt Check | Before | After |
| Important pages blocked | 0 | 0 |
| CSS blocked | 0 | 0 |
| JavaScript blocked | 0 | 0 |
| Product pages blocked | 0 | 0 |
| Blog blocked | 0 | 0 |
| Staging rules remaining | N/A | 0 |
A developer may use:
Disallow: /
on a staging website to prevent indexing.
That is fine for a private staging environment.
It becomes disastrous if the same rule reaches production.
Check XML Sitemap
Your new sitemap should contain the URLs you actually want search engines to discover.
Compare:
| Sitemap Metric | Before | After |
| URLs submitted | 1,200 | 1,180 |
| Important URLs | 1,050 | 1,045 |
| Redirect URLs | 0 | 25 |
| 404 URLs | 0 | 7 |
| Canonical mismatches | 0 | 4 |
Do not intentionally populate the sitemap with redirected, broken, or non-canonical URLs.
Measure Core Web Vitals Before and After
A redesign is an opportunity to improve performance, but a visually heavier website can also become slower.
Google’s current Core Web Vitals thresholds for a good user experience are:
| Metric | Good Target |
| LCP | ≤ 2.5 seconds |
| INP | ≤ 200 ms |
| CLS | ≤ 0.1 |
Google Search Central defines LCP as loading performance, INP as responsiveness, and CLS as visual stability.
Before vs. After Example
| Metric | Old Site | New Site | Result |
| LCP | 3.8s | 2.2s | Improved |
| INP | 260ms | 170ms | Improved |
| CLS | 0.18 | 0.06 | Improved |
This is the kind of measurable improvement you want from a redesign.
Do not judge performance from your own laptop alone. Google’s Search Console Core Web Vitals report uses real-user data, while other testing tools can provide laboratory measurements.
Compare Mobile SEO Before and After
Your redesign should be tested on actual mobile layouts.
Compare:
| Mobile Factor | Before | After |
| Responsive layout | Yes | Yes |
| Horizontal scrolling | No | No |
| Text readable without zoom | Yes | Yes |
| Navigation usable | Yes | Yes |
| Buttons accessible | Yes | Yes |
| Main content equivalent | Yes | Yes |
| Core Web Vitals | Needs improvement | Good |
Do not launch a redesigned desktop experience and assume mobile SEO will automatically remain intact.
Preserve Structured Data
If the old website uses structured data, make sure the new site does not remove it accidentally.
Depending on the website, check:
- Organization
- LocalBusiness
- Product
- BreadcrumbList
- Article
- FAQ where eligible and appropriate
- Event
- Review
Compare the markup before and after.
Example
| Schema | Before | After |
| Organization | Valid | Valid |
| Breadcrumb | Valid | Valid |
| Product | Valid | Valid |
| Article | Valid | Valid |
| LocalBusiness | Valid | Missing |
If LocalBusiness markup disappears during a local-business redesign, investigate whether it should remain.
Protect Backlinks
A website redesign can break valuable external links.
Suppose a page has:
75 referring domains
and the redesign deletes that URL.
If there is no relevant replacement, those backlinks may no longer lead users to the intended content.
Create a backlink protection list.
| Old URL | Referring Domains | New URL | Redirect |
| /seo-guide | 120 | /seo-guide | Not needed |
| /technical-seo | 84 | /technical-seo | Not needed |
| /local-seo | 61 | /local-seo-services | 301 |
| /old-report | 45 | /seo-report | 301 |
Prioritize URLs with strong backlink profiles.
Track Organic Conversion Rate
Traffic alone does not tell you whether the redesign worked.
You also need to compare conversions.
Example
Before:
50,000 organic visits
2% conversion rate
= 1,000 conversions
After:
55,000 organic visits
1.2% conversion rate
= 660 conversions
Organic traffic increased by:
10%
But conversions decreased by:
34%
That redesign did not necessarily improve SEO performance from a business perspective.
This is why you should measure traffic and conversion rate together.
Track Revenue Before and After Redesign
For ecommerce and lead-generation websites, revenue is the strongest business-level measurement.
Example
| Metric | Before | After |
| Organic visits | 100,000 | 110,000 |
| Conversion rate | 2.5% | 2.0% |
| Orders/leads | 2,500 | 2,200 |
| Average order value | $80 | $85 |
| Revenue | $200,000 | $187,000 |
Traffic increased by 10%, but revenue fell by 6.5%.
That means the redesign needs further investigation.
The problem may be:
- Weaker landing pages
- Poorer navigation
- Lower conversion rate
- Slower checkout
- Weak calls to action
- Missing product information
- Mobile UX problems
- Search intent mismatch
Post-Launch SEO Monitoring: 24 Hours, 7 Days and 30 Days
Do not launch the website and wait three months before checking SEO.
Use a structured monitoring schedule.
First 24 Hours
Check:
- Website accessibility
- HTTPS
- Robots.txt
- Sitemap
- Redirects
- 404 errors
- 5xx errors
- Canonicals
- Noindex tags
- Analytics tracking
- Search Console verification
- Important page rendering
- Forms
- Navigation
First 7 Days
Compare:
- Organic clicks
- Impressions
- Rankings
- Indexed URLs
- Crawl errors
- Redirects
- 404s
- Organic conversions
- Core Web Vitals
- Top landing pages
First 30 Days
Perform a complete comparison.
| KPI | Pre-Launch | Day 7 | Day 30 |
| Organic clicks | 48K | 44K | 51K |
| Impressions | 1.2M | 1.1M | 1.3M |
| Avg. position | 12.4 | 13.2 | 11.8 |
| Indexed pages | 1,180 | 1,175 | 1,190 |
| 404s | 6 | 21 | 4 |
| Organic conversions | 1,040 | 960 | 1,100 |
This gives you a much clearer picture than checking rankings once.
Before and After Redesign SEO Scorecard
Use this scorecard to determine whether the redesign actually improved SEO.
| Area | Before | After | Target |
| Organic traffic | 100% baseline | 110% | ≥ baseline |
| Organic clicks | 50K | 55K | Increase |
| Impressions | 1M | 1.2M | Increase |
| Ranking keywords | 800 | 950 | Increase |
| Indexed pages | 1,000 | 1,000 | No unexplained loss |
| 404 errors | 5 | 0 | Reduce |
| LCP | 3.4s | 2.3s | ≤ 2.5s |
| INP | 240ms | 180ms | ≤ 200ms |
| CLS | 0.15 | 0.06 | ≤ 0.1 |
| Organic conversion rate | 2.0% | 2.4% | Increase |
| Organic revenue | $80K | $96K | Increase |
The ideal redesign does not simply make the website look newer.
It improves the SEO and business numbers behind the website.
What a Bad Website Redesign Looks Like in Numbers
Consider this example:
| Metric | Before | After | Change |
| Organic clicks | 60,000 | 34,000 | -43.3% |
| Impressions | 1.5M | 950K | -36.7% |
| Ranking keywords | 2,400 | 1,480 | -38.3% |
| Indexed URLs | 1,800 | 1,350 | -25.0% |
| 404 errors | 12 | 186 | +1,450% |
| Organic conversions | 1,500 | 780 | -48.0% |
| Organic revenue | $150K | $78K | -48.0% |
This is not simply a design problem.
The numbers strongly suggest that the redesign introduced SEO or conversion problems that require investigation.
Possible causes include:
- Missing redirects
- Deleted ranking pages
- Content reduction
- Internal-link loss
- Noindex directives
- Incorrect canonicals
- Robots.txt problems
- Broken structured data
- Poor mobile experience
- Slower performance
- Changes in search intent
- Broken analytics
- Navigation changes
What a Successful Redesign Looks Like in Numbers
Now consider a different outcome:
| Metric | Before | After | Change |
| Organic clicks | 60,000 | 69,000 | +15% |
| Impressions | 1.5M | 1.8M | +20% |
| Ranking keywords | 2,400 | 2,850 | +18.8% |
| Indexed URLs | 1,800 | 1,820 | +1.1% |
| 404 errors | 12 | 3 | -75% |
| LCP | 3.4s | 2.1s | -38.2% |
| INP | 260ms | 170ms | -34.6% |
| CLS | 0.17 | 0.05 | -70.6% |
| Organic conversions | 1,500 | 1,800 | +20% |
| Organic revenue | $150K | $198K | +32% |
This redesign improved more than appearance.
It improved:
visibility + technical performance + user experience + conversions + revenue
That is the real goal.
Website Redesign SEO: The 15-Point Final Check
Before approving a redesigned website, confirm these 15 points:
- Existing organic traffic has been recorded.
- Top-performing URLs have been identified.
- Ranking keywords have been exported.
- Backlinks have been mapped.
- Existing content has been preserved or improved.
- URL changes have been mapped.
- Relevant 301 redirects have been tested.
- Internal links have been checked.
- Canonical tags have been validated.
- Robots.txt has been tested.
- XML sitemap has been checked.
- Structured data has been validated.
- Mobile UX has been tested.
- Core Web Vitals have been measured.
- Organic traffic, conversions, and revenue are being monitored after launch.
Final Words
A website redesign should never be judged only by whether the new design looks better.
Measure it against the old website.
Compare:
Organic clicks
Organic impressions
Rankings
Indexed URLs
404 errors
Redirects
Internal links
Core Web Vitals
Organic conversions
Organic revenue
Google’s guidance makes clear that URL changes require careful migration planning, while its Core Web Vitals documentation provides concrete performance targets of 2.5 seconds for LCP, 200 milliseconds for INP, and 0.1 for CLS for a good user experience.
The best redesign is therefore not simply:
Old website → New design
It is:
Old SEO data → SEO-safe redesign → Tested migration → Stable rankings → Better performance → More conversions → More revenue
That is what an SEO-first website redesign should achieve.
This blog is written by SEO experts and SEO content writers
Written by Atiq Ur Rehman
Atiq Ur Rehman is an SEO content writer with 6+ years of experience creating people-first, search-focused content. He focuses on search intent, topical relevance and turning complex SEO topics into clear, practical content.
Reviewed by Afaq Sadiq Khan
Afaq Sadiq Khan is an SEO expert with 10 years of experience in SEO strategy and organic search. He reviews content from a practical SEO perspective, focusing on search visibility, website performance and sustainable organic growth.
Read our Latest Blogs