Launching a new website is exciting.

But if your existing website already ranks in Google, a redesign can also be one of the easiest ways to accidentally damage your SEO.

I have seen businesses launch beautiful new websites only to discover that:

  • Ranking URLs disappeared
  • Redirects were never created
  • Important content was removed
  • Internal links broke
  • Canonical tags pointed to the wrong URLs
  • Analytics stopped tracking
  • The new website was accidentally left set to noindex

The problem is not the redesign itself.

The problem is treating SEO as something you will worry about after the new website goes live.

If your current website already has organic visibility, Google has history with those pages.

Some URLs may have backlinks.

Some may rank for valuable searches.

Some may generate leads every month.

A redesign should improve the business without unnecessarily throwing away the SEO value you already earned.

Quick Answer: What Should You Check Before Launching a New Website?

Before replacing an existing website, I want to know:

  • Which current URLs receive organic traffic
  • Which pages rank for important searches
  • Which URLs have backlinks
  • Which URLs will remain the same
  • Which URLs are changing
  • Where removed pages should redirect
  • Whether valuable content is being preserved
  • Whether the new site is crawlable
  • Whether important pages are indexable
  • Whether canonical tags are correct
  • Whether internal links point to the right URLs
  • Whether the XML sitemap is clean
  • Whether Google Analytics is working
  • Whether conversions are still being tracked
  • Whether Google Search Console is configured correctly

SEO should be part of the redesign before, during, and after launch.

Here are the 15 mistakes I recommend avoiding.

1. Changing Strong URLs Without a Good Reason

This is one of the first things I look at during a redesign.

Suppose an existing service page is:

example.com/bathroom-remodeling/

It ranks well.

It has backlinks.

It generates leads.

During the redesign, someone decides the new URL should become:

example.com/services/remodel/bathrooms/

My first question is:

Why?

Sometimes there is a legitimate reason to change the URL.

Maybe the old site structure is genuinely confusing.

Maybe several pages are being consolidated.

Maybe the business has changed its services.

But changing a strong URL simply because the new structure looks cleaner can create unnecessary SEO risk.

If an existing URL is performing well and still accurately represents the content, preserving it is often the safest choice.

2. Changing URLs Without Creating 301 Redirects

Sometimes URL changes are necessary.

That is when redirect planning becomes critical.

If:

example.com/old-service/

is being replaced by:

example.com/new-service/

the old page should generally redirect to the relevant new destination.

The important word is:

relevant.

Do not automatically send every retired URL to the homepage.

If several old articles are being merged into one stronger guide, redirecting them to the surviving article can make sense.

If an old service page has a direct replacement, redirect it there.

This is why I like building a redirect map before launch.

Do not wait until users start encountering 404s and rankings disappear before deciding where old URLs should go.

3. Deleting Pages Without Checking Their SEO Value

A redesign often begins with:

“We want to simplify the website.”

That can be a great idea.

But do not begin deleting pages without knowing what they currently contribute.

An older page may still:

  • Rank for keywords
  • Generate organic traffic
  • Earn backlinks
  • Generate leads
  • Support an important service page
  • Strengthen topical depth
  • Receive valuable internal links

Before deleting a URL, investigate it.

Sometimes the correct decision is:

Update it.

Sometimes:

Merge it.

Sometimes:

Redirect it.

Sometimes:

Delete it.

And sometimes the best decision is:

Leave it alone.

This is one reason I review existing content carefully during an SEO audit.

4. Accidentally Leaving the Live Website Set to Noindex

This mistake sounds too simple to happen.

It happens.

During development, it is normal to prevent a staging website from being indexed.

The problem occurs when the new website launches and those restrictions remain.

In WordPress, developers may temporarily discourage search engines from indexing the site.

Individual pages may also contain noindex directives.

Before launch, verify that pages intended to appear in search results are actually indexable.

A beautiful new website will not generate much organic visibility if you are telling search engines not to index it.

5. Mishandling Robots.txt

Your robots.txt file can control crawler access to parts of a website.

That makes it useful.

It also makes mistakes potentially serious.

An overly restrictive rule could prevent Googlebot from crawling content or resources you actually want accessible.

Also remember:

robots.txt and noindex are not the same thing.

Robots.txt primarily controls crawling.

Noindex controls whether a crawlable page should generally appear in the search index.

Do not casually copy staging robots rules onto the live website.

And do not change technical directives simply because someone says they are “better for SEO.”

Understand the purpose first.

6. Forgetting to Check Canonical Tags

Canonical tags help search engines understand which version of a page you consider the preferred version when duplicates or variations exist.

During a redesign or migration, canonical tags can accidentally:

  • Point to staging URLs
  • Reference the old domain
  • Point to outdated URLs
  • Point to unrelated pages
  • Conflict with the sitemap

For an important page, I want the signals aligned.

The URL says one thing.

The canonical supports it.

The internal links support it.

The XML sitemap supports it.

That creates a cleaner technical setup.

7. Completely Rewriting Every Ranking Page

A new website design does not mean every word on the old website needs to disappear.

Suppose a service page already ranks well.

During the redesign, someone changes:

  • The URL
  • SEO title
  • H1
  • Body content
  • Internal links
  • Page layout
  • Supporting sections

At that point, we have changed almost everything about a page Google previously understood.

Maybe the new version performs better.

Maybe it does not.

I prefer first understanding why the existing page works.

If it needs improvement, improve it intentionally.

Do not erase valuable SEO assets simply because the visual design is changing.

This is closely related to why I often recommend improving an existing website instead of automatically rebuilding it.

8. Breaking Internal Links

Internal links are extremely easy to damage during a redesign.

Pages move.

Navigation changes.

Buttons point to retired URLs.

Blog posts continue linking to old pages.

Important service pages lose links they previously received from other areas of the site.

Redirects can catch some of those mistakes.

But I do not want to rely on redirects forever when I control the internal link.

If a page now lives at a new URL, update important internal links so they point directly to the final destination.

Internal linking also helps communicate which pages are important and how topics relate across the website.

I explain that strategy in more depth in my guide to internal linking for SEO.

9. Launching With a Messy XML Sitemap

Your XML sitemap should reflect the website you actually want Google to understand.

After a migration, I check for:

  • Redirected URLs
  • 404 pages
  • Noindex pages
  • Old URLs
  • Staging URLs
  • Duplicate pages
  • Noncanonical URLs
  • Unnecessary archives

The sitemap should primarily contain clean, canonical, indexable URLs.

For most small business sites, you do not need to obsess over crawl budget.

The bigger priority is making your intended website architecture clear.

If your site is large or technically complex, I explain the difference in my guide to crawl budget in SEO.

And if the site is generating thousands of unnecessary URLs through filters, archives, calendars, or parameters, see my guide to SEO crawl traps and URL bloat.

10. Throwing Away Strong Titles, Headings, and Content

Metadata and headings should not be copied blindly from the old website.

But they should not be discarded blindly either.

Before changing a page that already ranks, document:

  • Current SEO title
  • H1
  • Important H2s
  • Main page copy
  • Search queries
  • Organic traffic
  • Internal links

Then decide what needs improvement.

The new page should have:

  • A useful SEO title
  • One clear primary topic
  • A descriptive H1
  • Logical headings
  • Relevant content
  • A compelling meta description
  • A strong call to action

And no—you do not need to optimize a meta keywords tag for Google.

Focus on the elements that actually help people and search engines understand the page.

11. Treating Mobile Design as an Afterthought

A website should not be designed beautifully on a desktop and then squeezed into a phone screen right before launch.

Test the actual mobile experience.

Can someone:

  • Read the text comfortably?
  • Tap buttons easily?
  • Use the navigation?
  • Fill out forms?
  • Make a phone call?
  • See important calls to action?
  • View images properly?
  • Understand the hero section?
  • Scroll without strange layout problems?

A technically responsive site can still provide a terrible mobile experience.

Remember that your customers are real people using the website—not SEO scores.

12. Making the New Website Much Slower

Website redesigns often add:

  • Massive hero images
  • Video backgrounds
  • Animations
  • Multiple font files
  • Tracking scripts
  • Chat widgets
  • Popups
  • Third-party integrations
  • Fancy visual effects

Any one of those may be fine.

The problem occurs when everything gets added at once.

Suddenly the beautiful new website is considerably slower than the old one.

Before launch, I look for obvious performance issues involving:

  • Oversized images
  • Excessive scripts
  • Layout shifts
  • Heavy plugins
  • Slow third-party tools
  • Elements delaying important content

I do not recommend destroying a good design just to chase a perfect performance score.

I want the site to feel fast, function reliably, and provide a good experience.

13. Forgetting Analytics and Conversion Tracking

Imagine launching your new website and seeing organic traffic increase.

Great.

Did leads increase?

Without tracking, you may not know.

During a redesign:

  • Forms change
  • Thank-you pages disappear
  • GA4 events stop firing
  • Call tracking breaks
  • Google Ads conversions stop recording
  • Booking systems change

Measurement should be part of the migration.

For a service business, I may want to track:

  • Contact forms
  • Phone calls
  • Consultation requests
  • Appointments
  • Purchases
  • Qualified leads

Traffic tells only part of the story.

A website exists to support business outcomes.

14. Forgetting Google Search Console

Google Search Console is one of the first tools I monitor following a major launch.

I watch:

  • Important queries
  • Landing pages
  • Clicks
  • Impressions
  • Average positions
  • Indexing
  • Sitemaps
  • Crawl-related issues

That does not mean I panic every time a chart moves.

Search visibility naturally fluctuates.

But if a major service page disappears, previously strong queries collapse, or indexing problems appear immediately after migration, I want to know.

Search Console helps identify those changes early.

15. Launching the Website and Walking Away

Launch day is not the end of a migration.

It is the beginning of the monitoring period.

After a redesign, I monitor:

  • Important rankings
  • Organic landing pages
  • Clicks
  • Impressions
  • Leads
  • Conversions
  • Indexing
  • Redirects
  • 404s
  • XML sitemaps
  • Technical errors
  • Google Business Profile links
  • Unexpected traffic changes

Some migration problems are not obvious until Google begins recrawling the new site.

Catching them early is much easier than discovering three months later that an important URL disappeared.

The Biggest Website Redesign Mistake I See

The biggest mistake is treating SEO like it starts over after the redesign.

It should not.

If your existing website already ranks, it has history.

Its URLs have history.

Its backlinks have history.

Its internal linking has history.

Some pages may have taken years to build visibility.

A redesigned website can look dramatically better while accidentally destroying much of that value.

That is why I want SEO involved before launch.

A designer may naturally focus on:

  • Branding
  • Layout
  • Photography
  • Typography
  • Navigation
  • Conversion design

All of those matter.

But someone also needs to ask:

What currently ranks?

Which URLs earn organic traffic?

Which pages have backlinks?

What are we deleting?

What are we changing?

Where will old URLs redirect?

What SEO assets need to survive?

Those questions should not wait until launch day.

Should You Keep Existing URLs During a Redesign?

When practical, yes.

I do not change a strong URL merely because the website is being redesigned.

If the URL still accurately describes the page and does not create a structural problem, preserving it reduces unnecessary migration risk.

There are situations where URL changes make sense.

Maybe:

  • The old site architecture is genuinely bad
  • Two pages are being consolidated
  • A service has changed
  • The old website accumulated years of confusing structure

That is fine.

The important thing is making the decision intentionally.

Do not change URLs simply because you can.

Should Every Old Page Be Redirected?

No.

Redirects should make logical sense.

If an old URL has a relevant new replacement:

301 redirect it.

If several overlapping pages are combined into one stronger resource:

Redirect them to the surviving page.

But if an old page has no meaningful replacement, sending it randomly to the homepage is not automatically helpful.

Sometimes a retired page should simply remain gone.

The goal is not:

Eliminate every 404 at any cost.

The goal is:

Create a logical experience for users and search engines.

What If the Website Has Hundreds of Old Blog Posts?

Audit them before automatically migrating everything.

Older sites often accumulate enormous content libraries.

Some articles may:

  • Rank strongly
  • Need updating
  • Overlap newer pages
  • Receive no meaningful traffic
  • Compete with stronger content
  • No longer reflect the business

Do not automatically delete everything.

But do not automatically migrate everything untouched either.

Ask:

Does this page still deserve to exist?

Sometimes a redesign is the perfect opportunity to clean up years of content accumulation.

That is also why I no longer believe publishing more blog posts automatically improves SEO.

Sometimes consolidation creates a stronger website.

What About Google Business Profile?

If your website address changes, make sure your Google Business Profile still points to the correct live website.

Also verify that the new website accurately communicates:

  • Business name
  • Contact information
  • Location
  • Service area
  • Hours
  • Services

For local businesses, the website and Google Business Profile should reinforce the same basic understanding of the company.

Do not send potential customers—or Google—to outdated pages.

Does Schema Need to Be Added Before Launch?

Structured data can be useful.

But I would not delay an entire website launch because someone claims schema is a magical SEO requirement.

It is not.

Structured data does not replace:

  • Useful content
  • Clear page purpose
  • Internal linking
  • Crawlability
  • Strong service pages
  • Site architecture
  • Authority
  • Accurate business information

Use appropriate structured data where it genuinely applies.

Do not treat it as a shortcut to rankings.

What If Rankings Drop After the Redesign?

Do not immediately start changing everything again.

Investigate.

Compare the old site with the new one.

Check:

  • Did URLs change?
  • Are redirects correct?
  • Was important content removed?
  • Did titles change?
  • Did H1s change?
  • Did internal links disappear?
  • Are pages still indexable?
  • Did canonical tags change?
  • Is Google crawling the new URLs?
  • Is the sitemap correct?
  • Did mobile usability get worse?
  • Did performance decline?
  • Is tracking still working?

The answer may become obvious once you identify what changed.

This is why documenting the website before migration is so valuable.

Without a baseline, diagnosing a ranking drop becomes much harder.

How Long Should You Monitor SEO After Launch?

There is no magic number of days after which I declare a migration completely successful.

The answer depends on:

  • Website size
  • Number of changed URLs
  • Scope of the redesign
  • Crawl frequency
  • How quickly search engines process the changes

I pay especially close attention immediately after launch, but I continue monitoring organic performance as Google recrawls and reassesses the website.

The larger the migration, the more careful I am.

If you want a broader understanding of SEO timelines, read my guide to how long SEO takes to work.

Do You Actually Need a New Website?

Before beginning a redesign, ask this question.

Sometimes a business tells me:

“My SEO isn’t working, so I think I need a new website.”

Not necessarily.

The existing website may simply need:

  • Better service pages
  • Stronger internal linking
  • Technical cleanup
  • Updated content
  • Better mobile formatting
  • Content consolidation
  • Improved page speed
  • Better conversion paths
  • Clearer keyword targeting

A redesign is a major project.

If the existing website can be improved without replacing everything, that may be the smarter option.

That is why I wrote a separate guide answering whether you actually need a new website for SEO.

A new website should solve a real problem.

It should not simply create a prettier version of the same problems.

My Website Launch SEO Checklist

Before launching a redesigned website, I want to answer yes to these questions:

Existing SEO Assets

  • Have important existing URLs been documented?
  • Do we know which pages receive organic traffic?
  • Do we know which pages rank for valuable searches?
  • Do we know which URLs have important backlinks?

URLs and Redirects

  • Are strong URLs remaining the same where possible?
  • Is there a redirect map for changing URLs?
  • Do redirects point directly to relevant final destinations?
  • Have redirect chains been avoided?

Content

  • Are valuable titles, H1s, and content being preserved or intentionally improved?
  • Have overlapping pages been consolidated intentionally?
  • Have important internal links been updated?

Technical SEO

  • Is the website crawlable?
  • Are important pages indexable?
  • Is robots.txt configured correctly?
  • Are canonical tags correct?
  • Is the XML sitemap clean?
  • Are staging URLs excluded from search?

User Experience

  • Does the mobile experience work properly?
  • Is performance acceptable?
  • Are forms working?
  • Are important calls to action visible?

Measurement

  • Is GA4 working?
  • Are conversions being recorded?
  • Is Google Search Console configured?
  • Is the correct XML sitemap submitted?
  • Does Google Business Profile point to the correct website?

After Launch

  • Is there a plan to monitor rankings?
  • Traffic?
  • Indexing?
  • Leads?
  • Redirects?
  • 404s?
  • Technical problems?

You do not need a 200-page migration document for every five-page business website.

But you should know what you are changing and what needs to be protected.

Frequently Asked Questions About SEO and Website Redesigns

Can launching a new website hurt SEO?

Yes. A poorly planned redesign can cause rankings and traffic to decline if important URLs, content, internal links, redirects, or technical signals are changed incorrectly.

The redesign itself is not automatically harmful.

The migration is what needs to be managed carefully.

Should I change URLs during a website redesign?

Not unless there is a good reason.

If an existing URL is clean, relevant, and performing well, I generally prefer keeping it.

If it must change, create an appropriate 301 redirect.

What is the biggest SEO mistake during a website redesign?

One of the biggest mistakes is launching without first understanding what the old website already ranks for.

That can result in valuable pages being deleted or replaced without anyone realizing their importance.

What happens if my new website is accidentally noindexed?

Important pages may be prevented from appearing in Google’s search index. Correct the issue as soon as possible and continue monitoring indexing in Google Search Console.

Should every 404 redirect to the homepage?

No.

Only redirect a retired URL when there is a relevant replacement.

A proper 404 or 410 can be appropriate when a page has genuinely been removed and no replacement exists.

Should I submit the new XML sitemap to Google?

Make sure Google Search Console has access to the correct XML sitemap for the live site and that the sitemap contains the canonical, indexable URLs you want search engines to discover.

How soon will Google crawl my redesigned website?

There is no guaranteed timetable.

Internal links, XML sitemaps, and normal discovery signals can help Google find new or changed URLs, but crawling and indexing happen on Google’s schedule.

Will a new website automatically rank better?

No.

A newer or more attractive website does not automatically deserve stronger rankings.

The redesign needs to preserve or improve the things that already contribute to organic visibility.

Should SEO happen before or after the redesign?

Before, during, and after.

Before launch:

Protect existing SEO assets and plan the migration.

During launch:

Verify technical implementation.

After launch:

Monitor indexing, rankings, traffic, leads, and conversions.

Protect the SEO You’ve Already Built

A website redesign should move your business forward.

It should not accidentally erase years of organic progress.

That is why I do not think about a migration as simply:

Old website → new website

I think about it as:

What does the old website already have that we need to protect—and what can we improve on the new one?

Preserve what works.

Fix what is broken.

Redirect what moves.

Remove what genuinely no longer belongs.

Improve what can perform better.

Then monitor the results.

That is a much safer way to launch a new website.

Planning a Website Redesign?

I’m Jen Ruhman, founder of Jen Ruhman SEO.

As an SEO expert in San Diego, I help businesses protect and improve organic visibility during website redesigns, migrations, technical cleanups, and content consolidations.

If you are planning a website change, I would much rather review the SEO before everything moves than troubleshoot lost rankings afterward.

If you’re looking for an experienced SEO consultant in San Diego, you can learn more about working with my San Diego SEO company.

Or start with my SEO audit guide to understand what I look for before making major website changes.

GET YOUR FREE SEO ANALYSIS →

Or call/text me at (619) 719-1315.

— Jen Ruhman
SEO Expert & Founder of Jen Ruhman SEO