Skip to content

Schema markup generator

Choose a type, fill in what you know and copy the JSON-LD into your page. Reavlo lists the properties Google requires or recommends that are still missing.

  • Runs in your browser
  • Nothing is uploaded
  • Free, no sign-up
  • method v1.0.0
  • Updated Oct 2026

Input

What the page is about, as visitors know it.

A full address starting with https://.

For example BusinessApplication.

For example Web, Android or Windows.

Digits only. Use 0 for a free app.

From 1 to 5. Only if visitors can see it on the page.

Whole number.

Updates as you type · nothing leaves this page

Result

Nothing on the bench yet

Fill in a few fields, or load an example to see the markup and the checks.

Turns a short form into JSON-LD for a software app, a product, an organization or a FAQ page, ready to paste into your page, and lists the properties Google requires or recommends that are still missing. For founders and marketers who want search engines and AI assistants to read the page correctly.

How to use it

  1. Choose the type of markup that matches what the page is about.
  2. Fill in the fields you know. The code and the checks update as you type.
  3. Add the properties listed under the findings, only if the page shows them to visitors.
  4. Copy the code into the head of the page, or download it as a file.
  5. Test the page with Google's Rich Results Test before you publish.

How Reavlo tests this

The JSON-LD is built in your browser from the fields you fill in. Fields left empty are left out, so the markup never claims something you didn't enter.

Types and properties. Property names follow schema.org release 30.1 (2026-09-16). The four types are SoftwareApplication, Product, Organization and FAQPage.

Checks. A critical finding is a property Google's documentation requires for the type's rich result. A warning is one it recommends. An info finding is a note. The rules come from Google's pages for software apps, product snippets and organizations, each read on the date shown under Sources:

  • Software app: name, offers.price and a rating or review are required; applicationCategory and operatingSystem are recommended.
  • Product: name and at least one of an offer, a rating or a review are required; the currency and availability of the offer are recommended.
  • Organization: nothing is required; Google recommends among others name, url, logo, description and sameAs.
  • FAQ: the markup is valid schema.org, but Google retired the FAQ rich result in 2026, so it no longer changes how the page looks in Google Search.

Limits. The tool checks which properties are present, not whether they are true or whether Google will show a rich result. Only mark up what visitors can see on the page. Ratings need real reviews. Google's Rich Results Test is the final check for your page.

Questions

Is what I type uploaded?

No. The markup is built in your browser and nothing you enter is sent to a server or stored. A share link carries the form values in the address fragment, which browsers don't send to servers.

Where do I paste the JSON-LD?

Paste the whole script element into the head or the body of the page it describes. Search engines read it from either place.

Does structured data improve my ranking?

Google says structured data helps it understand a page and can make the page eligible for rich results, but it doesn't promise a ranking boost. Treat it as a way to be read correctly.

Is FAQ markup still worth adding?

Google no longer shows FAQ rich results, so it adds nothing in Google Search. The markup stays valid schema.org, and other tools may still read it. Add it only if you want the questions in a machine-readable form.

Why does the tool ask for a rating on a software app?

Google requires either a rating or a review for the software app rich result. Add one only if visitors can see it on the page; marking up ratings that aren't shown is against Google's guidelines.