Schema Markup for Small Business: A Practical Guide (2026)

Key Takeaways

Schema markup is structured data that helps Google understand your business, content, and offerings — and can unlock rich results like star ratings, FAQs, and event listings
LocalBusiness schema is the highest-priority implementation for any small business with a physical location or service area
Most schema can be added via Google Tag Manager, a CMS plugin, or directly in your site's HTML — no full-stack developer required
Incorrect or spammy schema can trigger Google manual actions; accuracy and relevance are non-negotiable
Rich results improve click-through rates by an average of 20-30%, making valid schema one of the highest-ROI technical SEO investments available to small businesses

Schema markup sits in an unusual position in small business SEO: it's one of the highest-value technical improvements you can make, but it's widely misunderstood and frequently implemented incorrectly. Many business owners have either never heard of it, or heard of it and assumed it requires a developer to implement.

Neither is true. Understanding what schema does — and implementing a handful of the most relevant types — can meaningfully improve how your business appears in search results, and may directly influence whether Google shows rich results (star ratings, FAQ dropdowns, event listings) alongside your pages.

This guide covers the types of schema markup that matter most for small businesses, how to implement them correctly, and the most common mistakes to avoid. If you're newer to the technical side of SEO, you may want to read our technical SEO explainer first. For optimising your Google Business Profile alongside schema, our Google Business Profile optimisation guide is a natural companion.

What Schema Markup Actually Does

Schema markup is a vocabulary of structured data tags, defined at schema.org and supported by Google, Bing, and other major search engines. You add it to your website's HTML (or via a tag manager), and it provides explicit context that search engines can use to better understand what your page is about.

Without schema, Google has to infer context from your page content. With schema, you tell it directly: "This is a restaurant in Bristol, it serves Italian food, it's open Tuesday to Sunday, and these are the prices."

Rich Results: The Visible Payoff

The most tangible benefit of schema is the potential to appear as a rich result — an enhanced listing in Google Search that shows additional information beyond the standard blue link and meta description. According to data from Brodie Clark's rich results analysis (2024), rich results improve average click-through rates by 20-30% compared to standard listings in equivalent positions. For a small business competing on page one with larger, better-known brands, that CTR uplift can be the difference between a result users click and one they scroll past.

Rich result types include:

Review/Rating stars — requires AggregateRating schema
FAQ dropdowns — requires FAQPage schema (though Google has restricted these significantly since 2023)
Event listings — requires Event schema
Product information — requires Product schema with offers, availability, and price
Breadcrumbs — BreadcrumbList schema improves navigational display
Sitelinks searchbox — for larger sites with internal search

Google does not guarantee rich results even with valid schema. But valid, relevant schema is a prerequisite — you cannot appear as a rich result without it.

The Schema Types That Matter Most for Small Businesses

1. LocalBusiness Schema

This is the single most important schema type for the majority of small businesses. It tells Google precisely who you are, where you are, when you're open, and how to contact you.

A basic LocalBusiness schema in JSON-LD format looks like this:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Riverside Plumbing Services",
  "image": "https://example.com/logo.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "14 High Street",
    "addressLocality": "Leeds",
    "postalCode": "LS1 2AB",
    "addressCountry": "GB"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 53.7997,
    "longitude": -1.5492
  },
  "telephone": "+44 113 496 0000",
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
      "opens": "08:00",
      "closes": "18:00"
    }
  ],
  "url": "https://example.com",
  "priceRange": "££"
}

The @type value can be more specific than "LocalBusiness" — for example, Plumber, Restaurant, AutoRepair, DentalClinic. Using a specific subtype where applicable gives Google more precise context. A full list of LocalBusiness subtypes is available at schema.org/LocalBusiness.

For Restaurants: Menu and Restaurant-Specific Schema

Restaurants benefit from additional schema beyond the base LocalBusiness type. Restaurant-specific SEO and schema implementation covers the full setup, but the key additions are:

servesCuisine — explicitly names the cuisine type
hasMenu — links to a menu page (or embeds menu data inline)
acceptsReservations — boolean or URL for reservations
AggregateRating — if you have verified reviews, this unlocks star ratings in search

Google pulls restaurant data heavily from Google Business Profile, but on-page schema reinforces and supplements that data. When the two are consistent, Google has higher confidence in the information.

For Service Businesses: Service Schema

For trades, agencies, and service-area businesses, adding Service schema nested within or alongside LocalBusiness helps Google understand what you offer. Service business SEO has particular nuances — the schema for a business without a fixed address (a mobile dog groomer, a peripatetic music teacher) uses areaServed rather than a fixed address.

{
  "@context": "https://schema.org",
  "@type": "Service",
  "serviceType": "Emergency Boiler Repair",
  "provider": {
    "@type": "LocalBusiness",
    "name": "Riverside Plumbing Services"
  },
  "areaServed": {
    "@type": "City",
    "name": "Leeds"
  }
}

2. Person / Author Schema as an E-E-A-T Signal

One schema type that's often overlooked by small business owners is Person schema for the author or founder. Google's E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) framework explicitly rewards content attributable to identifiable, credible individuals — and Person schema is the structured way to communicate that.

Adding Person schema to your about page, blog post templates, and key service pages tells Google who wrote or is responsible for the content, their professional background, and their connections to the business. A practical implementation:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jane Davies",
  "jobTitle": "Chartered Accountant",
  "worksFor": {
    "@type": "LocalBusiness",
    "name": "Davies Accountancy Ltd"
  },
  "url": "https://example.com/about",
  "sameAs": [
    "https://www.linkedin.com/in/janedavies"
  ]
}

The sameAs property — linking to your LinkedIn profile, professional directory listing, or other authoritative third-party profiles — is particularly valuable. It gives Google verifiable external evidence of the person's identity, strengthening E-E-A-T signals in a way that on-page content alone cannot. For industries where credentials matter (accountancy, law, medicine, financial advice), this implementation is high priority.

3. FAQPage Schema

FAQPage schema marks up a page (or a section of a page) as containing frequently asked questions and their answers. Until 2023, this reliably triggered FAQ rich results in Google Search — the accordion-style Q&A dropdowns visible beneath a listing.

Google reduced the frequency of FAQ rich results significantly in late 2023 and again in 2024, limiting them largely to authoritative government and health sites. However, FAQPage schema is still worth implementing because:

It signals content structure to Google's understanding systems even when it doesn't trigger a visible rich result
FAQ content is disproportionately extracted for AI Overviews (see our AI SEO post)
Rich results may appear sporadically for certain query types

Implement FAQPage schema only on pages that genuinely contain FAQ sections. Marking up content that isn't question-and-answer formatted is a schema policy violation and can trigger a Google Search Console manual action.

4. Review and AggregateRating Schema

Star ratings in search results are one of the most click-through-rate-boosting rich results available. A listing displaying a 4.7 star average from 83 reviews will consistently outperform an identical listing without ratings.

AggregateRating schema is straightforward:

{
  "@type": "AggregateRating",
  "ratingValue": "4.7",
  "reviewCount": "83",
  "bestRating": "5",
  "worstRating": "1"
}

Critical warning: Google's structured data policy explicitly prohibits self-serving review schema — adding AggregateRating data where the business is both the subject and the publisher of the reviews. Reviews that trigger rich results must be sourced from genuine third-party reviews, or collected and displayed transparently on your site with clear provenance. Violating this can result in a manual action and complete removal of rich results from your domain.

5. BreadcrumbList Schema

Breadcrumbs are the navigational trail shown in search results beneath the URL — "Home > Services > Boiler Repair." BreadcrumbList schema formalises this for Google, which can then display the breadcrumb path in results rather than the raw URL.

This is a small UX improvement for searchers (cleaner, more readable URLs), and it helps Google understand your site's hierarchy. It's particularly valuable for service businesses with category-based navigation.

6. Product and Offer Schema (E-commerce and Service Packages)

If you sell products or clearly defined service packages at fixed prices, Product schema with an Offer can unlock price and availability data in search results. For e-commerce businesses, this is high priority. For service businesses, it's relevant if you offer standardised packages ("Basic SEO Audit — £299"). Our on-page SEO essentials guide covers how product and service page optimisation fits into the broader on-page picture.

A Real-World Implementation: What Changed in Practice

At SDB Digital, we added complete LocalBusiness, FAQPage, and Person schema to a family-run electrical contractor's website in early 2024. Before implementation, the site had no structured data at all and was appearing as a plain blue link for its primary service terms. Within six weeks of implementation, it began showing AggregateRating stars in search results (from 27 verified Google reviews), and the homepage rich snippet now displayed opening hours directly in the SERP. Click-through rate on the homepage's primary keyword improved from 3.2% to 5.8% over the following quarter — a gain attributable in part to the richer presentation. The implementation took approximately two hours using JSON-LD blocks added via Google Tag Manager, requiring no developer involvement.

How to Implement Schema Markup

Method 1: JSON-LD in Your HTML (Recommended)

Google recommends JSON-LD as the preferred schema format. It's added as a <script> block in your page's <head> or <body>, separate from your visible content — meaning you don't have to restructure your HTML.

For a small business homepage, a single JSON-LD block containing your LocalBusiness schema (and any nested types) covers the most critical ground.

Method 2: Google Tag Manager

If you're not comfortable editing HTML directly, Google Tag Manager (GTM) allows you to inject JSON-LD schema without touching your site's code. Create a Custom HTML tag containing your <script type="application/ld+json"> block, and set it to fire on the relevant pages. This is a clean, maintainable approach that keeps schema updates outside your codebase.

Method 3: CMS Plugins

For WordPress, Yoast SEO, Rank Math, and Schema Pro all generate schema automatically from your page and post data. Shopify and Squarespace have varying levels of built-in schema support — Shopify handles Product schema natively; local business schema often requires a third-party app.

Method 4: RnkRocket's Automated Schema Audit

RnkRocket's technical analysis tools flag missing or malformed schema as part of the automated site audit. If you're unsure what schema your site currently has, the audit output will tell you what's present, what's missing, and what's incorrect — without requiring you to manually inspect your HTML.

Common Schema Mistakes to Avoid

Marking up content that isn't on the page. Schema must reflect visible, on-page content. If you add AggregateRating schema but your site doesn't display reviews, Google will ignore it or issue a manual action.

Using outdated schema types. HowTo schema was deprecated by Google for rich results in September 2023. FAQ rich results are now rare. Check Google's current rich results test and documentation before investing time in any schema type.

Incorrect JSON syntax. A missing comma or unclosed bracket invalidates the entire schema block. Always validate with Google's Rich Results Test before deploying.

Duplicating schema across every page. LocalBusiness schema belongs on your homepage (and Contact page). FAQPage schema belongs on pages with FAQ sections. Putting LocalBusiness schema on every single page is technically redundant.

Inconsistent NAP data. Your business Name, Address, and Phone number in schema must exactly match your Google Business Profile, your website footer, and your major citation directories. Inconsistency undermines local search signals.

FAQ

Does schema markup directly improve my rankings?

Schema markup is not a direct ranking factor — Google has confirmed it doesn't use schema as a ranking signal in the traditional sense. However, it can indirectly improve rankings by making content easier for Google to understand, and it can improve click-through rates by unlocking rich results. Higher CTR can lead to more traffic and engagement signals that do influence rankings.

How do I check if my schema is working?

Use Google's Rich Results Test to validate specific pages. Google Search Console's "Enhancements" section reports detected schema types across your site, including any errors or warnings. It takes several weeks after implementation for schema to appear in Search Console reports.

What happens if I implement schema incorrectly?

Minor errors (missing optional fields, incorrect nesting) usually mean Google ignores that schema type. More serious violations — particularly fake reviews or hidden content — can trigger a manual action, which removes rich results from your domain and requires a reconsideration request. Always validate schema before deploying.

Schema markup is a category of structured data vocabulary — defined at schema.org and supported by all major search engines — that allows website owners to provide explicit, machine-readable context about their content directly within the page HTML. For small businesses in the UK, the highest-priority implementations are LocalBusiness schema (communicating name, address, phone number, opening hours, and service area), AggregateRating schema (unlocking star ratings in search results from genuine third-party reviews), and Person schema for key authors or founders (strengthening E-E-A-T signals by connecting content to verifiable credentials). Research consistently shows that valid schema delivering rich results improves click-through rates by 20-30% compared to standard listings in equivalent positions. Implementation requires no developer: Google Tag Manager, WordPress plugins such as Rank Math or Yoast SEO, and directly embedded JSON-LD blocks are all viable routes. The most common mistake is adding schema for content that is not actually visible on the page — this violates Google's structured data policy and can result in manual actions that suppress rich results across the entire domain.

Schema Markup for Small Business: A Practical Guide