Labeled facts instead of inference
Company name, address, opening hours, the author of an article, the steps in a procedure, the questions a page addresses and the replies supplied. Each fact carries a label, in a format built for software rather than left to be parsed out of sentences. Every system reading your pages rewards that plainness, because inference costs them effort.
Two decisions that run against common practice
Schema and meta descriptions do separate jobs, and get written apart from one another. A description is a human-facing pitch, built to earn a click from somebody scanning results. Structured data is a set of labeled facts for software. Merge the two and you get a summary reading like a database record, alongside markup that sounds like sales copy. We keep the jobs separate.
FAQ markup stays on the page even after the rich snippets went away. Google removed those results in May 2026, so a good deal of the industry stripped the schema out once the visible benefit had gone. We kept emitting it, because the value moved rather than vanished. A question explicitly paired with its reply, both labeled, is close to the ideal shape for a retrieval system assembling a citation. The visual snippet was never the only reason to publish it.
"When a visible reward disappears, the useful question is whether the underlying signal still does work somewhere else."
Generated from the finished work, not filled in by hand
The most common failure here is not absent markup, but markup that contradicts the page beneath. Someone fills in a plugin at publication, the content gets edited six months later, and the markup still describes the earlier version. The page now says one thing to a reader and something else to a machine. A contradiction is worse than having no markup at all, since a system catching it has reason to trust the whole domain slightly less.
We generate structured data from the finished piece rather than from a form. Article markup describes the piece as published, questions come from what the copy genuinely addresses, and procedure steps mirror the sequence actually listed. Contact details, opening hours and location come from one source that feeds both the visible page and the markup, so the two cannot drift apart.
Keeping the markup in code
Structured data has to be valid to be useful, and validity is not something a content editor should be asked to maintain in a text field. A missing bracket silently disables the whole block, while a property in the wrong place produces markup that parses cleanly and describes something other than what you meant. So the markup stays code-side, generated and validated by the system, injected into the head, and rendered identically whether a page came from a template, a builder or a hand-built layout. A redesign leaves it intact: the visual design can be rebuilt entirely while the machine-readable layer carries across untouched.
Which schema types earn their place
Not everything, and the temptation to mark up every property available should be resisted, because a page describing itself as fourteen types at once is not clarifying anything. Organization and LocalBusiness establish who you are, where you are and how to reach you. WebSite and WebPage establish what a page is. Breadcrumbs express where the page sits in the structure, which is also a compact statement of your topic architecture. Article carries authorship and publication facts, which matter when the question is who said this. FAQ pairs questions with answers. HowTo carries procedures in ordered steps.
The test for adding anything else is whether the property states a fact software would otherwise have to infer. Facts earn their place. A claim you would simply like a machine to believe does not.
Where structured data connects
Structured data works when the page beneath it is genuinely about one thing, which is why it sits next to the architecture rather than on top of it. Topic clusters covers how documents relate to each other, while page authority handles the originality and attribution signals that markup can describe but cannot manufacture. The delivery layer matters too: markup emitted into a document already carrying hundreds of kilobytes of framework code is competing for attention with everything else in the head. The Model Context Protocol covers how a clean document changes what reaches a parser.
How the engagement runs
Structured data work usually accompanies a technical audit, since the two share the same source material. It happens through screen shared sessions and starts within days.