Fast answer
Yes, a small business should have schema markup — but not because it improves rankings, because it doesn't: Google's own documentation makes no ranking promise for structured data, and even a structured-data penalty affects rich-result eligibility, not ranking. What schema actually does is state your key facts — business type, services, address, hours, reviews — in a format machines read directly, which makes you eligible for enhanced search listings and, increasingly more important, legible to the AI answer engines that don't guess well. For most small businesses four types cover it: LocalBusiness (using your specific trade subtype), Service, Review or AggregateRating on genuinely real reviews, and Breadcrumb. It's cheap, it's one-time work rather than a subscription, and the honest frame is insurance and eligibility — not a rankings lever.
Somewhere in the proposal an agency sent you, there's a line item that says "schema markup implementation," and it's priced like it matters. Or you've read that structured data is the secret weapon your competitors are using. Either way, you want a straight answer before you pay for it: does a small business actually need this?
Yes — but not for the reason it gets sold. Schema markup doesn't improve rankings, and that isn't my opinion: Google's own documentation makes no ranking promise for structured data anywhere, and even the penalty for abusing it removes rich-result eligibility rather than touching your rank. What schema actually does is state your key facts — what kind of business you are, what you sell, where you are, when you're open, what your reviews say — in a format machines read directly instead of inferring. That buys you two real things: eligibility for enhanced search listings, and legibility to the AI answer engines that increasingly sit between you and your customers. It's cheap, it's one-time work, and it's worth having — as insurance and translation, not as a rankings lever.
Fast answer. Yes — as one-time structural work, not a monthly service. It won't move rankings (Google's docs promise "eligibility," never rank). It makes your facts machine-readable: four types cover most small businesses — LocalBusiness (your trade's subtype), Service, real-review Review/AggregateRating, Breadcrumb.
What Schema Markup Actually Is, in Thirty Seconds
Schema markup — structured data — is a block of labelled facts embedded in your page's code, invisible to visitors, written in a vocabulary (schema.org) that search engines and AI systems agreed to share. Where a human reads "Family-owned plumbing in Grande Prairie since 2011" and understands it, a machine reading structured data doesn't have to interpret anything:
{
"@type": "Plumber",
"name": "Example Plumbing Ltd.",
"telephone": "+1-780-555-0123",
"areaServed": ["Grande Prairie", "Sexsmith", "Clairmont"],
"openingHours": "Mo-Fr 07:00-18:00"
}
That's the entire trick. No hidden signals, no optimization cleverness — just your page's facts, restated so nothing has to guess at them. Which is exactly why it's valuable and exactly why it's oversold: removing ambiguity is genuinely useful to every machine that reads your site, but it's a very different thing from ranking higher, and the sales pitch usually blurs the two.
What Google Actually Promises — and What It Doesn't
This is the part worth reading before you pay anyone, because Google's own language is unusually clear once you look at it.
The promise is eligibility, not results. Google's structured data documentation says markup "can enable search results that are more engaging" and that including required properties makes a page "eligible for appearance… with enhanced display." Can enable. Eligible. Nowhere in the documentation is structured data called a ranking factor, and no rich result is guaranteed — Google decides whether to show one regardless of how correct your markup is.
The penalty proves the point. If your markup violates the guidelines, Google can issue a structured-data manual action — and its documented effect is that your pages lose eligibility for rich results, without affecting web ranking. Read that twice: even the punishment for schema abuse doesn't touch rank, because schema and ranking are separate systems. Anyone selling markup as a rankings play is selling a connection Google explicitly doesn't draw.
The map pack runs on different fuel entirely. For a local business, the result that matters most — the map pack — is ranked on relevance, distance, and prominence, which in practice means your Google Business Profile, your reviews, and how well your site matches what was searched. LocalBusiness markup helps Google read your details correctly and connects your site to your profile cleanly; it does not move you up the pack. I've made this caveat before in the contractor website checklist, and it's the single most common overpromise I see in schema line items.
So why bother? Because ambiguity has a cost even when rank isn't the currency. A machine that knows — rather than guesses — that you're a Plumber serving these towns with these hours is a machine that can show your hours in a listing, attach your reviews to the right business, cite you for the right kind of question, and never confuse you with the similarly named company two provinces over. Small businesses are exactly the ones that can't afford to be misread, because nobody's spending authority to correct the record.
The FAQ Lesson: What 2026 Taught Us About Schema's Real Value
On May 7, 2026, Google retired FAQ rich results — the expandable question-and-answer dropdowns under search listings — with the Rich Results Test and Search Console support following over the summer. Thousands of sites had added FAQ markup specifically to win that feature. If the SERP decoration was the whole reason, that markup is now pointless.
And FAQ is not an isolated case — it's the pattern. Google's own changelog reads like a slow demolition of rich-result features: FAQ results restricted to government and health sites back in September 2023, HowTo results retired the same year, five more types (course info, estimated salary, learning video, special announcements, vehicle listings) de-documented in September 2025, practice problems gone by January 2026. Any schema strategy built on winning a specific SERP decoration is building on rented ground.
But Google's own announcement contained the more interesting sentence: it continues to use FAQ structured data to understand pages. The feature died; the reading didn't. And that's the honest summary of where schema's value has moved — away from decorating a search listing, toward being legible to every machine that reads your site, including the AI answer engines that don't render JavaScript and don't guess well.
We practice this split on our own site: our marketing pages don't carry FAQ markup anymore — there's no search feature left to earn, so it's weight without work. Our articles keep it, because real questions with direct answers are precisely the format answer engines lift, and that machine audience didn't go anywhere. That's the decision framework in miniature: not "does this markup exist," but "which machine is going to read it, and for what."
What the AI Companies Actually Say About Schema
"Schema helps you get cited by AI" is on its way to becoming the new version of "schema helps you rank" — so it's worth pinning down what the companies themselves have actually said, because it's more specific and more honest than the pitch.
Google, on its own AI features: no special markup exists. Google's documentation for appearing in AI Overviews and AI Mode says it outright: "There are no additional requirements to appear in AI Overviews or AI Mode," and — the sentence that should end a few sales calls — "There's also no special schema.org structured data that you need to add." If someone is selling you an "AI schema package" for Google's AI features, Google's own docs say the product doesn't exist. The same page still lists keeping structured data matched to visible text among the fundamentals — the ordinary markup keeps mattering; a magic AI variant of it doesn't.
Microsoft, on Copilot: standard schema helps their AI read you. Bing's principal product manager, Fabrice Canel, confirmed on stage in 2025 that Microsoft uses schema markup to help its LLMs understand content. That's the strongest direct statement any AI-search operator has made — and note what it endorses: the same ordinary structured data you'd add anyway, not anything AI-specific.
Everyone else: silence, plus one structural fact. OpenAI, Anthropic, and Perplexity publish crawler documentation but say nothing about how — or whether — their systems use schema. What's verifiable is narrower and still useful: their crawlers fetch your server-rendered HTML, and JSON-LD markup rides inside it as plain readable text. A machine that reads your page gets your labelled facts along with your prose. That's a reason to have clean markup in the HTML; it is not a documented citation lever, and anyone quoting one for these engines is guessing.
The through-line is the same as the Google story: schema buys legibility, not leverage — for AI systems exactly as for search. The honest case never needed inflating.
The Four Types a Small Business Actually Needs
The schema.org vocabulary has hundreds of types. A small service business needs about four, and precision matters more than quantity.
| Type | What it states | Worth it because |
|---|---|---|
| LocalBusiness — your trade's subtype | Who you are, where, when, serving which towns | The core record everything else attaches to |
| Service | The work you actually sell | Connects each service page to a machine-readable offer |
| Review / AggregateRating | Reviews that genuinely appear on the page | Attaches real reputation to the right business |
| Breadcrumb | How your pages relate | Makes your site's structure explicit in listings |
Use the specific subtype, not the generic one. LocalBusiness is fine; Plumber, Electrician, RoofingContractor, or HVACBusiness is better, because it answers the machine's first question — what kind of business is this? — with no interpretation required. Our own audit tool checks for exactly this, and the generic-when-specific-exists pattern is one of the most common things it flags.
Only mark up reviews that exist. Google's policies require structured data to be "a true representation of the page content," and marking up invisible content is explicitly prohibited. Review markup on real, visible testimonials: good. A 4.9 aggregate rating with no reviews anywhere on the page: a manual action waiting to happen — and the trust cost of getting caught inventing reviews is far worse than the penalty.
Match the markup to the page. LocalBusiness belongs on the pages that describe the business (home, contact); Service on each service page; Review where the reviews are. A machine reading markup that contradicts the visible page doesn't average the two — it stops trusting the markup.
Mistakes That Make Schema Worthless — or Worse
Markup describing things that aren't on the page. The cardinal violation, per Google's own policies. Every fact in your structured data should be verifiable by a human looking at the same page.
Schema that only exists after JavaScript runs. If your markup is assembled in the browser, the crawlers that don't execute JavaScript — which includes most AI answer engines on first pass — never see it. Structured data belongs in the server's HTML response. This is the same server-rendering argument that applies to everything else machines read on your site.
Paying monthly for static facts. Your business type, address, and hours change rarely. Schema for a small site is one-time structural work with occasional updates — a recurring "schema management" fee on a site that never changes is a subscription to nothing.
FAQ-stuffing service pages for a feature that's gone. Bolting question blocks onto every page was always a SERP-decoration play; since May 2026 the decoration doesn't exist. Real questions with real answers still earn their place — on content pages, for the machine audience that reads them.
Trusting that it's there because someone said so. Markup is invisible, which makes it easy to bill for and easy to botch — invalid JSON is silently ignored by search engines, so broken schema fails without any error you'd ever see. Validate with Google's Rich Results Test, or run the free check — it parses your structured data from the live page and tells you what a machine actually found.
How to Get It Without Getting Taken
If your site runs on a mainstream platform, you may be closer than you think: most modern builders and SEO plugins generate LocalBusiness and Article markup automatically once your business details are configured — verify what's already there before paying anyone. If you're having a site built, schema belongs in the build, not as an add-on line item: it's the same facts the pages already state, restated in JSON-LD, and takes an experienced builder hours, not months. Our own builds ship it by default for exactly that reason.
Sources: Google Search Central — Introduction to structured data ("can enable," "eligible" — no ranking claim appears in the documentation); Google Search Central — Structured data general policies (markup must be a true representation of visible content; a structured-data manual action removes rich-result eligibility without affecting web ranking); Google Search Central — documentation updates (FAQ rich results deprecated effective May 7, 2026 with documentation removed that June; FAQ restricted to government/health sites September 2023; course info, estimated salary, learning video, special announcement, and vehicle listing types de-documented September 2025; practice problems removed January 2026); Google Search Central — AI features and your website ("no additional requirements… no special schema.org structured data that you need to add"); Search Engine Land — Microsoft Bing/Copilot use schema for its LLMs (Fabrice Canel, SMX Munich 2025); schema.org (the LocalBusiness subtypes). OpenAI, Anthropic, and Perplexity publish crawler documentation but no guidance on structured data — that absence is reported here as an absence, not filled in. Current as of August 2026.
Where to Start
Ask one question of any schema pitch: which machine is going to read this markup, and what will it do with what it reads? If the answer is a real one — Google attaching your hours and reviews to the right listing, an answer engine citing your service page — the markup earns its place. If the answer is "it helps rankings," you've learned something about the pitch.
The practical path: check what your site already emits with the free Visibility Check — it parses your live page's structured data and reports what's found. If you're missing the basics, the four types above are an afternoon of work for whoever built your site. How schema fits the wider machine-readability picture is covered in what AI answer engines read on your website and how small businesses actually get found on Google — and SEO Foundations is the service where we build all of it in from the start, schema included, no monthly line item required.
Frequently asked questions
- Does schema markup improve Google rankings?
- No — and Google says so. Its structured data documentation promises that markup 'can enable' richer search appearances and makes pages 'eligible' for them; nowhere does it call structured data a ranking factor. Even the penalty for abusing it — a structured-data manual action — removes rich-result eligibility without affecting ranking, which tells you how separate the two systems are. Schema makes your listing eligible to look better and your facts easier for machines to read. Ranking comes from the content, links, and local signals the rest of your site earns.
- Which schema types does a small local business actually need?
- Four cover most of it: LocalBusiness — ideally the specific subtype for your trade, like Plumber, Electrician, RoofingContractor, or HVACBusiness — with your name, address, phone, hours, and the areas you serve; Service for the work you sell; Review or AggregateRating only on reviews that genuinely exist on the page; and Breadcrumb so your site's structure is explicit. Beyond those, add a type only when the content genuinely exists — markup describing things that aren't on the page is a guideline violation, not a bonus.
- Is it still worth adding FAQ schema now that Google dropped FAQ rich results?
- On the right pages, yes — but for a different reason than before. Google retired FAQ rich results on May 7, 2026, so the markup no longer earns the dropdown in search listings. But Google's own announcement says it continues to use the structured data to understand pages, and question-and-answer pairs are exactly the format AI answer engines lift. The honest split: don't add FAQ markup expecting a search feature; do keep it where real questions and answers live and being read by machines matters — articles and guides more than service pages.
- Can schema markup get my site penalized?
- Only if it lies. Google's structured data policies require markup to be a true representation of visible page content — marking up reviews that don't exist, star ratings you invented, or content readers can't see can draw a structured-data manual action. Notably, that penalty removes your eligibility for rich results rather than lowering your rankings. The rule of thumb is simple: markup describes what's on the page; it never adds anything that isn't.
- Is there special schema markup for AI search or AI Overviews?
- No — and Google says so directly. Its documentation for AI Overviews and AI Mode states there are no additional requirements and 'no special schema.org structured data that you need to add.' Microsoft has confirmed the opposite side of the same coin: Bing uses ordinary schema markup to help its LLMs understand content. OpenAI, Anthropic, and Perplexity document nothing about schema either way — what's verifiable is that their crawlers read your server HTML, and JSON-LD markup is readable text inside it. So the standard types done well are worth having for every machine that reads your site; an 'AI schema package' is a product Google's own docs say doesn't exist.
- Do I need to pay someone monthly for schema markup?
- Almost never. For a typical small-business site, schema is one-time structural work — your business facts change rarely, and the markup only needs updating when they do. Most modern platforms and SEO plugins generate the common types automatically once configured. A monthly line item for 'schema management' on a five-page site that never changes is a fee for work that isn't happening. Pay once to have it done right, verify it with Google's Rich Results Test, and revisit it when your services or locations change.
