How to use the Schema.org JSON-LD Generator

Generate clean, valid structured data in seconds, paste it into your pages, and verify it with Google’s official tools.

1. Using the generator

The generator is a chat interface powered by AI. You describe what you need in plain language and it returns ready-to-paste <script type="application/ld+json"> markup.

Describe your content — Type a free-form description of the page, product, article, business, event, recipe, FAQ, or person. The more specific details you give (name, price, location, dates, etc.), the better the first result will be.
Get the markup instantly — The AI generates the most appropriate Schema.org type(s) and returns a complete JSON-LD block.
Copy with one click — Use the “Copy schema to clipboard” button that appears under the response.
Refine if needed — If anything is missing or incorrect, just reply in the chat (e.g. “Add an Offer with price currency USD” or “Change the type to BlogPosting”). The generator will update the markup.

Tip: You can request multiple schemas at once (for example Product + Offer + AggregateRating, or WebPage + BreadcrumbList + Organization). The generator will combine them correctly.

2. Detailed example prompts

Here are two realistic prompts you can copy and adapt. Notice how specific details produce richer, more useful markup.

Example 1 – Product with Offer & rating

Good for ecommerce product pages. Including price, availability, brand, and a review summary lets Google show rich product results.

Generate a Product schema for “AeroRun Pro” blue running shoes. Price: $89.00 USD Availability: InStock Brand: AeroStride SKU: ARP-BLU-42 Description: Lightweight neutral running shoes with responsive foam midsole and breathable mesh upper. Ideal for daily training. Add an AggregateRating of 4.7 based on 128 reviews. Include a single Offer that points to https://example.com/products/aerorun-pro

Expected result: a Product with nested Offer and AggregateRating, ready for rich product snippets.

Example 2 – FAQPage for a SaaS help center

FAQ schema can unlock FAQ rich results in Google Search. Provide the actual questions and answers you want marked up.

Create an FAQPage schema for our onboarding help center with these three questions: 1. How do I invite team members? Answer: Go to Settings → Team, click “Invite”, enter their email, and choose a role. They will receive an email invitation that expires in 7 days. 2. Can I change my plan later? Answer: Yes. You can upgrade or downgrade at any time from the Billing page. Changes take effect immediately and are prorated. 3. Where can I find my API keys? Answer: API keys live under Settings → Developers. Create a new key, copy it once (it is shown only at creation), and store it securely. Use the main entity name “Onboarding & Account FAQ” and set the page URL to https://help.example.com/onboarding

Expected result: a valid FAQPage with three Question / Answer pairs that Google can display as expandable FAQs.

Bonus prompt ideas

“LocalBusiness schema for a coffee shop called Bean & Leaf at 123 Main St, Portland, OR 97201. Opening hours Mon–Fri 7am–6pm, Sat–Sun 8am–4pm. Phone (503) 555-0199.”
“BlogPosting for an article titled ‘10 Ways to Improve Core Web Vitals’ published 2025-11-12 by Jane Doe on example.com. Include author, datePublished, and a featured image.”
“Event schema for a free webinar ‘Intro to Structured Data’ on 2026-09-15 at 2:00 PM PDT, online, organized by Schema Academy.”

3. Applying the schema to your HTML page

Once you have the generated markup, adding it to your site is straightforward.

Recommended placement

Paste the entire <script type="application/ld+json">… </script> block into the <head> of the page, or just before the closing </body> tag. Both locations are valid; many developers prefer the head for consistency.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <title>AeroRun Pro Running Shoes</title>

  <!-- Schema.org JSON-LD generated by the Schema.org Generator -->
  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "Product",
    "name": "AeroRun Pro",
    "..."
  }
  </script>
</head>
<body>
  ...
</body>
</html>

Best practices

One primary entity per page is usually clearest, but you can include complementary types (e.g. Product + BreadcrumbList + Organization) in the same or separate script tags.
Keep the JSON valid — do not add comments inside the JSON. Trailing commas will break parsing.
Match visible content — the structured data should reflect what users actually see on the page. Misleading markup can lead to manual actions.
Update when content changes — if the price, availability, or title changes, regenerate or edit the schema so it stays accurate.
Multiple languages — if you have language-specific pages, generate separate schemas (or use inLanguage) for each version.

Dynamic sites: If your pages are rendered by a framework (Next.js, Nuxt, WordPress, Shopify, etc.), inject the JSON-LD via the appropriate head component or theme hook so it appears in the final HTML that search engines receive.

4. Verifying your structured data

After adding the script, always test it. These are the most important tools:

Google Rich Results Test

Official Google tool. Shows whether your page is eligible for rich results and highlights any errors or warnings.

Open Rich Results Test →

Schema Markup Validator

The official Schema.org validator. Excellent for checking pure JSON-LD syntax and type correctness independent of Google.

Open Schema Markup Validator →

Google Search Console

After Google crawls your pages, the “Enhancements” and “Rich results” reports show real-world coverage and issues across your entire site.

Open Search Console →

How to use the Rich Results Test

Go to https://search.google.com/test/rich-results/.
Choose URL (if the page is already live) or Code (to paste the full HTML including your new script tag).
Click Test URL / Test Code and wait a few seconds.
Review the results:
- Valid items detected — good. You should see the type (Product, FAQ, etc.) listed.
- Errors (red) — must be fixed; the rich result will not appear until resolved.
- Warnings (yellow) — recommended improvements; the result may still show but will be stronger if fixed.
Use the “Preview” when available to see how the rich result might look in Google Search.

Important: Passing the Rich Results Test means the markup is syntactically correct and eligible. It does not guarantee that Google will show the rich result for every query — that depends on relevance, authority, and other ranking factors.

Other useful checks

Mobile-Friendly Test and Core Web Vitals still matter; rich results perform best on fast, usable pages.
Bing Webmaster Tools also reads Schema.org markup and has its own URL inspection features.
After publishing, request indexing in Google Search Console for the updated URL so changes are noticed sooner.

5. Quick checklist before you publish

JSON-LD is valid (no trailing commas, proper quotes).
@context is "https://schema.org".
Required properties for the chosen type are present.
Data matches the visible content on the page (prices, titles, dates, etc.).
Tested with the Rich Results Test and (optionally) the Schema Markup Validator.
Script is present in the final rendered HTML (check “View Source” or the test tool’s code view).

Ready to generate your first schema? Open the Schema.org Generator →