Most of what Google knows about your business it has to figure out for itself — reading your pages, guessing at your structure, trying to determine whether you're a plumber in Nanaimo or a restaurant in Victoria. Schema markup is how you stop making Google guess and start telling it directly. Here's what that means in practice — and what it can do for your search results.
What schema markup actually is
Schema markup — sometimes called structured data — is a piece of code added to your website that describes your business to Google in a language it understands without ambiguity. It's not something visitors see when they load your page. It lives in the source code, and its only audience is search engines.
The code follows a shared vocabulary called Schema.org, which Google, Bing, and other search engines agreed on together. When you add it to a page, you're essentially labelling your content: "this is a business name," "this is a phone number," "this is a list of frequently asked questions," "this is a service offered in this city." Instead of Google reading a paragraph and inferring what it means, you're handing it a clear, machine-readable declaration.
Think of it this way. Without schema, Google reads your homepage like a stranger reads a flyer — they can usually figure out what you do, but they might miss things, misread context, or simply not trust what they've inferred. With schema, you're handing that stranger a completed form. It's one of the highest-value fixes I flag in a local SEO audit. Everything is labelled. Nothing is guesswork.
For a local Vancouver Island business, this matters more than it might for a national brand. Local search is competitive on a very small scale. The difference between appearing in the local map pack or not, between showing up with rich results or a plain blue link, often comes down to how clearly your website communicates who you are and where you operate.
What proper schema looks like in search results
The most visible payoff for schema is what Google calls rich results — enhanced listings in search that include extra information beyond the standard title, URL, and description. These take up more space on the page, they look more trustworthy, and they give the searcher useful information before they even click. Here are the ones that matter most for a local business.
FAQ snippets. When a page includes valid FAQPage schema, Google can expand it directly in the search results — showing two or three of your questions and answers right in the listing. A searcher looking for "SEO audit Campbell River" might see your result with expandable answers already attached. They're reading your content before they've visited your site.
Breadcrumb trails. BreadcrumbList schema tells Google the navigational hierarchy of a page — Home › Locations › Campbell River SEO Audit — and Google often displays this trail under the result title instead of the raw URL. It's cleaner, it communicates your site's structure at a glance, and it builds immediate trust that the page is exactly what the searcher is looking for.
Business information in the knowledge panel. LocalBusiness schema feeds directly into the information Google displays in the map pack and the right-hand knowledge panel — your name, address, phone number, hours, category, and service area. Without it, Google assembles this picture from scattered signals across your site and other directories. With it, you're giving Google authoritative data straight from the source.
Review stars. Review schema attached to specific services or pages can trigger star ratings to appear in search results. For a service business, a result showing 4.9 stars next to the title is meaningfully more compelling than a plain listing — and it costs no advertising spend.
The types of schema that matter for a local business
Schema.org defines hundreds of types, but for a local small business the list of genuinely useful ones is much shorter. Here's what I look for when auditing a Vancouver Island business site.
LocalBusiness (and its subtypes). This is the foundation. It declares your business name, address, phone number, hours, service area, and what type of business you are. The @id field — a stable URL that uniquely identifies your business across the web — is particularly important and consistently missing from the sites I audit. Without it, Google can't confidently link your website entity to your Google Business Profile entity and your citation mentions elsewhere. It's a small field that does a lot of trust-building work.
"@type": "LocalBusiness",
"@id": "https://yourdomain.ca/#business",
"name": "Your Business Name",
"telephone": "+12501234567",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main St",
"addressLocality": "Nanaimo",
"addressRegion": "BC",
"postalCode": "V9R 1A1",
"addressCountry": "CA"
}FAQPage. If your site has a FAQ section — or if you answer common questions anywhere in your page content — FAQPage schema is worth adding. Each question and answer is marked up explicitly, and Google can choose to surface these in search results as the expandable rich snippet shown above. It increases your result's footprint on the page and gives searchers a preview of useful information before they click. I add this to every location page and service page I work on.
BreadcrumbList. One of the easiest wins and one of the most commonly absent. Every page should have it. It takes ten minutes to implement and pays off in cleaner, more navigable-looking search results that tell the searcher exactly where the page sits within your site.
Service. If you have individual service pages — which you should — Service schema lets you declare each offering explicitly, including its name, description, price (if applicable), and area served. For a trades business or professional service, this helps Google match your service pages to specific search queries far more precisely than page content alone.
Person. For a solo operator or small agency where the individual behind the business is part of the brand, Person schema tied to your founder or owner page builds what Google calls entity authority — essentially, a verifiable connection between you as an individual, your business, and the work you do. It matters more for trust signals than for rankings directly, but trust signals do affect rankings over time.
WebPage and WebSite. These tie everything together — declaring each page's identity, its relationship to the overall site, and the site's relationship to the business entity. When every page has a WebPage schema pointing to the same WebSite @id, and the WebSite @id connects back to the LocalBusiness @id, Google has a coherent, consistent picture of your entire online presence — not a scattered collection of pages it's trying to make sense of.
What happens when schema is wrong — or missing
Missing schema is a missed opportunity but not a ranking penalty on its own. What it costs you is the visibility advantages described above — richer results, more confident local signals, the @id connections that build entity trust. In a market where competitors aren't doing it either, the absence is less costly. In a market where one or two competitors are doing it well, the gap can be significant.
Broken schema is a different matter. A trailing comma in a JSON-LD block, a mismatched quote, a malformed URL in an @id — any of these will cause the entire schema block to fail silently. Google reads the page, ignores the broken structured data, and moves on. The page looks fine to a visitor; the schema problem is completely invisible unless you check the source code or run it through a validator. I find broken schema on a significant percentage of the sites I audit — usually introduced during a site update, a theme change, or a copy-paste of someone else's example code that wasn't cleaned up properly.
Inconsistent schema is subtler but also common: a phone number in the schema that doesn't match the footer, an address @id that changes between pages, a business type declared as "Organization" on one page and "LocalBusiness" on another. These inconsistencies don't break anything dramatically, but they erode the entity signals Google relies on to confidently associate your website with your physical business. The more consistent and coherent your schema is across every page of the site, the more clearly Google understands that everything it's seeing belongs to one real business in one real place.
Schema as part of a full audit
When I audit a Vancouver Island business site, schema is one of the areas I review systematically on every page — not just the homepage. I check whether the right types are present, whether the @id values are consistent across pages, whether the JSON-LD is syntactically valid, and whether the declared information actually matches what's on the page and in the Google Business Profile. I validate every block with a parser before I consider it done.
It's rarely the most dramatic finding in an audit — organic visibility gaps and thin service pages usually carry more weight. But it's one of the most consistently underdone areas, and fixing it is straightforward once you know what's missing. It's also cumulative: every page you get right adds to the coherent picture Google builds of your business over time.
If your site has never had a structured data review, the SEO audit services page explains what a full audit covers, and the how it works page walks through the process step by step. If you're specifically wondering whether your schema is doing the job it should be, that's exactly the kind of thing an audit will tell you — clearly, in plain English, with specific fixes prioritised in order of impact.
For more on what an audit actually examines from top to bottom, the what is an SEO audit article covers the full scope — and for the broader picture of why local signals matter so much for a Vancouver Island small business, why local SEO matters is worth a read alongside this one.
Written by Michael Perks — Island Rank Canada, Duncan, BC. I do plain-English SEO audits for small businesses across Vancouver Island. If your schema situation is unclear, the contact page is the right next move.