Schema markup is one of those topics where the advice online is either far too vague — “add schema to boost your rankings” — or so technical it assumes you write JSON for a living. Neither helps if you run a business and just want to know whether this is worth anyone’s time.
Here is the short version. Structured data does not make Google rank you higher. What it does is let Google understand what a page is about with far less guesswork, and in some cases display your listing differently in the results. Those two things are worth having. Thirty different schema types on a five-page website are not.
What structured data actually does
A web page is written for humans. A search engine reading it has to infer what everything means — that a string of digits is a phone number, that “Closed Sundays” describes opening hours, that a name in bold near the top is the author rather than a client.
Structured data removes the inference. It is a block of code, usually JSON-LD, that sits in the page and states plainly: this is a LocalBusiness, its telephone is this, its address is this, it opens at these times. Google’s own documentation is explicit that this markup helps it understand the content, and that it can make a page eligible for richer presentation in search results.
Note the word eligible. Adding markup does not guarantee a rich result. Google decides whether to show one. Anybody promising a specific visual outcome from adding schema is overselling it.
The three types most small businesses actually need
The vocabulary at Schema.org runs to hundreds of types. Almost none of them apply to a typical service business. In practice the useful set is small.
LocalBusiness — the one that matters most
If you serve customers from a physical location or a defined service area, this is the foundational one. It states your name, address, phone number, opening hours, and the geographic area you cover.
Its real value is consistency. Google is cross-referencing what your website says against your Google Business Profile and every directory listing you appear in. When those disagree — an old suite number, a phone number from two offices ago — that is friction. LocalBusiness markup gives a clean, machine-readable statement from the source Google trusts most, which is your own site.
One rule: the markup must match what a visitor can see on the page. Marking up an address that appears nowhere on the site is exactly the kind of thing Google’s structured data guidelines warn against.
Organization — for the entity, not the location
Organization describes the business itself rather than a place you can visit: legal name, logo, official website, and the social profiles you actually control. It is what feeds the knowledge panel that sometimes appears when someone searches your brand name directly.
This one matters more than it used to, because AI assistants increasingly need to establish that a business is a real, identifiable entity before citing it. A clear Organization block is a cheap way to make that unambiguous.
FAQPage — useful, but only when the questions are real
FAQ markup describes a genuine question-and-answer section on the page. Used honestly it helps, particularly now that so much search is conversational — someone asking an assistant a question is more likely to surface a page that has plainly answered that exact question.
Used dishonestly it is a liability. Inventing questions nobody asks, stuffing keywords into answers, or marking up an FAQ that does not visibly exist on the page all violate the guidelines. The markup has to describe what is genuinely there.
What most small businesses do not need
Product markup, unless you sell products directly on the site. Recipe markup, obviously. Event markup, unless you run events. Review markup applied to your own business by yourself — Google restricts self-serving review snippets, and this is a common way sites end up with a manual action rather than a rich result.
Adding types speculatively does not help. It creates more surface area to keep accurate, and inaccurate markup is worse than none.
How to check what you already have
Most WordPress sites already output some structured data without anyone deciding to. SEO plugins add it automatically, themes add their own, and page builders sometimes add a third set. The common result is duplicate or contradictory blocks — two different Organization entries claiming different names, for instance.
Two checks are worth running before you add anything:
- Google’s Rich Results Test — enter a URL and it reports which structured data Google detects and whether any errors would prevent a rich result.
- The Enhancements reports in Search Console — these show errors and warnings across your whole site rather than one page, which is where duplicates tend to surface.
Run those first. It is common to find the problem is not missing markup but three plugins arguing with each other.
Why this is getting more important, not less
For most of the last decade structured data was an SEO nicety. That is changing, because the way people search is changing.
When an AI assistant answers a question, it has to decide which sources to draw on and how much to trust them. Content that states its facts unambiguously — who published this, what business it belongs to, where that business operates, when it was last reviewed — is easier to use with confidence than content where all of that has to be inferred from prose.
That is the same job structured data has always done. The audience for it has simply widened. If you want to go further on this, our answer engine optimization work covers how content gets selected and cited by AI search specifically, and it builds directly on the foundation described here.
A sensible order of work
If you are starting from nothing, do it in this order:
- Audit what is already being output, and remove duplicates before adding anything new.
- Get LocalBusiness right, and make sure it matches your Google Business Profile exactly — same name, same address formatting, same phone number.
- Add Organization for the brand entity, with the logo and only the social profiles you genuinely maintain.
- Add FAQPage only on pages with a real FAQ section that a visitor can read.
- Re-test, and check Search Console a week later for errors that only appear at scale.
That is a half-day of work on a typical small business site, not an ongoing project. Done once and kept accurate, it stays useful.
The honest summary
Schema markup is plumbing. It will not rescue thin content, it will not compensate for a slow site, and it is not a ranking lever you can pull. What it does is remove ambiguity about who you are and what you do, at a moment when more of your potential customers are getting answers from systems that have to make that judgment without ever visiting your homepage.
That is a small, unglamorous advantage. It is also one of the few that stays true regardless of which algorithm update lands next.
If you would like us to audit what your site is currently outputting, that is part of how we approach SEO and how we build every site in our web design work.
