Schema markup is structured data for search engines
Schema markup is a shared vocabulary for describing a page’s subject in a format machines can parse. You normally add it to a page as JSON-LD, then search engines use it as one input when they interpret the content.
A service page may visibly say who provides the service, where they work, and how to contact them. Structured data can state those same facts explicitly as an Organisation, LocalBusiness, ProfessionalService, or Person entity. An article can identify its author, publisher, date, and main topic. A product page can describe price, availability, and review data where the information is visible and eligible.
Structured data improves clarity. It does not replace useful page content, authority, technical accessibility, or relevance to the search query. Google also decides which rich-result treatments to show, so valid markup never guarantees a visual enhancement in the results.
Where schema markup helps most
| Page or entity | Useful schema type | What it clarifies |
|---|---|---|
| Company-wide information | Organization or LocalBusiness | Name, logo, contact details, service area, and official profiles |
| Service pages | Service and ProfessionalService | The service offered, provider, and local relationship |
| Articles and guides | Article, BlogPosting, BreadcrumbList | Headline, author, publisher, dates, and site hierarchy |
| Questions and answers | FAQPage | A visible set of genuine FAQs and answers |
| Products | Product and Offer | Visible product information such as price, availability, and review details where eligible |
| Navigation | BreadcrumbList | The page’s position in the site hierarchy |
The implementation principles that prevent problems
Match the markup to visible content
Mark up facts that a visitor can verify on the page. Do not add ratings, prices, FAQs, services, or credentials that are absent, misleading, or no longer current.
Choose the most specific accurate type
Start with the page’s primary entity. A London service business may need LocalBusiness or a more specific subtype, while a guide needs Article and BreadcrumbList. More markup is not automatically better.
Keep a single source of truth
The visible page, CMS fields, Google Business Profile, and structured data should agree on names, services, addresses, contact details, and dates. Conflicting data reduces trust in the implementation.
Test the rendered page
Validate the final HTML that search engines receive. Template changes, JavaScript rendering, and duplicate plugins can create broken, duplicated, or contradictory markup after the initial code looks correct.
A sensible schema order for a service business
Implement the information that defines the business and its key pages before chasing specialised enhancements.
- Establish accurate Organisation or LocalBusiness markup across the site, with consistent contact and location information.
- Add Person and Article markup to expert-led publishing so author and publisher relationships are explicit.
- Add BreadcrumbList where the visible navigation expresses a clear hierarchy.
- Model high-value services accurately and connect service pages to the provider entity where the information is visible.
- Use eligible rich-result types only where the page genuinely contains the required content and attributes.
Common schema mistakes
The most common failure is treating schema as a ranking shortcut. Markup cannot make a thin page authoritative or change a weak service proposition into a strong one. It should describe a page that already deserves to be understood.
Other frequent issues include using multiple plugins that output competing organisation data, leaving old opening hours or addresses in templates, marking up hidden FAQs, and adding review markup that represents the business itself rather than a product or service where the search feature allows it. Schema work needs content governance as much as development work.
From my workflow
I treat schema implementation as an information-modelling exercise before it becomes a code task. I list the facts a page needs to communicate, identify the entity those facts belong to, and check that the visible page gives a visitor the same answer.
The practical work is usually less about adding many types and more about removing contradictions. A clean organisation record, accurate article metadata, coherent breadcrumbs, and a tested service model give search engines a more reliable representation of the site.
Frequently asked questions
What is schema markup in SEO?
Schema markup is structured data that uses a shared vocabulary to describe a page and its entities in a machine-readable format. Search engines can use it to understand information such as an article’s author, a business’s contact details, or a product’s price and availability.
Does schema markup improve rankings?
Schema markup does not guarantee higher rankings. It can help search engines interpret a page and may make a page eligible for certain search-result enhancements, but relevance, quality, technical accessibility, and authority still determine whether a page ranks.
Should every page have schema markup?
Every important page should be assessed for structured data that accurately reflects its visible content. The right choice depends on the page’s primary purpose. Adding irrelevant or unsupported markup creates a data-quality problem rather than an SEO benefit.
Sources and further reading
Yiannis — Freelance SEO & AI Consultant, London
Semantic SEO Specialist · Technical SEO Auditor · AI-Assisted Search Strategist
I help London and UK businesses turn search intent into a clear, prioritised SEO programme. About me →
Related guides
Need your site’s structured data checked?
I audit the visible content, source code, entity relationships, and validation output before recommending the schema changes that matter.
Explore technical SEO audits