Google's next core update is already written.
You just don't know when it ships. And honestly, that's fine — because the businesses that get hurt by core updates aren't the unlucky ones. They're the ones whose sites were already built on shaky ground. The update just made it official.
A core update is Google's way of recalibrating its ranking system — a broad, significant change to how it evaluates which pages deserve to show up. Some sites rise, some drop, most barely move. The ones that consistently survive? They share the same traits. Not tricks. Traits.
Here's what those traits are, and how to build them into your site before the next one lands.
---
Why Chasing Updates Is a Losing Game
Every time Google announces a core update, a wave of speculation follows. People dissect which industries got hit, which signals seem to matter more now, what changed. Some of it is useful. Most of it is noise.
By the time the analysis trickles down to a small business owner, the update has already rolled out and the next one is likely already in progress. Any "fix" you apply is backward-looking by definition.
The better play is to build a site that Google would be embarrassed not to rank. That sounds smug, but it's practical: Google's core goal has never changed. It wants to send its users to pages that load fast, work on a phone, say something genuinely useful, and belong to a business that is clearly real. Every core update is, in some way, a better attempt to enforce that goal.
Build toward the goal, not toward the last set of rules.
---
The Four Fundamentals
1. Load Speed — Faster Than Your Customer's Patience
Speed is not a nice-to-have. If your site takes more than a couple of seconds to load on a phone with a decent connection, many visitors leave before the page finishes loading. Google knows this, measures it, and factors it into rankings.
For a local service business, the culprits are usually the same: images that were never resized before being uploaded, too many third-party scripts (live chat widgets, tracking pixels, and review badges all piling on), or a hosting plan that makes the server work too hard.
You don't need to understand the technical details. You need to know the symptoms. Pull up your site on your phone using mobile data, not your office Wi-Fi. Count slowly to three. If the page isn't loaded and usable by then, you have a problem worth fixing.
What to do: Ask whoever manages your site to run it through Google's PageSpeed Insights tool — it's free, and it produces a plain-language list of what's slowing you down. Prioritize the top three items on that list. Compressing images and removing unused scripts usually gets you most of the way there.
---
2. Mobile Design — Not "Mobile Compatible," Actually Mobile-First
There's a difference between a site that works on a phone and a site that was designed for a phone. Many local service business websites are the former. They squish down awkwardly, the phone number is too small to tap, the menu is a puzzle, and the contact form requires three scrolls and a pinch-zoom to complete.
Google uses the mobile version of your site as its primary basis for indexing and ranking — for most sites. That means your mobile experience is effectively your first impression with Google's crawlers.
The fix isn't always a full rebuild. Sometimes it's as straightforward as making tap targets bigger, increasing font size, stacking columns that shouldn't sit side by side on a small screen, and putting the most important action — call, book, get a quote — high enough on the page that a thumb can reach it without much scrolling.
What to do: Open your site on your own phone. Try to call yourself through the site. Try to submit a lead form. Notice every moment of friction. Write it down. That list is your mobile punch list.
---
3. Clear Calls to Action — Tell Them Exactly What to Do Next
A call to action (CTA) is simply the button, link, or instruction that tells a visitor what step to take next. "Call now." "Book your free estimate." "Get a quote today." Simple.
The mistake most local business websites make isn't having a bad CTA — it's having no clear one, or having five that compete with each other. When a visitor lands on your homepage and doesn't immediately understand what you want them to do, they leave. Not because they don't need you. Because you didn't make it easy.
Your primary CTA should be visible without scrolling — what's visible on screen before the visitor swipes down, which varies by device — on every device. It should be specific. "Get a Quote" beats "Learn More." "Book Online" beats "Contact Us." The more concrete the action, the more likely someone is to take it.
This matters for core updates because a page people leave immediately gives Google little reason to rank it highly. A page people actually interact with tells a different story — and more importantly, it tells a better story to the humans visiting it, which is the whole point.
What to do: Look at your homepage right now. Can you identify your single most important action within three seconds? If not, that's the first thing to fix. Remove competing CTAs or move them lower on the page.
---
4. Genuine Answers — Write for the Person, Not the Algorithm
This is the one that trips up the most businesses, and it's the one Google keeps finding new ways to enforce.
Keyword stuffing — repeating phrases like "best HVAC company in Coral Springs" a dozen times on a page — was never a good experience for the person reading it. Google has gotten progressively better at identifying it, and core updates consistently penalize it.
What works is writing content that actually answers what your customers are searching for. Not just the words, but the intent behind the words. Someone searching "why does my AC smell musty" isn't ready to book a service call yet. They want an explanation. Give them one, clearly and completely. That's the page that earns trust and, eventually, the call.
For a local service business, this plays out in a few specific ways. Your service pages should explain what you do, who it's for, what the process looks like, and what someone should expect. Your FAQ section — if you have one, and you should — should use the actual language your customers use, not industry jargon. Your homepage should answer "what do you do, where, and why should I call you" in the first screen.
None of this requires being a great writer. It requires being honest and specific.
What to do: Read your top three service pages out loud. Ask: does this answer the question a customer would actually type into Google? If it sounds like it was written for a robot, rewrite it for a human. Plain language, specific details, no fluff.
---
The Connective Thread
Notice that none of these four fundamentals are tricks. None of them expire. Load speed, mobile design, clear CTAs, and useful content were the right things to build five years ago and they'll be the right things to build five years from now. That's the point.
Core updates don't rewrite the rules. They tighten enforcement of rules that were always there. A site built on these fundamentals doesn't need to scramble when an update rolls out. It might even pick up ground from competitors who were cutting corners.
---
What to Do This Week
- Test your mobile speed. Open your site on your phone using mobile data. If it's slow, run PageSpeed Insights and ask your developer to address the top three issues it flags.
- Do the mobile friction test. Try to call yourself and complete a lead form on your own phone. Write down every moment of friction you hit.
- Audit your homepage CTA. Identify your single most important visitor action. Make sure it's visible without scrolling on mobile, and remove or demote anything competing with it.
- Read one service page out loud. Check whether it answers a real customer question in plain language. Rewrite any section that sounds like it was written for a search engine.
- Check your FAQ. If you don't have one, start one. Use the exact questions customers ask you on the phone or in messages — word for word if possible.
---
The next core update will come and go. The businesses that hold their positions, or improve them, won't be the ones who figured out some new trick the morning the update dropped. They'll be the ones who built something solid and left it alone to do its job.
Fast. Clear. Useful. Mobile. Hold your website to that standard, and the update noise becomes a lot easier to ignore.