What is Schema Markup & Confirm It’s Working

Last reviewed October 27, 2026.

Schema markup is structured data that describes what a webpage contains in a format search engines can interpret. It can identify an article’s author, a product’s price or a business’s address. You can check it with the Schema Markup Validator and Google’s Rich Results Test, then use Search Console to inspect what Google has indexed.

Schema can help Google understand a page and may make it eligible for a supported search feature. It is not a shortcut to first place: valid markup does not guarantee a rich result, a ranking increase or more traffic. The best starting point is a useful page with accurate information, followed by markup that describes that information.

What is schema markup?

Schema.org is a shared vocabulary for describing entities and their properties. A page about a blog article might identify an Article, its headline, author and publication date. A product page may describe a Product and its offer. The words on the page remain important; markup gives machines a more explicit description of the same information.

Schema.org provides the vocabulary. JSON-LD, Microdata and RDFa are ways to encode it. Google supports all three and recommends JSON-LD where practical. JSON-LD is usually added as a separate script in the page’s HTML; a content management system or SEO plugin can generate it for you. See Google’s introduction to structured data.

How schema markup can help SEO

Google can use structured data to understand page content and support particular search appearances, such as eligible product or recipe features. Each supported feature has its own requirements. A Schema.org type does not automatically correspond to a Google feature, and a page that passes a technical test may still appear as a standard search result.

Markup also cannot compensate for an inaccurate or unhelpful page. Google’s structured data guidelines require markup to represent the page and its visible content. Do not invent reviews, hide material claims from visitors, or add properties that do not apply simply to try to trigger a result.

Illustration: structured data can help search engines understand a page; rich results are not guaranteed.

Which schema type should you use?

  • Article or BlogPosting: for an editorial article, with details such as its headline, author and dates.
  • Product: for a page describing a real product or offer. Check Google’s product documentation for the particular result you want to support.
  • Organization: for information about the business or organization described on your site.
  • LocalBusiness: for a real local business or branch, using accurate information about that location.

Choose the type that describes the page, rather than adding every possible type. Google’s search gallery shows the structured-data features it supports and links to their specific requirements.

Schema markup example: a blog article in JSON-LD

The following is a fictional example for a blog article. The code is shown as text here; it does not install markup on this page. Replace each value with the real page URL, visible headline, author and dates. Do not copy the example details onto a live website.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Prepare for a Service Appointment",
  "url": "https://example.com/appointment-guide/",
  "author": {
    "@type": "Organization",
    "name": "Example Business",
    "url": "https://example.com/about/"
  },
  "datePublished": "2026-04-15T09:00:00-07:00",
  "dateModified": "2026-10-27T09:00:00-07:00"
}
</script>

Here, @context identifies the vocabulary and @type identifies the content. The other properties describe the actual article. Use the true publication and substantive modification dates; do not change a date merely to make an article appear fresh. Add other relevant properties when accurate. Google’s Article documentation currently lists recommended properties and states that this type has no required properties. Other search features can have different requirements.

How to add schema markup to a website

  1. Choose a representative page. Identify the main content and the supported search feature you want to help Google understand. Read that feature’s current documentation.
  2. Check for existing markup. Your website theme, builder or SEO plugin may already add it. Inspect the page with a validator before adding another version. Multiple entities can be legitimate; duplicate or contradictory descriptions of the same entity need review.
  3. Populate accurate details. Match the page’s visible headline, author, prices, business details or other relevant facts. Keep the information current.
  4. Add it through your site’s existing workflow. Use the SEO plugin or template that owns the markup, or add an appropriate JSON-LD script to the page HTML if your platform supports it. Avoid adding an unrelated block across every page.
  5. Test both the code and the published page. Correct errors at the source, publish, and verify that the public URL is accessible to Google.

For a WordPress site, find out what the existing SEO plugin or theme already generates before installing another schema plugin. A single maintained source is easier to keep consistent than two conflicting sources.

How to test schema markup

On small screens, scroll the table horizontally to view all columns.

Choose a test based on what you need to check
ToolWhat it checksWhat it does not prove
Schema Markup ValidatorDetects and validates Schema.org structured data, including types outside Google’s supported rich-result features.It does not guarantee a Google rich result.
Google Rich Results TestTests a public URL or code snippet for Google-supported rich-result structured data and reports detected issues.It does not show every possible Schema.org type or guarantee a displayed result.
Search Console URL InspectionShows information about Google’s indexed version of a URL and offers a live URL test.A successful live test does not by itself mean the page has been indexed or will receive a rich result.

To test the example, open Google’s Rich Results Test, select Code and paste the complete script shown above. Run the test, inspect the detected article item and read its messages. Once your real markup is live, repeat the test using URL so you can check the published page and its accessible resources. Some result types offer previews, but a preview is only an illustration of a possible appearance.

Then open Search Console for the correct property and inspect the page’s URL. Review the indexed version and, if necessary, run a live test. Fix critical errors, review warnings in context, and request recrawling when appropriate. Crawling and indexing can take time; a request does not guarantee immediate indexing or a search feature.

Common schema problems to fix

  • Markup differs from the page: update old prices, hours, authors or other fields to match current visible content.
  • Conflicting output: check what your theme and plugins generate before adding another block for the same item.
  • The page cannot be accessed: check login requirements, crawl restrictions and indexing settings when a public search result is intended.
  • A valid type has no Google preview: check whether Google supports a search feature for that type; general schema validity and rich-result eligibility are separate questions.
  • A preview is mistaken for a promise: results vary, and Google decides whether a particular feature appears.

Need help reviewing schema, page content and technical SEO together? Explore Oi Marketing’s SEO services or contact our team.

Scroll to Top