Overview
Structured data can support SEO by giving search engines clearer information about what a webpage contains, such as a business, product, article or review. It does not directly guarantee higher rankings, but correctly implemented structured data can help search engines interpret a page and may make eligible content available for enhanced search features.
Search engines are very good at reading text, but they still rely on context to understand what a page actually represents. When a page mentions a product, a business location, an article or a customer review, structured data provides extra information about what those elements mean.
For businesses investing in search visibility, this can make pages easier for search engines to categorise and, for supported types, can affect how information is presented within search results.
What is structured data?
Structured data is code added to a webpage that describes the meaning of its content in a standard format.
The vocabulary most commonly used is Schema.org, which provides agreed labels for things such as organisations, local businesses, products, articles and reviews.
For example, an address written on a contact page is understandable to a human reader. Structured data can explicitly tell a search engine that the text represents the business’s street address, postcode and country.
Without structured data, search engines can still interpret the page. The markup simply provides more explicit information.
JSON-LD is now one of the most practical ways of implementing structured data because the markup can be added separately from the visible page content.
A simple block normally begins like this:
<script type=”application/ld+json”>
{
“@context”: “https://schema.org”
}
</script>
The information contained within it then depends on what that particular page represents.
Why is structured data important for SEO?
Structured data helps search engines understand entities and relationships on a page.
This can include identifying:
- the organisation responsible for a website
- the location of a business
- the author and publication date of an article
- the price and availability of a product
- the subject of a customer review.
Certain structured data types can also make pages eligible for enhanced search features, commonly known as rich results.
A product result, for example, may be able to display information such as price, availability or ratings where the page and markup meet Google’s requirements.
Structured data should therefore be viewed as additional context rather than a shortcut to rankings.
A well-marked-up page with weak content is unlikely to become competitive simply because schema has been added.
How does structured data change search results?
A traditional organic result might contain a URL, meta title, and description. Where Google supports a particular structured data type, additional information may sometimes be displayed.
A product could show a price.
An article may provide clearer publication information.
A business may have its name, address and other details understood more accurately.
These additions can give somebody more information before they click.
There is no guarantee that Google will display a rich result simply because valid structured data is present. Google decides whether and how those features appear.
The practical aim should therefore be accurate markup first, with enhanced search presentation treated as a possible benefit rather than a guaranteed outcome.
Which types of structured data are worth implementing?
There are hundreds of types available through Schema.org, but most ordinary business websites only need a relatively small number.
The important part is matching the markup to what genuinely exists on the page.
For many businesses, the most useful types to consider are Organization, LocalBusiness, FAQ, Article, Product and Review.
When should you use Organisation schema?
Organisation structured data helps search engines understand the organisation behind a website.
It is particularly useful for identifying details such as:
- business name
- website address
- logo
- telephone number
- social profiles.
Google recommends adding organisation information to the homepage rather than repeating the same markup unnecessarily on every page.
A basic example could look like this:
<script type=”application/ld+json”>
{
“@context”: “https://schema.org”,
“@type”: “Organization”,
“name”: “Example Ltd”,
“url”: “https://www.example.co.uk/”,
“logo”: “https://www.example.co.uk/images/logo.png”,
“telephone”: “+44 121 000 0000”,
“sameAs”: [
“https://www.linkedin.com/company/example”
]
}
</script>
Use the information that accurately reflects the business rather than adding properties simply because they are available.
When should you use LocalBusiness schema?
LocalBusiness structured data is useful for businesses with a physical location or a defined local presence.
It can identify details including the address, telephone number and opening hours.
For example:
<script type=”application/ld+json”>
{
“@context”: “https://schema.org”,
“@type”: “LocalBusiness”,
“name”: “Example Dental Practice”,
“url”: “https://www.example.co.uk/”,
“telephone”: “+44 121 000 0000”,
“address”: {
“@type”: “PostalAddress”,
“streetAddress”: “1 Example Road”,
“addressLocality”: “Birmingham”,
“postalCode”: “B1 1AA”,
“addressCountry”: “GB”
}
}
</script>
Where a more specific business type exists, it is usually sensible to use it.
A restaurant, dentist or shop, for example, may have a more precise Schema.org type than the generic LocalBusiness.
The details should also agree with the information displayed on the website and elsewhere online. Incorrect opening hours or an old address in the markup simply gives search engines conflicting information.
Should you still use FAQ schema?
FAQ markup can describe a page containing questions and answers, but its role in Google Search has changed.
Google stopped displaying FAQ rich results in May 2026, so businesses should not add FAQ schema expecting expandable FAQ results beneath their organic listing.
If FAQ structured data is still being used to describe genuine question-and-answer content for Schema.org or other systems, a simple example might look like this:
<script type=”application/ld+json”>
{
“@context”: “https://schema.org”,
“@type”: “FAQPage”,
“mainEntity”: [{
“@type”: “Question”,
“name”: “How long does SEO take?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “SEO timescales vary according to the website, competition and work required.”
}
}]
}
</script>
The question and answer should also be visible on the webpage.
For Google specifically, however, FAQ schema should no longer be treated as a route to FAQ rich results.
That makes the quality and usefulness of the actual FAQ content considerably more important than the markup itself.
When should you use Article schema?
Article schema is suitable for blog posts, news stories and informational articles.
It can help search engines identify details such as the headline, author and publication date.
For example:
<script type=”application/ld+json”>
{
“@context”: “https://schema.org”,
“@type”: “Article”,
“headline”: “How Can Structured Data Boost Your SEO Performance?”,
“datePublished”: “2026-09-30”,
“dateModified”: “2026-09-30”,
“author”: {
“@type”: “Organization”,
“name”: “Example Ltd”
}
}
</script>
For blog-heavy websites, Article or BlogPosting markup can be applied consistently through the website template rather than manually creating a new block for every article.
The dates in the markup should match the dates genuinely associated with the content.
When should you use Product schema?
Product structured data is particularly relevant to ecommerce websites.
It can identify a product along with details such as its price, availability, brand and reviews.
A simplified example could look like this:
<script type=”application/ld+json”>
{
“@context”: “https://schema.org”,
“@type”: “Product”,
“name”: “Example Office Chair”,
“brand”: {
“@type”: “Brand”,
“name”: “Example”
},
“offers”: {
“@type”: “Offer”,
“priceCurrency”: “GBP”,
“price”: “199.00”,
“availability”: “https://schema.org/InStock”,
“url”: “https://www.example.co.uk/office-chair/”
}
}
</script>
Google can use Product structured data to understand information such as price and availability, and eligible pages may appear with additional product information in Search.
The important operational point is maintenance.
If a product changes from £199 to £229 on the visible page while the structured data still says £199, the website is sending contradictory information.
For ecommerce sites, product markup should therefore ideally update automatically alongside the product data itself.
When should you use Review schema?
Review markup describes an individual review or rating associated with an eligible item.
For example:
<script type=”application/ld+json”>
{
“@context”: “https://schema.org”,
“@type”: “Product”,
“name”: “Example Office Chair”,
“review”: {
“@type”: “Review”,
“author”: {
“@type”: “Person”,
“name”: “Sarah Jones”
},
“reviewRating”: {
“@type”: “Rating”,
“ratingValue”: “5”,
“bestRating”: “5”
},
“reviewBody”: “Comfortable for long periods of desk work.”
}
}
</script>
Review schema needs particular care.
Google does not allow businesses to gain review stars for self-serving reviews attached to their own Organization or LocalBusiness markup. This includes reviews about the business that it controls or displays itself.
Product reviews and other eligible review types can still be supported where Google’s requirements are met.
In practical terms, avoid adding star ratings throughout a website simply because a plugin makes it possible. Check whether the thing being reviewed is eligible first.
How should structured data be implemented?
Structured data is normally added to the code of a page.
Many content management systems now provide plugins or built-in functionality that generate common schema types automatically.
That can save time, although automated markup should still be checked.
A plugin can only work with the information it has been given. If the website contains an old phone number, incorrect organisation type or missing product data, the schema can reproduce the same problem.
Start with the markup that has a genuine purpose.
A service business may prioritise Organization or LocalBusiness markup, while an ecommerce website may need Product and Offer markup across thousands of URLs.
Once implemented, Google’s Rich Results Test can be used to check supported markup for errors.
Google Search Console can then help identify structured data issues affecting pages that Google has crawled.
Does structured data improve rankings?
Structured data should not be treated as a direct ranking lever.
Its main role is to give search engines clearer information about the page and, for supported types, make the content eligible for particular search features.
That distinction matters.
Adding schema to a poorly written product page does not make the product description more useful.
Adding Article schema to a thin blog post does not add expertise.
Structured data works alongside content quality, internal linking, crawlability and the wider technical health of the site.
Can structured data help AI search understand a website?
Structured data provides explicit information about entities and their properties, so it can make the structure of information easier for machines to interpret. That does not mean adding schema guarantees visibility within AI-generated answers.
For businesses thinking about both traditional SEO and newer AI search experiences, the more reliable approach is to combine clearly written content with accurate structured data.
If the page says one thing and the markup says another, the structured data is unlikely to solve the underlying problem.
How should structured data be maintained?
Structured data should change when the underlying information changes.
If a business moves premises, the LocalBusiness markup needs updating.
If prices change, Product markup should change with them.
If an article is substantially updated, its modified date may need updating.
This is why schema is best treated as part of the website rather than as a one-off SEO task.
It is also worth checking structured data after:
- website migrations
- redesigns
- plugin changes
- ecommerce platform updates
- major template changes.
Problems often appear when the visible page is updated while the code generating the schema is left behind.
What should happen to older structured data content?
If a website has several short pages explaining essentially the same subject, it can make sense to consolidate them.
A detailed structured data guide should generally be more useful than separate thin pages covering “schema”, “structured snippets” and “structured data” independently.
Where an older page has been absorbed into a more complete resource, its genuinely useful information should be retained and the old URL should normally be redirected to the stronger replacement page where appropriate.
This gives users one clear resource and avoids maintaining several competing explanations of the same subject.
What should businesses remember about structured data?
Structured data is most useful when it accurately describes information that already exists.
Choose a schema type because it matches the page.
Keep the information current.
Test the implementation.
Avoid marking up content that users cannot actually see.
And remember that eligibility for a rich result does not mean Google has to display one.
Used properly, structured data gives search engines clearer information about a website and can support richer search presentation where relevant.
FAQs
What is structured data in simple terms?
Structured data is code that labels information on a webpage so search engines and other systems can more clearly understand what that information represents.
Is schema markup the same as structured data?
Schema.org provides the vocabulary commonly used to create structured data. The terms are often used interchangeably in SEO, although structured data is the broader concept.
Does structured data improve Google rankings?
Structured data does not guarantee higher rankings. It helps Google understand information on a page and can make eligible content available for enhanced search features.
Should every page have structured data?
Only add markup that accurately describes the page. Different page types may need different schema, and some pages may need very little.
How can you test structured data?
Google’s Rich Results Test can check structured data used for supported search features, while Search Console can report certain markup problems found across a website.