Schema markup can help search engines interpret a page, but only when the structured data accurately describes visible content and follows the requirements for the chosen result type. This guide gives you a repeatable workflow for selecting schema, adding JSON-LD, validating the implementation, and troubleshooting errors before and after publishing.
Overview
Schema markup is a form of structured data that labels information on a webpage in a machine-readable format. It can identify details such as an article’s author, a product’s price, an event’s date, a recipe’s ingredients, or a business’s opening hours. The vocabulary commonly used for this purpose is Schema.org, while JSON-LD is a practical format for placing the data in a page.
Structured data is not a substitute for useful content, crawlable HTML, sound technical SEO, or search intent optimization. It also does not guarantee an enhanced search appearance. Instead, treat it as a clear description of the page that may help search systems understand eligible content.
Schema type comparison
| Page or entity | Potential schema type | Use it when | Important check |
|---|---|---|---|
| Blog post or news-style page | Article, BlogPosting, or NewsArticle | The page is a genuine article with identifiable editorial content. | Match the headline, author, image, and publication or modification dates to the visible page. |
| Product detail page | Product | The page describes one purchasable or identifiable product. | Keep offers, availability, currency, ratings, and reviews consistent with what shoppers can see. |
| Local business page | LocalBusiness or a more specific subtype | The page represents a real location or service-area business. | Use accurate business name, address, contact details, and opening hours. |
| Event landing page | Event | The page describes a specific event with a date, place, or online attendance details. | Do not use it for a general service, recurring availability, or an event that is not actually represented on the page. |
| How-to instructions | HowTo | The page provides a genuine sequence of steps for completing a task. | Steps, tools, materials, and outcomes should be visible and complete. |
| Frequently asked questions | FAQPage | The page contains questions and answers controlled by the site owner. | Mark only questions and answers that are visible and genuinely part of the page. |
| Organization or website identity | Organization or WebSite | The page explains the site, organization, or publishing entity. | Use stable names, URLs, logos, and profiles rather than promotional claims that are difficult to verify. |
The table is a starting point, not a reason to add every possible type. Select the smallest relevant set of entities that describes the page clearly. A blog post may need an Article entity and an author reference; it does not automatically need product, event, or FAQ markup.
A page-to-markup decision tree
- What is the page primarily about? Identify the main entity: an article, product, event, business, recipe, course, or another clearly defined subject.
- Is there a relevant Schema.org type? Choose the most specific type that accurately fits the visible content. If no specific type fits, use a broader type or leave the page unmarked.
- Does the chosen type support a result feature you are pursuing? Check the current requirements in Google’s Search documentation rather than relying on an old screenshot or plugin setting.
- Are the required details visible? Do not add properties solely because they might be useful. Every important value should be supported by the page.
- Can the implementation be tested? Generate JSON-LD, validate its syntax, test the URL or code, and inspect the rendered page after deployment.
Checklist by scenario
For an article or blog post
- Choose an article type that matches the editorial format.
- Use the page’s actual headline, canonical URL, primary image, author, and publication date.
- Use a modification date only when the page was meaningfully updated, and make sure the visible page supports that information.
- Connect the article to its author and publishing organization when those entities are clearly represented.
- Check that the structured headline does not contradict the title shown on the page.
Structured data should reinforce the page’s editorial purpose. For planning the content itself, the SEO Content Brief Template can help align the target query, intent, page type, and supporting information before markup is added.
For a product page
- Mark the specific product represented by the URL, not a whole category or collection.
- Use the product name, image, brand, identifiers, and description consistently with the page.
- Represent the offer accurately, including price, currency, availability, and the applicable seller when those fields are used.
- Only include review or aggregate rating information when the page visibly contains the corresponding reviews or rating.
- Test variant URLs carefully if size, color, or configuration changes the visible product information.
For a local business
- Select the most appropriate business subtype when one exists.
- Keep the name, address, phone number, URL, logo, and opening hours consistent across the page and business profiles.
- Distinguish a physical location from a service-area business; do not publish an address that is not intended for customers.
- Use one principal entity for the business page and connect related locations only when the page genuinely describes them.
For an event, how-to page, or FAQ
- Use
Eventonly for a specific event with accurate timing and attendance information. - Use
HowTowhen the page provides complete, sequential instructions rather than a brief list of tips. - Use
FAQPageonly when the questions and answers are visible and controlled by the site owner. - Remove properties that describe content no longer present after an update or template change.
For a WordPress website
First identify whether your SEO plugin, theme, or custom code already outputs structured data. Adding a second implementation without checking the source can create duplicate or conflicting entities. Review the rendered HTML, decide which system should be authoritative, and customize only the fields that your page actually supports. A plugin’s checkbox is not a substitute for validation.
How to add and validate JSON-LD
JSON-LD is usually placed in a script element in the page head or body. The following simplified example describes an article; replace every placeholder with real page data:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/example-article/"
},
"headline": "Example Article Headline",
"image": [
"https://example.com/images/example-article.jpg"
],
"datePublished": "2026-01-15",
"dateModified": "2026-02-01",
"author": {
"@type": "Person",
"name": "Example Author"
},
"publisher": {
"@type": "Organization",
"name": "Example Organization",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/images/logo.png"
}
}
}
</script>
For a smaller website, a manual JSON-LD block may be sufficient. For a site with many templates, dynamic generation is more practical, but it must pull values from the correct page fields. Never copy the same author, date, price, or URL into every template simply because the fields are required by a code example.
Implementation and validation checklist
- Record the page URL, canonical URL, page type, and primary entity.
- List the visible facts you intend to describe.
- Choose a schema type and review its properties and relevant result requirements.
- Generate valid JSON-LD with correctly escaped characters, complete URLs, and valid dates.
- Check the code with a structured-data testing tool, then use Google’s Rich Results Test when you are assessing eligibility for a supported result.
- Use the Schema Markup Validator for broader Schema.org syntax and vocabulary checks; passing it does not guarantee a Google search feature.
- Publish or update the page, inspect the rendered source, and test the live URL again.
- Monitor validation reports and search performance rather than assuming that an eligible result will always appear.
For indexing and live-page checks, pair structured-data testing with the Google Search Console URL Inspection Guide. This separates a markup problem from a crawl, indexing, canonical, or rendering problem.
What to double-check
- Visible-content alignment: The name, price, date, author, rating, answer, or instruction in the markup must be supported by the page.
- Canonical consistency: The URL in
mainEntityOfPage,@id, or related fields should not point to a different version without a clear reason. - Entity relationships: Use stable identifiers to connect an article to its author or a product to its brand, but do not create fictional entities.
- Date accuracy: Dates should use a consistent machine-readable format and reflect the page’s real publishing or update history.
- Image availability: Referenced images should be accessible, relevant, and representative of the entity they describe.
- Template behavior: Test several URLs, including older pages, paginated pages, variations, and pages with missing optional fields.
- Search eligibility: Separate syntax validity from eligibility. A valid Schema.org object may not qualify for every search appearance.
Common mistakes
Adding markup because it is available
More markup is not automatically better. Unsupported or irrelevant types make maintenance harder and can obscure the page’s primary entity. Start with the page purpose and add only information that improves clarity.
Marking up hidden or misleading content
Do not describe reviews, prices, FAQs, events, or offers that users cannot find on the page. If content is removed during a redesign, remove its structured data at the same time.
Copying example code without replacing every value
Placeholder URLs, generic author names, stale dates, and incorrect images are common causes of inaccurate markup. Create a field-by-field review before deployment.
Confusing warnings with errors
An error usually means the implementation cannot be interpreted as intended or is missing an important requirement. A warning may identify optional information or a recommended improvement. Review both, but prioritize errors and mismatches with visible content.
Ignoring duplicates after a platform change
When a theme, plugin, CMS, or template changes, inspect the source for repeated Article, Organization, Product, or breadcrumb entities. Consolidate competing outputs where they describe the same entity differently.
When to revisit your schema markup
Use this checklist whenever you publish a new page type, change a template, add products or reviews, migrate platforms, alter business details, or receive a new validation error. It is also sensible to review structured data during seasonal planning cycles, before major promotions or events, and whenever your SEO or publishing workflow changes.
At each review, compare the markup with the current visible page, retest representative URLs, check the canonical and indexability signals, and record unresolved warnings separately from blocking errors. Recheck documentation and testing tools after major changes to supported result requirements rather than relying on an old implementation guide.
For a practical maintenance routine:
- Keep a spreadsheet of page templates, schema types, responsible fields, and last validation date.
- Test one URL from every important template after releases or migrations.
- Review product, event, review, and business details whenever the underlying information changes.
- Investigate sudden changes in search appearance or organic performance alongside technical reports; do not attribute every change to structured data.
- Remove markup that no longer matches the page, then validate the revised live URL.
Used this way, schema markup becomes part of your technical SEO checklist rather than a one-time code insertion. The goal is not to mark up everything; it is to maintain an accurate, testable description of each important page as your website evolves.