Schema Markup for Small Business: The Types That Actually Matter

Key takeaways

• Schema markup is a shared vocabulary (schema.org) added to your pages as JSON-LD so Google, Bing, and AI assistants can read your business details without guessing.
• Only four types matter for most small businesses: LocalBusiness, Service, FAQPage, and Review. Finish those before you touch anything else.
• Google's own case studies are the best evidence it works: Rotten Tomatoes measured a 25% higher click-through rate on pages with structured data, and Nestlé measured an 82% higher CTR on pages shown as rich results.
• Google restricted FAQ rich results in August 2023, but FAQPage markup still pays off because AI search tools extract and quote those answers.
• Never mark up content that isn't visible on the page — that's the fastest way to get a structured-data manual action.
• Test everything with Google's Rich Results Test and the Schema Markup Validator, then monitor Search Console after launch.

What is schema markup, and why should a small business care?

Schema markup is structured data: machine-readable labels, usually written in JSON-LD, that tell search engines exactly what your content means — your business name, address, phone number, services, hours, prices, and reviews. It powers rich results and helps AI search tools describe your business accurately.

The vocabulary lives at schema.org, a project Google, Bing, Yahoo, and Yandex launched together in 2011. When you add it to a page, you're not changing what visitors see. You're adding a parallel layer of meaning that machines can parse in milliseconds instead of inferring from your prose.

Why care? Three reasons. First, rich results: pages with valid markup can show star ratings, FAQs, prices, and sitelink details directly in Google, which takes up more screen space and earns more clicks. Second, AI visibility: ChatGPT, Perplexity, and Google's AI Overviews pull from pages they can parse cleanly, and structured data removes ambiguity about who you are and what you sell. Third, it's one of the cheapest wins in all of technical SEO — a few hours of work, no ongoing cost, and benefits that compound as search gets more AI-driven.

The impact isn't theoretical. According to Google Search Central's structured data documentation, Rotten Tomatoes added structured data to 100,000 pages and measured a 25% higher click-through rate on enhanced pages compared to pages without it. The same documentation reports that Nestlé measured an 82% higher CTR on pages shown as rich results, and that the Food Network saw a 35% increase in visits after converting 80% of its pages to enable search features. Your plumbing company isn't Rotten Tomatoes, but the mechanism is the same: better-labeled pages get better treatment.

One honest caveat: schema markup is not a direct ranking factor. Google has said so repeatedly. What it does is make your existing rankings more visible and clickable, and it makes your content easier for AI systems to cite. Treat it as a conversion and visibility lever, not a rankings shortcut.

Which schema types actually matter for a small business?

Four types cover roughly 90% of what a small business needs: LocalBusiness (or Organization), Service, FAQPage, and Review with AggregateRating. Schema.org lists over 800 types; you can safely ignore almost all of them until these four are implemented correctly and validating clean.

Here's the short list, ranked by priority:

Everything else — Event, Product, JobPosting, Recipe, VideoObject — only matters if your business genuinely publishes that kind of content. A dental office does not need Event schema. A plumber does not need Recipe schema. Every unnecessary type you add is another thing that can break silently, so resist the urge to decorate.

One nuance on LocalBusiness: use the most specific subtype that fits. Schema.org has subtypes like Plumber, Electrician, Dentist, LegalService, AccountingService, and ProfessionalService. The more precise the type, the less guessing Google has to do about what you are.

What is JSON-LD, and how do you add it without a developer?

JSON-LD is a block of structured data in a script tag, placed in your page's head or body, written as simple key-value pairs. Google explicitly recommends it over the older Microdata and RDFa formats because it doesn't tangle with your visible HTML and is far harder to break during redesigns.

The mechanics are simpler than most guides make them sound. A JSON-LD block opens with two declarations — the context (always https://schema.org) and the type (like LocalBusiness) — followed by properties such as name, address, telephone, and opening hours. You can nest objects: an address is a PostalAddress object, a geo coordinate is a GeoCoordinates object, and so on. If you can read an address form, you can read JSON-LD.

You have three realistic implementation routes:

1. CMS plugin. On WordPress, Rank Math or Yoast generate LocalBusiness and basic FAQ markup automatically from your settings. Good baseline, weak on Service schema.
2. Hand-written JSON-LD. Write the block once, paste it into your site's header or per-page templates. This is what we do for service businesses — full control, no plugin bloat.
3. Tag manager injection. Possible via Google Tag Manager, but it's the most fragile option; server-side or template-level markup is more reliable.

Whichever route you pick, one rule is absolute: the markup must describe content that's actually visible on the page. Marking up services you don't list, reviews you don't show, or prices you don't publish violates Google's structured data guidelines and can earn you a manual action that suppresses all your rich results.

What does LocalBusiness schema look like in practice?

A solid LocalBusiness block declares your business subtype, name, full postal address, phone, website URL, geo coordinates, opening hours, price range, and sameAs links to your profiles. It takes about 30 properties at most, and once it's written it rarely changes.

The properties that matter, roughly in order of importance:

• @type — the most specific subtype available (Plumber, Dentist, LegalService), not just the generic LocalBusiness.
• name, telephone, url — exactly as they appear on your site and your Google Business Profile.
• address — a nested PostalAddress with street, city, state, ZIP, and country.
• geo — latitude and longitude from your map pin.
• openingHoursSpecification — structured hours per weekday, including holiday exceptions if you have them.
• areaServed — cities or regions you serve, which matters enormously for service-area businesses without a storefront.
• sameAs — links to your Google Business Profile, Facebook, LinkedIn, and Yelp pages, which ties your entity together across the web.
• priceRange — a rough indicator like $$ that sets expectations.

The unglamorous part that actually determines success: consistency. Your schema NAP (name, address, phone) must match your Google Business Profile, your footer, and your citations character-for-character. "Suite 200" in one place and "Ste 200" in another won't kill you, but a wrong phone number or a stale address absolutely erodes the trust the markup is supposed to build.

Does FAQ schema still work in 2026?

Yes, but the payoff has shifted. Google restricted FAQ rich results in August 2023 to well-known government and health websites, so your FAQ dropdowns almost certainly won't appear as expandable questions in regular search results anymore. The markup still matters for AI search visibility.

Here's the logic: ChatGPT, Perplexity, and AI Overviews need to extract question-and-answer pairs from pages to compose their responses. FAQPage markup hands those pairs to them pre-labeled, which makes your page dramatically easier to quote than a competitor's wall of text. In our client work, pages with clean FAQPage markup get cited by AI assistants far more reliably than identical content without it.

Three rules keep FAQ schema useful and safe. First, only mark up questions and answers that appear verbatim on the page. Second, write answers that genuinely answer the question in two to four sentences — thin one-liners and sales pitches get ignored. Third, keep it to questions customers actually ask; a fabricated FAQ stuffed with keywords is exactly the pattern spam filters are trained on.

Can you mark up your own reviews with Review schema?

You can mark up genuine reviews displayed on your page, but there's a catch: since September 2019, Google won't show star ratings for "self-serving" reviews — a LocalBusiness displaying reviews of itself on its own site. AggregateRating stars still appear for Product, Book, Course, Recipe, and a handful of other types.

So should you bother? Yes, for two reasons. First, review markup feeds AI assistants and other engines that do consume it — when Perplexity summarizes your reputation, clearly labeled reviews and an aggregate rating help it get the number right. Second, if you sell anything that qualifies as a Product or Course, those stars are still very much available and worth having.

The hard rules: reviews must be real, attributable to identifiable customers, and visible on the page. Never mark up your Google reviews as if they were collected on your site, never invent a rating, and never mark up a curated testimonial page where you've hidden the bad ones — Google's guidelines require that markup reflect content honestly. A 4.7 with some criticism marked up honestly beats a suspicious 5.0 every time.

How do you test schema markup before and after launch?

Run every page through Google's Rich Results Test and the Schema Markup Validator before publishing, then watch Search Console's enhancement reports after launch. The whole testing workflow takes about ten minutes per page and catches the syntax errors and missing required properties that silently kill rich results.

The three tools that cover everything:

A workflow that holds up in practice: write the markup, paste the URL (or the raw code) into the Rich Results Test, fix every error and investigate every warning, then validate again in the Schema Markup Validator to catch issues Google ignores but other consumers don't. After launch, check Search Console's enhancement and unparsable-structured-data reports monthly — markup breaks silently when templates change, and Search Console is where you'll see it first.

One realistic expectation: valid markup makes you eligible for rich results, it doesn't guarantee them. Google decides what to show based on query, quality, and site trust. If your markup validates and nothing shows after a few weeks, the fix is usually better content and stronger authority, not more markup. And if you want the monitoring piece handled for you — tracking rich-result eligibility, AI citations, and technical drift across every page — AutoRankFlow automates exactly that kind of ongoing SEO and AI-visibility surveillance. If you'd rather hand the whole implementation to a team, our SEO and GEO agency services for US businesses include structured data as a standard part of every engagement.

Frequently asked questions

Is schema markup a ranking factor?

No — Google has stated repeatedly that structured data is not a direct ranking signal. What it does is earn you richer, more clickable search listings and make your content easier for AI tools to parse and cite. Think of it as improving the yield from rankings you already have.

How much does it cost to add schema markup to a small business site?

If you do it yourself with a WordPress plugin or hand-written JSON-LD, it's free apart from a few hours of your time. Agencies typically fold it into technical SEO work; as a standalone project for a 10–20 page site, expect a few hundred dollars. Be suspicious of anyone charging thousands for markup alone.

How long does it take for rich results to appear?

Anywhere from a few days to a few weeks after Google recrawls the page, assuming your markup validates. You can nudge the process by requesting indexing in Search Console. And remember: eligibility isn't a guarantee — Google shows rich results selectively.

Can I just use Yoast or Rank Math for schema?

Yes, for the basics. Both generate solid Organization/LocalBusiness and FAQ markup from your settings. Where they fall short is detailed Service schema and anything custom — that's when hand-written JSON-LD or professional help is worth it.

What's the difference between schema.org and JSON-LD?

Schema.org is the vocabulary — the dictionary of types and properties like LocalBusiness and openingHours. JSON-LD is the format — the syntax you use to write that vocabulary into your page. You use JSON-LD to express schema.org terms.

Does schema markup help with ChatGPT and Perplexity?

Yes. AI assistants extract answers more reliably from pages where entities, services, and Q&A pairs are explicitly labeled. Structured data won't make a weak page get cited, but it gives a strong page a measurable edge over unstructured competitors.

What happens if my schema markup is wrong?

Syntax errors and missing properties usually mean Google just ignores the markup — no penalty, but no benefit either. Deliberately deceptive markup (fake reviews, invisible content) is different: that can trigger a manual action that suppresses structured data across your whole site until it's fixed and reviewed.

Do I need schema markup on every page?

No. Put LocalBusiness on your homepage and contact page, Service on each service page, FAQPage only where visible FAQs exist, and Review only where genuine reviews are displayed. Sitewide markup that's identical everywhere adds nothing and can dilute your entity signals.