Generators
Schema markup generator
Generate JSON-LD structured data for ten common page types, combined into one script and checked against Google's required and recommended properties as you type.
Free · No signup · Runs in your browser
Your schema markup
0 problems, 5 worth adding
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Article"
}
]
}
</script>Checked against Google's rules
- Worth fixing
Article has no
headline. Google recommends it for article results.In Article - Worth fixing
Article has no
image. Google may show it with your result.In Article - Worth fixing
Article has no
datePublished. Google recommends it for article results.In Article - Worth fixing
Article has no
dateModified. It tells Google when the article last changed.In Article - Worth fixing
Article has no
author. Google uses it to tell who wrote the article.In Article - Note
The markup must match what visitors can see on the page
Google's guidelines say structured data has to describe the page's visible content. Markup for things that aren't on the page can lose you rich results.
How it works
Tick what the page shows: an article, a product, a local business, breadcrumbs and so on.
Fill in the fields. The markup and Google's checks update as you type.
Copy the script tag or download it, and add it to the page's HTML.
What schema markup is for
Schema markup is a block of structured data, written in the Schema.org vocabulary, that states facts about a page in a form machines can't misread: this is a product, it costs $49, it's in stock, 212 people rated it 4.6. Google uses it to understand pages and to show rich results such as prices, review stars, event dates and breadcrumb trails.
Other systems read it too. Bing uses it, and an AI assistant that fetches your page gets the same facts in a clean, structured form. It isn't a shortcut to higher rankings; its value is a clearer, richer result and less room for a machine to get your details wrong.
One script, one @graph
Most pages describe more than one thing: an article, the organisation that published it, and the breadcrumb trail above it. This generator puts them in a single script using @graph, a list of separate items in one JSON-LD block. When you add an Organization, the article's publisher points at it by its @id instead of repeating the details, so everything on the page agrees.
JSON-LD is the format Google recommends. It sits in its own script tag, so you can add it to the head or the body without touching the visible HTML.
Which types still get rich results
Google's list of rich results changes, and several markup generators still offer types that no longer do anything in Google:
- FAQ: from August 2023 Google showed FAQ rich results only for well-known government and health sites, and from May 7, 2026 it stopped showing them for every site. FAQPage markup is still valid, and other tools can read it.
- How-to: removed in September 2023, so this generator doesn't offer it.
- Sitelinks search box: retired in November 2024. WebSite markup still helps Google pick your site name.
- Breadcrumbs: still shown on desktop. Since January 2025, mobile results show only the domain.
Article, Product, LocalBusiness, Event and SoftwareApplication markup can all still produce rich results. Organization and Person have no rich result of their own, but they help Google connect your brand, logo and authors. Each section in the generator is labelled with its current status.
Required, recommended, and what the checks mean
Each type has properties Google requires before it will show a rich result, and others it recommends. A Product needs a name plus an offer, a review or a rating. A SoftwareApplication needs a price (0 is fine) and a rating or review. An Event needs a name, a start date and a physical place with an address. In the checks, a problem is a missing requirement or a value Google can't read; "worth fixing" is a recommendation that can improve how the result looks.
Google also has quality rules no generator can check. The markup must describe what's visible on the page. Review stars must come from real reviews shown on that page, and a business can't earn stars by marking up reviews of itself on its own site. Markup that breaks these rules can be ignored, or lead to a manual action that removes rich results for the site.
After you add it
Publish the page, then check the live version. The schema validator reads the markup from any address, and Google's Rich Results Test shows exactly which rich results Google sees after rendering the page. Search Console's enhancement reports then track errors across the whole site as Google recrawls it. Rich results can take weeks to appear, and Google never guarantees them, even for flawless markup.
Questions people ask
Where do I put JSON-LD on the page?
Anywhere in the HTML. The head is common, but the body works too. Google can read JSON-LD added by JavaScript, but many AI crawlers don't run JavaScript, so markup in the HTML your server sends is the safer choice.
Can I use more than one type on a page?
Yes, as long as the page really shows each thing. An article with its author, publisher and breadcrumbs is a typical combination. Don't add Product markup to a page that only mentions a product in passing.
Does schema markup improve rankings?
Not directly. It helps search engines understand the page and can make your result richer, which can earn more clicks. The content still has to earn the position.
Should I still add FAQ markup?
It no longer produces FAQ rich results in Google. It does no harm and gives other tools a clean question-and-answer structure, so there's no need to remove it if the questions are visible on the page.
Is anything I type sent to RomeoSEO?
No. The markup is built and checked in your browser.
Want it done for you?
Romeo keeps structured data right on every page
He checks the markup across your whole site, fills in what Google requires, fixes markup that no longer matches the page, and sends each change for you to approve.
