- Schema.org's updated LocalBusiness subtypes now let you describe your business category with enough precision that AI search engines can confidently surface you for specific queries.
- The ServiceArea type, combined with areaServed properties on your LocalBusiness entity, is now one of the clearest signals for geo-targeted AI answers — more reliable than keyword stuffing city names.
- Review schema has new required properties in 2026; old implementations without itemReviewed or author structured data are being demoted in rich result eligibility.
- FAQPage schema is no longer shown as rich results on desktop for most queries — but it still feeds AI answer engines like Perplexity and ChatGPT Search, so it's worth keeping.
- HowTo schema remains one of the highest-conversion rich result types for service businesses, and Google has expanded the query types where it triggers.
- Implementing these schema types doesn't require a developer — a single JSON-LD block added to your site's head tag covers most of what matters.
Why Schema Updates Matter More Now Than They Did Two Years Ago
For most of search's history, schema markup was a nice-to-have. You'd add it, maybe get a star rating or an FAQ accordion in the results, and move on. The upside was marginal for most small businesses.
That calculus has shifted. AI-powered search engines — Google's AI Overviews, Perplexity, ChatGPT Search, and others — are now pulling structured data directly to populate their answers. When an AI engine decides which plumber to name in a "best plumber near me" answer, or which bakery to recommend for a custom cake query, it's drawing on structured signals, not just keyword frequency.
Schema markup is one of the clearest structured signals you can give. And because most small businesses still haven't updated their implementations since 2022 or earlier, the gap between businesses that have current schema and those that don't is widening fast.
Here's what actually changed, and what to prioritize.
The Schema Types That Got Meaningful Updates
1. LocalBusiness Subtypes — More Specific Is Now Better
Schema.org has always had LocalBusiness subtypes (FoodEstablishment, MedicalBusiness, HomeAndConstructionBusiness, etc.), but the guidance on how specific to get has changed. Previously, using a broad type like LocalBusiness was acceptable. Now, Google's rich result documentation and the AI search engines' training data both reward specificity.
If you run a nail salon, BeautySalon is better than LocalBusiness. If you run an HVAC company, HVACBusiness (a newer addition under HomeAndConstructionBusiness) is better than the parent type. The reason is disambiguation — when an AI engine is deciding which result to surface for "HVAC repair near downtown Austin," a business explicitly typed as HVACBusiness with areaServed pointing to Austin is a cleaner match than a generic LocalBusiness with "HVAC" in the description text.
What to do: Check your current schema type against the Schema.org LocalBusiness hierarchy. Find the most specific subtype that accurately describes your business. Update your JSON-LD block. This is a five-minute change with measurable upside.
2. ServiceArea and areaServed — The Geo-Targeting Signal AI Engines Actually Use
This is probably the highest-impact update for service-area businesses — contractors, cleaners, mobile pet groomers, delivery services, anyone who works across a region rather than at a single storefront.
The areaServed property on your LocalBusiness entity, combined with a properly structured ServiceArea type, tells AI search engines exactly where you operate. Without it, those engines have to infer your service area from your address, your website copy, and your backlink geography — all of which are noisier signals.
A properly structured implementation looks like this in JSON-LD:
{
"@type": "HomeAndConstructionBusiness",
"name": "Riverside Roofing Co.",
"areaServed": [
{"@type": "City", "name": "Portland"},
{"@type": "City", "name": "Beaverton"},
{"@type": "State", "name": "Oregon"}
]
}
You can also use GeoCircle or GeoShape if your service area is radius-based rather than city-based. For most small businesses, listing specific cities or counties is more readable and just as effective.
What to do: Add areaServed to your existing LocalBusiness schema block. List every city or county you actively serve. If you've been keyword-stuffing city names in your footer or a hidden paragraph, this is the cleaner replacement — and it won't get you penalized.
3. Review Schema — The 2026 Requirements Tightened
Google tightened its review schema requirements in late 2025, and businesses with older implementations are now losing rich result eligibility. The two most common issues:
- Missing
itemReviewed: Your Review entity needs to explicitly reference what's being reviewed. For a LocalBusiness, that means a nesteditemReviewedproperty pointing back to your business entity. - Unstructured
author: Theauthorproperty on a Review used to accept a plain string (just a name). Now Google expectsauthorto be a structuredPersonorOrganizationtype with at least anameproperty.
The practical consequence: if you added aggregate review schema years ago and haven't touched it, your star ratings in search results may have quietly disappeared. Check Google's Rich Results Test to confirm your current status.
What to do: Run your homepage and key service pages through the Rich Results Test. If review schema is failing, update the author and itemReviewed properties to use structured types rather than plain strings.
4. FAQPage Schema — Still Valuable, Just Not Where You Think
Google stopped showing FAQPage rich results on desktop for most queries in 2023, and the rollback continued through 2024. By now, you're unlikely to see the accordion-style FAQ expansion in desktop search results for most small business queries.
But don't remove it. FAQPage schema is now primarily valuable as a feed for AI answer engines. Perplexity, ChatGPT Search, and Google's AI Overviews all parse FAQ schema to populate their conversational answers. If your FAQ schema asks and answers "What areas do you serve?" or "Do you offer same-day appointments?" in structured markup, you're giving AI engines pre-formatted content to cite.
The format hasn't changed — FAQPage with mainEntity containing Question and acceptedAnswer types. What's changed is where the payoff comes from.
5. HowTo Schema — Expanded Trigger Conditions
HowTo schema continues to be one of the highest-value types for service businesses. Google has expanded the query types where HowTo rich results appear, including more "how do I" queries that have local or service intent.
For a plumber, a HowTo page about "how to shut off your water main in an emergency" with proper schema isn't just content marketing — it's a structured signal that you're an authoritative source in your trade. When someone asks Google or an AI engine "how do I shut off my water main," your structured HowTo has a real shot at appearing in the answer, with your business name attached.
What to do: Identify two or three "how to" questions your customers ask regularly. Write a short page or blog post for each, add HowTo schema, and make sure your business entity is referenced on the same page.
The Schema Types Most Small Businesses Are Still Missing
Beyond the updates above, there are a few schema types that remain underused across small business websites:
OpeningHoursSpecification — This is separate from the openingHours string property and allows you to specify holiday hours, seasonal variations, and special closures in a structured way. Google uses this to populate the "hours" panel in local results, and it's more reliable than the hours you enter manually in Google Business Profile.
PaymentMethod — Specifying accepted payment methods in schema helps AI engines answer "does [business] accept [payment type]" queries directly, without the user needing to visit your site.
hasOfferCatalog with Offer types — If you sell services at defined price points, structuring them as Offer entities gives AI engines the data to answer "how much does [service] cost" queries with your actual prices, not a competitor's.
Implementation Priority: What to Do First
If you're starting from scratch or haven't touched your schema since 2022, here's the order that gives you the most visibility gain per hour spent:
- Fix or create your core LocalBusiness block with the most specific subtype, your NAP (name, address, phone), and
sameAslinks to your Google Business Profile, Yelp, and social profiles. - Add
areaServedwith structured City or State entities. - Audit your Review schema with the Rich Results Test and fix
authoranditemReviewedif they're failing. - Add or update FAQPage schema on your homepage and key service pages with questions your customers actually ask.
- Add HowTo schema to any instructional content you already have.
- Add
OpeningHoursSpecificationso your hours are machine-readable.
All of this lives in a single JSON-LD <script> block in your page's <head>. You don't need a plugin, a developer, or a schema generator tool — though Google's Structured Data Markup Helper can speed things up if you're new to JSON-LD.
The Competitive Window Is Real but Finite
Schema adoption among small businesses is still low. A 2025 study by Ahrefs found that fewer than 30% of small business websites had any structured data beyond the most basic WebSite type. That means implementing even a moderately complete schema setup puts you ahead of the majority of your local competitors in the signals that AI search engines rely on.
That window won't stay open forever. As AI search becomes the default interface and more businesses realize schema is the mechanism, adoption will accelerate. The businesses that implement now — and keep their schema current as Schema.org continues to evolve — will have a compounding advantage.
Schema markup used to be a rich-result trick. Now it's the structured language AI search engines use to decide who gets named in the answer.
The good news for owner-operators: this is one of the few SEO levers that doesn't require ongoing content production, link building, or paid spend. You implement it once, check it quarterly, and update it when your business changes. It's the kind of low-maintenance, high-signal work that compounds quietly while you're focused on running the actual business.
“Schema markup used to be a rich-result trick. Now it's the structured language AI search engines use to decide who gets named in the answer.”
| Area | Outdated approach (pre-2024) | Current best practice (2026) |
|---|---|---|
| Business type declaration | Generic `LocalBusiness` type for most businesses | Most specific available subtype (e.g., `HVACBusiness`, `BeautySalon`, `AutoRepair`) |
| Geographic targeting | City names keyword-stuffed in footer text or hidden paragraphs | `areaServed` property with structured `City` or `State` entities in JSON-LD |
| Review markup | Plain string for `author` field; no `itemReviewed` property | Structured `Person` type for author; `itemReviewed` referencing the business entity |
| FAQ content | FAQPage schema added to chase desktop accordion rich results | FAQPage schema maintained primarily to feed AI Overviews and AI answer engines |
| Business hours | `openingHours` string property only (e.g., "Mo-Fr 09:00-17:00") | `OpeningHoursSpecification` type with support for holiday and seasonal hour variations |
| Service pricing | Prices mentioned only in body text, not machine-readable | `hasOfferCatalog` with structured `Offer` entities listing service names and price ranges |
How to Audit and Update Your Small Business Schema Markup
- 01Run the Rich Results Test on your key pages. Go to search.google.com/test/rich-results and test your homepage, your main service page, and any page with review or FAQ content. Note every error and warning — these are the gaps costing you rich result eligibility.
- 02Identify your most specific LocalBusiness subtype. Browse the Schema.org LocalBusiness hierarchy at schema.org/LocalBusiness and find the subtype that most accurately matches your business category. If you're a general contractor, `GeneralContractor` is better than `HomeAndConstructionBusiness`; if you're a dentist, `Dentist` is better than `MedicalBusiness`.
- 03Update your core LocalBusiness JSON-LD block. Replace your existing schema type with the specific subtype, confirm your NAP (name, address, phone) is accurate, and add `sameAs` links to your Google Business Profile URL, Yelp page, and any other authoritative directory listings.
- 04Add or update the areaServed property. Inside your LocalBusiness block, add an `areaServed` array listing every city, county, or state you actively serve as structured `City` or `State` entities — not plain strings. This is the clearest geo-targeting signal for AI search engines.
- 05Fix Review schema to meet 2026 requirements. If you have aggregate review markup, ensure the `author` field uses a structured `Person` or `Organization` type with a `name` property, and that `itemReviewed` references your business entity. Re-run the Rich Results Test to confirm the errors are resolved.
- 06Add or refresh FAQPage schema on high-traffic pages. Write five to eight questions your customers actually ask — covering services, pricing, hours, and service area — and mark them up as `FAQPage` with `Question` and `acceptedAnswer` types. Focus on the questions AI engines are likely to answer on your behalf.
- 07Validate the final implementation and set a quarterly reminder. Run every updated page through the Rich Results Test one final time, then check Google Search Console's Enhancements section in 48 hours to confirm Google has crawled the new markup. Set a calendar reminder to re-audit quarterly, especially after any site platform updates that might strip custom head code.