How to Add Schema Markup to a Single Page
A plain, step-by-step guide to adding schema markup to one page with JSON-LD. Copy the code, validate it, and help AI answers cite you instead of a rival.
To add schema markup to a single page, paste a JSON-LD script into the page's HTML head. That is the whole job. You write a small block of structured data that describes what the page is, wrap it in a <script type="application/ld+json"> tag, drop it in the <head>, and validate it. No plugin is required, though a plugin can do it for you. The steps below show the exact code and where it goes.
What is schema markup, in plain terms?
Schema markup is a labeled description of your page that machines read. Humans see your headline and your price. Search engines and AI models see raw HTML and guess. Schema removes the guessing. It tells them this is an article, this is a product, this costs $29, this person wrote it. The common format is JSON-LD, and both Google and the AI answer engines prefer it.
This matters more now than it used to. When ChatGPT or Perplexity answers a question, it picks sources it can parse cleanly. If a competitor labeled their page and you did not, the model understands their page better and may name them instead of you. Clean structured data is one small way to tilt that back toward you. More on that idea in what is AI visibility.
How do you add schema markup to a page?
Here is the direct path for one page. Pick the type that matches the page, fill in real values, and paste it in.
- Pick one type. An article uses
Article. A product page usesProduct. A service or homepage often usesOrganizationorWebPage. Do not stack five types on one page. One primary type is enough. - Write the JSON-LD. Copy the template below and swap in your real title, URL, author, and dates. Keep the field values honest. They must match what a visitor actually sees on the page.
- Paste it into the head. Put the full
<script>block inside the<head>of that one page. In WordPress you can drop it in a custom HTML block or a header-scripts field. In a static site or framework, add it to that page's template. - Validate before you trust it. Run the URL through Google's Rich Results Test and the Schema.org validator. Fix any red errors. Warnings are usually fine to leave.
- Recheck after edits. If you change the page title or price later, update the schema too. Stale schema that lies about the page can hurt more than no schema.
A working Article example
This is a minimal block you can adapt. Replace every value in quotes with your own.
"@type": "Article"sets what the page is."headline"is the visible title of the page."author"names the person or brand, as a nestedPersonorOrganization."datePublished"and"dateModified"use ISO dates like2026-07-24."mainEntityOfPage"points back to the page URL so the label is unambiguous.
Which schema type should you use?
Match the type to the job the page does. A blog post is an Article or BlogPosting. A pricing or store page is a Product with an Offer. An about or contact page is Organization. A how-to is HowTo. A FAQ block is FAQPage. If a page does two jobs, pick the main one. Trying to describe everything at once produces messy markup that validators choke on.
Why does one page's schema affect AI answers?
AI answer engines build a short list of sources they can quote with confidence. Structured data raises confidence. When your page clearly states its type, author, and key facts, the model has less to guess and more to cite. That is the whole point of answer engine optimization, and schema is one of its cheapest wins.
It is not magic. Schema will not rank a thin page or invent authority you do not have. But on a page that already deserves to be found, it removes friction. It is the difference between a machine reading your page and a machine understanding it.
Common mistakes to skip
- Marking up content that is not on the page. If the schema claims a rating, the rating must be visible to visitors.
- Copying a template and forgetting to change values. Placeholder author names and wrong URLs are the most common errors.
- Adding schema and never validating. A single missing bracket breaks the whole block silently.
- Stacking conflicting types on one page and hoping engines sort it out. They do not.
Add the block, validate it, keep it honest, and move to the next page. When you want a second opinion on how readable your whole site is to AI, start with the Page Audit and check your AI visibility from there.