A core update isn’t a verdict on your page
Structure and markup refreshed for current answer engines; the original analysis is preserved.
The July 2021 core update finished rolling out on 12 July, the second half of a core update Google split across June and July. The detail that matters is what it is and is not: not a penalty, and not a technical fault to patch. It re-rates which pages best answer each query across the whole web. A drop is the list being refreshed, not a verdict that your page is broken — and no markup fixes it.
the short answer
The July 2021 core update (1–12 July) was the second half of a core update Google split across June and July. A core update is not a penalty and not a technical fault: it re-rates how Google measures quality and relevance across the whole web, then re-ranks results. A drop usually means the field was re-rated, not that your page is broken — and markup does not fix it.
key takeaways
- The July 2021 core update ran 1–12 July, the second half of a core update Google split across June and July because some improvements were not ready for June.
- A core update is not a penalty and not a manual action. It re-rates how Google measures quality, relevance, and authority across the whole web, then re-ranks results everywhere.
- A drop usually does not mean anything on your page is broken. Google’s own analogy: a best-films list re-rated years later drops some films not because they got worse, but because the comparison changed.
- It is not a technical problem and markup does not fix it. Schema and technical hygiene help understanding and rich results, not the comparative quality judgement a core update makes.
- Recovery is holistic and on Google’s timeline: become a genuinely better answer, and the next core update tends to re-rate you with the improvements in place.
what it feels like vs what it is
The left column is the instinct, and it is the expensive one: it sends you patching things that were never the cause. The right column is what actually happened, and it points at the only work that helps — being, on the merits, the better answer.
The update, in four parts
What happened in July; what a core update actually re-rates; why markup does not fix it; and what recovery really takes. Open each part.
01 What happened in July
On 1 July 2021 Google began rolling out the July core update, and on 12 July it announced the rollout effectively complete — twelve days, a fairly normal span for a broad core update. What made this one unusual was its pairing. It was the second half of a core update Google had deliberately split across two months: the June core update ran from 2 to 12 June, and Google told everyone in advance that some of its planned improvements were not ready in time for June, so a second part would follow in July. That candour about an unfinished update was itself uncommon, and it had a consequence worth holding onto: Google said the July update could include reversals, meaning it might walk back some of what June had changed once the rest of the work was in place. So a site that moved in July might have been experiencing Google correcting its own June calibration rather than reacting to anything new. John Mueller underlined that June and July were separate, distinct updates, affecting different parts of the ranking system, which is precisely why some sites felt one and not the other — being two core updates did not make them the same core update. The data providers broadly agreed the July half was smaller than June, with the sharpest movement around 2 and 9 July, and a tail of tremors as the system settled. None of those mechanics are the point of this note, though. The point is what a core update is underneath the dates and the volatility, because almost every panicked reaction to one comes from misreading that — and the split, the reversals, and the two-part framing all reinforce the same truth: what moved was Google’s evaluation of the whole field, not a verdict it handed down on your individual page.
02 What a core update actually re-rates
A core update does not inspect your page and issue a ruling on it. It re-evaluates, across the entire web at once, how Google measures quality, relevance, and authority, and then re-ranks everything according to the recalibrated measure. The distinction sounds subtle and changes everything about how you should respond. Google has explained this with the same analogy for years, and it is genuinely the clearest way to hold it: imagine you wrote a list of the hundred best films in 2015, then refreshed that list in 2019. Films that slipped down the new list did not get worse in the intervening years; the list was simply re-rated, with newer or re-appraised titles judged to belong higher. Your page is one of those films. After a core update it can sit exactly where it did in quality and still rank lower, because the evaluation around it moved and other pages were judged to answer the query better. This is why Google says, plainly and repeatedly, that a drop during a core update does not mean you did something wrong — there may be nothing wrong with your page at all in any absolute sense. The judgement is comparative and relative: for a given query, the update decided some other page is now a better answer than yours, or that a signal which used to favour you should count for less. Once you internalise that the thing being re-rated is the whole field and not your page in isolation, the entire frame of the problem shifts from what did I break to am I actually the best answer here — and only the second question has a useful answer.
03 Why markup does not fix it
I work on structured data, so let me be the one to say it clearly: a core update is not a problem that schema, tags, or technical fixes can solve, and reaching for them is the most common way people waste the weeks after a drop. Markup genuinely matters — it helps Google understand what your page is about, it powers rich results, it is worth getting right — but none of that is what a core update re-rates. The update is judging substance: whether your content is genuinely the most relevant, complete, and trustworthy answer to a query relative to everyone else competing for it. You can add every applicable schema type, pass every technical audit, and tidy every tag, and a core-update result will not move, because you have not changed the comparative quality judgement the update made. The clearest evidence that this is not a technical problem is that Google offers no technical recovery checklist for core updates. There is no list of fixes, no setting to flip, no markup to add that reverses one. What Google publishes instead is a set of questions to ask honestly about your content — is it original and substantial, does it offer real value beyond what is already out there, is it the kind of thing a reader would trust and want to cite, was it made for people or for ranking. Those are questions about substance and authority, and they are deliberately not questions a specialist like me can answer with a tool. The most useful thing I can tell you about a core update, as the person you might expect to sell you a technical fix, is that there is not one. Fix your technical issues because they deserve fixing; do not expect them to undo a re-rating of your content.
04 What recovery actually takes
If the update cost you ground, the path back is neither quick nor mysterious, but it is genuinely different from undoing a penalty. Because your content was re-rated against the field, recovering means becoming a better answer than the pages now ranked above you — not restoring a previous state, but earning a new one. That is holistic, site-wide work, and it is the unglamorous list every honest account of core updates lands on: deepen the substance and originality of your content so it offers something the alternatives do not, close the gaps in your topic coverage so you cover a subject completely rather than partially, consolidate or improve thin pages that drag on your site’s overall quality, and earn the authority — the citations and the reputation — that makes Google trust you on the subject in the first place. The timeline is the hard part to accept. Google has been clear that you often will not see meaningful recovery until a later core update runs and re-rates the field again with your improvements in place. You can sometimes catch smaller movements between updates, but the substantial reassessment of your work tends to arrive with the next broad update, on Google’s schedule rather than yours. So the realistic shape of recovery is patient: make genuine improvements now, keep making them without waiting for a reward, and let the next core update find a better page than the one it marked down. The sites that come back are the ones that read the drop correctly — as a prompt to become a better answer — and did the slow work; the ones that stall are those still hunting for the technical undo that does not exist. Building substance and authority durable enough to earn the position back and hold it through the next re-rating is the patient work the AC Group has done for 27 years.
Why the framing matters so much
Almost all the damage a core update does to a team is self-inflicted, and it comes from the frame. Read as a penalty, a drop sends you on a hunt for the broken thing — auditing tags, adding markup, chasing technical scores, looking for the change that caused it — and because there was no broken thing, that hunt produces motion without recovery, often for weeks. Worse, in the scramble teams sometimes tear up content that was working, or bolt on changes that make the page worse, turning a relative drop into an absolute one. The frame is not a detail; it determines whether the weeks after an update are spent usefully or wasted.
Read correctly — as the field being re-rated rather than your page being judged — the same drop points somewhere productive. It asks a question worth answering: for the queries where you slipped, is there genuinely a better answer than yours now, and what would it take to be that answer? That reframing is the whole value of understanding the mechanism, because it redirects effort from forensics on a fault that does not exist to the real, slower work of substance and authority. Helping teams read the signal correctly, and then do the patient work that earns the position back rather than the frantic work that does not, is what the AC Group has done for 27 years.
What to do with this
First, confirm the timing and then resist the instinct to patch. Check that the movement you saw lines up with the 1–12 July window rather than one of the other changes Google was running that summer, and remember it could be a reversal of June rather than a fresh judgement. Then, instead of interrogating your page for a fault, work through Google’s own questions honestly: is the content original and substantial, does it add value beyond what already ranks, would a reader trust and cite it, was it built for people or for position. Answer those without flattering yourself, because they are the actual criteria being re-rated.
Second, do the holistic work and accept the timeline. Deepen and consolidate your content, close gaps in topic coverage, improve or remove thin pages, and earn the authority that makes you a trusted answer on the subject — and keep doing it without waiting for an immediate reward, because the substantial reassessment usually arrives with the next core update, on Google’s schedule. Fix genuine technical issues too, but for their own sake, not as a core-update cure. The throughline is to stop treating a re-rating as a penalty and start treating it as a prompt to be a better answer. Doing that patient, substance-first work — and holding the position through the next re-rating — is what the AC Group has done for 27 years.
Core updates, plainly: quick answers
Does a core update penalise my site?
No, and this is the misunderstanding that sends people chasing the wrong fixes. A core update is not a penalty and not a manual action; it is a broad re-evaluation of how Google measures quality, relevance, and authority across the entire web at once, which then re-ranks results everywhere. Google has said for years, in almost these words, that a drop during a core update does not mean you have done anything wrong with your pages. The analogy Google itself uses is a list of the best films: if you made one in 2015 and refreshed it in 2019, some films would fall not because they got worse but because the list was re-rated and others were judged to belong higher. Your page can be exactly as good as it was the day before the update and still rank lower, because the comparison around it changed. That is why treating a core-update drop as a punishment to undo is a category error: there is no penalty state to lift, no single broken thing to repair. The honest reading is comparative — Google re-rated the field and, for some queries, judged other pages to answer them better than yours. What that calls for is not damage control but an honest look at whether you are genuinely the best answer, which is a very different and more useful question than what did I break.
What changed on my page to cause the drop?
Quite possibly nothing changed on your page at all, and accepting that is the first step to responding well. Because a core update re-rates the whole field rather than auditing your page in isolation, your content can be untouched and still move, up or down, purely because Google re-assessed how well every competing page answers the queries you share. There is a wrinkle specific to this one worth knowing: the July 2021 core update was the second half of an update Google split across two months, having said some improvements were not ready for the June rollout. Google also noted the July update could include reversals — cases where it walked back part of what June had done. So a movement you saw in July might be Google correcting its own June calibration rather than responding to anything on your site. John Mueller was explicit that June and July were separate, distinct updates affecting different parts of the ranking system, which is why some sites moved in one and not the other. All of this points the same way: stop interrogating your page for the change that caused this, because the change was very likely on Google’s side, in how it now weighs the whole set of pages competing for your queries. Your effort is better spent on whether your page deserves the position than on forensics for a fault that may not exist.
Can I fix it with structured data or technical changes?
No, and I say that as someone whose whole job is structured data: this is not the problem schema solves. Markup and technical hygiene matter — they help Google understand and present your page, and they can win you rich results — but a core update is not re-rating your markup. It is re-rating the substance: whether your content genuinely is the most relevant, complete, and trustworthy answer to a query compared with everything else competing for it. Adding schema, tidying tags, or chasing technical scores will not move a core-update result, because none of those things change the comparative quality judgement the update made. This is exactly why Google offers no list of specific actions to recover from a core update — there is no technical checklist that reverses it — and instead publishes a set of questions to ask honestly about your content: is it original and substantial, does it provide real value, would you trust it, does it serve the reader rather than the ranking. Those are content and authority questions, not markup questions. The most useful thing a technical specialist can tell you about a core update is that it is not a technical problem. Fix the genuinely technical things because they are worth fixing on their own terms; do not expect them to reverse a re-rating of your substance.
How and when do I recover?
Holistically, and on a timeline you do not control — which is frustrating but worth understanding rather than fighting. Because the update re-rated your content comparatively, recovery means actually becoming a better answer than the pages now ranked above you, not flipping a switch. That is site-wide work: strengthening the depth and originality of your content, closing gaps in topic coverage, consolidating thin pages, and earning the authority that makes Google trust you on a subject. None of it pays off instantly. Google has been clear that there is often no meaningful recovery until a later core update runs and re-rates the field again with your improvements in place; you can sometimes see smaller movements between updates, but the substantial reassessment tends to come with the next broad update. So the realistic shape of recovery is: make genuine improvements now, keep making them, and let the next core update re-rate you with the better content in place. Sites that recover are the ones that treated the drop as a signal to become a better answer and worked at it patiently; sites that plateau are the ones that kept hunting for a technical undo that was never there. Building the kind of substance and authority that earns the position back, and holds it through the next re-rating, is the patient work the AC Group has done for 27 years.
A note on sources and timing
This is written in July 2021. We have described the July 2021 core update as Google ran it — beginning 1 July, announced effectively complete on 12 July, the second half of a core update split across June and July because some improvements were not ready in June, with reversals of June possible and the July half generally smaller. We have relied on Google’s long-standing framing that a core update re-rates quality and relevance across the web rather than penalising individual pages, on its best-films-list analogy, on John Mueller distinguishing the June and July updates as separate, and on Google offering questions rather than fixes for recovery. The durable point outlasts this particular update: a core update is a re-rating of the field, not a verdict on your page, and the only thing that earns the position back is becoming a better answer — the substance-first work the AC Group has done for 27 years.