SEO Smart Engine
Log inSign up

JSON-LD Schema Generator

Build valid structured data and unlock rich results in Google.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "",
  "url": ""
}
</script>

Why JSON-LD structured data matters

JSON-LD is the schema.org format Google, Bing, and modern AI search engines (ChatGPT search, Perplexity, Gemini) read to understand what a page is about - not just which words it contains. Valid structured data unlocks rich results (stars, prices, FAQs, breadcrumbs, recipe cards, sitelinks search box, knowledge-panel entries) and dramatically increases the likelihood of being cited in AI search answers.

Google's documentation is explicit: structured data is required for most rich-result types. Sites that ship it correctly routinely see 20-40% CTR lifts at the same ranking position.

Which schema type for which page

  • Organization - every site, in the root layout. Powers the knowledge panel and "sameAs" social profile linking.
  • LocalBusiness - physical locations. Required for Google Business Profile sync and "near me" queries.
  • Article / BlogPosting / NewsArticle - editorial content. Required for Top Stories and Discover.
  • Product + Offer + AggregateRating - product pages. Powers price, availability, and review stars in SERPs and AI Shopping.
  • FAQPage - Q&A blocks. Still drives expandable rich results for verified sites in some niches.
  • HowTo - step-by-step guides. Visual rich result with images per step.
  • Recipe - required for the Recipe carousel.
  • Event - concerts, webinars, conferences. Powers the Event rich result with date and location.
  • BreadcrumbList - every deep page. Replaces the URL with a clickable breadcrumb in the SERP.
  • SoftwareApplication - apps, SaaS tools. Powers App store-style rich result.

JSON-LD best practices

  • JSON-LD over Microdata or RDFa - Google explicitly prefers it; it's also the only format AI search engines reliably parse.
  • Match the visible content - schema must describe what the user sees. Hidden or contradictory data is a spam signal.
  • Include all required fields per type. Missing image on Article or price on Product disqualifies the rich result silently.
  • Use absolute URLs in image, url, and sameAs fields.
  • Use ISO-8601 dates in datePublished and dateModified.
  • Validate with our schema validator and Google's Rich Results Test before deploying.

Frequently asked questions

Where do I put JSON-LD on my page?

Inside a <script type="application/ld+json"> tag in the <head> (preferred) or anywhere in the body. Multiple schemas stack - an Article page can also carry BreadcrumbList and Organization.

Does schema help with AI Overviews and ChatGPT?

Yes. AI-search engines weigh structured data heavily because it removes ambiguity about page contents. Pages with valid Product, Article, and FAQ schema are cited disproportionately often in AI answers.

Will rich results appear immediately?

No. Google typically re-crawls within days, but rich-result eligibility is decided per-query and can take 2-8 weeks to stabilize. Use the Rich Results Test to confirm Google parses the markup correctly.

Can incorrect schema hurt rankings?

Misleading schema - claiming a Product page has a price it doesn't, fake reviews - can trigger a manual structured-data action that removes rich-result eligibility sitewide. Honesty is non-negotiable.