New Schema Types That Matter for Small Business Visibility

Why Schema Markup Suddenly Matters More Than It Did Two Years Ago

For most of the 2010s, structured data was a nice-to-have. You added it, got a star rating in the SERP, and moved on. The payoff was cosmetic.

That changed when Google started using schema as a primary sourcing signal for AI Overviews and when voice assistants started pulling direct answers from DefinedTerm and FAQPage markup rather than scraping paragraphs. Today, if your site doesn't have the right structured data, you're invisible to a growing share of queries — not because your content is bad, but because the machine can't parse it cleanly enough to cite you.

For small businesses, this is both a problem and an opportunity. Enterprise sites have whole teams managing schema. You probably don't. But the gap is closable in an afternoon if you know which types actually matter.

Here's what's moved in the past twelve months and what you should add first.

ServiceArea: The Local Schema Type That's Now a Citation Signal

What it is: ServiceArea is a property of LocalBusiness that specifies the geographic region a business serves. It's been in the spec for years, but Google elevated its use in AI Overviews in early 2026.

Why it matters now: When someone asks an AI Overview "who does X near Y," Google is increasingly pulling from ServiceArea markup to determine whether a business is a relevant citation — even when the business doesn't have a physical location in Y. Plumbers, cleaners, landscapers, mobile groomers, and any other service-area business benefit directly.

How to implement it:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Your Business Name",
  "areaServed": [
    {
      "@type": "City",
      "name": "Austin"
    },
    {
      "@type": "City",
      "name": "Round Rock"
    }
  ]
}

List every city or postal code you actually serve. Don't pad it — Google cross-references this against your Google Business Profile and your content. Mismatches suppress the signal.

OfferCatalog: Making Your Services Machine-Readable

Product businesses have had Product and Offer schema for years. Service businesses got OfferCatalog much earlier in the spec, but almost nobody uses it — which means the ones who do stand out.

OfferCatalog lets you list your services in a structured hierarchy: the catalog itself, then individual Offer items with names, descriptions, and optionally prices. This is the markup that feeds AI answers to queries like "what does [business type] include" or "does [service] cover [specific task]."

A cleaning business might structure it like this:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Sparkle Clean Co.",
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Cleaning Services",
    "itemListElement": [
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "Standard Home Clean",
          "description": "Full interior clean including kitchen, bathrooms, and living areas."
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "Deep Clean",
          "description": "Includes oven, fridge interior, baseboards, and window sills."
        }
      }
    ]
  }
}

This is the schema equivalent of a services page that Google can actually read. For AEO (Answer Engine Optimisation) and GEO (Generative Engine Optimisation), it's one of the highest-leverage additions a service business can make right now.

MerchantReturnPolicy: Now a Ranking Factor, Not Just a Display Feature

If you sell physical products online, this one is urgent. Google confirmed in its March 2026 merchant documentation update that MerchantReturnPolicy markup is now used as a ranking input for product carousels and Shopping results — not just as a way to display return info in rich results.

The logic is straightforward: Google wants to surface trustworthy merchants. A clearly marked return policy is a trust signal. Merchants without it are at a disadvantage in competitive product categories.

The key properties to include:

• returnPolicyCategory — use MerchantReturnFiniteReturnWindow or MerchantReturnUnlimitedWindow
• merchantReturnDays — number of days the window is open
• returnMethod — ReturnByMail, ReturnInStore, or both
• returnFees — FreeReturn or ReturnFeesCustomerResponsibility

This goes on your Product or Offer markup, or on a standalone MerchantReturnPolicy entity linked from your Organization block. If you're on Shopify, most themes don't add this automatically — you'll need to add it manually or via a JSON-LD snippet in your theme's <head>.

FAQPage: Tighter Rules, Still Worth It

Google tightened FAQPage rich result eligibility in Q1 2026. The main change: only one FAQPage rich result per domain per query. If you've been adding FAQ schema to every page, you're not getting the returns you think you are.

The new strategy: pick your highest-traffic, highest-intent pages and make sure those are the ones with FAQPage markup. For most small businesses, that means:

1. Your homepage (if it ranks for brand queries)
2. Your primary service or product category page
3. Any page that already ranks in position 3–10 for a high-volume query — FAQ schema can push it into the featured snippet position

The format hasn't changed — FAQPage with mainEntity containing Question and acceptedAnswer items. What's changed is the prioritisation logic. Be selective.

PriceSpecification Extensions: Feeding AI Comparison Answers

This is the least-known update on this list and potentially the most valuable for service businesses with tiered pricing.

Schema.org extended PriceSpecification in late 2025 to support minPrice/maxPrice ranges and unitCode for per-unit pricing (per hour, per square foot, per session). Google's AI Overviews now use this to generate comparison answers like "how much does X cost" — and they cite the businesses whose markup gives them a clean price range.

For a personal trainer:

{
  "@type": "PriceSpecification",
  "minPrice": "75",
  "maxPrice": "120",
  "priceCurrency": "USD",
  "unitCode": "HUR"
}

For a lawn care company:

{
  "@type": "PriceSpecification",
  "minPrice": "45",
  "maxPrice": "180",
  "priceCurrency": "USD",
  "description": "Standard mow and edge, varies by lot size"
}

You don't have to publish exact prices if your pricing is custom. A range is enough — and it's far better than nothing, which is what most of your competitors have.

What to Skip (For Now)

Not every new schema type deserves your attention. A few that are getting buzz but don't yet have meaningful Google support for small business use cases:

• EducationalOccupationalCredential — useful for staffing agencies and training providers, not general SMBs
• HealthcareConsideration — only relevant if you're in a regulated health vertical
• MediaObject subtypes — Google's use of these in AI results is still inconsistent

Focus on the five types above before touching anything else.

The Implementation Reality for Owner-Operators

Here's the honest version: most small business owners know they should have schema markup, and most don't have it — or have it half-implemented from a plugin that hasn't been updated since 2023.

The good news is that JSON-LD doesn't require a developer. You write a <script type="application/ld+json"> block, paste it into your page's <head>, and validate it with Google's Rich Results Test. The whole process for a single page type takes 20–40 minutes the first time and five minutes for every subsequent page once you have a template.

The bad news is that keeping it current is where it breaks down. Prices change. Services change. Service areas expand. Most businesses update their website and forget to update their schema. That drift is how you end up with structured data that contradicts your content — which Google penalises by suppressing your rich results entirely.

The fix is treating schema like any other piece of business data that needs to stay in sync: build a review cadence into your quarterly ops checklist, or automate the monitoring so you're alerted when something goes stale.

Schema markup is no longer a cosmetic upgrade — it's the layer of machine-readable truth that AI search engines use to decide whether your business gets cited or skipped.

If you're already doing the work of keeping your Google Business Profile updated and your services page current, the schema layer is just making that same information legible to machines. It's not extra work — it's the same work, done twice, in two formats. The businesses that treat it that way are the ones showing up in AI Overviews while their competitors wonder where their traffic went.

Validate Before You Publish

Every schema block should pass three checks before it goes live:

1. Google Rich Results Test — confirms the markup is parseable and eligible for rich results
2. Schema.org Validator — checks for spec compliance beyond what Google tests for
3. Manual review — read the output. If the data in your schema doesn't match what's on the page, fix the mismatch before publishing

Invalid schema is worse than no schema in some cases — it can trigger manual actions for structured data spam if Google determines you're marking up content that doesn't match the page. Don't skip validation.

For related reading on keeping your local search presence accurate across the board, see our guides on NAP consistency and Google Business Profile optimisation.