SEO structured data (datos estructurados seo) is a set of standardized information added to a webpage to tell search engines what the page contains and how the various pieces of information are related. For example, a product’s name, price, and stock status can be expressed through explicit properties, rather than relying entirely on search engines to infer them from the body text.
Structured data helps search engines understand a page and may enable eligible pages to receive richer search result presentations. However, it does not guarantee rich results or improved rankings. Whether a search engine displays them also depends on whether the markup is valid, whether the content complies with its policies, and the specific search context.
Text and images on a webpage are primarily intended for people to read. When people see “Price: $100,” they generally understand that this is the selling price of an item. Search engines, however, need to use the page context to determine what the number refers to, which currency it is in, and which product the price belongs to.
Structured data reduces this ambiguity through types and properties. For example, Product represents a product, name represents its name, and offers links it to a sales offer, with additional properties specifying the price and currency. This helps search engines identify the information more clearly, though they still evaluate it alongside the webpage content and other signals.
Schema.org provides a widely used vocabulary of types and properties. JSON-LD, Microdata, and RDFa are different formats for expressing this information. These are not the same kind of thing: the former defines which terms to use to describe content, while the latter determines how that content is written into a webpage.
Google supports these formats and recommends using JSON-LD when appropriate. It is usually placed in a separate script block, so each property does not need to be embedded in the visible body text, making it relatively easy to maintain. Regardless of the format used, however, the marked-up content should match the information users can actually see on the page.

When choosing markup, start with the page’s actual content rather than working backward from the search appearance you hope to achieve. The existence of a type in Schema.org does not mean Google will necessarily provide a corresponding rich result for it.
A page can include multiple types, but each must correspond to content on the page. For example, an article about equipment maintenance can include Article and BreadcrumbList markup. If the page also embeds a tutorial video that visitors can watch, VideoObject markup may also be appropriate. In contrast, marking an entire article as a product sales page simply because it mentions a product can create a mismatch between the page’s subject and its markup.
Regular search results generally consist of elements such as a title link, URL information, and a snippet. In applicable contexts, rich results display additional information related to the page content, such as a product’s price, stock status, or rating. This additional information can help users decide whether a page meets their needs before clicking, but the search engine determines how it is displayed; a website cannot directly specify the appearance.
Structured data is an important way to qualify for some rich results, but it is not the only requirement. For example, even if the code on a product page is correctly formatted, the page may not receive the corresponding display if the price is missing, the page cannot be accessed, the markup conflicts with visible content, or the page does not comply with Google’s specific feature policies. Even when all requirements are met, Google may still choose not to display a rich result.
It is also important to distinguish rich results from other search presentations, such as knowledge panels and regular snippets. Not every change in search results is triggered by structured data. If a special appearance does not show up after markup is added, that does not necessarily mean the search engine has failed to understand the page.
A practical principle is: Markup should describe the main content of the current page and match the information visible to users. If a product is out of stock but the code still marks it as in stock, the page displays a price in dollars but the markup uses another currency, or a rating appears only in the code with no corresponding source of reviews on the page, the information may be unreliable or fail to comply with relevant policies.
Export websites should also account for differences between language and regional versions. The same product may have different currencies, prices, or sales terms on different pages, so structured data should match the page it appears on. A B2B inquiry page without a publicly displayed price can mark up genuine product information; there is no need to enter a fictitious offer just to try to display a price.
Review information requires particular care. Product reviews should relate to the specific product being reviewed and comply with search engine requirements for review content and sources. Do not present a company’s own promotional statements as customer reviews or copy ratings from unrelated pages onto multiple product pages.
When webpage templates generate markup automatically, also watch for duplication and outdated information. For example, a theme plugin and another tool may each output product markup, resulting in two conflicting sets of prices. Old markup may also remain after a product is discontinued or a page is updated. When checking, verify not only that the code exists, but also that all the information refers to the same entity.
Start by using Google’s Rich Results Test to check the page and confirm which items it can recognize, the required properties, and any relevant errors. Schema Markup Validator can help check the basic structure of Schema.org markup, but it is not the same as Google’s rich result eligibility test.
After publishing the page, use Google Search Console to review the relevant reports and monitor changes in detected items and errors. The reports available depend on the website’s content and the features Google currently supports. If the testing tools cannot detect the markup, also check whether the page can be crawled, whether the script is being output correctly, and whether the markup contains syntax errors.
Passing validation means that the relevant code meets the conditions checked by the tool; it does not mean that search results will necessarily change. A more reliable approach is to monitor the page’s indexing status, Search Console data, and actual search appearances over time, and to recheck when product information, webpage templates, or search engine rules change.
Related Articles
Related Products


