Article

Why did my Google traffic drop after we launched the new website?

The reasons Google gives for each page it left out of its index are the place to start, before anyone touches the new site.

By Brandon Kelly · Updated June 2026 · 8 min read

Google traffic falls after a new website launches when Google can no longer reach, index or match the pages that earned it: old URLs that now return errors or all redirect to the home page, a staging noindex or robots.txt block carried live, or ranking content cut in the rebuild. Part of a dip can be expected: Google's guide to traffic drops says changed URLs may bring ranking fluctuations while the site is recrawled and reindexed. Search Console narrows the cause down: the reason Google gives for each page it left out, and whether the drop hit the whole site or one group of pages.

Read the drop in Search Console before changing the site

A post-launch drop gets checked in Search Console before anything on the site changes, and Google's guide to debugging traffic drops sets the steps. Set the date range to 16 months, which Google says helps confirm the fall is not a drop that happens every year due to a festivity or a trend. Then see whether the drop is site-wide or limited to a group of pages: Google says to check the Page indexing report for a site-wide issue and to inspect a few pages with the URL Inspection tool when one group is affected. If impressions held steady while clicks fell, Google says the title and snippet may not be as good as they could be, which points at rewritten titles rather than missing pages.

For small sites, Google's Page indexing report help adds, "If your site has fewer than 500 pages, you probably don't need to use this report", and suggests Google searches instead (its examples are site: searches). Running those searches and reading a URL Inspection result is explained in technical SEO basics for local sites. Google lists the main causes of traffic drops without ranking them, and the report groups every page it left out under a reason, so the checks below read those reasons in the order an owner can rule them out.

Some Page indexing reasons mean the launch worked

Some reasons in Search Console's Page indexing report mean the launch did what it should. Google says it is fine for a URL not to be indexed for the right reasons, such as an expected robots.txt rule, a noindex tag, a duplicate URL, or a 404 for a page removed with no replacement. After a launch that changed URLs, "Page with redirect" is the expected label for the old addresses: Google defines it as a non-canonical URL that redirects to another page and so is not indexed, while the redirect target may or may not be. "Duplicate without user-selected canonical" means Google picked another page as the canonical, which Google calls working as intended "because Google does not serve duplicate pages", as long as the page Google chose is the new address and not an old URL still serving its own copy.

"Alternate page with proper canonical tag" sits here too, though not as a sign of a redesign problem: Google defines it through AMP pages and mobile or desktop versions of a page that correctly point at an indexed canonical, and says "there is nothing you need to do". A clean report narrows the search without ending it.

A crawl block carried over from staging

A rule that kept a staging copy out of Google, carried onto the live site, shows up in the Page indexing report as "URL blocked by robots.txt" or "URL marked 'noindex'". Google's help says a drop in total indexed pages without a matching rise in errors may mean pages are blocked by robots.txt, noindex or a required login. Its debugging guide explains why a noindex left in a template looks like a slow slide rather than a cliff: a misplaced noindex tag "would depend on Google crawling the page, meaning there would be a slower drop in traffic".

On WordPress, the setting to check is the "Discourage search engines from indexing this site" box on the Settings, Reading screen, which asks search engines not to index the site; since version 5.3 WordPress outputs a noindex,nofollow robots meta tag in the page head, in its documentation's words "(if wp_head is used)". For "URL marked 'noindex'", Google's instruction is to remove the directive from any page that should be indexed. A robots.txt rule that disallows every crawler shuts out more than Google, and unblocking AI crawlers walks through reading and fixing the file.

Old addresses now answering Not found

Old URLs that were neither kept nor redirected in a new website stop answering with a page, and when they return a 404 the Page indexing report lists them under "Not found (404)". Google's crawling documentation says Google does not index URLs that return a 4xx status and removes indexed URLs that start returning one, so a page that ranked, lost its address and got no redirect drops out. Google is measured about 404s: "404 responses are not necessarily a problem, if the page has been removed without any replacement." It generally recommends fixing only the 404 errors for URLs a site links to itself or lists in a sitemap, and says a page that has moved should get a 301 to its new location.

The report keeps a short memory: Google says it shows only URLs that returned 404 errors in the past month, and that Googlebot will probably keep trying a 404 URL for some time, less and less often. "Soft 404" is the quieter cousin, a page that shows a user-friendly not-found message without returning a 404 status code; Google's crawling documentation says an empty page or an error message served with a success status shows up the same way.

Redirects that loop, chain or all land on the home page

Redirects that fail outright after a launch appear under "Redirect error" in the Page indexing report, which Google's help says covers a redirect chain that was too long, a redirect loop, a redirect URL that eventually exceeded the maximum URL length, and a bad or empty URL in the chain. A chain forms when new redirects are stacked onto older ones instead of pointing straight at the final page.

The other pattern produces no redirect error at all. Sending every old URL to the new home page looks tidy, but Google's site-move guide rules it out: "Don't redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site. This can confuse users and might be treated as a soft 404 error." The repair is a map that sends each old address to its closest matching page, which is the core of planning a redesign that keeps its rankings.

Pages that kept their address but lost the text that ranked

No reason in the Page indexing report names content cut in a rebuild, because the page still exists and may still be indexed. Google says an indexed page is not guaranteed to show in results, and a page that no longer carries the words, sections or answers that matched its searches has less to match them with. Comparing the searches a page appeared for before the launch with the ones it appears for now shows which topics went missing, and the missing topics point at the missing text.

Text can go missing when long service descriptions are shortened to fit a new layout, when FAQ sections are dropped, when city or service pages are merged into one, or when words move into images that carry no readable text. Restoring the text that ranked, on the page that now answers that search, is a content repair rather than a redirect fix; where two old pages really were merged, Google's site-move guidance allows redirecting both old URLs to the consolidated page.

A drop that settles and a drop that does not

For changed URLs, Google's debugging guide gives a general timescale, not a deadline: "As a general rule, a medium-sized website can take a few weeks for Google to notice the change; larger sites can take longer." Small position changes, it adds, can happen at any time and reverse without anyone doing anything. The same guide draws the line: "If you see a drop after moving and it's not recovering, check the site move troubleshooting section for common mistakes when migrating a site with URL changes."

Fixes take time to register too. Google says indexing is never instant, even with a crawl request, and that validating a fix in the Page indexing report typically takes up to about two weeks but in some cases much longer. If the launch also moved the site to a new domain, check the old domain's redirects and the Change of Address request as well; moving to a new domain without losing traffic lists what each needs.

If the report's reasons and the traffic still do not line up, a free SEO audit puts another reader on the new site's indexing, titles and technical health.

Sources

Frequently asked questions

Could the traffic drop have nothing to do with the new website?

Yes. Google's guide to traffic drops lists algorithmic updates, technical issues, security issues, spam issues, seasonality and changing interests, and site moves and migrations as the main causes to investigate, and notes a drop can come from a data processing change or a logging error. A 16-month date range in Search Console shows whether the same dip happened at the same point in earlier years.

Are the 404 errors in Search Console hurting the site?

Not necessarily. Google says 404 responses are not necessarily a problem when a page was removed with no replacement, and it generally recommends fixing only the 404 errors for URLs the site links to itself or lists in its sitemap. A 404 on an old URL that used to rank and has a matching new page is the one worth fixing, with a 301 to that page.

Should every fixed page be resubmitted to Google?

Not one by one. Google says indexing is never instant, even when a crawl request is submitted directly, and for pages reported as crawled but not indexed it says there is no need to resubmit them. Fixing the cause and starting validation in the Page indexing report is the documented route, and Google says validation typically takes up to about two weeks, and in some cases much longer.

Why would a noindex mistake cause a slow decline instead of a sudden drop?

Google's debugging guide says a misplaced noindex tag depends on Google crawling each page, which means a slower drop in traffic, because each page leaves the index when Googlebot next visits it. A whole site going down is the site-wide case Google describes separately.

Why does Search Console still show old URLs weeks after the launch?

Old URLs that redirect are expected to appear as Page with redirect, which Google defines as a non-canonical URL that redirects and is not indexed itself. Old URLs that return 404 can stay on Googlebot's list for some time: Google says it will probably keep trying them, less and less often, and there is no way to make it permanently forget a URL.

Ready to get found?

See where you stand in Google and AI search

We will run a free audit of your local rankings and your visibility across ChatGPT, Gemini, Perplexity, and Google AI Overviews, then show you the fastest path to more booked jobs.

Get my free audit Call (239) 747-0465