Rankings Dropped After a Redesign: How to Find What Broke

⏱ 15 min read

A redesign that loses rankings almost never loses them to bad luck or a mysterious algorithm shift. It loses them to a specific, findable change that shipped on launch day. The new site looks cleaner, the team is relieved, and two weeks later organic clicks in Search Console are down 30 or 40 percent. The cause is sitting in the difference between the old site and the new one, and the job is to find it fast.

This guide is written for Shopify stores, and the Shopify context matters more than most articles admit. A generic post will tell you the first thing to check is missing redirects. On a Shopify theme change that advice is often wrong, because a reskin usually keeps every URL exactly where it was. Below is the diagnosis a specialist actually runs, in order, with the tools, thresholds, and numbers that decide each call.

First, Confirm the Traffic Drop Is Real

Before you touch a single template, confirm the decline is genuine and not a broken measurement. Redesigns frequently re-tag a site, and a Google Analytics 4 property or Google Tag Manager container reinstalled incorrectly will show a cliff in sessions while real visitors keep arriving. Separate three failures, because each points somewhere different:

• A rankings drop shows as lost positions and impressions in Search Console. This is an SEO problem.
• A traffic drop shows as lost sessions in analytics. If Search Console clicks are flat but sessions collapsed on launch day, the tag broke, not the ranking.
• A conversion drop shows as stable traffic with fewer orders. That usually means a broken form, a slow checkout, or a layout change, not a search issue.

Google documents this measurement-first approach in its debugging traffic drops guide, and it is the correct starting point. Mobile makes the check urgent: mobile is roughly 60 percent of ecommerce traffic, so a mobile-only tracking break or layout fault hides a large share of the picture.

Broken Inbound Links and a Missing Google Tag Manager Container

Two launch-day breaks look like an SEO loss in reports but have different fixes, so check them before you work through the seven causes.

• A missing or duplicated Google Tag Manager container. On Shopify, the GTM snippet and other tags are often pasted into theme.liquid. Code edits made to the previous theme do not come across to a newly installed theme, so the new theme can launch without the container, and sessions fall while Search Console clicks stay flat. The opposite also happens: the snippet is added to the new theme while an app or a custom pixel already loads the same tags, and every pageview and purchase is counted twice.
• Tracking that lived outside the theme. Tags set up in Shopify’s Customer events (app pixels and custom pixels) do not depend on the theme, while scripts that used to sit in the checkout’s additional scripts need their own review. Our checkout extensibility checks cover what to verify when legacy checkout scripts are retired.
• Broken inbound links. Backlinks and internal links that point to URLs which now return 404 lose their value immediately. In Search Console, compare the Links report (top linked pages) with the “Not found (404)” list in Page indexing. Any linked URL that now 404s needs a 301 to its closest equivalent.

To confirm the tracking side, open the live store with GTM’s preview mode or Google Tag Assistant, click through a product page, add to cart and start checkout, and check that each tag fires exactly once. Then compare one week of GA4 sessions from organic search with Search Console clicks for the same week. They will never match exactly, but they should move together.

Isolate What Dropped: Page Type, Query, Device, Country

A drop is a clue only once you know its shape. Open the Search Console Performance report, set the range to 16 months for context, and slice the loss four ways. The pattern tells you where to look before you form a theory.

• By page type. Shopify has distinct URL families: /products/, /collections/, /pages/, and /blogs/. If only collections lost visibility, the fault lives in the collection template, not site-wide.
• By query. A loss concentrated on a handful of high-value terms points to on-page content or intent changes on those exact pages.
• By device. A mobile-only drop points hard at Core Web Vitals or a mobile layout regression, since Google evaluates most experience signals on mobile.
• By country. A drop confined to one market on a DE and EN store points at hreflang or locale routing, covered further down.

Rule Out a Google Update Before You Blame the Redesign

Two things can move at once. If your launch happened to land inside a broad core update, you could be chasing a template bug that does not exist, or ignoring a real one because you assume the update explains everything. Resolve it with dates. Check the Search Status Dashboard for the start and end of any recent core update, then line those dates against your deploy date.

• Drop starts on launch day, no update running: the redesign is the cause. This is good news, because self-inflicted problems are fixable this week.
• Drop tracks an update window, templates and URLs intact: you are likely looking at an algorithmic reassessment, which is a content-quality project on a different timeline.

Google recommends waiting a full week after an update finishes before drawing conclusions, so do not act on the first noisy day of data.

Why Shopify Redesigns Break SEO Differently

The single most useful distinction in this whole diagnosis is redesign versus replatform, because it decides which causes are even possible. Most generic advice fails here by assuming every redesign changes URLs.

• A same-store theme reskin keeps your domain, your Shopify backend, and almost always your URL handles. When you change an individual product or collection handle in the Shopify admin, the option to create a URL redirect is selected by default, so a 301 is created unless someone clears that checkbox, but a visual redesign rarely touches handles at all. So on a straight reskin, redirects are seldom the culprit. The damage comes from what the new theme renders: less text, different headings, client-side content, weaker links, and a heavier page.
• A replatform or restructure is the opposite case. Moving from WooCommerce or Magento to Shopify, or changing your URL taxonomy, rewrites large numbers of addresses at once. Here redirects, sitemap regeneration, and canonical behaviour are the primary risks, and a careful Shopify migration plan is what protects rankings.

Cause One, Missing or Broken Redirects (Mostly a Replatform Problem)

Broken redirects are the classic cause, but they mainly bite when URLs actually changed. Every old URL that earned rankings or backlinks and now returns a 404 is lost authority. For example, renaming /collections/womens-boots to /collections/boots-women without a redirect turns every ranking and every backlink the old URL held into a dead end. Diagnose it in the Search Console Page indexing report by watching for a spike in “Not found (404)” after launch, then cross-reference those URLs against a pre-launch export of your site.

On Shopify, redirects live in the admin under Content and then URL redirects, and Shopify supports permanent 301 redirects only, which is exactly what you want for a move. Two facts trip teams up. Shopify auto-redirects when you rename a handle, but it does not create a redirect when you delete a page, so deleted collections and discontinued products need manual rules. And scale is not the constraint: the standard plan allows up to 100,000 redirects and Shopify Plus allows up to 20 million, so completeness is the real work. Shopify’s own redirect documentation covers bulk CSV import for large maps.

• Map each old URL to its closest new equivalent, product to product, collection to collection.
• Never funnel everything to the homepage. Google treats a mass homepage redirect as a soft 404 and drops the relevance signal.
• Avoid chains. Point A straight to C, not A to B to C, because each hop leaks a little equity and slows the crawl.
• After importing, resubmit the sitemap and use URL Inspection to request recrawls on your highest-value pages.

Redirects and canonicals are both strong signals to Google, so a 301 map that points one way and a canonical tag that points another sends a mixed message. If the redesign was part of a platform move, work through a full redirect checklist for a Shopify migration before you look at anything else.

Cause Two, Template-Level Content Loss

This is the quiet killer on same-store reskins, and Google names it directly: in its own guidance, “template issues” are listed as a common root cause because a new template can affect large portions of a site at once. A cleaner design almost always means less text, and Google reads less text as less relevance. A collection page that carried 600 words of category copy and now shows 90 has handed Google far less to rank on.

Look for the specific ways a Shopify rebuild strips copy:

• Collection intro and footer descriptions removed for a tidier grid.
• Product descriptions moved into collapsed accordions or tabs, so the detail is present but demoted.
• The old keyword-bearing H1 replaced by a logo lockup or a generic hero line.
• Long-form buying guides on /pages/ trimmed to look modern.

Diagnose by comparison, not memory. Pull the old page from the Wayback Machine, crawl both the archived version and the live version with a tool like Screaming Frog, and compare word count, H1 text, and title tags per URL. Any page that lost a meaningful share of its indexable text is a suspect. Restoring that content is often the fastest single win, and it is core to ongoing Shopify SEO.

Cause Three, JavaScript Rendering and Lost Structured Data

Modern Shopify themes and headless builds lean heavily on JavaScript, and that changes how Google sees the page. Content injected client-side, or hidden behind an interaction, may not be indexed with the same weight as content in the initial HTML. If your redesign moved key copy, reviews, or specifications into a script-rendered component, the page can look complete to a shopper and thin to a crawler. Two things break most often:

• Indexable text. Copy that only appears after a click or a script runs can be discounted or missed entirely.
• Structured data. Product schema, review and rating markup, and breadcrumbs are frequently generated by the old theme or an app, and a rebuild can drop them silently. Losing rich results means losing star ratings and price snippets, which cuts click-through even when positions barely move.

Diagnose both with the URL Inspection tool. View the rendered HTML for a key product and confirm your important text is present after rendering, then run the same URL through the Rich Results Test to confirm the schema still validates. If the rendered HTML is missing content the old page had, that is your regression.

Cause Four, Broken Internal Linking and Navigation Depth

Internal links tell Google which pages matter and how they connect, and a redesign rewrites navigation wholesale. A simplified mega-menu, a stripped footer, or removed breadcrumbs can quietly orphan pages that used to be one click from the homepage. Pages that fall to four or five clicks deep get crawled less often and ranked lower, because crawl budget and internal PageRank both thin out with depth.

Diagnose it by crawling the new site and sorting by crawl depth and by number of internal inbound links, then compare the worst offenders against the pages that lost rankings. Overlap is your answer. Rebuild the important paths: return category links to the header or footer, restore contextual links inside collection and blog content, and keep breadcrumbs if the old theme had them.

Cause Five, Indexability Regressions (noindex, robots.txt, Canonicals)

The most damaging bugs are the ones that tell Google to stay away, and they hide well because the pages still load perfectly for visitors. Three regressions account for most of them:

• A leftover noindex. Staging and preview builds are commonly set to noindex, and that directive can survive the push to production. A single template-level noindex can deindex an entire page type overnight.
• A robots.txt disallow. A block added during development to keep the unfinished site out of the index can ship live and cut off crawling.
• Canonical errors. A new theme’s canonical logic can point pages at the wrong URL or at the homepage, which consolidates them out of the index. Google’s own troubleshooting lists a non-canonical page as a leading reason a page vanishes from results.

Diagnose with URL Inspection on a sample of each page type, read the Page indexing report for a jump in “Excluded by noindex tag” or “Blocked by robots.txt”, and confirm each important page reports itself as its own canonical. These are usually one-line fixes with an outsized recovery.

For canonicals, URL Inspection shows two values side by side: the “User-declared canonical” from your theme and the “Google-selected canonical”. If they differ on pages that lost rankings, or the Page indexing report shows a new rise in “Duplicate, Google chose different canonical than user”, the new theme’s canonical output is the suspect. Shopify themes normally print the tag from the canonical_url Liquid object, so a custom override in the redesigned theme is where to look first. Our guide on setting up a Shopify canonical URL properly shows the target state per page type.

Cause Six, a Core Web Vitals Regression From a Heavier Theme

Speed is a ranking signal and a redesign is where it regresses, because new themes ship with larger hero media, more fonts, animation libraries, and app scripts. It is common for a store carrying a couple of dozen apps to load fifteen or more external scripts on every page, and each one competes for the main thread. Google measures three field metrics from real Chrome users at the 75th percentile over a rolling 28-day window, so a regression takes weeks to fully surface and weeks to fully clear. The Core Web Vitals thresholds are precise:

INP replaced First Input Delay on 12 March 2024 and is now the metric most sites fail. That matters for Shopify because the pages that struggle most with INP are exactly the commercial ones: a variant selector that lags, an add-to-cart button that responds slowly, or a filtered collection that stalls all run JavaScript on the main thread. The 2025 HTTP Archive Web Almanac found that roughly 76 percent of Shopify origins passed all three Core Web Vitals on mobile, against about 35 percent of WooCommerce origins, so Shopify starts ahead, and a heavy redesign is one of the fastest ways to give that lead back.

Diagnose with the Core Web Vitals report in Search Console and confirm with field data in PageSpeed Insights, not lab scores. Recovery is realistic: Rakuten’s documented Core Web Vitals work on web.dev drove a 33 percent rise in conversion rate without a full rebuild. If a heavier theme is the cause, a focused Shopify speed audit isolates the offending assets, and the web.dev reference explains why the bar sits at the 75th percentile.

Cause Seven, Broken hreflang on International Stores

If you run both DE and EN storefronts, a redesign can break the hreflang pairing that tells Google which language version to serve to which audience. This shows up in the country slice from step two as a drop confined to one market. Two failure modes dominate:

• Missing or one-way tags. Each version must reference itself and its counterpart. If the EN page points to DE but DE does not point back, Google may ignore the pair and let the versions compete.
• Wrong locale routing. On a multi-store or multi-domain setup, a redesign can change the routing that maps a locale to its URLs, so the wrong language ranks.

Diagnose by crawling for hreflang annotations and confirming reciprocal tags with correct language and region codes. Fixing them restores the split cleanly, usually within a crawl cycle.

Traffic Held but Conversion Rate Dropped After the Redesign?

Sometimes Search Console looks fine and the problem is revenue. If organic clicks are stable but orders fell after the new site design launched, this is a conversion problem, and the SEO checks above will not find it. These are the metrics to check, in this order:

Why did the conversion rate drop after redesigning the site? In most cases one of three things happened: tracking changed, so the “drop” is partly a measurement artefact; an element that answered a buying question (delivery time, returns, sizing, reviews, trust badges) was removed or pushed below the fold; or the new theme added friction on mobile. Compare old and new templates screen by screen on a phone before you change anything. Our guide to diagnosing low conversion after a Shopify redesign goes deeper, and a structured CRO audit for Shopify runs the same funnel analysis with session recordings and a prioritised fix list.

A Diagnostic Sequence You Can Run in One Afternoon

Treat the drop as an incident, not a marketing task, and it stops feeling overwhelming:

1. Assign one owner. One person holds the investigation so findings do not scatter across three inboxes.
2. Write the changelog. List everything that shipped at launch: theme, apps, URL changes, template edits, tag changes.
3. Work the checks in order. Stop at the first confirmed cause instead of guessing across all of them.

This table maps the symptom to the likely cause and the tool that confirms it.

Run it top to bottom. Most post-redesign losses resolve within the first three rows, and a structured Shopify SEO audit follows this same order when the internal team runs out of road.

The Tool Set for the Diagnosis

You do not need a large tool stack for this. Three sources answer almost every question in the table above:

• Google Search Console. Performance (clicks, impressions and position by page, query, device and country), Page indexing (404, noindex, robots.txt and canonical statuses), URL Inspection (rendered HTML and canonical), Core Web Vitals and the Links report.
• A crawler. Screaming Frog SEO Spider is the common choice. Its free version crawls up to 500 URLs, which covers many small stores; larger catalogues need the paid licence at £199 per user per year (as of October 2026). Crawl the live site and, where possible, an export or archive of the old one, then compare titles, H1s, word count, canonicals, status codes and crawl depth per URL.
• Field speed data. PageSpeed Insights and the Core Web Vitals report show real-user data. Lighthouse lab scores are useful for debugging, but they do not decide rankings.

Export the Search Console Performance data for 28 days before and 28 days after launch by page. Sorting that export by lost clicks gives you the list of URLs to crawl and inspect first.

How Long Recovery Actually Takes

Set expectations before you fix anything, because the biggest mistake after a redesign is to keep changing things while Google is still reprocessing. Different fixes recover on different clocks:

The discipline is simple. Fix the confirmed cause, request recrawls on the important pages, then hold steady and measure, rather than layering new changes that muddy the signal.

Website Redesign SEO Checklist: How to Redesign Without Losing SEO Next Time

Does a website redesign affect SEO? Yes, whenever it changes what Google can crawl and evaluate: URLs, indexable text, headings, internal links, structured data, index directives or speed. A redesign that keeps all of those stable usually causes no more than a short fluctuation while Google recrawls. The checklist below keeps the next relaunch in that category.

On Shopify, keep the previous theme in the theme library after launch. If a template-level problem appears, you can republish the old theme while you fix the new one, instead of leaving a broken template live for weeks.

If the redesign is still ahead of you, it is cheaper to build these checks into the project than to recover afterwards. That is how we plan Shopify website redesign projects at Skalum, and it is the first question we ask as a Shopify agency when a team brings us a relaunch: which pages earn the traffic today, and what exactly will change on them.

Conclusion

A redesign that lost rankings did not fail because the new site is ugly. It failed because something in the rebuild broke the continuity Google relied on: a URL, a block of text, a rendering path, a link, an index directive, or a speed budget. Every one of those is visible in Search Console and a crawler, and every one is fixable once you have scoped the drop and worked the checks in order. Confirm the loss is real, isolate its shape, rule out an update, then follow the seven causes from most to least likely for your kind of rebuild. Find the specific change, fix it, and let Google recrawl.