Meta Tag Generator
Fill four fields and copy a block of head meta tags.
Generate schema.org JSON-LD structured data for a page. Pick a type (Article, Organization, Product, LocalBusiness or FAQPage), fill the fields and copy the script.
Your browser is preparing the tool. It runs 100% locally.
Choose one of five schema types (Article, Organization, Product, LocalBusiness or FAQPage), fill in the fields, and the tool outputs a ready-to-paste JSON-LD script (the format Google recommends for structured data). It builds the @context, @type and your details into valid markup. It covers the core properties, not every recommended one, and structured data must describe content that is visible on the page. The Schema Markup Generator works inside your browser.
Structured data tells search engines what a page is about in a machine-readable way, using the shared schema.org vocabulary. Pick a type, enter the relevant details (a headline and author for an Article, a name and price for a Product), and the tool wraps them in a JSON-LD script you paste into the page.
JSON-LD is Google's preferred format because it sits in its own script block, separate from your HTML. The tool produces the core fields for each type; for a Product it also nests an Offer with the price and currency. You can add further properties by hand if you need them.
When you choose a type, the form shows that type's fields and, as you fill them, assembles a JSON object with @context set to schema.org and @type set to your choice, plus your values. FAQPage builds a mainEntity list of Question and Answer pairs; Product nests an Offer; the others map fields straight across.
The result is wrapped in a script of type application/ld+json. Google reads it to understand the page and, for some types, to show a richer result. Valid markup never guarantees a rich result, though; Google decides case by case.
Article — headline, author, datePublished, image
Organization — name, url, logo
Product — name, description, price, priceCurrency (in an Offer)
LocalBusiness — name, telephone, address
FAQPage — up to 2 question-and-answer pairsCore properties only, not every property Google recommends (an Article, for example, can also carry a publisher and dateModified). Add extra fields by hand if a type needs them.
| Types | Article, Organization, Product, LocalBusiness, FAQPage |
|---|---|
| Output | JSON-LD in an application/ld+json script |
| Product | nests an Offer (price, currency) |
| FAQPage | up to 2 question-and-answer pairs |
| Fields | core properties per type |
| Placement | in the head or body of the page |
| Where it runs | In your browser, nothing uploaded |
It generates the core properties for each type, not the full set Google can use. An Article can also take a publisher, a dateModified and a properly-sized image; a Product can take a review and an aggregate rating. Add those by hand if you want the richest eligible markup.
Structured data must match what is visible on the page. Marking up a price, review or FAQ that a visitor cannot actually see is a Google guidelines violation and can cost you the rich result or bring a manual action. Mark up only content that is on the page.
Valid markup does not guarantee a rich result. Google decides whether and when to show one, and it has been retiring rich-result types: FAQ rich results ended in 2026, and HowTo earlier. The Rich Results Test checks eligibility, but it cannot promise a rich result.
The LocalBusiness address is a single text field here, not a structured PostalAddress with separate street, city and postal-code properties. For full local markup you would expand it by hand.
It does not validate the result. Run the output through Google's Rich Results Test or the Schema.org validator before relying on it, and check the @type matches your actual content.
Mark up a blog post or news article with its headline, author and date.
Add Product markup with price and currency for a shop page.
Describe your site's organisation with a name, URL and logo.
Give a storefront page a name, phone and address in machine-readable form.
Need many FAQ pairs? Use the dedicated FAQ schema generator. Need a breadcrumb trail? Use the breadcrumb schema generator. Need a type not listed, or every property? Hand-write it from the schema.org reference and test it.
Outputs valid schema.org JSON-LD for five common types with their core fields; it is explicit that it omits some recommended properties, that the markup must match visible content, and that valid markup never guarantees a rich result.
Fill four fields and copy a block of head meta tags.
Top words in your content and the share each one takes.
Add utm_source, utm_medium and utm_campaign to any URL.
Write the og: tags that control link previews on social apps.
See roughly how a title and description could look in Google.
Set crawler and AI-bot access and point to your sitemap.
It's free, needs no account, and nothing you enter is sent to a server.