Structured Data and Rich Results for Small Sites

Most SEO advice is about persuasion — write better, link better, be more relevant than the next site. Structured data is different. It isn’t persuasion at all. It’s paperwork. You are filling out a form, in a machine-readable format, stating facts about your page: this is a product, it costs this much, it’s in stock; this is a recipe, it takes forty minutes; this is a local business, open Tuesday through Saturday, at this address. And like most paperwork, it’s unglamorous, mildly tedious, and quietly decisive — because the entities that read it make decisions about you based on whether you filed it.

Here is the problem structured data solves. A search engine reading your page is doing inference. It sees “$49” near a product name and guesses that’s the price. It sees five stars in an image and guesses that’s a rating. The guesses are good but not certain, and a search engine will not put uncertain facts in its own interface. Rich results — the prices, star ratings, event dates, and FAQ dropdowns you see decorating some listings — are the search engine vouching for facts on your behalf. It only does that when you’ve stated the facts formally. The standard vocabulary for these statements lives at schema.org, a joint project of the major search engines, and the usual way to embed it is a small block of JSON — called JSON-LD — in your page’s head. Invisible to visitors, unambiguous to machines. The rendered page says $49 in whatever typography you like; the JSON says price: 49, currency: USD, with no inference required.

What do you get for filing? Not rankings, directly — search engines are explicit that structured data is not a ranking factor in itself. What you get is a better-dressed search listing, and it’s easy to underrate what that’s worth. Two results sit side by side. One is two lines of gray text. The other shows a star rating, a price, and whether it’s in stock. The second gets the click even from a lower position, and clicks are the actual currency; a ranking is only a claim on them. There’s a useful way to think about this: on the results page, you don’t control your position, but structured data is one of the few levers you have over your appearance. It’s the difference between showing up to the audition and showing up dressed for the part.

The reason I’m writing this for small sites specifically is that structured data is one of the rare corners of SEO where being small doesn’t hurt you. Rich results aren’t awarded for authority. Your product listing with clean markup can display a price and rating just as brightly as a giant retailer’s, in a way your two-page site could never compete on backlinks. Big sites mostly have this handled, because they have teams. Small sites mostly don’t, because nobody told them — which means that within a small site’s actual competitive set, other small sites, markup is often a differentiator rather than table stakes. When I look at GazeSite scans of small-business sites, structured data is close to uniformly absent, sitting right alongside the missing meta descriptions. Everyone is competing in prose. The form sits on the counter, unfiled.

There are two honest caveats. First, only certain content types are eligible for rich treatment — products, recipes, events, job postings, reviews, FAQs, local business info, a handful of others — and the list shifts as search engines gain and lose enthusiasm for features. Marking up a page type that gets no rich result still helps machines understand you, but don’t expect visible decoration from it. Second, and more important: structured data is testimony, and search engines audit it. The markup must describe what’s actually on the page. Claiming a five-star aggregate rating your page doesn’t show, or marking up reviews that don’t exist, is the kind of lie that’s trivially detectable — the auditor holds both documents — and sites caught at it lose rich result eligibility entirely. The system runs on a simple bargain: you state facts plainly, they display facts prominently, and the whole thing only works because false filings get prosecuted.

If you have a small site and want to start, start narrow. Pick the one page type where facts matter most to a searcher deciding whether to click — products if you sell, events if you host, the local-business basics if you serve a neighborhood. Add the JSON-LD for that type, stating only what the page already says. Search engines publish validators that will tell you in seconds whether your markup parses and what it’s eligible for; run them, because a syntax error fails silently otherwise — the form simply goes unread, and you’ll never know. Then stop. You don’t need to mark up everything. You need your most decision-relevant facts to be machine-legible.

I find structured data philosophically satisfying in a way little of SEO is. So much of the field is trying to seem — seem relevant, seem authoritative, seem trustworthy. Structured data is just saying. Here is what this page is. Here is what it costs. Here is when we’re open. The web is drowning in ambiguity, most of it strategic, and the machines that organize the web increasingly reward whoever is cheapest to understand. Being small makes you easy to overlook. Being unambiguous, it turns out, is a partial cure — and it’s one of the few advantages on the results page that’s simply free for the filing.