Schema Markup for Small Business Websites: What Actually Moves the Needle

A client came to us this spring convinced their previous SEO agency had "installed schema" on their site and that this was supposed to be doing something for them. When we opened the page source, there was a single block of JSON-LD sitting in the footer, copied from some template, declaring the business a LocalBusiness with an address in a city they'd moved out of two years earlier and a phone number with a typo in the area code. It wasn't helping anything. It was quietly telling Google the wrong things about a business that otherwise looked fine.

That's roughly half of what we find when we audit schema on small business sites: not an absence of structured data, but data that's stale, copied from somewhere else, or technically present without doing anything useful. The other half is genuine absence, sites that have never touched it, usually because whoever built the site five years ago didn't know it existed or didn't think it mattered for a five-page brochure site. Both problems are fixable in an afternoon, which is more than you can say for most technical SEO work.

What schema markup is actually doing, and what it isn't

Schema markup, most commonly written as JSON-LD, is a block of code you add to a page that describes what's on it in a format search engines can parse directly instead of guessing at. Rather than Google inferring "this is probably a bakery, its hours are probably these, that's probably a phone number" from scattered text and layout cues, you state it plainly: this is a LocalBusiness, here are the hours, here is the phone number, here is the address. It's translation, not persuasion. You're not telling Google your business is good. You're making it easier for Google to correctly describe what your business already is.

The part people get wrong, and where a lot of vendors oversell it, is treating schema as a ranking lever you pull to climb positions. It mostly isn't, at least not directly. Google has said as much for years, and our own before-and-after numbers across maybe two dozen client sites back it up: adding schema to a page rarely shifts its position for a competitive keyword on its own. What it does is make you eligible for richer results, a star rating under a listing, an address and phone number sitting inside the search result itself, and richer results tend to pull a noticeably better click-through rate than a plain blue link sitting in the same position. So the real effect is indirect: not ranking higher, showing up bigger once you're already there, and getting clicked more because of it. That distinction matters, because if you go in expecting a ranking jump you'll write it off as useless the first time it doesn't happen.

Which schema types are actually worth your time

Schema.org lists several hundred types and properties, and almost none of them are relevant to a small business site. Chasing completeness here wastes a day you don't have. In practice, four or five types cover nearly every situation we run into with clients, and it's worth being specific about what each one is actually for rather than treating them as an interchangeable checklist.

• LocalBusiness, or a more specific subtype like Restaurant, Dentist, or ProfessionalService — put this on your homepage and contact page if you have a physical location or a defined service area, and match it exactly to your Google Business Profile details. A mismatch here is one of the quieter reasons local rankings stall, and it's a problem covered in more depth in our Google Business Profile optimization guide
• Product, including price and availability — essentially non-negotiable for ecommerce. If you already worked through our ecommerce SEO checklist and skipped the structured data step, this is the piece most stores leave on the table
• FAQPage — genuinely useful to add, but worth setting realistic expectations on, which I'll get into below, because this one changed meaningfully in 2023 and a lot of advice online still hasn't caught up
• Article or BlogPosting — mainly useful for author and publish-date signals rather than a visible rich result most of the time, but low-effort enough that there's no real reason to skip it on blog content
• Review or AggregateRating — handle this one carefully. It's the type most likely to get a site flagged rather than helped, and I'd rather a client skip it entirely than implement it the wrong way

A genuinely useful FAQ section at the bottom of a service page isn't a formality for the one anxious visitor who scrolls that far. It's some of the cheapest content real estate on the page, whether or not it ever earns a visual rich result.

The FAQ schema expectation problem

I want to flag this specifically because we still get asked about it constantly and most of the answers floating around are two or three years out of date. Through 2022, FAQ schema was close to a guaranteed win: mark up a page's Q&A content correctly, and there was a good chance Google would show an expandable dropdown right under your listing, taking up extra vertical space in the results and pushing competitors further down the page. In August 2023, Google changed that. FAQ rich results are now shown far less broadly, and largely reserved for well-known, authoritative sites, mostly government and health information sources. For a typical small business or service company, the visual dropdown mostly doesn't appear anymore, no matter how well the markup is written.

We still add FAQPage schema to client sites, and we still write genuinely useful FAQ content into the page itself, not just the JSON-LD. It costs almost nothing to include, it occasionally still surfaces, and the underlying Q&A content helps with something separate: it gives Google's systems clean, direct answer text to pull into featured snippets or an AI-generated overview, which is arguably more valuable in 2026 than the old dropdown ever was. What we don't do anymore is promise a client that adding FAQ schema will visibly change how their listing looks in search. That promise stopped being honest a while ago, and making it anyway is exactly the kind of overselling that gives SEO work a bad name.

Where this actually goes wrong on real sites

Most of the schema problems we find aren't from sites that tried nothing. They're from sites where someone tried something once, years ago, and nobody has looked at it since.

• Copy-pasted templates with the wrong details, exactly like the footer example above — an old address, a former phone number, hours that haven't matched reality since before a renovation
• Marking up content that isn't actually visible on the page, which Google's structured data guidelines explicitly prohibit and can trigger a manual action against, not just a missed opportunity
• Self-authored review or rating schema with no genuine third-party reviews behind it — Google's guidelines are specific that aggregate ratings need to come from real, verifiable reviews, and a business that fabricates or inflates this is one of the few schema mistakes that can actively work against you rather than just doing nothing
• Duplicate or conflicting schema blocks stacked from multiple sources — a WordPress theme, an SEO plugin, and a review widget each independently adding their own LocalBusiness or Organization markup, sometimes with contradictory details on the same page
• Schema that was correct at launch and never touched again, so it quietly drifts out of sync every time the business updates its hours, moves address, or changes its phone number on the actual page but not in the code behind it

Adding it without needing a developer for every small change

On WordPress, most SEO plugins generate basic Organization and Article schema automatically, which covers the low-effort baseline. LocalBusiness and FAQPage markup usually need either a plugin add-on or a manually written JSON-LD block dropped into the page template, which is a one-time setup rather than something you touch per page once it's in place correctly. On a custom-built site, it's typically a handful of lines of structured JSON per page type, wired into the template so it updates automatically whenever the underlying content does, which is the better long-term setup precisely because it removes the chance of the drift problem described above. If your site is due for a rebuild anyway, this is worth specifying up front rather than bolting on afterward; our SEO team usually builds it into the page templates directly on any site we develop, so a business owner updating their hours on the visible page updates the schema at the same time without knowing schema exists.

Whichever way you add it, validate before publishing with Google's Rich Results Test rather than trusting that a plugin got it right. We catch errors in roughly a third of the sites we first audit, usually small ones, a missing required field or a malformed date format, that don't break the page but do mean Google silently ignores that block of markup entirely. And build a habit of rechecking it after any site change that touches contact details, pricing, or a redesign. Structured data is exactly the kind of thing that gets forgotten during a migration; we cover the broader version of that risk in our website redesign checklist if a rebuild is coming up.

Does it actually affect rankings? The honest answer

Directly, in most cases, no. Indirectly, often yes, and the mechanism is worth understanding rather than taking on faith. When we've added correct LocalBusiness and FAQPage schema to a client's key pages and then watched Search Console for six to eight weeks afterward, position in the rankings has typically stayed flat, sometimes moving a fraction of a place in either direction, well within normal noise. Click-through rate on those same pages, though, has moved more consistently, usually somewhere in the range of a ten to twenty percent relative improvement once a rich element like a star rating or business details starts appearing. Google's own algorithm doesn't reward schema directly. But a search result that looks more complete and trustworthy earns more clicks at the same position, and enough clicks over enough time is itself a signal that can support ranking indirectly. It's a second-order effect, not a lever, and any agency telling you schema alone will move you up the page is either mistaken or not being straight with you.

A schema audit you can actually run this week

• Run your homepage, contact page, and top two or three service or product pages through Google's Rich Results Test and note any errors or warnings, not just outright failures
• Check the Enhancements section of Search Console for existing structured data issues Google has already flagged, which most site owners have never opened
• Compare the address, phone number, and hours in your schema against what's live on the page and against your Google Business Profile, and fix any mismatch immediately since this one is the most common and the most damaging
• Remove any duplicate schema blocks left behind by old plugins, themes, or a previous agency, keeping one clean source of truth per page
• Add FAQPage markup to your two or three highest-traffic service pages if it isn't there already, treating it as useful content and snippet fodder rather than a guaranteed visual upgrade

Back to that client from the opening. We rewrote their LocalBusiness schema with the correct current address and a corrected phone number, added genuine FAQ content with matching markup to their three main service pages, and left the Review schema out entirely since their review volume on independent platforms wasn't yet strong enough to responsibly aggregate. Rankings for their core terms didn't move much over the following two months, which we'd told them to expect. Click-through rate on their Google Business Profile-linked listing did, up a bit over 15% once the corrected details started showing consistently in search. Small fix, honestly framed, modest but real result. If your site's schema hasn't been looked at since it was built, or you're not sure it was ever added at all, get in touch and we'll run the audit above on your actual pages rather than a generic checklist.