A practical structured-data guide for service business websites covering Organization, Service, Article, Breadcrumb and FAQ schema without misleading markup.
- Schema should describe content and entities that are actually present; it is not a place to manufacture trust signals.
- Use a consistent Organization entity and connect page-specific WebPage, Service and Article markup to it.
- Validate JSON-LD after template changes and monitor Search Console for structured-data errors.
Use Organization schema to define the business entity
Organisation markup can establish the canonical business name, website, logo and contact information in a machine-readable form. Keep the organisation identifier consistent across pages so Service and Article markup can reference the same entity.
Use Service schema on real service pages
A service page can describe the service type, provider, area served, URL and description. The markup should match what the user can see. Do not claim locations, awards, prices or service coverage that the page does not support.
Use BlogPosting or Article schema on editorial pages
Article markup can identify the headline, publisher, author, publication dates and page relationship. Use accurate publication and modification dates; do not refresh dates simply to make old content look new.
Use BreadcrumbList to clarify hierarchy
Breadcrumb structured data can show how a page fits into the site. Service pages can sit under Services, while articles can sit under Insights. Keep the URLs canonical and the hierarchy consistent with internal navigation.
Use FAQPage only for visible questions and answers
If a page contains a genuine FAQ section, the questions and accepted answers can be represented in FAQPage markup. Do not add hidden questions only for schema. Also remember that valid FAQ markup does not guarantee a visible FAQ rich result.
Avoid fake LocalBusiness, ratings and reviews
Do not add a U.S. address simply because you want to rank in the United States. Do not create AggregateRating markup from testimonials that are not genuine review data. Misleading structured data can make markup ineligible and weakens trust.
Validate the schema and the rendered page together
Use Google's Rich Results Test for supported features and Schema.org validation for broader vocabulary. Then use URL Inspection after deployment to make sure the HTML Google receives contains the expected JSON-LD.
This work supports the entity clarity discussed in our AI Overviews and AI Mode guide, but structured data is not a guaranteed ranking shortcut.
