Schema Markup & Structured Data: The Hidden SEO Opportunity Most Businesses Miss

The FAQ that didn't exist

A client once asked us to add FAQ schema to a page to win the question-and-answer block in Google. We opened the page. There was no FAQ on it. No questions, no answers, nothing visible to a human visitor.

The plan was to put the questions and answers in the code only, so Google would show them while the page stayed short. That's not optimisation. That's a policy violation, and it's the fastest route to a manual action on structured data.

The whole conversation is a decent illustration of what schema markup is for and what it isn't. It's a way of stating clearly what is already on the page, in a vocabulary search engines understand. It is not a way to add information that isn't there.

What structured data actually does

Schema markup is a shared vocabulary, published by Schema.org and supported by Google, Bing, and others, that lets you label the parts of a page: this is a business, this is its address, this is a service, this is a price, this is a question and this is the answer.

Without it, a crawler is inferring meaning from text and layout. With it, you're stating it. The difference shows up in how confidently a search engine can treat your page as a known thing rather than a document containing words.

The practical payoff is structured data SEO in two places: eligibility for enhanced results (review stars, prices, business details), and increasing clarity about your entity, which matters more than most people realise in a search landscape built on entities and relationships rather than strings.

Rich snippets: what's real in 2026

Expectations here need calibrating, because a lot of advice was written in 2019 and never updated.

Review stars in results. Still available for products and some business types, but Google has narrowed eligibility repeatedly and is strict about self-serving reviews on LocalBusiness. Don't plan a strategy around stars appearing for your service page.

FAQ rich results. Google dramatically reduced FAQ rich result display in 2023, largely limiting it to well-known authoritative government and health sites. Implementing FAQPage markup will not bring back those expandable questions for a local business. It can still help machines understand the page, but if a vendor is selling you FAQ schema as a visibility win, ask them when they last checked.

Breadcrumbs, organisation details, product availability, events. These still render and still help. Less glamorous, more reliable.

Entity clarity. Undervalued and hard to measure. Consistent, well-formed markup helps Google connect your site, your Google Business Profile, and your mentions elsewhere into one confident entity.

The types worth having, in order

Organization or LocalBusiness

The foundation. Name, logo, address, phone, URL, and the same social profiles you list elsewhere. Use the most specific subtype you can: a dentist gets Dentist, not LocalBusiness. Specificity earns more confident handling than a generic label.

Keep the details identical to your Google Business Profile, character for character, including suite formatting. Half the value of this markup disappears when the address in the code disagrees with the address in your profile.

Service or Product

What you sell, with a description and a price or price range where one exists. This is what lets a listing show something more useful than a blue link, and it pre-qualifies clicks: people who see a price range self-select before they arrive.

Article and author

For anyone publishing content. Author, publisher, dates. It ties your writing to a real person, and connects to author pages, which is the topic of a different article but the same underlying idea: be legible as a specific entity, not an anonymous site.

Breadcrumb

Cheap, harmless, occasionally improves how the URL appears in results. If you have a category structure, add it.

Implementation, and the one decision that matters

Google recommends JSON-LD, and the recommendation is well-earned. Microdata and RDFa require annotating the HTML itself, which means every template change risks breaking your markup. JSON-LD sits in a script block, separate from the layout, and survives redesigns.

Put a single JSON-LD block on the page using an @graph array rather than several disconnected blocks. Link them with @id references so the crawler can see that the organisation, the website, and the article are related rather than three strangers who happen to share a page.

Two rules worth taping to the wall:

1. Markup must describe what's visible. Prices, hours, reviews, questions. If a user can't see it, it shouldn't be in the code.
2. Markup must stay current. Hours change at Christmas. Prices change in January. Stale structured data is worse than none, because it makes you look wrong at exactly the moment someone is deciding.

Testing it without fooling yourself

Google's Rich Results Test tells you whether a page is eligible for a specific enhanced result. The Schema Markup Validator tells you whether the markup itself is syntactically correct and complete against the schema vocabulary.

Use both. A page can pass the validator and be ineligible for rich results, because the type is valid but not supported for display. That distinction confuses people into thinking their markup is broken when it's simply not going to produce stars.

Then check in Search Console, under the enhancements reports, a couple of weeks later. That's the only place that tells you what Google actually did with it, rather than what it could theoretically do.

Mistakes that cause real damage

• Marking up content that isn't on the page. Manual action territory, and it's not subtle when they find it.
• Duplicating business details with small differences. Two versions of your address in the code and on your profile is worse than one consistent version in either place.
• Self-serving review markup. Adding review stars for your own business on your own site is explicitly discouraged and rarely renders.
• Treating schema as a ranking fix. It changes how results appear far more than where they rank. If the page isn't worth ranking, markup won't rescue it.
• Set-and-forget. Hours, prices, and services change. Somebody has to own the block.

Where to start

Add LocalBusiness or Organization markup with the same details as your profile, one Service block on your main money page, and Article markup on your content. Then stop, and verify all of it.

A free digital presence audit on Webcheckhub includes the SEO basics, structured data among them, alongside website health and Google presence, so you can see whether the technical layer is holding up before you add to it. If you'd rather have it built properly and kept current, Solutions Elites implements and maintains structured data for small businesses.