What is schema markup?
Structured data that tells a machine what a page is about, rather than making it infer.
Structured data that tells a machine what a page is about, rather than making it infer.
Schema markup is structured data embedded in a page using the Schema.org vocabulary, usually as JSON-LD. It states explicitly what the content represents — an organisation, an article, a set of questions and answers, a service — so machines do not have to infer it from the text.
| Organization / LocalBusiness | Who you are, where, how to contact you. |
|---|---|
| WebSite | Site-level information including internal search. |
| BreadcrumbList | Where a page sits in the hierarchy. |
| FAQPage | Questions and answers, eligible for rich results. |
| Article / BlogPosting | Author, dates, word count and reading time. |
| Service | What a service page actually offers. |
| Person | Leadership profiles, connected to the organisation. |
Schema must reflect what is genuinely on the page. Marking up questions that do not appear, or ratings that do not exist, is a policy violation and risks manual action. It is a description layer, not a place to make claims.
A discovery call is a working session on your constraint, not a sales pitch.
A short note is enough. You'll hear back from the team, not a bot — usually within one working day.
Answers go to the Digistan team. See our privacy policy.