Schema.org structured data: making a landing page readable by Google (and by AI)
Published on 3 August 2026 · 8 min read
Structured data is a piece of code invisible to the visitor that describes the page's content in a standardised vocabulary — Schema.org — that search engines understand unambiguously: “this is a product, its price is €89, its average rating 4.8 across 23 reviews”. In exchange, Google can enrich how the page appears in its results: stars, expandable questions, price ranges. For a landing page that lives on organic traffic, this markup is one of the few SEO projects that is fast, risk-free and visibly effective at once. This guide complements our general article on landing page SEO.
What structured data changes — and doesn't change
Let's be precise, because the topic carries inflated promises: Schema.org markup is not a direct ranking factor. A marked-up page doesn't leapfrog a better-built one. What it changes is the appearance of the result — and therefore the click-through rate at equal position. The stakes are real: eye-tracking research on search results pages, notably the study by Edward Cutrell and Zhiwei Guan at Microsoft Research presented at CHI 2007 (“What Are You Looking For? An Eye-Tracking Study of Information Usage in Web Search”), showed that attention on a results page is distributed according to the visual and informational richness of each result: lengthening or enriching the snippet measurably changes reading and clicking behaviour. A result with stars and an FAQ occupies more visual surface and provides more relevance cues — that's exactly the lever rich snippets pull.
The four useful markup types on a landing page
| Type | For which page | Possible effect in Google |
|---|---|---|
| FAQPage | Any page with a genuine FAQ section | Expandable questions under the result |
| Product + Offer | Sales page for a product or template | Price, availability, stars if reviews are marked up |
| AggregateRating / Review | Page displaying real customer reviews | Stars in the result |
| Organization / LocalBusiness | Company page, local business | Knowledge panel, local NAP consistency |
The FAQ section is the most profitable starting point: most landing pages already have one (it serves conversion by handling objections), and FAQPage markup is mechanical — each question becomes a Question entity with its answer as acceptedAnswer. Product markup applies as soon as a price is displayed; LocalBusiness as soon as the business has a geographic area, which concerns all local pages like tradespeople or neighbourhood businesses.
JSON-LD: the only syntax worth remembering
Schema.org can be written three ways (microdata, RDFa, JSON-LD); Google explicitly recommends JSON-LD, and it's also the easiest to maintain: a <script type="application/ld+json"> block in the <head> or body, separate from the visible HTML. In a modern stack like Next.js, this block is generated from the same data as the page itself — the displayed price and the marked-up price come from the same variable, which eliminates any risk of divergence. It's one of the structural advantages of a coded landing page over visual builders, detailed in our Next.js vs WordPress comparison.
The rules that avoid a penalty
- Only mark up what's visible on the page — Google's cardinal rule: marked-up reviews absent from the page, or an FAQ in the code but not on screen, expose you to a manual action for misleading structured data.
- Real reviews, never fabricated — marking up a 4.9 rating without verifiable reviews is doubly punishable: by Google, and by consumer law on fake reviews. The core rule from our article on testimonials applies to markup too.
- Test after every release — Google's Rich Results Test and Search Console's “Enhancements” report flag syntax errors and missing properties.
- Don't mark up everything — Article markup on a sales page, a forced HowTo on content that isn't one: off-topic types add nothing and muddy the engine's reading of the page.
The 2026 bonus: structured data also speaks to AI
A second reader has appeared over the past two years: generative AI answer engines, which cite sources in their responses. Clean markup — clear entities, explicit prices, structured FAQ — makes it easier for these systems to extract your information correctly, exactly as it does for Google. Our article on visibility in ChatGPT and generative AI develops this point; the takeaway here is that the same work serves both channels, which further improves its return on effort.
Concretely, for a typical landing page: an Organization block (name, logo, URL), an FAQPage block if the page has an FAQ, a Product block with Offer if it sells something at a displayed price — all in JSON-LD generated from the page's data. It's a few dozen lines of work, to be checked in Search Console the following week. Since LanderKit templates (€89 each, €229 for the 10-template bundle) ship as Next.js code, the addition slots cleanly into the page component, next to the metadata — and if your page is slow, start with load speed instead: rich snippets attract the click, but the page behind them still has to deserve it.
FAQ
Frequently asked questions
Does structured data improve Google rankings?
Not directly: Schema.org is not a ranking factor. What it does is enrich the result's display (stars, expandable FAQ, price), which increases click-through rate at equal position — and that is genuine extra traffic.
Which format should you choose: JSON-LD, microdata or RDFa?
JSON-LD, without hesitation: it's the format Google recommends, it lives in a block separate from the visible HTML, and in a stack like Next.js it's generated from the same data as the page, eliminating divergence between displayed and marked-up content.
Can you mark up an FAQ that doesn't appear on the page?
No: Google requires marked-up content to be visible on the page. Structured data describing absent content counts as “misleading structured data” and exposes the site to a manual action that removes all its rich results.
How do you check that your markup works?
Run the page through Google's Rich Results Test after every release, then monitor Search Console's “Enhancements” report: it lists valid pages, warnings and errors for each markup type detected.
Read next
Related articles
- Do you need breadcrumbs on a landing page?"Home > Templates > Coach & Consultant": that small trail of links under the header looks harmless, almost mandatory out of habit. But a breadcrumb trail assumes a hierarchy of pages to climb back through — exactly what an ad-driven landing page, built to show a single path to a single CTA, doesn't have. Two studies on actual breadcrumb usage and a quiet change Google made in 2025 help settle the question page by page, rather than on principle.
- Attribution models: who really deserves credit for your landing page's conversions?One landing page, five traffic sources, a single form submission: who gets the credit? The answer depends entirely on the attribution model you apply — and that choice, usually made by default, decides where your ad budget goes next month. A tour of the six models, the reasons your tools will never agree, and the stance to take when you have no data team.
- Google reviews widget on a landing page: where to put it and how to mark it up without slowing the page downDropping a Google or Trustpilot reviews widget at the top of a landing page seems like the fastest way to reassure a visitor who has never heard of you. In practice, most of these integrations slow the page down, misuse the Schema.org markup Google actually allows, or ignore the cookie consent banner the script itself triggers. Here's how to get all three right.