A core update is a site-wide reassessment, not a penalty you can appeal. The pages that fall are usually scaled, thin, or written for the crawler instead of a customer. When a drop hits, confirm the rollout dates, find which pages fell, and improve them; deleting everything or re-dating old posts recovers nothing.
What a core update actually does
Several times a year Google reweights how it scores the whole index, and rankings shuffle even for pages nobody touched. Two things follow from that. First, a drop during a core update is not a manual penalty; there is no violation to confess and nothing to appeal. Second, the old "helpful content system" no longer exists as a separate signal — Google folded it into core updates in March 2024, so site-wide content quality now rides along with every core rollout. The judgment is about your site in aggregate, which is why one great article rarely survives on a site carrying three hundred weak ones.
The pages that get hit have a profile
Look at cannabis sites that fell in past updates and the same shapes repeat. Fifty city pages with identical text and a swapped place name. Strain descriptions paraphrased from Leafly with nothing added. Posts that exist because a keyword tool spat out a phrase, not because a customer ever asked the question. Google's own guidance frames the test bluntly: was this made for people, or made to rank? Content summarizing what everyone else already says, at scale, with no first-hand input, is the profile updates keep demoting.
The checks that predict survival
Google publishes self-assessment questions for exactly this, and they work as a pre-publish filter. Would a reader who lands here feel they got a satisfying answer, or need to search again? Does the page show first-hand experience — your inventory, your counter conversations, your state's rules — or could any site have written it? Is there a real author a reader could look up? A dispensary answering those honestly for each post before it ships is doing more update-proofing than any tactic list can offer.
After a drop: improve, don't churn
Wait for the rollout to finish before diagnosing; mid-rollout numbers swing daily. Then pull Search Console, sort by clicks lost, and work the list. Pages with real queries behind them get rewritten deeper. Near-duplicates get consolidated into one strong page with 301s. True dead weight, pages that never earned an impression, can go. What does not work is churn: re-dating posts without changing them, deleting and republishing the same text at a new URL, or rewriting titles weekly. Google has also said recovering sites are mostly reassessed at subsequent core updates, so the realistic timeline is months, and the work should fill that window.
A worked example: sixty strain posts
A dispensary blog with sixty strain writeups loses a third of its organic traffic during a core update. The posts were 400-word paraphrases of the same terpene facts every competitor lists. The fix was consolidation and specifics: the sixty posts became twenty-two, keeping only strains the shop actually stocks, each rebuilt with the store's own data — price per eighth, how fast it sells, what budtenders steer first-timers toward instead, and a photo taken in the store. The removed posts 301ed to their nearest surviving page. Traffic did not move for eleven weeks, then recovered past its old baseline when the next update rolled through. Slow, boring, and repeatable.
Key takeaways
- Core updates reassess sites in aggregate; helpful-content scoring folded into them in March 2024.
- The at-risk profile: scaled near-duplicates, paraphrased strain facts, keyword-tool posts with no reader.
- Run Google's people-first questions against every post before it ships.
- After a drop: wait out the rollout, rank pages by clicks lost, rewrite and consolidate rather than delete.
- Expect reassessment at the next update, not next week, and spend the gap improving section by section.
Frequently asked questions
How do I confirm a drop was a core update?
Check Google's Search Status Dashboard for update rollout dates and lay them over your Search Console traffic. A drop that starts inside a rollout window and hits many pages at once points to the update. A drop on one page usually has a more boring cause, like a lost redirect or an indexing issue.
Should I delete pages that lost rankings?
Not as a first move. Improve the pages that have a real query behind them, consolidate near-duplicates into one stronger page with redirects, and remove only pages that never earned an impression and serve no customer purpose.
Does changing the publish date help recovery?
Not by itself. A new date on unchanged text is churn, and it erodes trust in every date on the site. Update the date when the content changes in a way a reader would notice, and keep an on-page note of what changed.
Is AI-written content why sites get hit?
The tool is not the trigger. Google's guidance says AI-assisted content is acceptable and scaled low-value content is not. Sites get hit for publishing hundreds of pages that add nothing, which is easier to do with AI but was a losing pattern long before it.
How long does recovery take?
Usually until a following core update rolls out, which can mean months. Google has said improvements are largely reassessed on that cycle. Use the window to fix the site section by section rather than shipping one tweak and refreshing Search Console daily.
Want this done for your brand?
We build cannabis & CBD search visibility with full transparency, for dispensaries, brands, and MSOs.
Get a free cannabis SEO audit ›