Skip to content
EN · $
Panel Login Buy Package
Technical SEO

Structured Data (Schema.org, JSON-LD) Guide: How to Add It

6 min read

Structured data (schema.org markup) is a way of explicitly describing a page's content to search engines using a standard vocabulary: this is an article, that is a product, and this one is a business's address information. Google uses structured data to understand your page more accurately and, when appropriate, to display it richly in search results (such as breadcrumbs, product prices, or review stars). In this guide we explain step by step what schema.org and JSON-LD are, which types genuinely work, how to add them, and how to test them.

What is structured data?

When a person sees "$199.90," they understand it is a price; a bot can only guess that from context. Structured data removes that guesswork. schema.org is the shared vocabulary developed jointly by Google, Microsoft, and other search engines; it defines hundreds of types (Article, Product, Organization, Event, Recipe...) and the properties of each type (name, price, author...).

An important fact: structured data is not a direct ranking factor. It does not move your page up. Its contribution comes in two ways: better understanding of the content, and the chance to earn a rich result appearance. A more eye-catching result can increase the click-through rate, which is an indirect gain (you can review our CTR improvement guide on click-through rates).

Why JSON-LD?

Structured data can be written in three formats: JSON-LD, Microdata, and RDFa. Google recommends JSON-LD. The reason is simple: JSON-LD is not interspersed among the page content; it sits in a separate <script type="application/ld+json"> block. This makes it manageable independently of the design, easy to maintain, and less prone to errors. The block can be placed in either the <head> or the <body> section of the page.

Which types are useful?

You do not need to add every type to every page. What matters is choosing the type that matches what the page really is. The table below summarizes common cases:

TypeOn which page?What does it provide?
OrganizationHome page / about usBrand name, logo, official profiles; clear definition of the organization
Article / BlogPostingBlog and news articlesClarifies the title, author, and date information
BreadcrumbListInner pagesDisplays a trail (category > subcategory) in results instead of the address
Product + OfferProduct pagesProduct rich results such as price, stock, and reviews
LocalBusinessLocal business pageAddress, opening hours, phone; supports local visibility
Event, Recipe, JobPostingRelated content pagesSpecial rich results such as events, recipes, and job listings

Rich result support changes over time. In 2023, Google limited the FAQ rich result to well-known government and health sites, and removed the HowTo rich result entirely. Adding these markups does no harm, but for most sites the appearance in results does not change. Always check the current list of supported types in the Google Search Central gallery.

If you are a local business, the LocalBusiness markup should be considered together with your visibility in Google Business Profile and maps; for the full topic, see our local SEO guide.

Example: Article and Organization markup

A basic JSON-LD block for a blog post can be written like this. Change the field names and values to suit your own page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "What is a canonical tag?",
  "datePublished": "2026-11-06",
  "dateModified": "2026-11-06",
  "author": {
    "@type": "Person",
    "name": "Jane Smith"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Ltd.",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.example.com/logo.png"
    }
  },
  "mainEntityOfPage": "https://www.example.com/blog/canonical-etiketi-nedir"
}
</script>

In this, @context specifies that the vocabulary is schema.org, and @type specifies the type of the object. All fields must be consistent with the information visible on the page: if the page has no author name, do not put an invented author in the block. On a corporate site's home page, an Organization type can similarly provide the name, logo, and official social media addresses (sameAs). To make the author and organization's credibility visible on the page as well, see our E-E-A-T guide.

The BreadcrumbList markup used for the breadcrumb trail is a list of ordered items:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Blog",
      "item": "https://www.example.com/blog"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Technical SEO"
    }
  ]
}
</script>

For the last item (the page you are currently on), the item address is optional. Each item must appear in the same order and with the same names as the visible breadcrumb trail on the page.

On product pages, if offers (price, currency, stock status) are included in the Product type and there are genuine user reviews, aggregateRating is added. The rule here is very clear: price and stock information must match what is shown on the page, and the rating must come from real and verifiable customer reviews. Markup showing an old price misleads users and turns into a warning in Search Console.

Step-by-step implementation plan

  1. Identify your page types. How many different templates does your site have? Home page, category, product, article, contact, and so on. A single markup plan per template is sufficient.
  2. Map the right type to each template. Use the table above; do not add a type you are unsure of.
  3. Generate it dynamically in the template code. Fill fields such as title, date, and price from the database; hand-typed fixed values become outdated over time.
  4. Test three to five sample pages. If there are no errors, roll it out more broadly.
  5. Monitor in Search Console. After publishing, check the counts of valid and erroneous pages, and prioritize the warnings.

Google's core rules

  1. Markup must match the visible content. Adding a price, rating, or review that is not on the page violates Google's spam policies and carries the risk of a manual action.
  2. Use the correct type. Do not add Product to a page that is not about a product, or AggregateRating without a genuine review.
  3. Fill in the required properties. Each rich result type has required and recommended fields; if a required field is missing, the result will not be shown.
  4. The page must be crawlable. Markup on a page blocked by robots.txt or carrying noindex is not used.
  5. Structured data guarantees nothing. Being valid does not mean the rich result will appear; Google decides for itself whether to show it.

How detailed a markup should be is your decision, but there is no need to go into unnecessary depth. For an article, the title, author, publication and update dates, image, and publisher information are often sufficient. Before adding a new property, check whether it has a counterpart in Google's documentation; if it does not, adding it will have no effect on results.

Testing and validation

Carry out a two-stage check before and after publishing:

  • Google Rich Results Test: By pasting a URL or code, you can see which rich results the page is eligible for, along with errors and warnings.
  • Schema Markup Validator (validator.schema.org): Validates general schema.org syntax that is not specific to Google.
  • Search Console → Enhancements: Tracks the counts of valid, warning, and erroneous pages for the types found on your site. If you have added a new type, expect the report to appear a few days later.
  • URL Inspection: Confirms that the markup is present in the version of the live page processed by Google; it is especially useful for blocks added with JavaScript.

If you have not yet set up Search Console, follow our getting-started guide. Structured data is part of the technical health check; for other items, use our technical SEO checklist.

Common mistakes

  • Marking up content that is not visible. Information the user cannot see should not appear in the markup either.
  • Adding fake reviews or ratings. Marking up reviews that did not come from real users, but that you wrote yourself, is a policy violation.
  • Duplicate blocks from a plugin. If the theme and an SEO plugin both generate the same Article markup, they conflict; keep only one.
  • Malformed JSON. A missing comma, quotation mark, or curly brace invalidates the entire block. Do not publish before passing it through a validator.
  • Outdated information. If the price, stock, or event date changes but the markup is not updated, Search Console issues a warning and user trust suffers.
  • Unnecessary excess. Filling a page with types that have no rich result is a waste of time; first focus on the three to five types your site really needs.

Frequently asked questions

Does structured data improve my rankings?

Not directly. It helps the content be understood and increases the chance of earning a rich result; this can indirectly affect the click-through rate.

Which plugin or tool should I use?

Your CMS's SEO plugin automatically generates the basic types; for most sites this is sufficient. For custom types, add JSON-LD by hand or through template code, and always pass it through a validator.

Is it a problem to add JSON-LD with JavaScript?

Google can process JSON-LD added with JavaScript, but where possible, placing it server-side in the initial HTML response is more reliable.

I got an error, will my rich result disappear immediately?

Invalid markup or markup that violates a policy can cause the rich result appearance to be lost. Fix the error and start validation from Search Console; re-evaluation takes time.

Conclusion

Structured data is not a shortcut promising quick gains; it is a regular way of presenting your content accurately. Use JSON-LD, mark up only the information that is genuinely on the page, test with validators, and monitor regularly in Search Console. To start, adding Organization to the home page, Article to articles, BreadcrumbList to inner pages, and Product to products is enough for most sites. Spend the rest of your time on content quality and speed.

Is your keyword missing clicks?

HitBot generates real sessions that search for your target keyword, find your site and click it. The results accumulate in Search Console as impressions and clicks.

Other posts