Schema markup for small business websites: what to add (and what to skip) in 2026.

Schema markup is a standardized code format, usually JSON-LD, that tells search engines exactly what your content means, not just what it says. A page can say "Open Mon-Fri, 9-5" in plain text and a crawler has to guess whether that's your hours or a quote from a customer. Schema removes the guessing: it labels that text as openingHours on a LocalBusiness entity, unambiguously. Content with proper schema has roughly 2.5x higher odds of being pulled into AI-generated answers, according to data Google and Microsoft have both confirmed, which makes this less optional than it used to be.

What schema markup actually does

Schema doesn't change how your page looks to a human visitor. It's invisible markup sitting in a <script type="application/ld+json"> tag, read only by machines: Google's crawler, Bing's crawler, and increasingly the retrieval systems behind ChatGPT, Perplexity, and Google's AI Overviews. Done well, it can earn you rich results (star ratings, breadcrumbs, sitelinks in search) and, more importantly in 2026, it's how AI systems verify facts about your business before citing you as a source.

The types worth adding today

• ▸Organization or ProfessionalService: your business name, logo, contact info, and social profiles, the foundational entity everything else references
• ▸LocalBusiness: for any business with a physical location or service area, name, address, phone, hours, geo coordinates, priceRange
• ▸Service: what you offer, who provides it, and what area it covers
• ▸Article or BlogPosting: headline, author, publish date, and publisher for every blog post, exactly what powers this post's own markup
• ▸BreadcrumbList: the navigation path to a page, cheap to add and genuinely useful for both crawlers and rich results
• ▸Product and Offer: for e-commerce, pricing, availability, and SKU data that feeds Google Shopping
• ▸Review and AggregateRating: only when the reviews are real and verifiable. Fabricated review schema violates Google's structured data policies and FTC endorsement guidance, and it's easy to get caught

What to skip

Not every schema type still earns its keep. A few common ones are worth avoiding or retiring:

• ▸HowTo: Google removed how-to rich results back in September 2023. Adding this schema today does nothing for your SERP appearance
• ▸FAQPage for the sake of a rich result: Google fully retired FAQ rich results for every site on May 7, 2026. It no longer changes how you appear in classic search
• ▸Any schema with placeholder text left in from a template ("[Business Name]", "[City]"). This actively damages trust signals and can trigger manual review
• ▸Duplicate or conflicting schema blocks on the same page describing the same entity differently, this confuses crawlers more than having no schema at all

LocalBusiness schema if you serve a specific area

If your business serves customers in specific cities, LocalBusiness schema is one of the highest-leverage additions you can make, alongside the Google Business Profile work covered in our local SEO guide. Include your exact NAP (name, address, phone) matching what's on your GBP listing, your service area, and your hours. Inconsistency between your schema and your GBP listing sends a mild distrust signal to Google, so keep them identical.

Schema is now an AI search signal too

Structured data used to be purely a Google SERP play. That's changed. As covered in our guide to AEO and GEO, AI systems retrieve and verify facts using structured data during answer generation, it's one of the clearest, lowest-effort signals you can give a language model about who you are and what you do. A business with clean Organization and Service schema is simply easier for an AI system to describe accurately than one with none.

How to add schema without hiring a developer

1. 1Identify the entity type that matches your page (Organization, LocalBusiness, Service, Article, Product)
2. 2Write the JSON-LD block by hand or generate it with a schema generator tool, filling in only real, verifiable data
3. 3Add it inside a <script type="application/ld+json"> tag in your page's <head> or body
4. 4Test it in Google's Rich Results Test and the Schema.org validator before publishing
5. 5Re-test after any redesign, since schema is easy to lose silently when a template changes

Common mistakes that undo the benefit

• ▸Relative URLs instead of absolute (https://yoursite.com/page, not /page)
• ▸Dates not in ISO 8601 format (2026-07-13, not "July 13")
• ▸Schema describing something the visible page doesn't actually say, Google calls this a mismatch and can ignore or penalize it
• ▸Only adding schema to the homepage and forgetting service and blog pages, where it matters just as much

Schema markup is a few hours of careful, unglamorous work that pays off every time a crawler or an AI model tries to understand your site. It won't rescue thin content or a slow page, but layered on top of a site that's already solid, it's one of the cheapest ways to make sure both Google and AI search describe your business correctly. It's part of the technical SEO we build into every site from day one, not bolted on after launch.