What Is Schema Markup and Why Google Loves It

October 17, 2026 • NOFYI Editorial Team

Schema markup sounds technical, and in a way it is. In practice, it is a simple idea: you add a small amount of structured information to a page so that search engines can understand what the page is about. That structured information does not change what visitors see, but it can change how search engines interpret your content and, in some cases, how your page appears in search results.

This guide explains schema markup in plain language, focusing on JSON-LD, the format Google recommends. It covers the most common types for ordinary websites — Article, FAQ, and Product — and includes a worked example for a chocolate cake recipe. It also explains the limits: rich results are not guaranteed, and schema is not a shortcut to better rankings. Used well, it is a way to communicate clearly with search engines.

What Is Schema Markup?

Schema markup is a vocabulary for describing content on the web. It was created through Schema.org, a collaboration by major search engines to agree on a shared way to label things such as articles, products, events, recipes, people, organisations, reviews, and questions. When you add schema to a page, you are labelling the parts of that page in a way that a machine can read. For example, you can label a headline as the name of an article, a date as the date it was published, and a person as the author.

Without schema, a search engine has to guess the meaning of text from context alone. With schema, you provide an explicit map. The text on the page might say Chocolate Cake Recipe, followed by ingredients and steps. Schema can state that this is a Recipe, that the preparation time is 20 minutes, that the recipe yields eight servings, and that a particular block of text is an ingredient. That clarity helps a search engine understand the page more reliably, even if the page design is unusual or the wording is creative.

Schema markup is not visible to most visitors. If you add it correctly, the page looks the same in a browser. The structured data sits in the code of the page, either in the head section or in the body, depending on the format. That invisibility is part of why beginners sometimes find it confusing. You cannot see the result by looking at the page, but you can check it with testing tools, which we will cover later.

JSON-LD: The Format Google Recommends

There are several ways to add structured data, but Google recommends JSON-LD, which stands for JavaScript Object Notation for Linked Data. JSON-LD is a block of code, usually placed in a script tag, that contains the structured data as a set of key and value pairs. It is separate from the visible content, which makes it easier to maintain than formats that require you to add attributes to every HTML element on the page.

A simple JSON-LD block starts by declaring its context as https://schema.org, then its type, such as Article or Recipe, and then its properties. Properties can include simple values, such as a headline or a date, or nested objects, such as an author with a name and a type. The structure is logical once you have seen a few examples. You do not need to memorise every property. You need to understand the pattern and to check the documentation for the type you are using.

Many content management systems and SEO plugins can generate JSON-LD automatically. In WordPress, for example, Rank Math and similar plugins can add Article schema to posts, FAQ schema to FAQ blocks, and Product schema to product pages. That automation is helpful, but it is still worth understanding what the plugin is generating. If the plugin produces incorrect or incomplete data, you will be better placed to spot the problem if you know the basics.

Common Schema Types: Article, FAQ, and Product

Article schema describes a written piece of content, such as a blog post or news article. It can include the headline, the author, the date published, the date modified, an image, and the publisher. For a blog, Article schema is one of the most relevant types. It helps search engines understand that the page is an article, who wrote it, and when it was published. It does not guarantee a special appearance in search results, but it provides a clear, structured summary of the article.

FAQ schema describes a page, or a section of a page, that contains questions and answers. Each question is paired with its accepted answer. This type is useful when a page genuinely contains a FAQ section that helps readers. It is not meant for adding a list of questions that do not appear on the page. The questions and answers in the schema should match the visible content. If they do not, the schema is misleading and may be ignored.

Product schema describes a product that can be bought. It can include the product name, image, description, brand, price, availability, and review information. For an online store, Product schema is important because it helps search engines understand what is being sold and whether it is in stock. It must be accurate. If the price in the schema does not match the price shown to shoppers, that mismatch can erode trust and may cause the structured data to be treated as invalid.

There are many other types, including Recipe, Event, HowTo, LocalBusiness, and Person. You do not need to use all of them. Choose the type that best matches the main purpose of the page. If a page is primarily a recipe, use Recipe. If it is primarily an article with a short FAQ at the end, use Article for the main content and FAQ for the FAQ section. Matching the type to the content is more important than adding as many types as possible.

How to Add Schema Markup

For most site owners, the simplest route is to use an SEO plugin or a dedicated structured data plugin. These tools add JSON-LD automatically based on the content you publish. After installing and configuring the plugin, publish a test post, then use a testing tool to check that the schema is present and valid. The plugin settings usually let you choose which types to enable for posts, pages, and products, and let you add default information such as the publisher name and logo.

If you need custom schema, you can add a JSON-LD block manually. In WordPress, you can add it through a custom HTML block, through your theme settings if they support it, or through a plugin that lets you insert code into the head of a page. When you add schema manually, be careful with syntax. JSON is sensitive to missing commas, unclosed brackets, and misplaced quotation marks. A single syntax error can make the whole block invalid. Always test after adding manual schema.

Whichever method you use, keep the schema in sync with the visible content. If you update the price of a product, update the Product schema as well. If you change the date of an event, update the Event schema. If you remove a FAQ from the page, remove it from the FAQ schema. Search engines compare structured data with what users see, and inconsistencies can cause the data to be ignored.

Worked Example: A Chocolate Cake Recipe

Imagine you publish a blog post with a chocolate cake recipe. The visible page includes a title, a short introduction, a list of ingredients, step-by-step instructions, preparation time, cooking time, and the number of servings. Without schema, a search engine sees that text and tries to infer that it is a recipe. With Recipe schema in JSON-LD, you can state it directly.

In the JSON-LD block, you would set the context to https://schema.org and the type to Recipe. You would set the name to something like Classic Chocolate Cake. You would add the author as an object with a type of Person and a name, and the datePublished as the date the post was published. You would add a description that summarises the cake in one or two sentences, and an image that shows the finished cake.

Next, you would add the recipe-specific properties. Preparation time might be 20 minutes, cooking time 30 minutes, and total time 50 minutes, expressed in the ISO 8601 duration format that schema expects. Recipe yield might be 8 servings. Recipe ingredients would be a list of items such as 200 grams of plain flour, 200 grams of caster sugar, 75 grams of cocoa powder, and so on. Recipe instructions would be a list of steps, each as a HowToStep with its own text. The order matters, because the steps describe the process in sequence.

The point of this example is not that you must memorise the exact JSON syntax, but that you can see how each visible part of the page maps to a structured property. The title maps to name. The ingredients list maps to recipeIngredient. The steps map to recipeInstructions. The times map to prepTime, cookTime, and totalTime. When that mapping is clear and accurate, the structured data is a faithful summary of the page, not a separate piece of marketing.

If you use a recipe plugin or an SEO plugin, much of this will be generated from fields you fill in when you publish the recipe. You would enter the ingredients, steps, times, and servings in the plugin interface, and the plugin would output the JSON-LD for you. The worked example shows what the plugin is doing behind the scenes, and it helps you check that the output matches the visible recipe.

How to Validate With the Rich Results Test

After adding schema, you should test it. Google offers a Rich Results Test that lets you enter a URL or paste code and see whether the page is eligible for rich results. The tool shows which types of structured data it detected, whether there are errors or warnings, and which properties are missing. It does not guarantee that a rich result will appear, but it tells you whether the code is valid and whether Google can read it.

To use the test, open the Rich Results Test, enter the URL of the page you want to check, and run the test. Review the results carefully. Errors need to be fixed because they can prevent the structured data from being understood. Warnings are less severe, but they often indicate that a recommended property is missing. For example, a warning might say that an image is missing for a recipe. Adding the missing property can improve the completeness of the data.

You can also use the Schema Markup Validator, which checks structured data more generally and is not limited to rich results. It is useful for types that do not produce a rich result but still help search engines understand the page. Test after every significant change to a page, especially if you edit the title, price, date, or other fields that appear in the schema.

Limitations: Rich Results Are Not Guaranteed

Adding schema does not guarantee that your page will get a rich result. A rich result is an enhanced appearance in search results, such as a recipe card with a rating and cooking time, or a FAQ drop-down. Google decides whether to show a rich result based on many factors, including the quality and relevance of the page, the search query, and whether the structured data meets its guidelines. Valid schema is a requirement for eligibility, not a promise of display.

Schema also does not directly improve rankings on its own. It helps search engines understand content, which can indirectly support good search performance, but it does not replace quality content, good user experience, or a well-structured site. A page with perfect schema but thin content is unlikely to perform well. A page with excellent content and no schema can still rank. Schema is a supporting tool, not a ranking shortcut.

There is also a risk of misuse. Adding schema for content that does not exist on the page, adding fake reviews, or using a type that does not match the page can violate search engine guidelines. For example, adding FAQ schema to a page that has no visible FAQ, or adding Product schema to a page that does not sell a product, is misleading. Search engines may ignore the structured data or take manual action in serious cases. Always keep schema honest, accurate, and visible in the page content.

FAQ

Do I need to know how to code to use schema markup?

No. Many SEO and structured data plugins generate JSON-LD automatically. You only need to understand the basic concepts, choose the right type, and test the output. Manual coding is an option for custom cases, but it is not required for most sites.

Will schema markup make my page rank higher?

Not on its own. Schema helps search engines understand your page and can make it eligible for rich results, but rankings depend on content quality, relevance, links, and user experience. Treat schema as a way to communicate clearly, not as a ranking trick.

Can I add more than one type of schema to a page?

Yes, if each type matches real content on the page. For example, an article with a FAQ section can have both Article and FAQ schema. Avoid adding types that do not match the visible content, as that can be misleading.

How often should I test my schema?

Test when you first add schema, after you change a page, and periodically as part of routine site checks. If you change a price, date, ingredient, or other field that appears in the schema, test again to confirm the data is still valid and in sync with the page.

Conclusion

Schema markup is a way to speak the same language as search engines. By adding structured data in JSON-LD, you label your content clearly, whether it is an Article, a FAQ, a Product, or a Recipe such as a chocolate cake. You make it easier for Google to understand what the page is about, and you make the page eligible for rich results. You do not guarantee those results, and you do not replace good content, but you do give your pages a clearer chance to be understood. Add schema accurately, keep it in sync with what visitors see, validate it with the Rich Results Test, and treat it as part of a broader commitment to clear, helpful content.