Schema Explorer
Browse the JSON-LD blocks we ship — and copy the ones you need.
A curated library of production-tested JSON-LD templates: Organization, LocalBusiness, Product, FAQPage, HowTo, BreadcrumbList, Article. Copy, adapt, deploy.
Organization
Base entity schema for the brand. Deploy on the About page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Optimize Plus",
"url": "https://optimizeplus.com",
"logo": "https://optimizeplus.com/logo.png",
"sameAs": [
"https://www.linkedin.com/company/optimize-plus",
"https://twitter.com/optimizeplus"
]
}
</script>Structured data doesn't move rankings directly, but it is the clearest channel you have for telling search engines and AI answer systems exactly what an entity, product, or piece of content is — unambiguously, in a format machines parse without guesswork. Every rich result Google shows (FAQ accordions, review stars, breadcrumbs in the URL line, HowTo steps) is sourced from JSON-LD markup, and every large language model crawling the web for grounding data leans on the same structured signals to disambiguate entities faster than free text allows.
This explorer holds seven templates we deploy repeatedly across client sites: Organization, LocalBusiness, FAQPage, Article, BreadcrumbList, Product, and HowTo. Each one has been validated against Schema.org's current vocabulary and Google's Rich Results guidelines. The goal isn't to hand you generic boilerplate — it's to show correctly nested, minimally-complete examples you can extend with your own data without breaking validation.
Which schema type to use, and when
Organization schema belongs once per site, typically referenced from the homepage or a global template, and anchors your brand as an entity in Google's Knowledge Graph and in any LLM's training or retrieval corpus. LocalBusiness extends Organization with address, geo-coordinates, and hours — use it on any page representing a physical or service-area location, and prefer a stable @id so multiple pages can reference the same entity rather than duplicating it.
FAQPage and HowTo are content-shape schemas: they only qualify if the visible page content genuinely contains the questions and answers, or the steps, you're marking up. Google has tightened enforcement here — decorative or hidden FAQ markup that doesn't match visible content risks a manual action, not just a missed rich result. Product and Article are the remaining two: use Product on true e-commerce PDPs with real price and availability data, and Article (or its BlogPosting variant) on editorial content where you want author, date, and headline eligible for Top Stories and other article-specific surfaces.
- Organization — once per domain, ideally with sameAs links to verified social/business profiles.
- LocalBusiness — one per physical or service-area location, with @id reuse across pages.
- FAQPage — only when the Q&A pairs are visible, verbatim, on the page.
- HowTo — sequential, numbered steps with genuinely distinct actions per step.
- Product — needs price, currency, and availability to qualify for rich results.
- Article/BlogPosting — needs author, headline, and datePublished at minimum.
Validation and common nesting errors
The single most common defect we find in audits is malformed nesting: an `address` object missing its own `@type: PostalAddress`, or a `sameAs` array containing a string instead of a list. Both pass casual eyeballing but fail Google's Rich Results Test and the Schema.org validator. Another frequent error is placing multiple `@type` blocks inside one `<script>` tag without wrapping them in a `@graph` array — this silently breaks parsing in some crawlers.
Always validate with Google's Rich Results Test and the Schema Markup Validator before shipping, and re-validate after any CMS template change, since a single conditional that drops a required field (e.g. `datePublished` missing on draft posts) can invalidate schema sitewide without triggering a visible bug.
Schema and AI answer engines
Beyond Google's rich results, structured data is increasingly a grounding signal for AI Overviews, Perplexity, and other retrieval-augmented systems that crawl the live web. A page with clean Organization, Article, and FAQPage markup gives these systems an unambiguous entity graph to cite from, which is a meaningful lever inside an AEO/GEO programme even though no vendor publishes a direct 'schema boosts citations' claim you should take at face value. Treat it as removing ambiguity, not as a magic switch.
Step-by-step workflow
- 1Identify the entity type
Decide whether the page represents an organisation, a location, a product, an article, or instructional content.
- 2Select the closest template
Pick the matching schema from the explorer list on the left.
- 3Copy and adapt the JSON
Replace placeholder values with your real NAP, URLs, dates, and content — never leave sample data in production.
- 4Paste into the page <head>
Wrap in a <script type="application/ld+json"> tag, ideally rendered server-side so crawlers see it without executing JS.
- 5Validate before deploy
Run the markup through Google's Rich Results Test and fix any nesting or required-field errors.
- 6Re-validate after template changes
Any CMS or component refactor can silently drop a required field — spot-check quarterly.
Frequently asked questions
- Does adding schema guarantee a rich result in Google?
- No. Valid schema makes a page eligible for a rich result; Google still decides algorithmically whether to display one, based on content quality, page authority, and query context. Treat schema as necessary, not sufficient.
- Can I use multiple schema types on one page?
- Yes, and it's normal — a blog post might carry Article, BreadcrumbList, and FAQPage schema simultaneously. Combine them in one script tag using a `@graph` array, or use separate script tags, both are valid.
- Will FAQPage schema still show as an accordion in Google's SERP?
- Google has restricted FAQPage rich results largely to authoritative government and health sites since 2023. Non-qualifying sites should still add FAQPage schema for AI-answer-engine grounding value even without the classic SERP accordion.
- What's the difference between Organization and LocalBusiness schema?
- LocalBusiness is a more specific sub-type of Organization that adds address, geo-coordinates, and opening hours. Use Organization for the parent brand entity and LocalBusiness for individual physical or service-area locations.
- Do I need a developer to add JSON-LD, or can I paste it manually?
- Many CMSs (WordPress plugins, Shopify theme files, custom head snippets) allow manual JSON-LD insertion without code changes. For dynamic values like price or hours, you'll want the fields templated so schema stays accurate as data changes.
- How do I know if my existing schema is broken?
- Run any indexed URL through Google's Rich Results Test or Search Console's Enhancements reports, which flag missing required fields and invalid nesting site-wide.
- ·Bootstrapping schema on a new site
- ·Finding the right template fast
- ·Learning correct nesting
SERP Preview Simulator
See how your title and meta description render on Google — with pixel-accurate truncation.
Meta Length Checker
Bulk-check title and description length across dozens of pages at once.
Reading-Grade Analyser
Score any paragraph on readability — because AI Overviews reward clarity.
Programmes that use this exact analysis.
Technical SEO agency in Austin fixing Core Web Vitals, schema, and crawl issues. We ship the fixes that get you ranked and cited by AI.
Austin web design agency building high-performance, conversion-optimized marketing sites. We bridge the gap between aesthetic excellence and technical SEO requirements for Austin brands.
Austin SEO analytics agency wiring GA4, Google Search Console, Semrush, and Looker Studio into executive-grade dashboards. Monthly reports Austin CFOs actually read. Quarterly business reviews tied to revenue.