Skip to main content

Boulder Decisions

Website Migrations Can Impact SEO, Even When URLs Stay the Same

Table of Contents

Many businesses believe that if every URL stays the same during a migration, their SEO is safe. No redirects to map, no broken links, no problem. Unfortunately, that is one of the most common and costly assumptions in SEO.

URLs are only one part of what search engines evaluate. When you move to a new CMS, redesign your templates, switch hosting or rebuild your front end, the HTML, content, links and technical signals behind those URLs can all change. As Search Engine Land recently highlighted, website migrations can hurt SEO even when URLs do not change.

Google has said this for years. As John Mueller put it, reported by Search Engine Roundtable: “If you change design, you generally change the content.” And on site revamps, he added: “You can’t change everything and expect folks to act like nothing changed.”

Here is why same-URL migrations still carry risk, the hidden issues to watch for, and how to protect your rankings before, during and after launch.

What Counts as a Website Migration?

A migration is any major change to how your website is built, hosted or delivered. Many of them keep the same URLs:

  • CMS or platform migration: for example, moving from WordPress to Webflow, Shopify or a headless CMS.
  • Website redesign: new templates, layouts and navigation on the same platform.
  • Front-end rebuild: switching to a JavaScript framework such as React or Next.js.
  • Hosting or server change: moving to a new host, server or CDN.
  • Protocol change: moving from HTTP to HTTPS.

Ahrefs’ Patrick Stox notes in Ahrefs’ migration guide that migrations keeping the same URLs are generally simpler than those that change them. Simpler, however, does not mean risk-free.

what stays the same and what changes during a same-url website migration

Why Google Sees It as a “New” Website

Search engines do not rank URLs in isolation. They rank pages based on their content, structure, links and technical signals. When a migration changes those signals, Google has to re-crawl, re-render and re-evaluate your pages, even if the addresses are identical.

When asked whether traffic loss can be prevented during a revamp, Mueller’s answer was simply “No.” He explained: “It means if you make a new website (revamping the old), you will have a new website.” Google’s Gary Illyes has made a similar point: “if you redesign your site, your rankings may go nuts.”

8 Hidden Ways Migrations Hurt SEO When URLs Stay the Same

1. Content and on-page elements change

New templates often remove or rewrite content without anyone noticing. According to Search Engine Journal, common causes of post-migration drops include missing title tags and meta descriptions and removed body copy that weakens relevance. Headings, FAQ sections, image alt text and supporting text blocks can also disappear in a redesign.

2. Canonical tags break or point to the wrong place

On a traditional CMS, a plugin or theme may generate canonical tags reliably. After moving to new code, canonicals can go missing, become malformed or turn inconsistent, as developer Ali Farhat explains in his analysis. Search Engine Journal also warns about canonicals still pointing to old URLs or staging domains after launch.

3. JavaScript rendering hides content and links

Moving to a JavaScript framework or headless CMS can shift essential text and links out of the initial HTML and into client-side rendering. Ahrefs notes that JavaScript-based systems may not load all content into the DOM, so search engines may miss some of it. If important content only appears after scripts run, crawlers may see a much thinner page.

raw html vs rendered page showing javascript rendering issues

4. Internal links and navigation change

Ahrefs points out that breadcrumbs, related posts, footer links and main navigation often change during a migration. Fewer internal links to a page can weaken how important it appears. Links that were plain HTML anchors may also start depending on JavaScript, making them harder for crawlers to follow.

5. Structured data, hreflang and meta robots are lost

Schema markup, hreflang tags and meta robots directives are easy to lose when templates change. One of the most damaging mistakes is launching with leftover noindex tags from staging, which Search Engine Journal lists as a common cause of migration traffic drops. Ahrefs recommends checking meta robots carefully for accidental noindex tags.

6. Wrong status codes create soft 404s

A new platform may show a friendly “page not found” message while still returning a 200 OK status code. Search engines treat that differently from a proper 404. The reverse can also happen, where working pages return errors due to server or routing problems.

7. Robots.txt and sitemaps drift

Robots.txt rules and XML sitemaps are often rebuilt during a migration. A staging block left in robots.txt can stop crawling entirely, and a new sitemap may leave out URLs you still want indexed. Search Engine Journal recommends confirming robots.txt and noindex settings before go-live and submitting a fresh XML sitemap in Search Console right after launch.

8. Page speed and hosting changes

A new design, CMS or host can make pages slower. Search Engine Journal lists page speed regressions as a common cause of migration hangovers, and Ahrefs notes that speed can differ after a move. Hosting changes also bring risks such as missing server-level redirects and expired HTTPS certificates. For a broader view of preserving rankings, see our guide on planning a website redesign without losing SEO equity.

Planning a Website Migration?

Get a pre-launch SEO audit and protect the rankings and traffic you have worked hard to earn.

Get My Migration SEO Audit →

Normal Dip or Migration Hangover?

Some short-term ranking movement after a migration is normal. The problem is when it does not recover. Search Engine Journal describes a “migration hangover” as a prolonged, significant drop in organic traffic after a migration, which in severe cases can last 12 to 18 months.

SignalNormal volatilityMigration hangover
Traffic dropAround 10-20%Above 30-50%
Recovery timeStabilizes in 2 to 6 weeksNo stabilization after 4+ weeks
Search Console errorsNo ongoing errorsNew crawl errors or 404s
Indexed pagesStableFalling indexed page count

Source: Search Engine Journal. The author notes that thresholds vary by site and experience.

If your traffic falls sharply after launch, our guide to website traffic drop causes and fixes can help you narrow down the cause.

normal post-migration traffic dip vs migration hangover

Your Same-URL Migration SEO Checklist

Before launch

  1. Involve your SEO team before the project starts, not after.
  2. Crawl the current site and save a full baseline of URLs, titles, meta descriptions, headings, canonicals, schema and internal links.
  3. Back up all content, media, databases and custom code, as Semrush recommends.
  4. Benchmark page speed and Core Web Vitals on key templates.
  5. Crawl the staging site and compare it against your baseline.
  6. Check rendered HTML on key templates to confirm content and links are visible without relying on JavaScript.
  7. Audit structured data, hreflang, robots.txt and meta robots.
  8. Restrict staging access so it cannot be indexed.

Launch day

  • Remove staging noindex tags and robots.txt blocks.
  • Confirm canonicals point to the correct live URLs.
  • Check that status codes are correct (200 for live pages, 404 or 410 for removed pages).
  • Confirm the HTTPS certificate is valid and redirects are in place at the server level.
  • Submit a fresh XML sitemap in Google Search Console.

After launch

  • Crawl the live site and compare it with your pre-migration crawl, as Ahrefs recommends, to catch changes to canonicals, hreflang, schema and meta robots.
  • Run a full site audit (Semrush Site Audit or a similar tool) and fix errors and warnings.
  • Monitor indexing, crawl errors and performance daily for the first few weeks in Search Console.
  • Compare organic keywords and top pages before and after launch to find where traffic was lost.
  • Keep a rollback plan ready. As Ahrefs notes, “you can fix almost anything that goes wrong.”

Search Console is your best early warning system here. Our guide to fixing Google Search Console indexing issues explains how to read and resolve common errors.

google search console page indexing report after a website migration

Avoid Staggered Migrations

Moving part of a site now and the rest later can create its own problems. In a case reported by Search Engine Journal, Mueller said a partial domain move “is not going to be seen as a full site move,” adding: “You’ll have a hard time tracking things & Google will have a hard time understanding your sites.” He recommended cleaning up the split “as soon as you can.”

Set the Right Expectations

Even a well-run migration can change your rankings. Mueller has said there is “no specific time or guarantee” for recovery, and that the outcome “can be a negative, it can be a positive.” In his words, “There is no ‘back to the same’.”

That is why the goal is to reduce risk, not eliminate it. Share a realistic timeline with stakeholders, monitor closely, and fix issues fast. Avoiding the most common SEO mistakes that are killing traffic will also put your new site in a stronger position.

Frequently Asked Questions

Can a website migration hurt SEO if URLs stay the same?

Yes. Content, templates, canonicals, internal links, structured data, rendering, status codes and page speed can all change during a migration, even when URLs remain identical.

How long does it take to recover from a website migration?

A normal dip often stabilizes within two to six weeks. A poorly executed migration can cause a hangover lasting many months. Google has said there is no guaranteed recovery time.

Does changing my CMS affect SEO?

It can. A new CMS may handle titles, canonicals, schema, internal links and rendering differently. Crawl and compare the old and new sites before launch.

Will a website redesign affect my rankings?

Often, yes. Google has said that changing design generally changes content, so rankings may move up or down after a redesign.

What is the most common migration mistake?

Launching with leftover staging settings, such as noindex tags or robots.txt blocks, is one of the most damaging and most common mistakes.

Conclusion

Keeping the same URLs removes one major source of migration risk, but it does not make a migration SEO-safe. Content, code, links and technical signals all change behind those URLs, and Google evaluates the site you launch, not the one you had before. Plan with SEO involved from day one, compare everything before and after launch, and monitor closely until performance stabilizes.

Planning a migration or redesign? Our digital marketing and SEO team can audit your current site, review staging and monitor launch so your rankings stay protected.

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts

Many businesses believe that if every URL stays the same during a migration, their SEO ...

SEO never slows down. In 2026 alone, Google rolled out its May core update over ...

Choosing the right keywords is one of the most important decisions in SEO. Pick the ...