Is the drop normal, or is something broken?
Some movement after a relaunch is normal while Google re-crawls. A drop that grows or does not recover is not. Use this as a guide:
| What you see | What it usually means |
|---|---|
| Small dip for 1 to 3 weeks, URLs changed, clicks climbing back | Normal re-crawl. Keep watching. |
| Sharp drop the week of launch, not recovering after 3 to 4 weeks | Something broke. Start the checks below. |
| Drop only in Google Analytics, Search Console clicks steady | Tracking problem, not rankings |
| Drop only on some page types (blog, products, locations) | A template or a URL pattern lost its redirects or content |
| Drop that started weeks after launch | Probably not the relaunch. Check a Google update or seasonality with the playbook. |
Check 1: Is it a tracking problem? (5 minutes)
New templates often ship without the analytics tag, or with a new cookie banner that blocks it.
- In Search Console, open Performance > Search results and compare the 28 days after launch with the 28 days before.
- In GA4, compare Organic Search sessions for the same dates.
- If GA4 fell much more than Search Console clicks, check that the GA4 tag is on every new template and that your consent banner did not change. Your rankings are probably fine.
Check 2: Old URLs vs new URLs (15 minutes)
This is where most redesign drops are found.
- In Performance > Search results, set Date > Compare to the 28 days after launch vs the 28 days before. Open the Pages tab and sort by Clicks Difference.
- Export the list. You now have your old top pages (losing clicks) and new pages (gaining clicks).
- For each old URL that lost clicks, open it in your browser. You want one hop to the matching new page with a 301 (or 308) status. Use any redirect checker or your browser's developer tools (Network tab) to see the status.
- Check that the new page is getting the clicks the old one lost. If the old URL lost 900 clicks and the new one gained 850, the move is working. If the new one gained 100, the redirect, content or indexing is off.
What each redirect result means:
| What you find | What to do |
|---|---|
| 404 or soft 404 | No redirect. Add a 301 to the closest new page |
| 302 or 307 | A temporary redirect. Change it to 301. Many plugins and platforms default to 302 |
| Redirect to the homepage | Google advises against sending many old URLs to one unrelated page and may treat it as a soft 404. Map each one to its real match |
| Chain (old to older to new) | Point the old URL straight to the final URL. Google advises redirecting to the final destination, and if not, ideally no more than 3 hops |
Check 3: Did Google stop indexing the new pages? (10 minutes)
- Open Indexing > Pages for the property the new site lives on. Look at the chart for a jump in "Not indexed" in the week of launch.
- Open the reasons. The usual relaunch suspects: Excluded by 'noindex' tag (the staging "hide from search" setting went live), Blocked by robots.txt (a leftover
Disallow: /), Alternate page with proper canonical tag (new templates pointing canonicals at the old domain or staging), Not found (404), and Page with redirect. For what each reason means, see our page indexing fix guide. - Paste your top 5 new URLs into URL Inspection. Check "URL is on Google", the crawl date, and that the Google-selected canonical matches the URL itself.
- Open Indexing > Sitemaps. Make sure the new sitemap is submitted and lists only new, live URLs. A sitemap still listing old URLs sends Google to redirects.
If your domain changed, also check that both domains are verified, and that you used Settings > Change of address on the old property. Google says that tool is only for domain or subdomain changes.
Check 4: Did content or links get lost in the redesign? (20 minutes)
A tidier design often means shorter pages, and the pages that ranked may have lost the text that made them rank.
- Compare old and new pages. Open the old version in the Wayback Machine (web.archive.org) next to the new page. Look for missing paragraphs, FAQs, tables, reviews, or product details.
- Check titles and meta descriptions. Page builders often reset them to the page name. If the Pages table shows the same position but lower CTR, a weaker title is a likely reason.
- Check headings and structured data. Use URL Inspection's "View tested page" or a crawl tool to confirm the H1 and schema came across.
- Check internal links. New menus and footers often drop links to deep pages. A page that lost most of its internal links can slide even with a correct redirect. Update links in body text to point at new URLs, not old ones through redirects.
A fictional example
oakline-legal.com moved from Wix to WordPress and changed blog URLs from /post/slug to /insights/slug. Search Console clicks fell 40% in week two, and GA4 fell by about the same, so it was not tracking. The Pages comparison showed the old /post/ URLs losing clicks, but the new /insights/ URLs gaining only a fraction. A redirect check showed 302 on every blog URL, set by a plugin default. Indexing > Pages also showed "Excluded by 'noindex' tag" on the service pages, from a template setting left on during the build. They switched the redirects to 301, removed the noindex, updated internal links and resubmitted the sitemap. Clicks were back near the old level about 5 weeks later. (Fictional example to show the method.)
How long recovery takes after a relaunch
| Fix | When you can expect movement |
|---|---|
| Tracking fixed | Same day (missed days stay missing) |
| Noindex or robots.txt removed | Days, once Google re-crawls; use Validate fix in the Page indexing report, which usually takes up to about two weeks |
| Redirects fixed (302 to 301, 404 to 301) | Days to weeks, as Google re-crawls the old URLs |
| Domain move settling | A few weeks or more for medium sites, longer for large sites, per Google |
| Lost content restored | Weeks, as pages are re-crawled and re-evaluated |
Keep every redirect live. Google says to keep them as long as possible, generally at least one year.
What not to do
- Do not undo the whole launch in a panic. Rolling back to the old site creates a second migration. Fix the specific problem.
- Do not change URLs again. Every URL change restarts the clock.
- Do not redesign and rewrite at the same time next time. Change one thing, measure, then change the next.
How to use this with an AI assistant
Connect SEOmatic at https://seomatic.ai/mcp and ask: "Run gsc_performance compare_periods by page on mysite.com for the 28 days after my relaunch vs the 28 before, then gsc_indexing batch_inspect on my 20 biggest losing old URLs, and tell me which ones lack a 301, are not indexed, or point their canonical elsewhere." Reading needs a free sign-in; fixes like redirects are staged for your approval.