Schema Markup for Small Businesses: A Practical Guide

You’ve filled out your Google Business Profile, written a decent homepage and listed your products. Yet search results for your competitor show star ratings and prices while yours show a plain blue link. Often the difference is a few dozen lines of code most visitors never see: schema markup.

Schema markup won’t rescue a weak website, and it isn’t a ranking shortcut. What it does is remove guesswork. It tells search engines, in a standard format, that this page is a bakery at this address, open these hours, or that this product costs $24 and is in stock. This guide explains what schema markup is, which types matter for small businesses in 2026, copy-ready examples you can adapt, and how to test it.

What schema markup is

Schema markup (also called structured data) is a block of code that describes the content of a page using the shared vocabulary at Schema.org. Google, Bing and other search engines read it to understand pages more precisely.

There are 3 formats: JSON-LD, Microdata and RDFa. Google says that in general it recommends JSON-LD where your site’s setup allows it. JSON-LD sits in a single <script> block, separate from the visible page content, so it’s the easiest to add, edit and debug. Every example in this guide uses it.

What schema markup can do:

• Make pages eligible for rich results, such as product prices, review stars on product pages, event dates and breadcrumbs.
• Give search engines clear facts about your business, such as name, address, phone number and hours.
• Reduce ambiguity, for example that “Apple Pie Co.” is a bakery, not a recipe.

What it can’t do:

• Guarantee rich results. Google says adding structured data can enable richer results, but display isn’t guaranteed.
• Replace good content. Markup must describe what’s actually on the page.
• Act as a special ticket into AI answers. Google’s guidance on AI features in Search says there’s no special schema.org structured data you need to add to appear in AI Overviews or AI Mode.

For how this fits into the broader shift to AI search, see our guide to AEO vs GEO vs SEO.

What changed in 2025 and 2026

Google has been trimming the rich result types it supports. Knowing what’s gone saves you effort.

Google also removed documentation for several niche types in 2025, including course info, estimated salary, learning video, special announcement and vehicle listing, and dropped practice problem markup in January 2026. If a plugin still offers these, skip them.

Key takeaway: For most small businesses, schema markup comes down to 3 types: LocalBusiness (or Organization) on the homepage, Product on product pages, and BreadcrumbList on sites with categories. Get those right before adding anything else.

LocalBusiness markup example

Google’s local business documentation lists name and address as required, and recommends properties such as telephone, url, geo, openingHoursSpecification and priceRange. Use the most specific subtype available, such as Bakery, Dentist, AutoRepair or HairSalon, rather than plain LocalBusiness.

Here is a template for a bakery. Replace every value with your real details, and keep them identical to your Google Business Profile and website footer.

```html

```

Tips: Google recommends at least 5 decimal places for latitude and longitude. If you have several locations, give each its own page with its own markup. Service-area businesses without a public address should mark up only what they show publicly. Our local SEO checklist covers the rest of local optimization.

Product markup example

If customers can buy from your site, Google’s merchant listing documentation requires name, image and an offers block with price and priceCurrency. Recommended properties include availability, brand, gtin, sku, shipping details and return policy. Most ecommerce platforms, such as Shopify and WooCommerce, add basic product markup automatically, so check what your theme already outputs before adding more.

```html

```

Keep prices and stock status in the markup synced with the page. Mismatches are a common reason products lose rich results. Our guide to SEO for product and category pages covers the on-page side.

Review markup example (and the self-serving rule)

Review stars are where small businesses most often get schema wrong. Google’s review snippet guidelines say that if a business controls the reviews about itself, its pages using LocalBusiness or Organization markup are not eligible for star review features. That includes reviews pulled in through a widget from Google or Facebook. In other words, you can’t put star markup for your own business on your homepage.

Review markup is eligible on product pages, among other types, when the reviews come from real customers. Google’s guidelines also prohibit fake reviews and undisclosed incentivized reviews in the page or the markup. Add an aggregateRating inside your Product markup like this:

json "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.7", "reviewCount": "38" }, "review": [ { "@type": "Review", "author": { "@type": "Person", "name": "Jordan P." }, "datePublished": "2026-08-14", "reviewRating": { "@type": "Rating", "ratingValue": "5", "bestRating": "5" }, "reviewBody": "Starter was bubbling in 4 days. Clear instructions." } ]

The numbers must match the reviews visible on the page. Collect genuine reviews; our guide to getting more Google reviews explains how to ask without breaking platform rules.

FAQ markup example

Google stopped showing FAQ rich results on May 7, 2026, and removed the feature’s documentation in June 2026. FAQPage is still a valid Schema.org type, and existing markup does no harm, but it won’t produce an expandable FAQ in Google results. If your site already has it, you don’t need to remove it. If you’re adding it new, do so only because it’s easy and describes real content, not for a Google feature.

```html

```

What still matters for AI answers is the visible FAQ itself: clear questions phrased the way people search and short, direct answers. Our guide on how to show up in Google AI Overviews covers that in more depth.

Where to start: a 6-step plan

1. Check what you already have. Run your homepage and a product page through Google’s Rich Results Test. Many themes and plugins already output markup.
2. Fix your homepage first. Add LocalBusiness (with the most specific subtype) or Organization markup with name, address, phone, hours and logo.
3. Cover product pages. Make sure every product has name, image, price, currency and availability.
4. Remove risky markup. Delete self-serving review stars on business pages and any deprecated types.
5. Validate. Use the Rich Results Test for Google features and the Schema Markup Validator for general Schema.org correctness.
6. Monitor in Search Console. Watch the enhancement reports for errors. Our Google Search Console guide shows where to find them.

How to add it. On WordPress, SEO plugins such as Yoast or Rank Math generate markup from settings. On Shopify, most themes include product markup, and apps can add more. On custom sites, paste the JSON-LD into the page’s HTML, usually in the <head>. For a wider review of site health, see our technical SEO checklist.

Common mistakes

• Markup that doesn’t match the page. Hours, prices or ratings that differ from visible content can make pages ineligible.
• Duplicate markup. A theme and a plugin both outputting Product markup can conflict.
• Self-serving review stars. Ineligible for LocalBusiness and Organization pages.
• Generic types. LocalBusiness when Dentist or Plumber exists.
• Set and forget. Holiday hours, price changes and sold-out items need updating.

Conclusion

Schema markup is one of the few SEO tasks that’s mostly a one-time setup with lasting value. Describe your business accurately on the homepage, mark up every product, skip review stars for your own business and test everything. Then keep it in sync as hours and prices change. For more help, browse our glossary or our on-page SEO checklist.

Sources

• Google Search Central: Introduction to structured data — JSON-LD recommendation and testing with the Rich Results Test
• Google Search Central: Local business structured data — required and recommended LocalBusiness properties
• Google Search Central: Merchant listing structured data — required Product and Offer properties
• Google Search Central: Review snippet structured data — self-serving review rule and fake review guidance
• Google Search Central: Documentation updates — FAQ rich result deprecation and removal of other types
• Google Search Central: AI features and your website — no special schema needed for AI Overviews and AI Mode