Schema markup in plain English, and where it shows up in search

Schema markup is code you add to a page that tells search engines what the content means, not just what it says. A phone number becomes a machine-readable phone number, not a string of digits sitting in the footer. A star rating becomes a review score Google can show under your listing. Get it right and you become eligible for the search features that sit above and beside the normal results. Skip it and you're relying on Google to guess at content it could have been told directly.

What schema markup actually does

Most business owners already have the information schema markup needs. It's on the page: opening hours, address, star ratings, FAQs, article dates. The problem is that this content sits inside plain HTML, and plain HTML doesn't distinguish between a phone number and a price. Schema markup, written using the Schema.org vocabulary and usually placed as a block of JSON-LD in the page's code, labels that information explicitly. "This number is a telephone. This block of text is a customer review, and it scored 4.8 out of 5. This date is when the article was published."

That's the whole idea. You're not adding new content to the page. You're adding a translation layer that turns content a human can read into content a machine can categorise with certainty.

Where it shows up in search results

This is the part that gets business owners' attention, because it's visible. Structured data is what makes the following possible in Google's results:

None of that is decorative. A result with a star rating and an FAQ dropdown takes up more space on the page and gives a searcher more reasons to click before they've even reached your competitor's plain blue link underneath it.

That distinction matters. Schema is not a ranking factor you can tune your way up with. It's an eligibility layer. You still have to earn the position through the usual SEO work, schema just decides what your listing is allowed to look like once you're there.

The schema types that actually matter for a small business site

The Schema.org vocabulary covers hundreds of types, most of which a local service business will never touch. In practice, four cover nearly everything worth doing:

• LocalBusiness (or a more specific subtype like Plumber, Dentist, Restaurant): address, hours, service area, phone number
• Review and AggregateRating: the star scores pulled from your genuine customer reviews
• FAQPage: the questions and answers you already have on service or pricing pages
• BreadcrumbList: the navigation trail from homepage to category to page

If you sell products online, Product schema (price, availability, SKU) joins that list. If you run a content-heavy blog, Article schema is worth adding too. Beyond that, most businesses are better off getting the core four right than chasing marginal types that rarely trigger a visible result.

How to check if you already have it, or if it's broken

Don't assume. We regularly find sites where a plugin added schema years ago, a template change broke it, and nobody noticed because nothing throws a visible error on the page itself. Structured data fails silently.

• Run the page through Google's Rich Results Test and paste in the live URL
• Check for both errors and warnings, not just errors, warnings mean a required field is missing even if the type is technically valid
• Fix required fields first (name, address, phone for LocalBusiness; question and answer text for FAQPage)
• Prefer JSON-LD over inline microdata for anything new, it lives in one script block instead of being scattered through your HTML, which makes it far easier to update later

Adding it without touching template code

You don't need a developer for basic coverage. WordPress site owners running Yoast or RankMath get LocalBusiness and Article schema generated from settings you've probably already filled in. Some page builders do the same automatically for business profile fields. Where it breaks down is FAQPage and Review schema tied to genuinely dynamic content, and anything on a custom-built site without a plugin layer, that's where a developer needs to add a JSON-LD block by hand and keep it in sync with the visible content.

This is exactly the layer we check as part of SEO work: confirming what schema exists, what's broken, and what's worth adding for the search features your business actually has a shot at, rather than markup for its own sake.

FAQs

A short FAQPage block on this topic, which is itself a good example of the schema type in action.