SEO Updates

An SEO update is Google changing how its ranking systems evaluate pages. Most of these are broad core updates that happen a few times a year. When one rolls out, some pages go up, some go down. The mistake I see most often — and made myself — is treating the drop as a punishment that needs an instant reversal. Google's own guidance is clear: do not try to react with quick fixes. Instead, step back and ask whether your page genuinely helps the person who lands on it.

Concretely, I start by pulling the date of the update from the [Google Search](/google-search/) Status Dashboard. Then I go into Search Console and compare the 28 days before the rollout with the 28 days after. I look at total clicks, impressions, and average position for the site as a whole, then for the pages that lost the most. If a page lost 60% of its clicks but its average position only dropped from 3 to 5, that tells me the drop is in click-through rate, not relevance. That points to a title or snippet problem, not a content problem. If the page dropped from position 3 to 15, the content itself is likely misaligned with what users now expect after the update.

Google's [SEO](/seo/) starter guide says the best response is to improve the quality of your content for the user, not for the algorithm. That means checking if the page answers the query better than the new top results. I look at the current SERP for the affected keyword. If the top result now includes a video, a table, or a more recent date, I need to match that standard. The update is not a personal attack; it is a recalibration of what Google considers helpful.

I also keep an eye on [SEO news](/seo-news/) to see whether the update was specifically about product reviews, spam, or something else. Google sometimes announces narrow updates. If you know the target, you can check your pages against that criteria. But for broad core updates, the advice is the same: improve the page, don't delete it.

SEO updates matter when your traffic drops noticeably and you need to decide whether to act or wait. For most sites, the first sign is a dip in Search Console organic clicks. I check every Monday morning. If I see a drop of more than 20% week-over-week, I check the dashboard for confirmed rollouts. If there is an update, I wait until it finishes — typically one to two weeks — before making any changes. Acting during the rollout is pointless because the rankings are still settling.

Once the update is complete, I prioritise the pages that lost the most traffic. I look at the queries that used to drive visits. If the page was ranking for a broad informational query but now the SERP shows more transactional results, the intent has shifted. That page needs a rewrite or a redirect. If the page is still relevant but outdated, I update the date, add fresh statistics, and strengthen internal links from related posts. For example, a page I had on "how to start a blog" lost 40% of its traffic after a core update. I checked the new top results: they all had step-by-step guides with images. My page was a text wall. I added screenshots, broke the content into numbered steps, and improved the [internal linking](/seo-strategy/) from newer posts. Traffic recovered in six weeks.

Technical issues also matter. After an update, Google may recrawl pages differently. I check the affected pages in Search Console's URL Inspection tool. If the page is not indexed, or if the canonical tag points somewhere unexpected, that is the real problem. I also look at page speed and mobile usability. An update can amplify existing technical problems. If your page is slow and the competitors are fast, the update will hurt you more.

I do not rush to change every page. I pick the top three by traffic loss, improve them, and measure again after the next update. If they recover, I apply the same pattern to the next tier. This approach avoids the frantic edits that Google warns against.

My first big mistake was treating every update as an emergency. I would drop everything, rewrite pages, add keywords, and delete old content. That cost me more than the update itself. I deleted a page that had been ranking for "best running shoes for flat feet" because it dropped from position 5 to 20. A month later, the page was gone and the traffic never came back. I should have kept it, updated the product list, and added a comparison table. Google's own documentation says deleting content is a last resort. I learned that the hard way.

Second mistake: copying what worked for someone else. I read a blog post that said adding FAQ schema helped recover from a core update. I added it to every page. It did nothing. The problem was that my content was thin, not that the schema was missing. I wasted time on a tactic that addressed the wrong symptom. Now I only change one thing at a time and measure the effect in Search Console.

Third mistake: measuring vanity metrics. I used to watch my average position obsessively. After one update, my average position improved from 8 to 6, but my clicks dropped by 30%. I had gained ranking for low-volume queries and lost ranking for high-volume ones. Average position is misleading if you do not weight it by impressions. Now I look at clicks and impressions first, and position only as context.

Fourth mistake: ignoring the possibility that the update was not the problem. Sometimes a drop is caused by a technical issue — a server error, a misconfigured robots.txt, or a change in the CMS that broke the page. I once spent a week rewriting content only to discover that a plugin had blocked Googlebot. The update was a coincidence. Check the crawl stats in Search Console before you touch the content. That should be step one, not step three.