Look at your own organic traffic and enquiries across the announced dates before doing anything. Most updates affect a slice of sites, and the coverage is written for the slice that was affected.

The pattern

An update is announced or detected, the industry writes about it for a fortnight, and a small business owner reads that things have changed significantly.

They look at their site with a sense of foreboding, find nothing obviously wrong, and are left uncertain whether to act.

Some then make changes on the strength of general advice, aimed at a problem they may not have.

Which is the actual risk in these episodes. The update rarely hurts a small local business. The reaction sometimes does.

Why the coverage is disproportionate

Not because anybody is being dishonest.

The people writing about updates work with sites that are affected, because those are the ones that call them, so their experience is genuinely dramatic and genuinely unrepresentative.

Sites that saw nothing produce no articles, no case studies, and no urgent enquiries, so the quiet majority is invisible in the coverage.

Publications also have an incentive to treat every update as significant, since that is the story.

None of that makes the reporting wrong. It makes it written for a different reader from a plumber with an eleven-page site.

Most updates affect a slice

Worth understanding, because it explains who tends to be hit.

Updates are usually aimed at a particular problem: thin content produced at scale, sites making claims in sensitive areas, reviews written without first-hand experience, or a specific manipulation that had been working.

The sites affected are the ones doing that thing, plus some collateral.

A local business with a modest site describing services it actually performs is usually not in the target set, because it is not doing the thing being addressed.

That is not a guarantee, and it is why the check below matters more than the reasoning.

The ten-minute check

The fourth is the one that decides whether anything matters. Traffic moving without enquiries moving is frequently noise; enquiries falling is a real problem regardless of the cause.

Timing is the evidence

The discipline that separates an update effect from ordinary variation.

An update effect appears within the rollout window and persists, rather than dipping for a week and recovering.

A change that started three weeks before the announcement is not the update, and one that began after it finished probably is not either.

Small sites also produce noisy data, so a movement of ten or fifteen percent on modest traffic is frequently nothing at all.

Look for a step rather than a wobble, at the right date, sustained over several weeks.

If you cannot see a step, the honest conclusion is that you were not affected.

A worked example

A firm read about a significant update and spent an afternoon worrying, then two evenings rewriting pages on the basis of advice they had read.

They had never looked at their own numbers.

When they did, organic traffic across the rollout was flat, enquiries were slightly up on the previous year, and nothing in their top ten pages had moved at all.

The rewriting had been unnecessary, and two of the changes made pages worse by removing specific detail in favour of the general advice they had read.

They restored the originals.

Their conclusion was that ten minutes of looking would have saved two evenings and prevented a small self-inflicted problem.

If it did affect you

The response differs from the panic version.

Wait for the rollout to finish before concluding anything, since positions move during it and a mid-rollout reading is unreliable.

Identify which pages lost, rather than treating the site as uniformly affected, because it is almost never uniform.

Read what the update was actually about, from the source rather than the commentary, and ask honestly whether those pages do that thing.

Then improve those pages on their own merits: more specific, more genuinely useful, written from actual experience.

Avoid technical remedies aimed at a problem you have not confirmed, which is how sites acquire changes nobody can explain a year later.

What not to do

Three responses that reliably make things worse.

Changing many things at once, which means you cannot tell what helped when recovery comes.

Buying a product or a service sold specifically as a remedy for the update, which is an industry that appears within days of every announcement.

And rewriting pages that were performing well, on general advice, which is the most common self-inflicted damage.

If the pages that lost are identifiable, work on those and leave everything else alone.

Who the advice is written for

A useful filter when reading anything published in the fortnight after an announcement.

Most of it is written for sites with substantial traffic, several people working on them, and a commercial model that depends on search volume.

Advice about auditing thousands of pages, consolidating content at scale, or restructuring internal linking assumes a site large enough for those to be meaningful operations.

On an eleven-page site describing services you actually perform, most of it has no application, and applying it anyway produces churn rather than improvement.

Read it, notice what size of business it assumes, and discard whatever does not describe yours.

The counter-case

Complacency is a real failure mode too.

Some updates do reach ordinary small business sites, particularly those relying on thin location pages, content produced at volume, or an approach that was always fragile.

A business that ignores every announcement on principle will eventually be affected by one and will notice late.

There is also a difference between a single update and a direction: this year's changes to page experience and mobile evaluation were gradual and cumulative rather than a single event, and dismissing them as noise would have been wrong.

Check your numbers each time, act only when they show something, and pay attention to direction rather than to individual announcements.

The habit

  1. Check your own numbers before reading advice.
  2. Look at enquiries, not only traffic.
  3. Require a step at the right date, sustained.
  4. Wait for the rollout to finish.
  5. Identify which pages actually lost.
  6. Read the source, not the commentary.
  7. Change one thing at a time, or nothing.

Step one is the whole article, and it is the step that gets skipped because reading is easier than looking.

This year's actual changes are covered in what changed on the web this year.


Frequently asked questions

How do I know if an update affected me?

Look at your own organic traffic and enquiries across the announced dates, compare against the same period last year, and check your top ten pages individually.

Why is the coverage so alarming?

Because the people writing work with sites that were affected, since those are the ones that call them. Sites that saw nothing produce no articles, so the quiet majority is invisible.

What counts as evidence of an effect?

A step at the right date, sustained over several weeks, not a dip that recovers. On modest traffic, a ten or fifteen percent movement is frequently nothing.

What should I do if I was affected?

Wait for the rollout to finish, identify which pages actually lost, read what the update was about from the source, and improve those pages specifically.

What makes things worse?

Changing many things at once, buying a product sold as a remedy, and rewriting pages that were performing well on the strength of general advice.

Is ignoring updates safe?

Not entirely. Some reach ordinary small business sites, particularly those relying on thin pages. Check each time, and pay attention to direction rather than individual announcements.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Reading about a major update?

Open your own analytics before you open another article. Ten minutes usually ends the question.

Start a Conversation