Structured Data for Small Sites: What to Add and What to Skip
By ABD Web Tools Editorial · 2026-01-19 · 8 min read
Structured data is a small, machine-readable summary you attach to a page so search engines and assistants do not have to guess what the page is. It will not rescue thin content, and it does not directly raise rankings. What it does is make you eligible for richer presentation and reduce the chance that a machine misreads your page. For a small site, three or four schema types cover almost everything worth doing.
How structured data actually gets used
When a crawler parses your page it builds a rough model of what the page is about from headings, links and body text. Structured data replaces guesswork with declarations: this is an article, published on this date, by this author, about this topic. Assistants that summarise pages lean on those declarations heavily, because they are cheap and unambiguous.
The format to use is JSON-LD, a small script block in the page head. It sits apart from the visible markup, so redesigns do not break it.
The types worth adding
Most small sites need a short list rather than an exhaustive one. Adding more types than you can maintain is how markup drifts out of sync with the page, which is worse than having none.
- Organization or WebSite, once, sitewide — establishes the brand entity.
- Article or BlogPosting on every editorial page.
- BreadcrumbList on anything more than one level deep.
- Product with real price and availability, on commerce pages only.
- LocalBusiness if you serve customers from a physical address.
Advertisement
The rule that breaks most implementations
Everything you mark up must be visible on the page to a normal visitor. Marking up a rating that appears nowhere, an author who is not credited, or a price that differs from the checkout is a policy violation, and the usual outcome is that all rich results for the site are quietly withdrawn.
When in doubt, read your markup back as sentences and ask whether a reader of the page would agree with each statement.
Validating before and after publishing
Run every new template through a structured-data validator once, then spot-check a live URL after deploy. Templating errors are common: an unescaped quote in a title, a date rendered in a local format instead of ISO 8601, or a missing image URL on posts that have no hero.
Set a reminder to re-check after any redesign. Markup lives in templates, and templates get rewritten.
What structured data will not do
It will not lift a page that does not deserve to rank, will not compensate for slow loading, and will not force a rich result — eligibility is not a guarantee. Treat it as clarity work: cheap, durable and worth doing once properly rather than repeatedly in a panic.
Frequently asked questions
Is JSON-LD better than microdata?
For most sites, yes. JSON-LD keeps the markup separate from your HTML, so it is easier to generate, easier to validate and less likely to break during a redesign.
Can too much schema hurt me?
Redundant markup is ignored, but inaccurate markup can cost you rich-result eligibility across the whole site. Accuracy matters far more than quantity.
How soon do rich results appear?
After the page is recrawled, which can take days to weeks. Eligibility also depends on the query, so the same page may show a rich result for one search and a plain listing for another.
Do I need author markup on every post?
It helps if a real, credited person wrote the piece. If your posts are published under an editorial team, name the team consistently rather than inventing personas.
Advertisement
