Schema Markup Examples.
Schema.org structured data is the layer that makes content machine-readable to Google's quality systems. The Knowledge Graph reads it, the EEAT signal layer reads it, the rich-result rendering surfaces it on the SERP. The natural SEO program treats the schema layer as architecture: implemented once at the template level, validated through the Rich Results Test, grounded in content the page actually carries.
Schema Markup Examples is the entity-architecture reference for natural SEO services. The schema layer is implemented once and reads across every page.
Article, Person, Organization, nested as the EEAT entity architecture.
The Article schema describes a piece of content. Required properties include headline, image, datePublished. Recommended properties include dateModified, author (pointing at a Person), publisher (pointing at an Organization), and articleSection. The Article type carries the publication-level entity for every blog post, hub, and spoke that ships on the site.
The Person schema describes the named author. Required and recommended properties include name, jobTitle, image, url, sameAs (the identity chain pointing at LinkedIn, ORCID, professional registries), knowsAbout (an array of expertise tags), and hasCredential (credential entities pointing at issuing organizations). The Person node is the entity that the Quality Rater Guidelines and the Reviews System read for the author Expertise and Experience signal.
The Organization schema describes the publishing entity. Properties include name, legalName, url, logo, description, contactPoint, and sameAs. The Organization node carries the brand entity, and the publisher pointer on every Article points back to it. The full entity stack reads Article author Person and Article publisher Organization at the schema layer, surfacing the EEAT signal machine-readably.
The nesting matters more than the per-node completeness. A site that ships rich Person and Organization nodes but does not actually point Article.author at the Person node carries the data without surfacing the relationship. The implementation discipline is the @id-based reference pattern in JSON-LD: every entity carries an @id, and references resolve through the @id rather than through duplicated content.
Service, Local Business, Product, Review, at the commercial entity layer.
The Service schema describes a commercial service the publishing entity offers. Properties include name, serviceType, description, provider (pointing at an Organization), areaServed, and audience. Service schema does not produce a rich-result rendering by itself, but it surfaces the commercial entity to the Knowledge Graph and clarifies the page's commercial intent to the indexing systems.
The Local Business schema describes a physical-location business. The schema requires address, telephone, and openingHoursSpecification. It is the foundation for local pack and knowledge panel rendering for queries with location intent. The schema integrates with the Google Business Profile, which is the ground-truth source for location data; the schema is the publication-side reflection of the same entity.
The Product schema describes an e-commerce product. Required properties include name, image, offers (with price and priceCurrency and availability). Recommended properties include brand, sku, gtin, aggregateRating, and review. The schema unlocks the product rich-result rendering across Google Search and Google Shopping; the unverified merchant data carries less weight than data verified through the Merchant Center feed.
The Review schema describes a review of a product, service, or business. Properties include itemReviewed, reviewRating, author, and reviewBody. After the 2019 self-review crackdown, Google ignores Review schema on self-reviewed entities (a company reviewing its own product or service). The Review type is for third-party reviews on review-oriented pages.
FAQPage, HowTo, Breadcrumb, and the content-surface rich-result reality.
FAQPage schema describes a question-and-answer section on a page. The rich result rendering was visible across most FAQ pages from 2018 until August 2023, when Google limited FAQ rich result eligibility to authoritative government and health sites. Most commercial sites no longer see the rich result, but the schema continues to surface the entity content to the Knowledge Graph and to the People Also Ask block selection.
HowTo schema describes a step-by-step instructional page. Google deprecated the desktop HowTo rich result in September 2023; the mobile rich result followed in October 2023. The schema continues to carry the entity content, and the deprecation does not prevent indexing or ranking; it only removes the visual rendering on the SERP.
Breadcrumb schema describes the navigation hierarchy of the page. The rich result rendering replaces the URL display under the page title with the breadcrumb trail, which improves SERP clarity for deeply nested URLs. Required properties: itemListElement (an array of ListItem with position, name, item). Every commercial and informational page on the site carries Breadcrumb schema as part of the layout-level implementation.
Other content-surface types worth implementation: Course for educational content, Recipe for food content, JobPosting for hiring content, Event for time-bound events. Each type carries a specific rich-result and Knowledge Graph integration, with per-type required properties documented in the Search Central reference.
The Rich Results Test, and the structured-data spam boundary.
The Rich Results Test is the supported validation surface for structured-data implementation. The test renders the page through Google's processor, extracts the structured data, validates against the supported schema types, and flags errors and warnings per type. The test replaced the deprecated Structured Data Testing Tool for Google-supported schema. The schema.org validator covers the broader schema.org coverage that Google does not currently surface in rich results but that the Knowledge Graph may still read.
The structured-data spam policy is the boundary every implementation runs against. Google enforces against markup that is hidden from the user, irrelevant to the page, or otherwise deceptive. The boundary tests are visibility (does the user see the content that the schema describes?), relevance (does the schema describe content material to the page's purpose?), and accuracy (does the schema describe the content correctly?). A site that fails any test carries manual-action risk under the structured-data issue policy.
The Search Console structured-data report surfaces both valid and invalid schema across the site, segmented by type. The report carries warnings for missing recommended properties and errors for missing required properties. Pages with errors are not eligible for the corresponding rich result rendering, even if the page itself ranks well organically. The continuous remediation of structured-data warnings is part of the technical SEO cadence.
What operators ask about structured data before the implementation begins.
- 01.Does schema markup directly improve rankings?
- Schema markup does not directly improve ranking position. Structured data makes content machine-readable, which qualifies a page for rich result rendering on the SERP and surfaces entity information to the Knowledge Graph. Rich result rendering can improve click-through rate, and the entity-graph integration contributes to the EEAT signal layer that the ranking systems do read. The schema work is signal architecture rather than a ranking lever in itself.
- 02.What schema types matter most for a natural SEO program?
- Article, Person, and Organization carry the EEAT entity architecture. Local Business carries the local pack and knowledge panel signal. Service carries the commercial-page entity. FAQPage and HowTo carry the rich-result rendering on informational pages, when the content actually matches the schema type. Breadcrumb carries the site hierarchy. Product and Review carry the e-commerce rich-result surface. The selection depends on the site's actual content surfaces, not on maxing out coverage.
- 03.How is JSON-LD different from microdata?
- JSON-LD is a separate script block in the page head or body that declares the structured data independently of the visible HTML. Microdata is inline markup attached to the HTML elements that carry the data. Google supports both. JSON-LD is the recommended format because it is easier to maintain, easier to debug, and decoupled from the visible HTML rendering. The Search Central documentation worked examples use JSON-LD throughout.
- 04.Can schema markup trigger a manual action?
- Yes, when the structured data marks up content that is hidden from the user, irrelevant to the page, or otherwise deceptive. The Search Console manual actions report includes a structured-data issue category. A page that marks up FAQ content that does not actually render to the user, or that marks up a Review with a star rating that the page does not actually carry, is at risk. Schema markup that accurately describes the rendered page content is not at risk.
- 05.How often do the schema requirements change?
- Google publishes regular updates to the per-type structured-data documentation. Required properties shift when Google deprecates or adds rich-result features. The 2023 deprecation of How-To rich results on desktop and the 2024 changes to FAQ rich-result eligibility (limited to authoritative health and government sources) are recent examples. A natural SEO program watches the Search Central change log and updates the schema implementation when requirements shift.
- 06.How does Grove implement schema on an engagement?
- The architecture is implemented at the layout or template level so the schema generates consistently across the site rather than being authored page by page. Article + Person + Organization nesting is built into the article template. Service schema is built into the commercial-page template. Local Business schema is rendered once site-wide with location data. The Rich Results Test validates every template variant before the implementation is considered done.
If you want schema implemented as entity architecture across the template layer rather than per-page authoring, see how we work.
Two-week diagnostic. Article and Person and Organization nesting at the layout layer; commercial and content types per the actual page surfaces; every variant validated through the Rich Results Test before the implementation is considered done.