How to add structured data to your site — step by step, no plugins

Good news: structured data isn't a plugin, a builder, or a toggle in some dashboard. It's a text block you paste into the page head yourself. The first page takes about twenty minutes; every page after that takes five, because you do it once in the template.
Bad news: half the examples online start with a type Google no longer shows. Let's begin there.
Step 1. Pick a type — and don't pick FAQPage
The type must describe what's genuinely on the page. Three options cover almost everything:
- Article (or BlogPosting) — a post, an article, a write-up.
- Organization — your homepage: who you are, logo, links.
- Product or LocalBusiness — a product, or a business with an address.
Do not take FAQPage, even though it dominates the examples. Google switched FAQ snippets off in Search on 7 May 2026 and removed the documentation in June. The markup will pass validation and give you nothing.
Step 2. Build the block
The format is JSON-LD: ordinary JSON inside its own script tag. Here's a working starter for an article, straight from Google's docs:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Title of the article",
"image": ["https://example.com/photos/16x9/photo.jpg"],
"datePublished": "2026-09-03T08:00:00+03:00",
"dateModified": "2026-09-03T08:00:00+03:00",
"author": [{
"@type": "Person",
"name": "Author Name",
"url": "https://example.com/about/"
}]
}
</script>
Three things people trip on:
@contextand@typeare mandatory — without them it's just JSON, not markup.- Dates in ISO format, with a timezone.
- The image as an absolute URL, starting with
https://.
Step 3. Paste it into the page head
It goes inside the head tag. Not by hand into every HTML file: put the block in your shared page template and fill the values from the article's data. New pages then get their markup automatically.
One rule: the block describes this page. Article markup belongs on the article page, not on the homepage.
Step 4. Check with two tools, not one
They do different jobs, and you need both:
- validator.schema.org — checks syntax and vocabulary. Answers "is this valid markup at all."
- search.google.com/test/rich-results — checks eligibility for a rich result. Answers "would Google show a card."
Markup can pass the first and fail the second — for example, when a required property for that type is missing. Run them in that order.
Step 5. Match the markup against what's visible on the page
This is the step people skip, and the only one that carries a penalty.
The rule from Google's guidelines: "Don't mark up content that is not visible to readers of the page." If the markup says a 4.9 rating, the page must show a 4.9 rating. If it declares a price, the price must be in the listing.
A mismatch earns a manual action, and the wording in the docs is harsh: the page loses eligibility to appear as a rich result. So you don't merely miss out on stars — you lose the ability to earn them.
Walk through every property in your block and find it with your eyes on the page. Can't find it? Delete the property.
Step 6. Ship it and watch Search Console
Markup won't appear the moment you deploy: the crawler has to revisit the page first. After that, Google Search Console has a rich results report showing how many pages of that type Google saw and where it found errors.
What you get
In the page source: one invisible block. In search: a card with an image, a date and an author instead of a bare blue link.
Just keep the main limitation in mind — it's written into the docs in plain words:
Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly.
If the markup is there and valid but no card appears, that's its own story with three typical causes: why your rich snippet isn't showing.
If your pages are generated by code
A separate case that trips up anyone whose site isn't a pile of static files.
Interpolate the values, don't hand-write the block. The headline, date and author already exist in your article data — take them from there. Otherwise half your pages will carry someone else's date within a month.
Escape your quotes. If an article title contains a quote mark and you're pasting it into JSON as a string, the block breaks silently. Build an object and serialise it with your language's own tools instead of gluing strings together.
Ship the block in the HTML itself. Google can execute JavaScript, but there's a gap between "can" and "will, on your page, today." Markup painted in by a script in the browser gets indexed later, and not always.
How to check: open the page source (the actual source, not the devtools panel) and search for your block in it. Not there? A script is drawing it.
And one rule from Google's guidelines worth remembering right away: don't create blank or empty pages just to hold structured data.
How long until the card appears?
From a few days to a couple of weeks — the page has to be recrawled first. If the page isn't indexed at all, markup won't help: sort out indexing first.
Can one page carry several types at once?
Yes. For example Organization for the site and Article for the piece itself. Each type in its own script block is perfectly normal.
Will markup slow my site down?
No. It's a few lines of text in the head — no requests, and no scripts that execute anything.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





