THE SHORT ANSWER
Organization and LocalBusiness markup matter most, because they establish who you are as an entity. FAQPage helps because it pairs a question with a self-contained answer, which is exactly the retrieval unit. Article and Product add useful attribution and specification data. Schema does not make weak content citable; it removes ambiguity from content that already deserves to be cited, which is a smaller job than vendors imply and still worth doing.
Structured data occupies a strange position in AI-visibility advice: universally recommended, rarely explained, and frequently oversold as the mechanism rather than a support for it.
The accurate framing is narrow. Language models read prose perfectly well. What they read poorly is context that a human infers from layout: which of the three phone numbers is yours, whether that price is per unit or per project, whether the company named in the footer is the publisher or a client.
The numbers, at a glance
Highest value: Organization and LocalBusiness, because they fix your identity as an entity
Strong value: FAQPage, because question-and-answer pairs match the retrieval unit exactly
Useful: Article for authorship and dates, Product or Service for specifications and price
What it does not do: make thin content citable; schema clarifies, it does not create substance
Organization and LocalBusiness: the identity layer
This is the one type worth getting exactly right before anything else. Organisation markup states your legal name, your URL, your logo, your social profiles and your contact points in a form that cannot be misread. LocalBusiness adds address, service area, opening hours and geographic coordinates.
Its real job is entity resolution. An assistant asked about your company has to decide which of several similarly named businesses you are, and it does that by reconciling signals across your site, directories, review platforms and registries. Consistent, explicit markup is the cheapest way to win that reconciliation. Inconsistent markup, where the schema name differs from the footer name which differs from the Google Business Profile, is the most common cause of an assistant describing a business incorrectly.
FAQPage: still worth it, for a different reason than before
Google reduced FAQ rich results in search for most site types, which led a lot of people to strip the markup out. That was a reasonable response to the old rationale and the wrong response overall.
The retrieval rationale is different from the rich-result rationale. A FAQPage block hands a retrieval system a question paired with a self-contained answer, which is precisely the shape it wants. The markup makes the pairing explicit rather than inferred from heading structure. Keep it where the questions are real and the answers stand alone; remove it where it was only ever there to farm a rich result.
Article, Product and Service: attribution and specification
Article supplies author, publisher and dates. Author and date are increasingly load-bearing, because assistants are tuned to prefer attributable and current sources over anonymous, undated ones.
Product and Service supply price, currency, availability and specification in a form that cannot be misparsed. If you publish prices, this is how you reduce the odds of an assistant quoting a number without its conditions.
BreadcrumbList is minor for retrieval but cheap, and it helps establish the topical hierarchy of a large hub.
The mistakes that make schema counterproductive
Marking up content that is not visible on the page is the serious one: it is a policy violation in classic search and a credibility problem for retrieval, because the mismatch is trivially detectable. Stale prices in Product markup are the second, since the markup is machine-read first and will be quoted after the visible page has been updated. Multiple conflicting Organization blocks across a site is the third, and it is common on sites that have accumulated three generations of plugins.
The rule that avoids all three: schema describes what a human can already see on the page, it is generated from the same source as the visible content, and there is exactly one of each identity type per site.
A schema pass worth doing
Add one Organization block, sitewide, with the exact legal name used everywhere else.
Add LocalBusiness with a service area if you serve a region rather than a walk-in address.
Keep FAQPage where the questions are genuine and the answers stand alone.
Add author and date to Article markup, and keep the date honest.
Validate every template, then re-validate after any theme or plugin change.
Want leads like this in your pipeline?
Flock runs the campaigns, screens the enquiries and hands you only the ones that match your service area, job size and capacity. You pay per lead, not per month.
Book a 15-minute fit check | See lead package pricing
Related answers
Frequently asked questions
Will adding schema get me cited?
Not on its own. It removes ambiguity from content that already deserves citation. A well-marked-up thin page stays a thin page.
Is FAQ schema still worth adding after Google reduced rich results?
For retrieval, yes, because the question-answer pairing matches how passages are retrieved. For rich results in classic search, largely no. Add it for the first reason.
JSON-LD or microdata?
JSON-LD. It is the recommended format, it is easier to generate from a template, and it keeps markup separate from presentation so a design change does not silently break it.
How do I check what my markup says?
Use a schema validator on the live URL rather than on your source, since tag managers and plugins frequently inject a second, conflicting block you did not write.
NEED A CLEARER PLAN?
Let’s turn your next move into momentum.
Talk to us →