--- title: "Traffic dropped after a Google core update: what now?" author: "Performetic Ekibi" url: "https://www.performetic.com/en/blog/google-core-update-traffic-drop-recovery" published: "2026-02-14T08:00:00.000Z" updated: "2026-10-05T02:41:53.582Z" --- # Traffic dropped after a Google core update: what now? > If traffic fell after a core update, do not panic: wait at least a full week after the update finishes, then compare that week with one before it in Search Console. Google recommends no drastic action for small drops. For large, sustained drops, assess content quality across the whole site, avoid quick fixes and track improvements over months. ## What should you do if traffic dropped after a Google core update? First confirm the drop is really related to the update. Google recommends waiting at least a full week after a core update completes before analysing your site in Search Console, then comparing that week with a week before the rollout began. Small position losses do not need drastic changes. Large, sustained drops call for a site-wide content quality assessment. Core update periods often trigger panic in ecommerce teams: product descriptions get rewritten en masse, category copy gets deleted, pages get removed. Google explicitly recommends avoiding quick-fix changes. This article sets out a calm, systematic diagnosis process. ## What is a core update? Google describes core updates as significant, broad changes to its search algorithms and systems. They happen several times a year and Google announces them. The aim is to present helpful and reliable results overall. Google's own analogy is useful: when a list of top restaurants is refreshed, the restaurants that move down are not necessarily bad; there are simply others that now make the list. A ranking loss does not always mean something is broken on your site. You can track update dates on the Google Search Status Dashboard, which shows when ranking updates start and finish. ## Is the drop really caused by the update? Google's guide to debugging traffic drops lists several causes: algorithmic updates, technical issues, security issues, spam policy violations, seasonality or changing interest, and site moves. Rule out the others before blaming the core update: | Possible cause | Symptom | Where to check | |---|---|---| | Technical issue | Sudden, sharp drop on specific page types | Search Console Page indexing report, server logs | | Manual action | Drop across the site or a section | Search Console Manual actions report | | Security issue | Warnings in search results | Search Console Security issues report | | Seasonality | Same dip in the same period last year | 16 months of Search Console data, Google Trends | | Site or URL change | Drop coincides with a change date | Redirect and canonical checks | | Core update | Gradual position loss aligned with update dates | Search Status Dashboard and Performance report | Google recommends looking at 16 months of data to spot yearly patterns and using Google Trends to separate an industry-wide decline from one specific to your site. In ecommerce, seasonality is very often mistaken for an update. We explain how to run this analysis in our [Search Console guide for ecommerce](/en/blog/google-search-console-for-ecommerce). ## How do you compare the right dates in Search Console? The diagnosis steps are: 1. Note the start and end dates of the update on the Search Status Dashboard. 2. Wait at least one full week after it ends. 3. In the Performance report, compare that week with a week before the rollout began. 4. Sort by page and find the pages that lost the most clicks. 5. Check which queries those pages lost position on, and by how much. 6. Determine whether losses are site-wide or concentrated in a section (blog, categories, products). Google also recommends analysing search types (web, image, video) separately. A drop in image search can have different causes than a drop in web search. ## What is the difference between a small and a large drop? Google draws a clear line. For a small drop in position (its example is moving from position 2 to 4), there is no need for drastic action; Google even recommends avoiding changes to content that is already performing well. A large drop (its example is 4 to 29) calls for a deeper assessment. If you see a sustained, large drop across the site, Google recommends using its self-assessment questions to check whether your site overall, not just individual pages, delivers helpful, reliable, people-first content. You can also ask trusted people unaffiliated with your site to run the assessment. ## What should ecommerce sites look at? Applied to ecommerce, the self-assessment most often surfaces these issues: - **Copied manufacturer descriptions:** if hundreds of product pages carry the same text found on other sites, your pages add no original value. See our guide to [writing SEO-friendly product descriptions](/en/blog/how-to-write-seo-product-descriptions). - **Thin category pages:** pages that are just a product grid, multiplied through filter combinations. - **Mass-produced content:** Google's spam policies define generating many pages primarily to manipulate rankings without adding value as scaled content abuse. - **Product review and comparison content:** Google's reviews system aims to reward high-quality reviews with insightful analysis and original research written by experts or enthusiasts who know the topic well. Shallow "top 10 products" lists fall short here. - **Trust signals:** contact details, return terms, genuine customer reviews and clarity about who is selling. ## What should you avoid? Google's core updates page is clear on several points: avoid quick-fix changes, make changes that make sense for your users and are sustainable in the long term, and treat deleting content as a last resort. In practice: - Rewriting every product description overnight with AI can create a new scaled content problem instead of solving the old one. - Removing every page that lost traffic means losing valuable content too. - Doing nothing while waiting for the next update is not the answer either. - Changing your theme, URL structure and content all at once makes it impossible to tell which step worked. Make changes in batches and log their dates. - Rather than trying to copy competitors who now outrank you, ask what your shoppers genuinely need for that search. Google's self-assessment questions are built on the same perspective. ## How long does recovery take? According to Google, improvements can take time to show: some changes take effect in a few days, while others can take several months. You do not have to wait for the next core update to recover, because Google says it is continually updating its search algorithms, including smaller core updates. Still, making improvements does not guarantee that lost positions will return. ### Example recovery plan Example: a cosmetics brand sees that most of its blog traffic disappeared after an update, while category and product pages were unaffected. Diagnosis shows the losses are concentrated in mass-written, near-identical "best products" posts. The plan: merge these posts by topic and enrich them with real product experience, ingredient analysis and expert input, and redirect the few posts that add nothing to the relevant guide. Results are tracked monthly in the Performance report. ## Key takeaways - Compare a week after the update completes with a week before it started. - Rule out technical issues, manual actions, seasonality and site changes first. - Do not make drastic changes for small losses; assess the whole site for large drops. - In ecommerce, focus on copied descriptions, thin category pages and shallow review content. - Avoid quick fixes and track the impact of improvements over months. If you would like help finding the real cause of your drop, the Performetic team can review your Search Console data as part of a [free growth analysis](/en/contact). ## FAQ ### Is a drop after a core update a penalty? No. Google describes core updates as broad changes intended to make results more helpful and reliable overall. A ranking drop can simply mean other pages are now judged more relevant. You can separately confirm whether there is a manual action in the Manual actions report in Search Console. ### When should I start analysing the drop? Google recommends waiting at least a full week after the update completes. Then compare that week with a week before the rollout began in Search Console. Analysis done while the update is still rolling out can mislead, because changes may not be fully reflected yet. ### Do I have to wait for the next core update to recover? No. Google says it is continually updating its algorithms, including smaller core updates, and improvements can take effect in a few days or take several months. Making improvements does not guarantee that previous positions will definitely return, though. ### Should I delete pages that lost traffic? Google treats deleting content as a last resort. First assess whether each page genuinely helps users. Improve weak pages with potential or merge them with similar ones. Only remove or redirect pages that add no value after that assessment. ## Sources - [Google Search's core updates (Google Search Central)](https://developers.google.com/search/updates/core-updates) - [Debug Google Search traffic drops (Google Search Central)](https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops) - [Creating helpful, reliable, people-first content (Google Search Central)](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) - [A guide to Google Search ranking systems (Google Search Central)](https://developers.google.com/search/docs/appearance/ranking-systems-guide) - [Google Search Status Dashboard](https://status.search.google.com/)