JSON-LD structured-data wizard
Generate valid Schema.org JSON-LD for the rich-result types that drive most of the SERP enhancements in 2026: Product (with offer and aggregate rating), Article, FAQPage, HowTo, Recipe, Course, JobPosting, LocalBusiness, Event, Review and BreadcrumbList. Pick a type, fill the form, copy the script tag. The output follows the Google Search Central documentation, validates with the Rich Results Test and Schema.org validator, and ships with optional fields turned off by default so it stays clean.
Generated JSON-LD is plain Schema.org markup. Paste the <script> tag in your page <head> or just before </body>. Re-run the Google Rich Results Test after deploying.
What Schema.org JSON-LD does for SEO in 2026
Schema.org is the shared vocabulary used by Google, Bing, Yandex, DuckDuckGo, Apple and several AI search products to understand what a web page is about. When a page declares a Product, Google can show a star rating, a price and an availability chip in the search result. When a page declares a Recipe, Google can show the cooking time, calories and a thumbnail. When a page declares JobPosting, the listing can appear in the Google Jobs experience. The mechanism is opt-in: search engines do not infer structured data; you publish it explicitly on the page in JSON-LD format. Sites that publish clean structured data on the right page types win significantly more click-through than sites that publish nothing or sites that publish broken markup that is silently ignored.
This wizard helps you produce the JSON-LD for the rich-result types that Google currently supports and that materially impact organic visibility: Product, Article, FAQPage, HowTo, Recipe, Course, JobPosting, LocalBusiness, Event, Review and BreadcrumbList. The forms only ask for the fields that Google flags as Required or Recommended in 2026 documentation, so the output passes the Rich Results Test without manual edits. You can extend the output by hand for vendor-specific extensions; the baseline shipped by the wizard is what most teams need.
How the wizard generates valid Schema.org markup
- Pick the schema type from the list of 11 currently supported rich-result types. Each type has its own form template with the right field set.
- Fill the form. Required fields are flagged; recommended fields are shown but can be skipped. Complex sub-objects (such as Product Offer, Recipe Instructions, JobPosting hiringOrganization) are split into clearly labelled sub-sections.
- Generate the JSON-LD by clicking the button. The wizard builds the object tree, drops empty fields, normalises dates to ISO 8601, prefixes prices with the currency code, and wraps the result in the standard
@contextand@typeenvelope. - Validate by clicking the “Open Google Rich Results Test” link with the generated markup pasted in. A green check confirms eligibility; warnings list the optional fields you can add for better display.
- Publish by copying the full
<script type="application/ld+json">tag into the page<head>or just before</body>. The location does not affect ranking; consistency does.
Common use cases for the wizard
- E-commerce product pages. Generate the Product schema with offer (price, availability, currency), aggregateRating, brand and SKU. Pages with the right Product markup show price chips in the SERP and qualify for the Shopping experience.
- Editorial article. Generate Article with headline, author, datePublished, image and publisher. Required to appear in Google News and Discover, and to compete in the Top Stories carousel.
- FAQ block on a landing page. Generate FAQPage with 4-8 question / answer pairs. Major SERP-feature gain when the page is already ranking in top 5.
- How-to tutorial. Generate HowTo with ordered steps and optional supplies / tools. Useful for kitchen tutorials, DIY guides, technical setup pages.
- Local business. Generate LocalBusiness with address, geo, openingHoursSpecification, telephone, priceRange. Feeds Google Business Profile signals.
- Job posting. Generate JobPosting with title, description, datePosted, validThrough, hiringOrganization, jobLocation, baseSalary. Required for Google Jobs visibility.
- Online course. Generate Course with name, description, provider and offers. Increasingly indexed in the SERP since 2023.
- Event listing. Generate Event with name, startDate, location, performer, organizer. Powers the Events SERP feature.
- BreadcrumbList. Generate the navigation crumbs that replace the URL in the SERP result. Small but consistent CTR win.
Limitations and validation tips
Schema.org markup is a strong signal of eligibility, not a guarantee of display. Google decides whether to show a rich result based on the markup, the query intent and quality signals. Marking up a Product on a non-product page leads to a manual action. Marking up FAQPage on the same page as Article works as long as the FAQ content is genuinely visible to users; hidden or generated FAQ blocks have been the source of multiple Google manual actions since 2023. The wizard sticks to the Required and Recommended properties, but Schema.org is a much larger vocabulary; extend the output by hand when your content has additional structured data worth declaring.
The wizard runs entirely in your browser. Field values are processed locally and never sent to PeopleAreGeek or to Google as part of the generation step. The “Open Google Rich Results Test” button opens Google’s official validator in a new tab; that is when the JSON-LD reaches Google, exactly the same way as if you had used the public web tool directly.
Frequently asked questions
Where in the page should the JSON-LD script go?
Either in the <head> or anywhere in the <body>. Google parses both. Just before </body> is common because it does not block first paint. The location does not affect ranking; consistency across the site does.
Can I publish multiple JSON-LD blocks on the same page?
Yes. A page can declare BreadcrumbList, Article and FAQPage simultaneously. Use one <script type="application/ld+json"> tag per type or wrap them in @graph. The wizard outputs one type at a time; assemble multiple outputs manually if needed.
Why does my markup pass the validator but no rich result appears?
Eligibility and display are different. Google decides per query whether to show the enhanced result based on quality signals, query intent and site authority. Valid markup is necessary but not sufficient. Track Search Console enhancements for the type to confirm eligibility.
Does Google still support FAQPage rich results?
Yes, but with reduced eligibility since the 2023 update. FAQPage rich snippets now mostly appear on government, official and well-known authoritative sites. Marking up an FAQ remains useful for the wider semantic web and for AI agents that read JSON-LD.
Is BreadcrumbList enough or do I also need on-page breadcrumbs?
Best practice is to publish both: visible HTML breadcrumbs in the layout and BreadcrumbList JSON-LD in the head. Google honours the markup even without visible crumbs, but visible crumbs help users and pass the design review.
Are the generated values stored?
No. The wizard runs in your browser. The form values, the generated JSON and the downloaded file never reach PeopleAreGeek or any other server. The “Open Rich Results Test” button is the only outbound link; clicking it sends the markup to Google, which is the point of validation.
