What we measured ·
What Google shows for "json-ld schema markup" right now
Method: Live Google results (United States, desktop, English) for "json-ld schema markup" retrieved through DataForSEO's SERP API on 2026-10-22. Page types are our own classification of each ranking URL.
The top 7 organic results for "json-ld schema markup" were 4 guides or explainers, 2 product or service pages, 1 free tool. The first three were revalin.com, skills.rest, blog.varkido.com.
Google returned an AI Overview placeholder that loads after the page, so whether the Overview appears for a given searcher, and which sources it cites, could not be captured.
People Also Ask listed: "How does schema markup work?"; "Is there a JSON Schema?"; "What is the difference between JSON-LD and microdata?"; "Is JSON considered a markup language?". The sections below answer the ones within this page's scope.
| Position | Domain | Page type |
|---|---|---|
| 1 | revalin.com | Free tool |
| 2 | skills.rest | Product or service page |
| 3 | blog.varkido.com | Guide or explainer |
| 4 | aiseogrow.com | Guide or explainer |
| 5 | skills.rest | Product or service page |
| 6 | www.indexbolt.com | Guide or explainer |
JSON-LD versus microdata
Microdata and RDFa embed structured data in HTML attributes around visible content; JSON-LD keeps it in a separate script block. Google supports all three but recommends JSON-LD because it is easier to generate, maintain, and validate without touching page markup. JSON-LD can be in the head or body. Google can read JSON-LD added by JavaScript, but server-rendered JSON-LD is more reliable.
Properties by type
Key properties for the most common types.
| @type | Key properties | Used on |
|---|---|---|
| Organization | name, url, logo, sameAs, contactPoint | Homepage or About |
| WebSite | name, url, publisher (@id of Organization) | Homepage |
| Article | headline, datePublished, dateModified, author, publisher, image | Blog posts and guides |
| BreadcrumbList | itemListElement of ListItem with position, name, item | Any page in a hierarchy |
| FAQPage | mainEntity of Question with acceptedAnswer | Pages with visible FAQs |
| Product | name, image, brand, sku, offers (price, priceCurrency, availability) | Product pages |
| SoftwareApplication | name, applicationCategory, operatingSystem, offers | Software product pages |
| LocalBusiness subtype | name, address, telephone, openingHoursSpecification, geo | Location pages |
Connecting entities with @graph and @id
Instead of repeating the organisation inside every Article, give the Organization an @id such as https://www.example.com/#organization and reference it from Article publisher and WebSite publisher with an object containing only that @id. A page can include a @graph array holding several entities, such as WebPage, Article, BreadcrumbList, and Person, that reference each other. This keeps markup consistent and avoids contradictions.
Rules that matter more than syntax
Mark up only content visible to users. Keep values identical to the page, especially prices, dates, and ratings. Do not declare the same @id with different properties on different pages. Use absolute URLs. On serionflow.com, the site-wide Organization, WebSite, and SoftwareApplication entities are declared once in the shared head, and page-level blocks such as Article, BreadcrumbList, and FAQPage reference them; the build checks schema semantics such as matching list counts and real breadcrumb URLs.
Validating JSON-LD
Use Google's Rich Results Test for types Google supports for rich results, and the Schema.org validator for general correctness. Search Console's enhancement reports show errors across the site for supported types. Our free schema builder and validator generates JSON-LD for the types above from a form and checks markup on a live page. SerionFlow is the wrong tool for adding structured data to your existing templates; it outputs JSON-LD only on the pages it publishes.
Clear answers
Frequently asked questions
What is the difference between JSON-LD and microdata?
+
Microdata adds attributes to visible HTML elements; JSON-LD is a separate script block of JSON. Both express Schema.org data; Google recommends JSON-LD.
Where should JSON-LD go?
+
In a script element of type application/ld+json, in the head or body of the page it describes.
About the author
Shadrack Kumi · Founder, SerionFlow
Shadrack builds SerionFlow's site research, page generation, and Search Console tooling, and runs the free tools these guides pair with. Search Console figures cited on these pages come from serionflow.com's own property.
Continue exploring
Related SerionFlow resources
More in Guides
- Meta description length and best practices
- Programmatic SEO on Next.js and Vercel
- Programmatic SEO on Shopify: what works and what does not
- Programmatic SEO on Webflow: how to set it up and where it stops
- Programmatic SEO on WordPress: how to set it up and what to watch
- robots.txt for AI crawlers: how to allow or block GPTBot, ClaudeBot, and others
- robots.txt monitoring: how to detect changes and outages
- Title tag length and best practices
Make the next move obvious
Let SerionFlow turn your market evidence into momentum.
Confirm the market, rank the opportunities that matter, create brand matched pages on your domain, and keep moving with controlled weekly intelligence.