Build a JSON-LD draft
Free, unlimited browser-based formatting. No account or AI model call. Enter public facts; inputs stay in this page. The tool formats your details and does not verify eligibility for rich results.
Only the types supported by the active form are available. Use current, public facts that match the page.
Start with the right entity
An article describes published editorial content. An organization describes the business or publisher. A software application describes the product. Choose the entity actually represented on the page; adding extra types does not automatically create a richer search result.
Review every generated value
Check names, URLs, dates and relationships. Use the actual publication date for a published article. Do not give a draft a false history, assign an invented author or copy a review rating from an unrelated product.
If a value is unknown, resolve it before publishing the corresponding claim. The generator formats supplied information; it cannot verify your business identity or customer reviews.
Choose a type that matches the page
| Page or entity | Vocabulary to investigate | Facts to establish first |
|---|---|---|
| Business identity | Organization or an appropriate LocalBusiness subtype | Correct name, website and applicable location details |
| Editorial article | Article or BlogPosting | Actual headline, author, publication history and page URL |
| Navigation trail | BreadcrumbList | The real hierarchy and destination URLs |
| A software product | SoftwareApplication where appropriate | Verified product identity and the visible offer, if any |
This table helps select a vocabulary; it is not a promise that every type is implemented in this generator. Use only the types offered by the working form and check the rules of any search feature you want to support.
Avoid duplicate or conflicting markup
Inspect existing output from the CMS, theme and plugins before adding another block. Keep identifiers and URLs consistent when the same organization appears on several pages. After insertion, inspect the resulting page again; a valid standalone example can conflict with markup already present.
JSON-LD is the data format of the proposed output. The surrounding script wrapper, if needed, belongs in the implementation location your site supports. Never paste secrets or private customer details into public structured data.
Validate the markup and the page
Use the Schema.org validator to inspect syntax and vocabulary. Use Google's Rich Results Test for supported Google search features. A syntactically valid type may have no associated rich result.
After implementation, confirm the markup appears on the intended public URL and matches the visible content. Check for a second plugin producing conflicting entities.
Example: a real author relationship
If a named editor genuinely wrote and reviewed an article, the page can identify that person and link to an accurate biography. The markup should represent that relationship. An invented biography added only to satisfy a field undermines the information it claims to describe.
See Google's structured data introduction for how structured data relates to search features. For the page itself, use the SEO checker and review the content visible to readers.
Does valid schema guarantee a rich result or AI citation?
No. Validation checks particular requirements. It does not control whether a search system chooses to display an enhanced result or cite a page.
Should I add review stars to my own product page?
Use only genuine, applicable review information and check the requirements of the search feature you are targeting. Never generate ratings or review counts to fill a template.
