We Added Schema Markup to 47 Local Websites — What Happened to Rankings

If your Google Business Profile is optimized, your reviews are strong, and you've even built out location pages, but you're still not ranking in every city you serve, this video is going to show you exactly why. After adding schema markup to 47 local business websites through our agency, the same pattern showed up every single time. Google wasn't ranking these businesses because it couldn't confidently connect their website to their GBP signals. And without that connection, all the work they'd done on their GBP — all those reviews, all those posts, all that optimization — wasn't being amplified by their website the way it should be. We're talking 80 to 100 qualified calls per month sitting on the table, going to competitors who had figured this out. Today, I'm breaking down the exact schema setup we added to those 47 websites, the specific fields that made the difference, and what happened to their rankings when we did it.

If you're new here, welcome to The Branding Agency channel, your source for local SEO that actually works. I'm your host, Steve, and thanks so much for making us part of your marketing education today. We're free on YouTube, so please hit that subscribe button right now. And one of the fastest ways to help us grow is by dropping a comment below — tell me which tactic you're most excited to implement. I personally read and reply to every single one.

Let me start with a plain-English explanation of what schema actually is, because most content about this makes it way more complicated than it needs to be. Schema is a direct message you send to Google. That's it. When Google crawls your website, it's reading your content and trying to interpret what your pages are about. Schema removes the guesswork. It lets you explicitly tell Google: this page is for this specific service, in this specific city, for this specific type of business. Most local SEO advice focuses on content and backlinks. Schema is the silent layer underneath all of that — it tells Google how to interpret everything else on your page.

And here's why this matters right now, specifically. Google's May 2026 core update is actively rolling out. Local directories are losing near-me rankings right now — rankings they've held for years. The businesses picking up that ground are the ones with clean, consistent schema signals. So the timing on this couldn't be better. Here are the four things we're covering today: one, the wrong schema type and why it's hurting more than it's helping; two, the correct LocalBusiness schema structure field by field; three, the one field almost every site skips and what it costs them; four, the trust loop between your schema and your GBP.

Of the 47 sites we audited, the majority had one of two things: either no schema at all, or Organization schema. And here's the problem with Organization schema — it tells Google you're a business. That's it. It doesn't tell Google what you do, where you do it, or who you serve. It's essentially handing Google a blank business card and expecting it to figure out the rest. The number one mistake I see here is Organization schema copied and pasted across every page on the site — same block, every page — which means every single page is sending Google the exact same generic signal: "we're a business," with no location, no service, no specificity at all.

What you need instead is LocalBusiness schema. This is a completely different schema type, and it's the one that gives you the fields you actually need to tell Google what city you serve, what service this page covers, and how your website connects to your Google Business Profile. This is how enterprise SEO agencies structure websites — not one Organization block for the whole site, but one unique LocalBusiness block per page, specific to that page's location and service.

Let me walk you through the four non-negotiable fields inside LocalBusiness schema — the ones that showed up as missing or wrong in nearly every audit we ran. Field one: this is where most people stop at "local business," but you can go deeper. Google recognizes specific business types like plumber, HVAC business, attorney, medical business. The more specific your type, the stronger the signal. Instead of telling Google you're a local business, you're telling Google you're a plumber — and that directly ties your schema to the search intent your customers are using. Field two, areaServed: this is the ranking signal most local websites are completely missing, and I'll give it its own section in a minute because it's that important. Field three, serviceType: this names the exact service the page covers — HVAC installation, emergency plumbing repair, family law consultation — which ties your schema to the specific queries you want to rank for. Field four, address and NAP data: your business name, address, and phone number, and they must match your Google Business Profile exactly. Not approximately. Exactly.

Now here's the part that kills a lot of location page campaigns. People build out location pages — which is the right move — and then copy the same schema block across every page with just the city name swapped. Same business type declaration, same service type, same NAP, only the city name changes. Google sees that the same way it sees duplicate content: it filters it. You've done the work, you've built the pages, and the schema is making them invisible. Every location page needs its own unique schema block — unique business type declaration where applicable, unique service type for that page's service, unique service area declaration for that location. This tells Google and customers: we're local to Concord, we know Concord, we actively serve Concord. That's a completely different signal than a copy block with a different city name dropped in.

Let me talk about areaServed specifically, because this single field was missing on nearly every site we audited, and adding it moved rankings for multiple clients. areaServed is how you explicitly declare to Google every city you actively serve — not a general region, not "greater metro area," but each city listed individually, spelled exactly the way it appears in your Google Business Profile service area. What this means for service-area businesses is significant: you don't need a location page for every single city you serve to start showing up in those cities. areaServed lets you declare your full service footprint at the schema level, and Google uses that to determine which searches your pages are eligible to rank for.

What I see most often is the areaServed field left completely blank, or filled in with something like "Southeast United States" — that tells Google nothing specific. What you do instead is list every city you actively serve, one per entry, consistent with your GBP service area: Concord, Charlotte, Kannapolis, Harrisburg, spelled out individually in the same format they appear on your GBP. Managing 47-plus businesses across different industries and markets, I've seen what works and what destroys rankings. Adding areaServed alone moved local pack appearances for three of our clients within 45 days of implementation — not because we changed their content, not because we built new links, just because we finally gave Google the explicit geographic declaration it needed to rank those pages with confidence.

Here's something most schema tutorials don't cover, and it cost several of our clients rankings before we caught it. Even if your schema type is right and your fields are filled in correctly, Google cross-references your schema and NAP data against your Google Business Profile — your business name, your address, your phone number. Any mismatch breaks the trust signal between your website and everything Google already knows about your business. I'm not talking about major discrepancies. I'm talking about "St." on your schema and "Street" on your GBP. A local direct number on your website and a tracking number on your GBP. "The Branding Agency LLC" in your schema and "The Branding Agency" on your GBP. Small things that look harmless but break the connection Google is trying to make.

Here's the three-point consistency check I run on every audit. Business name: identical across schema, GBP, and every citation. Address: same format, same abbreviations everywhere. Phone number: same number, no tracking number discrepancies between your site and your GBP. When these three match perfectly, Google treats your website and your Google Business Profile as one unified local authority signal. Your website amplifies your GBP, your GBP amplifies your website — that's the trust loop, and schema is what closes it. Get it right and every other local SEO signal you've built gets stronger. Get it wrong and your website and GBP are working independently instead of together.

Here's a quick action you can take today. Go to Google's Rich Results Test — it's a free tool, I'll reference it in the description. Paste in one of your location page URLs and run the test. There are three outcomes. One: LocalBusiness detected with fields populated — you're in good shape; check that your business type is specific, your areaServed is filled in, and your NAP matches your GBP. Two: Organization schema detected — your schema type is wrong; switch it to LocalBusiness and add the four fields we covered. Three: no structured data detected — your pages are completely invisible to Google's schema parser, and everything your GBP has built is getting zero amplification from your website. Run this test on your top three location pages this week.

Let me share what we actually found across these 47 audits. Client one had Organization schema across all location pages; we switched to LocalBusiness with specific business type declarations and areaServed populated for each service area, and within 60 days the business started appearing in local pack results for four cities it had never ranked in before — same GBP, same reviews, same content, the only change was the schema. Client two had LocalBusiness schema in place, but the NAP data didn't match the GBP — the address format was different and the phone number was a tracking number; we fixed the consistency across schema, GBP, and citations, and map pack visibility improved within 30 days as call volume from organic started climbing. Client three had no schema at all on any page; we built out full LocalBusiness schema with areaServed, specific @type, and consistent NAP, and GSC impressions jumped in the first reporting cycle. The common thread across all 47: Google wasn't confidently connecting these websites to their GBP signals. Schema is the connector — the explicit trust bridge between everything on your website and everything Google already knows.

One more thing worth knowing before we close out. The same LocalBusiness schema signals that tell Google to rank you are the same signals AI tools — ChatGPT, AI Overviews, Perplexity — pull from when recommending local businesses. Fix your schema and you're not just positioning yourself for Google; you're building the foundation for AI search too. Same work, done once, sets you up for both. Let's recap: wrong schema type, switch from Organization to LocalBusiness; specific business type declaration; service area declaration for every city; service type matching the page content; and your name, address, and phone consistent with your GBP. If you want us to help you build a properly structured local website with schema built in from the ground up and location pages that rank in every city you serve, that's exactly what we do at The Branding Agency.