Skip to main content
GARGLOO

Schema Markup Generator

JSON-LD that earns rich results — and the types that no longer do.

Runs on your device

At a glance

Input:
Text / data you paste
Processing:
Runs locally in your browser
Privacy:
Nothing you type is sent to a server

Last updated: 2026-11-11

Common use cases

  • Writing the JSON-LD block for a new product page before publishing it
  • Checking whether an old FAQPage block is still worth keeping after the May 2026 removal
  • Adding Organization markup with social profiles to a company home page
  • Building a Recipe block with prep and cook times for a food blog post

About this tool

Pick a schema type — Organization, Article, Product, LocalBusiness, Event, Breadcrumbs, Software, Person, Job Posting, Recipe, Video or FAQ — fill in the fields, and copy a ready-to-paste JSON-LD block. Required fields are marked, empty optional fields are left out, and every block is checked against the table that matters most: which types still earn a Google rich result, and which ones Google retired — HowTo in September 2023, six types in September 2025, FAQ in May 2026.

How to use it

  1. Pick a schema type — start with the one that matches your page, not the one you wish Google still showed.
  2. Fill in the required fields, then the optional ones that are true about your page.
  3. Copy the JSON-LD block and paste it inside the <head> of your page.
  4. Validate the live page in Google's Rich Results Test and the Schema Markup Validator — this generator builds markup, it does not validate it.

Worked examples

Input: Organization 'Bean & Leaf' · URL https://www.example.com · logo · 2 social profiles

Output: JSON-LD block with @type Organization, name, url, logo, description and a 2-item sameAs array

Verified against the real generator: the block parses as JSON and carries all 5 fields — the sameAs array holds exactly the 2 URLs entered.

Input: Product 'Trailhead Hiking Boots' · $89.99 USD · InStock · brand Trailhead · 4.6 from 128 reviews

Output: JSON-LD block with @type Product, an Offer at 89.99 USD with availability https://schema.org/InStock, and an AggregateRating of 4.6 from 128 reviews

Verified: the generated Offer carries price "89.99", priceCurrency "USD" and availability "https://schema.org/InStock"; the rating is the number 4.6, not the string "4.6".

Input: FAQPage with 2 questions — opening hours and whole beans

Output: JSON-LD block with @type FAQPage and a mainEntity array of 2 Question nodes, each with an acceptedAnswer

Verified: the block parses as JSON with exactly 2 Question nodes — and the page warns that Google stopped showing FAQ rich results on 7 May 2026, so this block earns no visible result.

Practical tips

  • Mark up only what visitors can see on the page — hidden markup can cost the page its rich-result eligibility.
  • Fill in the required fields first: a Product without a price, or an Article without a publish date, is not eligible for its rich result.
  • Check the table before you pick a type — FAQPage and HowTo are valid schema.org, but Google no longer shows either as a rich result.
  • Validate on the live page, not on the block alone — the Rich Results Test checks the published URL, which is what Google actually reads.

Common mistakes

  • Adding FAQPage markup expecting a dropdown — Google stopped showing FAQ rich results on 7 May 2026 for every site.
  • Copying a generator's HowTo block for a tutorial — HowTo rich results ended on 13 September 2023.
  • Quoting 'seven types retired in June 2025' — only six were removed; Book Actions was kept.
  • Treating a block that parses as a block Google will use — parsing is syntax; eligibility is Google's decision.

How this compares

Most schema generators in the field emit every type the same way, retired ones included, and never say which rich results still exist. This one carries the dated retirement table — HowTo (September 2023), six types (September 2025), FAQ (May 2026) — marks required fields per type, leaves empty optional fields out, and sends you to Google's own validators instead of pretending to validate. The tradeoff: it generates markup, it does not audit your site — for the tags around it, pair it with the meta-tag, sitemap and robots.txt generators.

Good to know

  • The generator builds markup; it does not validate it — use the Rich Results Test and the Schema Markup Validator on the published page.
  • Schema markup is not a ranking factor and gives no guarantee of a rich result — Google decides whether to show one.
  • Retired types (FAQPage, HowTo, the six June 2025 types) produce valid schema.org, but no Google rich result.
  • Dates in the table are Google's changelog dates as of November 2026 — Google can retire further types, so re-check the table before relying on it.

Frequently asked questions

Are my details sent anywhere?

No. Everything runs in this tab — the form, the JSON-LD block and the table. Nothing is uploaded, and there is no signup.

Will adding schema markup improve my ranking?

No. Google has said repeatedly that structured data is not a ranking factor. It makes a page eligible for rich results — the enhanced displays — but Google decides whether to show one, and a rich result can appear or disappear without the ranking changing.

Should I still add FAQPage markup?

You can, but expect nothing visible from Google: FAQ rich results stopped appearing on 7 May 2026 for every site, and Google removed the documentation on 15 June 2026. The markup stays valid schema.org and other systems may still read it — but no Google FAQ dropdown will come back.

Why does the table say six types retired in June 2025, not seven?

On 12 June 2025 Google announced the retirement of seven types: Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing. Only six were actually removed on 9 September 2025 — Book Actions was kept, because a Search feature still uses the markup. The table says so; most generators still say seven retired.

Does this tool validate my markup?

No — it builds it. Validation is a separate step, and the page links it: paste your published URL into Google's Rich Results Test, and paste the block into the Schema Markup Validator at validator.schema.org. A block that parses is not the same as a block Google will use.

Which fields are required?

The ones marked Required in the form — Google's documentation lists them per type. For a Product that is the name, price and currency; for an Article, headline, author and publish date. Empty optional fields are left out of the block automatically.

Can I mark up content that is not on the page?

No. Google's structured data policies say to mark up only content visible to readers. Hidden markup — reviews you do not have, prices you do not charge, questions with no visible answer — can lose the page's rich-result eligibility.

All developer tools
Schema Markup Generator | GARGLOO