Structured data in practice: Schema.org markup for Google and AI search engines

Summary
Structured data is a machine-readable label on your content: it states clearly what the company, product, or article is. Not a magic bullet, but a low-cost, durable investment.
What is structured data?
A human visitor looks at a web page and immediately recognises what is a company name, a price, or opening hours. To a machine, all of that is just raw text. Structured data conveys that meaning in an explicit, standardised format, using the shared schema.org vocabulary maintained jointly by the major search engines.
The recommended format today is JSON-LD: a data block embedded in the page's code that is invisible to human visitors but read directly by search engines and AI crawlers.
What it does and what it does not do
- Disambiguates your content: search engines no longer have to guess what an element represents.
- Enables rich results: such as ratings, prices, stock status, or breadcrumbs displayed directly on search result pages.
- Connects entities: the relationship between your company, the author, and the article can be traced programmatically.
- Helps AI assistants identify accurately who and what a page is about.
What it does not do: it will not boost rankings on its own, nor does it guarantee rich result display: search engines decide what to show on the results page. Markup never turns weak content into strong content.
Which schema types matter most?
| Type | Where it belongs | What it describes |
|---|---|---|
| Organization / LocalBusiness | Home page, contact page | Company name, address, contact details, logo, and social profiles |
| WebSite | Home page | The website's name and language |
| BreadcrumbList | Every subpage | The page's position in the site hierarchy |
| Article / BlogPosting | Articles, blog posts | Headline, author, publication date, and last updated date |
| Product and Offer | Product pages | Name, price, currency, and availability |
| Service | Service pages | Service name, provider, and area served |
| FAQPage | Question-and-answer sections | Questions and their corresponding answers |
| Person | Author and team pages | Name, role, and affiliation with the organisation |
Keep in mind that search engines periodically adjust which schema types trigger visual enhancements in search results. Even when visual treatment changes, the markup remains valuable because it helps machines understand your content.
Five rules for sound markup
- Only mark up what is visible on the page. Structured data should mirror visible content, not smuggle in extra claims.
- Keep it truthful. Fabricated ratings or misleading attributes violate search engine guidelines and can trigger manual penalties.
- Stay consistent. Your company's name, address, and phone number should match character for character everywhere.
- Link your entities. An article's author and publisher fields should reference the person and organisation defined on the site.
- Generate it automatically. When markup is built from the exact same data source as the visible page, the two can never drift apart.
How to verify your markup
You can validate structured data with free tools: the Schema Markup Validator checks standards compliance, while Google's Rich Results Test checks whether a page is eligible for enhanced display. Google Search Console reports detected entities and errors across your entire domain.
Structured data is a great investment when it is baked into your templates rather than maintained by hand. When planning a new website, decide during the design phase which schema types each page template will output automatically.
Key takeaways
- Structured data tells machines explicitly what appears on a web page.
- The schema.org vocabulary paired with JSON-LD is the industry standard.
- It aids machine comprehension and unlocks rich results, though it does not guarantee higher rankings.
- Only mark up genuine information that is visibly present on the page.
- Markup stays reliable when generated automatically from the same data source as the visible content.
Frequently Asked Questions
Do we need a developer to add structured data?
For initial setup, usually yes, because the markup lives inside the page templates. Many CMS platforms generate basic schema out of the box, but accurate, interconnected markup tailored to your business typically requires developer work.
Does every page need structured data?
Not the same type on every page. Organization details and breadcrumbs are useful across almost any site, while other types belong where the content matches: Product on product pages, Article on editorial posts.
What happens if our markup has syntax errors?
Search engines generally ignore malformed or incomplete markup without penalising the page's normal ranking. Deceptive markup (claiming things that contradict the visible page) can, however, result in losing rich-result eligibility across the site.