Schema Markup for Small Business: What to Add and How to Do It

Schema markup is a shared vocabulary for describing things on the web. It comes from Schema.org, a project backed by the major search engines, and it gives every common thing a name and a set of properties. A business has a name, address, phone number, opening hours, and a price range. A product has a price, availability, and a brand. An article has an author and a publish date.

You add that description to your page as a small block of code. Visitors never see it. Search engines read it and stop guessing.

There are three formats, but you only need to care about one. JSON-LD is the format Google recommends, and it sits in its own script block rather than being tangled through your page design. That means you can add, edit, or remove it without touching how the site looks. If someone offers to add schema using the older inline formats in 2026, ask why.

Think of it as a labelled filing cabinet sitting behind your shopfront. Customers walk past the window. Google opens the drawers.

The honest case for schema is less dramatic than some SEO sales pitches make it sound, and that's fine. It earns its place by doing three useful jobs.

1. It removes ambiguity about your business. If there are three businesses with similar names in your region, structured data helps search engines connect your website, your address, your Google Business Profile, and your social profiles into one clear entity.
2. It makes some pages eligible for richer search results. Product prices, review stars on product pages, breadcrumbs, and article details can show up in search when the markup is correct. Eligibility is not a promise. Google decides what to display.
3. It feeds the machines that answer questions. AI Overviews, ChatGPT, and other answer engines work better with sources that state facts clearly. Schema won't get you cited on its own, but it helps your basics stay consistent everywhere they're read.

That third point matters more each year. If you want the wider picture, our guide on how to rank in Google AI Overviews covers the content side, and answer engine optimization for small business explains why clear, consistent facts beat clever wording.

For a small business, the effort is small and the downside of doing nothing is quiet. Nobody complains that your schema is missing. Search engines just understand you a little less well than the competitor who bothered.

Before we get to the how, a reality check. Schema is a label, not a strategy.

Perfect structured data on a confusing, slow website is like a beautifully printed name badge on someone who won't answer questions. Google knows who you are. Customers still leave.

Schema will not fix thin content, a homepage that hides what you do, slow mobile pages, or a contact form nobody can find. It won't override a page that Google hasn't indexed in the first place. If your site isn't showing up at all, start with why your website isn't showing up on Google before you worry about markup.

It also won't guarantee rich results. Google has narrowed several rich result types over the years. FAQ rich results, for example, are now mostly limited to well-known government and health sites, and HowTo rich results have been retired. FAQ schema can still be useful for describing visible content, but don't add it expecting expandable questions to appear under your listing.

Schema.org lists hundreds of types. You need a handful. Here's the short list, sorted by how much it matters for a typical service business or local shop.

That's it for most businesses. A dentist, a plumber, an accountant, and a cafe will all use roughly the same core set. The difference is in the subtype and the details.

Schema repeats your business facts in code. If those facts are already inconsistent, schema just repeats the mess more precisely.

Before writing a line of markup, line up your name, address, and phone number across your website, Google Business Profile, Facebook page, and any directories you're listed on. Same business name. Same address format. Same phone number. If your website says Level 1 and your Google profile says Suite 1, pick one.

Ten minutes here saves you a quiet credibility problem later. Search engines notice when your details don't agree, and so do customers.

This is the most important piece of schema markup for small business websites, and the one most often skipped. Google's local business structured data documentation lists the required and recommended properties.

Start by choosing the most specific type available. Schema.org has subtypes such as Dentist, Plumber, Electrician, AccountingService, LegalService, AutoRepair, HairSalon, and Restaurant. A specific type tells search engines more than the generic LocalBusiness label. If nothing fits exactly, LocalBusiness is a perfectly good fallback.

A simplified example for a fictional plumbing business looks like this:

{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "Example Plumbing Ltd",
  "url": "https://www.example.co.nz",
  "telephone": "+64-6-000-0000",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "1 Example Street",
    "addressLocality": "Napier",
    "postalCode": "4110",
    "addressCountry": "NZ"
  },
  "openingHours": "Mo-Fr 07:00-17:00",
  "sameAs": ["https://www.facebook.com/example"]
}

That code sits inside a script tag with the type application/ld+json, usually in the page head. The business name, number, and address here are placeholders. Swap in your real details and make sure every value matches what visitors can see on the page.

Service-area businesses that don't want customers turning up at a home address can describe the area they cover instead of publishing a street address. Keep it truthful and keep it consistent with your Google Business Profile.

Once the homepage describes the business, each other page can describe itself. Different page, different label.

• Service pages: a Service block naming the service, the business that provides it, and the area served.
• Blog posts: Article or BlogPosting with the headline, author, publish date, and updated date.
• Product pages: Product with an Offer showing price, currency, and availability. Reviews belong here only if they're real customer reviews of that product.
• Every inner page: BreadcrumbList, which shows the path from homepage to the current page.
• Pages with visible FAQs: FAQPage, matching the questions and answers word for word.

You don't need to mark up everything at once. Homepage first, then your highest-value service or product pages, then the blog. Planning this during a build is easier than retrofitting later, which is why we cover it in our guide to SEO website design.

Schema that doesn't validate is worse than useless, because you think it's working. Testing takes five minutes.

1. Run the page through Google's Rich Results Test. It shows which rich result types the page is eligible for and flags errors.
2. Run it through the Schema Markup Validator to catch general Schema.org issues that Google's tool doesn't care about.
3. Check Google Search Console after a few weeks. The enhancement reports show valid items, warnings, and errors across the whole site.
4. Re-test whenever you change themes, plugins, or page templates. That's when schema quietly breaks.

Warnings are usually about optional properties. Errors need fixing. If Search Console says the page isn't indexed at all, schema is the wrong problem to solve first. Our Google not indexing fix checklist covers that.

The method depends on your platform. The principle doesn't change: one clean, accurate block per type, matching what's on the page.

Custom-built sites are the easiest of all, because the schema can be written into the templates once and filled automatically from the page content.

Most schema problems aren't technical. They're optimism dressed up as code.

Google's structured data guidelines are clear that misleading markup can make a page ineligible for rich results. Accurate and boring beats ambitious and wrong.

All three work. The right choice depends on your platform, your patience, and whether the site is about to be rebuilt anyway.

If your site is solid and you only need the basics, DIY is fine. If you're paying for a new build, schema should already be in the scope. Ask about it directly, and if it's listed as a separate premium add-on, that tells you how the rest of the SEO work is approached. Our guide to web design and SEO packages covers what else should be included as standard.

What doesn't make sense is paying for schema as a monthly retainer when nothing about your business has changed. Markup needs maintenance when your details change, not a subscription.

We treat structured data as part of the foundation, the same way we treat headings, page speed, and a clear contact path. It's built into the templates from day one, filled from real page content, and tested before launch.

We're a young studio, so we'd rather show our thinking than wave a wall of claims at you. If you want to know whether your current site's structured data is doing its job, get a free website audit and we'll flag schema issues alongside the things that cost you enquiries. If you're planning a new site, our services and pricing page shows what's included in each package.

Schema markup for small business is one of the few SEO jobs that's cheap, quick, and almost always worth doing. Get your details consistent, add LocalBusiness to the homepage, label your key pages, and test everything.

Just keep it in proportion. Schema helps search engines understand your business. Your website still has to convince the customer. If you'd like both checked at once, start with a free audit.