Blog Traffic Dropped After a Google Core Update? What a Small Business Should Do, Step by Step (2026)
My small business blog lost traffic after a Google core update. What should I do?
Wait first, then compare the right weeks. Google's own guidance is to confirm on the Search Status Dashboard that the core update has finished, wait at least a full week after it completes, and then compare that week in Search Console with a week from before the rollout began. A small drop, such as position 2 to 4, needs no drastic action; a large, sustained drop, such as position 4 to 29, calls for an honest review of your content. The November 2026 core update started on 10 November 2026 and was still rolling out when we checked on 12 November 2026.
PilotaSEO is a done-for-you SEO blog service that writes SEO posts for your site and publishes them automatically. We follow the same wait-then-compare rule on our own sites while an update rolls out, so this is the routine we actually use.
What is a Google core update?
A core update is a broad change to Google's ranking systems that happens several times a year and does not target specific sites. Google's core updates documentation says these changes "don't target specific sites or individual web pages", and that most sites "don't need to worry about core updates and may not even realize one has happened".
Google's analogy is a list of 20 favourite restaurants that you rewrite years later: new places appear, and the ones that move down "aren't necessarily 'bad'; there are just other restaurants" that made the list. For a small business blog, that means a drop can simply mean other pages now answer the same question better.
How long does a core update take to roll out?
Usually about two weeks. Google's Search Status Dashboard entry for the November 2026 core update says it was released on 10 November 2026 at 10:07 US Pacific time (19:07 in Central Europe), "applies globally and to all languages" and "may take up to 2 weeks to complete". The dashboard's history shows how long recent ones actually took:
| Core update | Started | Rollout length shown on the dashboard |
|---|---|---|
| November 2026 | 10 Nov 2026 | In progress on 12 Nov 2026 |
| May 2026 | 21 May 2026 | 11 days, 21 hours |
| March 2026 | 27 Mar 2026 | 12 days, 4 hours |
| December 2025 | 11 Dec 2025 | 18 days, 2 hours |
Until the dashboard marks the rollout complete, positions can still change, which is why Google tells you to confirm it has finished before you analyse anything. Add Google's recommended extra week, and the earliest fair comparison for the November 2026 update is roughly three weeks after it started.
How do I check if the core update hit my blog?
Use Search Console's Performance report with a date comparison, not your gut or a third-party "volatility" chart. The method from Google's documentation, step by step:
- Confirm the update has finished on the Search Status Dashboard and note its start and end dates.
- Wait at least one full week after the end date.
- Compare that week with a week before the rollout started, so the comparison isn't polluted by mid-rollout movement.
- Review your top pages and queries: is the change small or large?
- Check search types separately, because Google suggests looking at Web, Images, Video and News on their own.
Our guide to the monthly Search Console report for an SEO blog shows where the Performance report and date comparison live. Seasonal businesses should also compare with the same week last year, because a November drop may be normal for your trade.
Small drop or large drop: what changes?
A small drop means leave the page alone; a large, sustained drop means review the whole site against Google's helpful-content questions. Google's own examples are a move from position 2 to 4, where it recommends "avoiding making changes to content that's already performing well", and a move from position 4 to 29, which deserves a deeper assessment.
| What you see after the update | What Google suggests | What a small business should do |
|---|---|---|
| Small drop (for example 2 to 4) | No drastic action | Keep publishing; don't rewrite pages that still work |
| Large drop on a few pages (4 to 29) | Deeper assessment | Compare each page with what now ranks above it |
| Large drop across the site | Self-assessment of the site as a whole | Ask whether the blog is written for customers or for search engines |
| Gains | None | Note which pages rose; they show what Google rewards on your site |
For the deeper review, Google points to its helpful, reliable, people-first content questions, and suggests asking someone unaffiliated with your site to answer them too. Look at the pages that fell most and at the pages that now outrank them: Google says "there may be other pages on the web that are doing a better job of helping the searcher".
What should you not do after a core update?
Don't make quick fixes. Google warns against changes "like removing some page element because you heard it was bad for SEO", and recommends changes that make sense for readers and last. In practice, avoid these common panic moves:
- Changing dates without changing content. Refreshing a post's date to look new isn't an improvement; see our guide on showing dates on blog posts.
- Mass-deleting posts. Google calls deleting content "a last resort". Our decision table for whether to delete old blog posts applies here too.
- Rewriting everything mid-rollout. You can't tell which change helped, and positions are still moving.
- Blaming AI writing by default. Google judges quality, not the tool; see what Google says about AI-written blog content.
How long until a blog recovers?
From a few days to several months, with no guarantee. Google says some improvements "can take effect in a few days", but it could take "several months" for its systems to confirm a site now produces helpful content, and sometimes that means waiting for the next core update. Smaller, unannounced core updates can also lift improved pages in between.
That timeline is why steady improvement beats a one-off rescue. When a page has lost ground to better answers, the refresh-or-write-new test helps you decide whether to improve it at the same URL or cover a gap with a new post. If you would rather hand that ongoing work to someone else, PilotaSEO has two yearly plans: Autopilot at €322 a year and Growth at €8,250 a year, both shown in the PilotaSEO plans section.
FAQ
Is a core update a penalty?
No. Google says core updates are broad changes that don't target specific sites or pages. A page that drops hasn't necessarily done anything wrong; other pages may simply serve the searcher better.
Should I change my blog during a core update rollout?
Not in reaction to ranking moves. Keep publishing as normal and fix genuine errors, but wait until the rollout ends and a further week has passed before judging any drop.
How do I know when the November 2026 core update is finished?
Check the Google Search Status Dashboard. Its entry for the update, released on 10 November 2026, will be updated when the rollout completes.
Will fixing my content bring rankings back straight away?
Not necessarily. Google says some changes take effect in a few days, while others take several months or the next core update, and there's no guarantee any change will have a noticeable impact.
Sources
- Google Search Central: Google Search's core updates and your website (checked 2026-11-12)
- Google Search Status Dashboard: November 2026 core update (checked 2026-11-12)
- Google Search Status Dashboard: history of ranking updates (checked 2026-11-12)
- Google Search Central: Creating helpful, reliable, people-first content (checked 2026-11-12)