Free browser-based tool
Schema Markup Generator
Draft JSON-LD schema details for common pages using page URL, page title, description, organization, author, FAQ, breadcrumbs, logo, image, and sameAs URLs.
Enter your details
Result
Your result will appear here.
How this helps
Draft JSON-LD schema details for common pages using page URL, page title, description, organization, author, FAQ, breadcrumbs, logo, image, and sameAs URLs. The goal is to make the first working draft clear enough to review, share, and improve instead of starting from a blank document.
Real-world example
Use schema to describe the real page content and test the final JSON-LD before publishing.
Common mistakes
- Adding schema that does not match visible content.
- Publishing invalid JSON.
- Stuffing schema with unrelated keywords.
Schema Markup Generator: what the result means
Create a JSON-LD draft that matches the visible page and selected schema type. Complete only properties you can support with real page content, then validate the output before deployment.
A realistic way to use it
For an Article, provide the canonical URL, headline, description, author, publisher, image, and dates. For FAQPage, add only questions and answers that visitors can read on that same page.
Checks that prevent a bad result
Do not invent ratings, prices, authors, addresses, or FAQs. Avoid adding multiple conflicting Organization or WebSite entities, and do not mark hidden content.
Mark up what the page visibly proves
Schema works best when the selected type, properties, visible content, canonical URL, and page purpose all describe the same real entity.
| Schema decision | Evidence on the page | Validation step |
|---|---|---|
| Choose the main type | The page has the matching primary purpose and required visible details | Check current Google-supported features and Schema.org definitions. |
| Identify the entity | Stable name, canonical URL, description, image, author, or organization data | Use absolute URLs and avoid creating duplicate entities. |
| Add nested details | Visible FAQs, breadcrumbs, offers, authorship, or organization relationships | Do not add claims that visitors cannot find on the page. |
| Publish and monitor | JSON-LD matches the final rendered page | Run a syntax validator and review Search Console enhancement reports. |
Before you act: validate the exact production URL after publication because plugins, templates, and duplicate markup can change the final rendered graph.
When this tool is not enough
Valid JSON-LD does not guarantee a rich result. Eligibility also depends on Google policies, page quality, visible content, and supported result types.
Frequently asked questions
Where should JSON-LD be placed?
It can be placed in the head or body as a script with type application/ld+json.
Should every page use FAQ schema?
No. Use it only where visible, relevant FAQs genuinely help the page.