Launching a new website is exciting.
But if you already have a website that ranks on Google, a redesign can also be one of the easiest ways to accidentally damage your SEO.
I’ve seen businesses launch beautiful new websites only to discover that important URLs disappeared, redirects were never created, ranking content was removed, internal links broke or the entire website was accidentally left set to noindex.
The problem isn’t the redesign itself.
It’s treating SEO as something you’ll worry about after the new website launches.
If your existing website already has search visibility, Google has history with those pages. Some URLs may have backlinks. Some may rank for valuable keywords. Some may generate leads every month.
You don’t want to throw all of that away just because you’re changing the design.
Here are 15 SEO mistakes I recommend avoiding when launching, migrating or redesigning a website.
Quick Answer: What Should You Check Before Launching a New Website?
If you’re replacing an existing website, SEO should be part of the project before launch day.
At minimum, I want to know:
- Which existing URLs receive organic traffic or rank for important keywords
- Which URLs will remain the same
- Which URLs are changing
- Where removed pages should redirect
- Whether important content is being preserved
- Whether the new site is crawlable and indexable
- Whether canonical tags are correct
- Whether internal links point to the right URLs
- Whether the XML sitemap contains the correct pages
- Whether analytics and Google Search Console are working
A website redesign should improve the business without unnecessarily sacrificing the organic visibility it already earned.
1. Changing URLs Without a Good Reason
This is one of the first things I look at during a website redesign.
Suppose an existing service page is:
example.com/bathroom-remodeling/
It ranks well, has backlinks and generates leads.
During the redesign, someone decides the new URL should be:
example.com/services/remodel/bathrooms/
Why?
Sometimes there’s a legitimate reason to change a URL.
But changing URLs simply because the new structure “looks cleaner” can create unnecessary SEO work and risk.
If an existing URL is performing well and still accurately represents the content, my first question is:
Why change it at all?
Preserving strong URLs is often the safest option.
2. Changing URLs Without Creating 301 Redirects
Sometimes URLs genuinely need to change.
That’s when redirect planning becomes critical.
If:
example.com/old-service/
is being replaced by:
example.com/new-service/
I generally want the old URL permanently redirected to the relevant new destination.
Not every old URL should automatically redirect to the homepage.
The destination should make sense.
If you’re consolidating several overlapping articles into one stronger resource, for example, those old articles may appropriately redirect to the surviving page.
This is exactly why I like creating a redirect map before launch.
Don’t wait until rankings disappear and users start landing on 404 pages to figure out where everything should go.
3. Deleting Pages That Already Rank
A redesign often begins with someone saying:
“We want to simplify the website.”
That’s fine.
But don’t start deleting URLs before checking whether they’re doing anything valuable.
An old-looking page might still:
Rank for keywords.
Generate organic traffic.
Earn backlinks.
Generate leads.
Support another important page through internal links.
Establish topical depth.
Before removing content, I want to know what the page is contributing.
Sometimes the right decision is deletion.
Sometimes it’s a rewrite.
Sometimes it’s consolidation.
Sometimes it’s a 301 redirect.
And sometimes the smartest thing you can do is leave the URL alone and improve what’s already there.
4. Leaving the New Website Set to Noindex
This is one of those mistakes that sounds almost too simple to happen.
It happens.
During development, it’s common to prevent a staging website from appearing in search results.
That’s good.
The problem occurs when the new website goes live and those indexing restrictions remain.
In WordPress, for example, site owners should pay close attention to settings that discourage search engines from indexing the site.
Individual pages can also contain noindex directives.
Before launch, I want to verify that pages intended to appear in Google are actually indexable.
A beautiful website won’t generate much organic visibility if you’re accidentally telling search engines not to index it.
5. Mishandling Robots.txt
robots.txt is another area where a small technical mistake can create a large problem.
It can be used to control crawler access to certain areas of a website.
But you need to understand what you’re blocking.
An overly restrictive robots.txt file can prevent Googlebot from crawling resources or sections of the site you actually want it to access.
Also remember:
Robots.txt and noindex are not the same thing.
Robots.txt primarily controls crawling.
Noindex controls whether a page should be included in the search index.
If you’re not sure why a directive exists, don’t casually change it during a redesign.
6. Forgetting to Check Canonical Tags
Canonical tags help search engines understand which version of a page you consider primary when similar or duplicate URLs exist.
During a migration or redesign, canonical tags can sometimes be copied incorrectly from a staging environment, point toward old URLs or reference the wrong version of a page.
That’s why I include canonical checks in launch reviews.
For important pages, I want all of the signals pointing in the same direction.
The page URL says one thing.
The canonical supports it.
The internal links support it.
The sitemap supports it.
That’s a much cleaner setup than sending conflicting signals.
7. Rewriting Every Ranking Page Just Because the Website Is New
A new design does not mean every word of the website needs to change.
This is one of the most overlooked redesign risks.
Suppose a service page already ranks well.
Then during the redesign, someone completely rewrites:
The title.
The H1.
The body content.
The internal links.
The page structure.
The URL.
Now we’ve changed almost everything about a page Google previously understood.
Maybe the new version performs better.
Maybe it doesn’t.
I prefer understanding why the existing page ranks before making major changes.
If the content needs improvement, improve it strategically.
Don’t erase proven SEO assets simply because the website has a new design.
8. Forgetting About Internal Links
Internal links are easy to break during a redesign.
Navigation changes.
Pages move.
Blog articles still link to old URLs.
Buttons point to deleted pages.
Important service pages lose links that previously helped users and search engines discover them.
I don’t want to rely on redirects for every internal link indefinitely.
If an internal link points to an old URL that now redirects somewhere else, I generally prefer updating the link to point directly to the correct destination when practical.
Internal links also help communicate which pages are important.
That’s why a redesign is a good opportunity to evaluate the site’s overall architecture—not just its appearance.
For larger websites, I often use a keyword map to make sure important pages have distinct search purposes and supporting content connects to them logically.
9. Launching With a Messy XML Sitemap
Your XML sitemap should help search engines discover the canonical URLs you actually want indexed.
After a redesign, I check that the sitemap isn’t filled with:
Redirected URLs.
404 pages.
Noindex pages.
Old URLs.
Staging URLs.
Duplicate pages.
Unnecessary archives.
The new sitemap should reflect the website you actually want Google to understand.
And after launch, I want Google Search Console to have access to the correct sitemap.
This connects closely with crawlability and crawl-budget SEO, although most small-business sites don’t need to obsess over crawl budget itself.
The bigger priority is giving search engines a clean, logical website to crawl.
10. Forgetting About Existing Metadata and Headings
Metadata shouldn’t be copied blindly from an old website.
But it shouldn’t be thrown away blindly either.
If an existing page ranks well, I want to know what its current title and H1 are before replacing them.
The new site should have:
A useful SEO title.
A clear H1.
Relevant page copy.
A compelling meta description.
Logical headings.
And each important page should have a clear purpose.
One correction from the original version of this article is worth mentioning:
You do not need to optimize a meta keywords tag for Google.
I focus on the elements that actually help search engines and users understand the page.
11. Treating Mobile Design as an Afterthought
A website shouldn’t be designed beautifully on a desktop and then squeezed into a phone screen at the end of the project.
I want to test the actual mobile experience.
Can you read the text comfortably?
Are buttons easy to tap?
Do menus work?
Are forms usable?
Does anything overlap?
Are important calls to action visible?
Are huge images slowing the page down?
Does the hero section make sense on a smaller screen?
Mobile usability is important because your customers are real people trying to use the website—not because you need to chase some simplistic “mobile SEO score.”
A technically responsive website can still provide a terrible mobile experience.
12. Ignoring Website Performance
A redesign sometimes adds:
Large hero images.
Video backgrounds.
Animations.
Multiple font files.
Third-party scripts.
Tracking tools.
Chat widgets.
Popups.
Fancy visual effects.
Individually, these may seem harmless.
Together, they can turn a fast website into a slow one.
I don’t recommend destroying a good design simply to chase a perfect performance score.
But I do want the website to load reasonably quickly and function smoothly.
Before launch, I look for obvious performance problems such as unnecessarily large images, excessive scripts, layout shifts and elements that delay the useful content visitors came to see.
13. Forgetting Analytics and Conversion Tracking
Imagine launching a new website and seeing traffic increase.
Great.
Did leads increase?
We need tracking to answer that.
During a redesign, analytics implementations can disappear or change.
Forms may be replaced.
Thank-you pages may change.
Phone-number tracking may break.
Google Ads conversions may stop recording.
GA4 events may no longer fire correctly.
That’s why measurement needs to be part of the launch process.
At minimum, I want to know whether we’re accurately tracking the actions that matter to the business.
For a service company, that might include:
Contact-form submissions.
Phone calls.
Consultation requests.
Appointments.
Purchases.
Qualified leads.
Traffic without conversion context tells only part of the story.
14. Forgetting Google Search Console
Google Search Console is one of the first places I monitor after a website launch or migration.
It can help us evaluate:
Indexing.
Sitemaps.
Search queries.
Landing pages.
Clicks.
Impressions.
Average positions.
Crawl-related information.
That doesn’t mean you should panic every time a chart moves after launch.
Search data naturally fluctuates.
But if important pages suddenly disappear from search, previously strong queries collapse or indexing problems appear, I want to know.
Search Console gives us visibility into what Google is seeing.
15. Launching the Website and Walking Away
Launch day isn’t the end of a website migration.
It’s the beginning of the monitoring period.
After a significant redesign, I want to keep an eye on:
Important rankings.
Organic landing pages.
Clicks and impressions.
Conversions.
Indexing.
404 errors.
Redirects.
Sitemaps.
Technical errors.
Google Business Profile links where relevant.
Unexpected traffic changes.
Some issues don’t become obvious until Google begins recrawling the new website.
Catching those problems early is much easier than discovering months later that a valuable page disappeared during the migration.
The Biggest Website Redesign Mistake I See
One of the biggest mistakes I see is treating a website redesign as if SEO starts over after the new website launches.
It shouldn’t.
If an existing website already ranks, its URLs, content, internal links and backlinks have history.
Some of those pages may have taken years to build visibility.
A redesign can dramatically improve the way a website looks while accidentally damaging the search visibility the business already earned.
That’s why I want SEO involved before the new website goes live—not after rankings disappear.
A designer may understandably focus on:
Branding.
Layout.
Typography.
Photography.
Navigation.
Conversions.
Those things matter.
But someone also needs to ask:
What currently ranks?
Which URLs have backlinks?
Which pages generate organic traffic?
What are we removing?
What are we changing?
Where will old URLs redirect?
What SEO elements need to survive the migration?
Those questions should be answered before launch.
Should You Keep Your Existing URLs During a Website Redesign?
When practical, yes.
I don’t change a strong URL simply because I’m redesigning a website.
If the URL still accurately describes the page and isn’t creating a structural problem, keeping it can reduce unnecessary migration complexity.
There are situations where URL changes make sense.
Perhaps the old architecture is genuinely terrible.
Maybe two pages are being consolidated.
Maybe a service changed.
Maybe years of website growth created a confusing structure that needs cleanup.
That’s fine.
But I want the decision to be intentional.
Don’t change URLs just because you can.
Should You Redirect Every Old Page?
No.
Redirects should make sense.
If an old page has a clear new equivalent, a permanent redirect may be appropriate.
If several old pages cover essentially the same topic and you’ve consolidated them into one stronger resource, redirecting them to that resource can make sense.
But if an old page has absolutely no relevant replacement, redirecting it randomly to the homepage isn’t necessarily useful.
Sometimes an intentionally removed page should simply remain gone.
The goal is not to eliminate every 404 at any cost.
The goal is to create a logical experience for users and search engines.
What If the Old Website Has Hundreds of Blog Posts?
This is where I recommend auditing before migrating everything automatically.
Older websites can accumulate enormous amounts of content.
Some articles may still perform well.
Some may need updates.
Some may overlap newer content.
Some may receive no meaningful organic visibility.
Some may compete with stronger pages.
Some may no longer reflect the business.
I wouldn’t automatically delete all of them.
I also wouldn’t automatically migrate all of them untouched.
This is a good opportunity to ask:
Does this page still deserve to exist?
I’ve been doing this kind of cleanup extensively on established websites because publishing more and more pages isn’t always the answer.
Sometimes the stronger SEO strategy is to consolidate.
I explain that idea further in why publishing more blog posts doesn’t necessarily improve SEO.
What About Your Google Business Profile?
If your website URL changes, make sure the website link associated with your Google Business Profile is still correct.
I also want the business information on the new site to accurately represent the real business.
That includes basics such as:
Business name.
Contact information.
Location or service-area information where appropriate.
Hours.
Services.
Don’t turn this into a frantic hunt to make every citation on the internet character-for-character identical.
Focus first on ensuring that your primary business information is accurate and that customers and search engines aren’t being sent to outdated pages.
For local businesses, the website and Google Business Profile should support a consistent understanding of what the company does and where it operates.
You can learn more about the broader strategy in my Local SEO guide for San Diego businesses.
Does Schema Need to Be Added Before Launch?
Structured data can be useful when it accurately describes content on the page and follows the requirements for the particular markup being used.
But I wouldn’t delay a website launch because someone told you schema is a magical SEO requirement.
It isn’t.
Structured data doesn’t replace:
Useful content.
Clear business information.
Good site architecture.
Internal linking.
Crawlability.
Relevant pages.
Authority.
A technically sound website.
Use structured data where it makes sense.
Don’t treat it as a shortcut to rankings.
What If the New Website Looks Better but Rankings Drop?
Don’t immediately start changing everything again.
First investigate.
Compare the old and new versions.
Check:
Did URLs change?
Were redirects implemented correctly?
Was important content removed?
Did titles or H1s change?
Did internal links disappear?
Are pages still indexable?
Did canonical tags change?
Is Google crawling the new URLs?
Did the sitemap change?
Did the mobile experience become worse?
Did site performance change significantly?
Are tracking systems still working?
The cause may be obvious once you compare what actually changed.
This is another reason documenting the old website before migration is so useful.
Without a baseline, troubleshooting becomes much harder.
How Long Should You Monitor SEO After a Website Launch?
I wouldn’t choose an arbitrary number of days and declare the migration successful.
The amount of monitoring depends on the size of the website, how much changed and how quickly search engines process those changes.
I pay particular attention during the period immediately following launch, but I continue watching organic performance as Google recrawls and reassesses the site.
The bigger the migration, the more carefully I want to monitor it.
If you’re wondering more generally how quickly SEO changes can produce results, I explain that separately in my guide to how long SEO takes.
Do You Actually Need a New Website?
This is worth asking before beginning a redesign.
Sometimes a business comes to me thinking:
“My SEO isn’t working, so I probably need a new website.”
Not necessarily.
The existing website might need:
Better service pages.
Improved internal links.
Technical cleanup.
Stronger calls to action.
Better mobile formatting.
Content consolidation.
Improved page speed.
A clearer keyword strategy.
A redesign is a major project.
If the existing site can be improved without replacing it, that may be the better option.
That’s why I rarely recommend a completely new website just for SEO.
A new website should solve an actual problem—not simply create a prettier version of the same one.
My Website Launch SEO Checklist
Before launching a redesigned website, these are the questions I want answered:
- Have we documented the important existing URLs?
- Do we know which pages currently receive organic traffic?
- Do we know which pages rank for valuable searches?
- Are important URLs staying the same where possible?
- Is there a redirect map for URLs that are changing?
- Are redirects going directly to relevant destinations?
- Are important titles, H1s and content being preserved or intentionally improved?
- Are internal links updated?
- Is the site crawlable?
- Are pages intended for Google indexable?
- Are robots.txt directives correct?
- Are canonical tags correct?
- Is the XML sitemap clean?
- Are staging URLs excluded from search?
- Is the mobile experience working properly?
- Is site performance acceptable?
- Are forms working?
- Is analytics tracking working?
- Are conversions being recorded?
- Is Google Search Console set up correctly?
- Is the Google Business Profile pointing to the correct website?
- Is there a plan to monitor organic performance after launch?
You don’t need a 200-page migration document for every five-page business website.
But you do need to know what you’re changing.
Frequently Asked Questions
Can Launching a New Website Hurt SEO?
Yes, particularly if existing URLs, content, internal links or technical signals change significantly.
A redesign doesn’t automatically hurt SEO, but a poorly planned migration can cause a business to lose valuable organic visibility.
Should I Change My URLs When Redesigning My Website?
Not unless there’s a good reason.
If an existing URL is relevant, clean and performing well, I generally prefer preserving it.
If URLs must change, create appropriate 301 redirects from the old URLs to the most relevant new destinations.
What Is the Biggest SEO Mistake During a Website Redesign?
One of the biggest is launching without understanding what the existing website already ranks for.
That can lead to valuable URLs and content being removed without anyone realizing their importance until traffic or leads decline.
What Happens If I Forget to Remove Noindex?
Pages containing a noindex directive generally aren’t intended to remain in Google’s search index.
If important production pages accidentally remain noindexed after launch, investigate and correct the issue as quickly as possible.
Should I Redirect Every 404 to My Homepage?
No.
If an old URL has a relevant replacement, redirecting it may make sense.
If no relevant replacement exists, forcing the URL to the homepage isn’t automatically better.
Should I Submit My New Sitemap to Google?
Make sure Google Search Console has the correct XML sitemap for the live website and that the sitemap contains the canonical URLs you actually want search engines to discover.
How Soon Will Google Crawl My New Website?
There isn’t a guaranteed timetable.
Discovery and crawling can vary depending on the website and URL. Internal links, sitemaps and other discovery signals can help Google find important pages, but submitting a URL doesn’t guarantee immediate crawling, indexing or ranking.
Will a New Website Automatically Rank Better?
No.
A newer or more attractive website doesn’t automatically deserve better rankings.
The redesign needs to preserve or improve the things that matter for search visibility rather than focusing only on appearance.
Should SEO Be Done Before or After a Website Redesign?
Ideally, SEO should be considered before, during and after the redesign.
Before launch, protect existing assets and plan the migration.
During launch, verify technical implementation.
After launch, monitor indexing, rankings, traffic and conversions.
Protect the SEO You’ve Already Built
A website redesign should move your business forward.
It shouldn’t accidentally erase years of organic progress.
That’s why I don’t look at a website migration as simply:
Old website → new website.
I look at 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’s working.
Fix what’s broken.
Redirect what moves.
Remove what genuinely no longer belongs.
Improve what can perform better.
Then monitor the results.
That’s a much safer way to launch a new website.
Planning a Website Redesign? Don’t Wait Until After Launch to Think About SEO
I’m Jen Ruhman, founder of Jen Ruhman SEO.
As an SEO expert in San Diego, I help businesses protect and improve their organic visibility during website changes, redesigns and SEO cleanups.
If you’re planning to launch a new website, I’d rather look at the SEO before everything changes than troubleshoot lost rankings afterward.
Call or text: (619) 719-1315
Thanks for reading,
Jen Ruhman
Founder, Jen Ruhman SEO