JSON-LD Code Editor

No schema processed yet. Fetch a URL or Paste code to run the audit.

No tree hierarchy available.

Schema JSON-LD Boilerplates

Select a template below to load it into the editor automatically.

FAQ Page Schema

Popular

Render Frequently Asked Questions directly within Google Search Engine Result Pages (SERPs).

Local Business Schema

Essential

Use for physical storefronts (offices, shops, restaurants) to stand out in Google Maps & Local Pack.

Article / BlogPosting Schema

Perfect for blogs, news sites, or content portals. Helps qualify pages for Google Discover and Top Stories.

Product & Offer Schema

Display review ratings, pricing, and stock availability directly on organic search result listings.

Organization Schema

Link your brand name, logo, and social profile links together for Google's Knowledge Graph.

Schema Structured Data Rule

Best practices for entity-based structured data deployment for Google Search & AI crawlers.

1

JSON-LD as Primary Delivery Format

Use the <script type="application/ld+json"> tag. Avoid Microdata or RDFa because JSON-LD separates metadata from HTML presentation and is Google's strongly recommended format.

2

Mandatory @context & @type

Every root schema block must declare a valid "@context": "https://schema.org" and a corresponding @type. Missing either parameter invalidates the entire structured data block.

3

Explicit Nesting over @graph Arrays

Nest related entities hierarchically (WebSite β†’ WebPage β†’ Article β†’ Author) rather than using flat @graph lists to prevent disconnected or orphan nodes.

4

@id as Entity Anchors & Identifiers

Provide a consistent, lowercase, domain-matching @id with a hash anchor (e.g., https://domain.com/#organization) to establish unique entity identities across different pages.

5

No Floating Nodes (Strict Connectivity)

All entities in the schema must connect back to the page's main root entity or anchor (e.g., via isPartOf, publisher, author, or about). Isolated/floating nodes are ignored by search crawlers.

6

Self-Confirming Loops (Cycles)

Build bidirectional or circular relationships (e.g., Organization β†’ Product β†’ Offer β†’ Organization) to create strong, self-validating entity connections in the knowledge graph.

7

Triple-Validator Verification Flow

Ensure your schema passes a serial testing flow before deployment: Schema.org Validator (syntax), Classy Schema / this visualizer (floating nodes), and Google Rich Results Test (eligibility).

8

Prevent Schema Drift

Ensure all schema property values (prices, telephone, ratings) match the visible on-page body text exactly. Discrepancies can lead to search penalties or loss of rich snippets.

9

Capitalization Consistency

Keep capitalization consistent for matching entity names (e.g., "Google" vs "google" are treated as two different entities by crawlers).

10

Optimize Schema Weight & Volume

Mark up only the primary entities on the page. Bloated schemas increase page size, slow down crawling, and can cause validation engine failures.

Visualizer Graph Legend

Root Node / Core Page Entity
Main Entity (Person, Organization, etc.)
Self-Confirming Shape / Cycle Connection
Floating Node / Disconnected Entity
Literal Text Attribute / Technical Value