Will a Domain Move Fix a SaaS Site's Quality Problem? What Mueller Said in November 2026
John Mueller said a site move does not improve overall quality. Here is when a domain move helps a B2B SaaS site, and what to audit and fix first.
- Desk
- SEO
- Format
- Explainer
- Reading time
- 7 min
- Published
- Nov 17, 2026
No. A domain move changes where your pages live, not how Google judges their quality. John Mueller said so on November 17, 2026, replying to a site that was still poorly indexed ten months after moving. If your pages are thin, copied or unhelpful, fix that first. Move domains only for a real branding or technical reason.
This guide is for B2B SaaS founders and marketers who are weighing a new domain after a traffic drop or a rough core update. It covers what Mueller said, why a move does not reset quality, when a move is justified, and how to run one safely. cekpr covers technical SEO for software companies, and a site move made for the wrong reason is one of the costlier errors a team can make.
What did Mueller say about site moves and quality?
Mueller said that a site move does not improve a site's overall quality. He wrote it on Bluesky, in reply to a site owner whose domain change was ten months old. The new site still was not being indexed properly. Mueller suspected Google's quality systems were unconvinced, not that the move itself had broken something.
Search Engine Roundtable reported the exchange in its November 17 coverage. Mueller advised the owner to step back and think about the overall value the site adds to the web. The same outlet noted a similar reply to another site a month earlier, after a move that dragged on for four months.
The lesson is simple. Slow indexing after a move can come from a technical fault. It can also come from weak pages that Google has little reason to prefer. Treat both as possible until you have checked.
Why does a domain move not reset a SaaS site's quality?
A move redirects the same pages to a new address. The words, the structure and the usefulness stay the same. Google's own site move guide says permanent redirects do not cause a loss of PageRank, so links carry across. Nothing in a move rewrites a weak feature page into a strong one.
Many teams hope a new domain will shed a bad history. That hope is understandable after a hard core update. If the pages that sank were thin, repetitive or built for search engines first, they will sink again on the new domain. You will also pay the cost of a migration, which brings its own turbulence.
Google's guide warns about that turbulence. It says any significant change can cause ranking fluctuations while Google recrawls and reindexes. For medium-sized sites, it can take a few weeks or more before the new URLs replace the old ones. Larger sites take longer. A move for the wrong reason adds a dip to a problem you already have.
When is a domain move the right call for a SaaS company?
A move is right when the address itself is the problem. Google's guide names three kinds of move: HTTP to HTTPS, domain name changes, and URL path changes. A company merging two brands into one domain is a clear case. So is a rebrand after an acquisition. The table below compares common triggers.
| Reason for moving | Does a move help? | Better first step |
|---|---|---|
| Rebrand or company rename | Yes, if planned well | Map every URL before launch |
| Merging two domains | Yes | Redirect to the closest matching pages |
| Still on HTTP | Yes | Install certificates, then redirect |
| Traffic fell after a core update | No | Audit the pages that dropped |
| Pages are thin or copied | No | Rewrite or remove the weak pages |
If your reason falls in the last two rows, pause. Our checklist for how to diagnose a SaaS organic traffic drop separates quality problems from tracking errors and seasonal dips. Run it before any migration plan reaches your developers.
What should you fix instead of moving?
Fix the content and the experience. Google's guide to helpful content suggests a self-assessment with a few direct questions. Does the page offer original analysis? Does it add value beyond the sources it summarizes? Would you bookmark it or send it to a colleague? A weak answer on a page that lost traffic tells you where to start.
The same page lists warning signs of search engine-first content. Examples include producing lots of content on many topics in hopes some will rank, using extensive automation, and mainly summarizing what others say. It also warns against changing page dates to look fresh. Check your own library against that list, one section at a time.
Our guide to how to fact-check AI-assisted content helps with the automation point. If a batch of pages was generated quickly, review each one for errors and thin spots before you decide anything about the domain.
Deleting pages is a possible step, but only a late one. Google's core update guidance calls deletion a last resort, and says that wanting to remove whole sections can be a sign they were made for search engines. If you remove pages, follow our walkthrough on how to handle 404 errors on a SaaS site so the old URLs behave correctly.
For the current ranking update, read the November 2026 core update plan. It explains when to measure and what to leave alone. At cekpr, we advise teams to finish that measurement before they touch a domain, because the data often shows the drop is small.
How can you tell a technical fault from a quality problem?
Check the technical basics first, because they are quick and cheap. Then judge quality. Work through these checks in order:
- Inspect a sample of missing URLs with the URL Inspection tool, which Google's guide recommends for pages that seem absent from the new site.
- Look for noindex tags or robots.txt rules left over from development.
- Test redirects for wrong or non-existent targets.
- Compare crawl errors on the new domain with the old one.
If all four checks come back clean and pages are crawled but still not indexed or ranked, quality is the likelier cause. That matches Mueller's reading of the case. Treat it as a content problem and return to the self-assessment above.
How do you run a site move safely if you still need one?
Follow Google's process and keep each step separate. The steps below come from its site move documentation.
- Prepare the new site and test it, including robots.txt, certificates and analytics.
- Verify every variant of both the old and new sites in Search Console.
- Build a URL mapping from each old address to its closest new one.
- Turn on server-side redirects and check canonical tags on the new URLs.
- Submit a Change of Address in Search Console for the old domain.
- Monitor both sites with sitemaps, indexing reports and server logs.
The guide says to change only one thing at a time. If you plan a new domain, a new CMS and a new layout, do them in sequence. It also suggests moving a small, stable section first when the site is large. That test shows problems before the whole site depends on the result.
Time the move for a quiet period when you can. Fewer visitors are affected by a hiccup, and Googlebot has more server capacity. Keep the old domain registered and redirecting for as long as it earns traffic or links.
What mistakes stall a site move?
The most common mistakes are simple. Google lists leftover noindex rules or robots.txt blocks from the development phase. It also lists redirects pointing to the wrong or missing URLs, and spikes of crawl errors on the new site. Test for each one before and after launch.
One redirect error deserves its own warning. Do not send many old URLs to a single irrelevant page such as the new home page. Google says this can confuse users and may be treated as a soft 404. Redirect each page to its closest equivalent. Consolidated content is the exception, since several old pages can point to one new page that replaces them.
Sitemaps help you watch progress. Google suggests keeping one sitemap of old URLs and one of new URLs. Over time, indexing should fall on the old list and rise on the new one. Our guide to sitemap.xml setup for a SaaS site covers how to build those files cleanly.
How long should you wait before judging the move?
Wait weeks, not days. Google says a move is complete only when Googlebot has visited every old and new URL at least once, and the move happens URL by URL. There is no fixed crawl schedule. Larger sites take longer than medium-sized ones, which already need a few weeks or more.
If indexing is still poor after several months, stop blaming the migration. Check redirects and blocks first. Then review quality honestly. Mueller's recent replies point to the second step.
What is a practical decision rule for a domain move?
Move for a reason that has nothing to do with rankings, such as a rebrand or a merger. Do not move to escape a quality problem. Audit the pages that lost traffic, improve or remove the weak ones, and give Google time to see the change. A domain move can happen later, once the content earns its place.
Does moving to a new domain improve a SaaS site's rankings?
How long does a site move take to settle in Google?
Do 301 redirects lose link value during a domain change?
Should I use the Change of Address tool for a domain move?
Up next · SEO How to Respond to Google's November 2026 Core Update on a B2B SaaS Site join the club.
The week's best SEO and AI search posts, plus one thing to check in your own Search Console, every Thursday morning. Unsubscribe whenever.