---
title: Schema Generator
description: Generate JSON-LD for one page or a whole site, download it as a ready package, and know where each block goes.
---

Use **Schema Generator** to turn the gaps found in [Schema](../schema-check/) into ready Schema.org code. You choose what to describe, enter facts that are true for the page, and get JSON-LD blocks with instructions on where to paste them. The generator prepares code and saves a package in your project; it does not change your website.

There are two generators. The **single-page generator** builds markup for one page. The **whole-site generator** builds a package for every page of a site that needs work, asking for repeated data only once.

## Generate markup for one page

Open a checked page in Schema and select the action shown for it (**Generate schema**, **Generate missing** or **Fill in optional**). You can also start from the guide band's **Generate schema** button without a checked page. The generator opens full screen and has three steps.

1. **Set** — tick the schema types to generate. Types the check found missing are already ticked and marked **from analysis**. Organization, LocalBusiness and WebSite describe the whole company or site; every other type describes the page you are generating for.
2. **Data** — enter shared data (company or site name, page address, logo) once. The name and logo go into Organization, LocalBusiness and WebSite, which point to your homepage; every other type has its own name field and uses the page address. **fill in** marks a field the check reported as missing, and an asterisk marks fields the type requires. Dates use a date picker, and event start and end times use date and time — the code adds your computer's current time zone. Prices are numbers; currency, availability, event status, country and app category are chosen from lists. Addresses, emails and numbers outside the allowed range show a hint under the field. For repeated items such as FAQ questions, breadcrumb entries, profile links or opening hours, use **Add row** and the remove control. **Fill in automatically** fills empty shared fields from your project settings: the brand name, the project domain and the project icon. When you start without a checked page, enter the page address before continuing; the package is saved for that page.
3. **Deployment** — review the generated blocks. Organization, LocalBusiness and WebSite go into one block for the homepage; every other type, including breadcrumbs, people, services and apps, goes into a block for this page. When a block holds several types, they share one `@graph`. If the check found a type already on the page, a note asks you to replace that markup instead of adding a second copy. If required fields are still empty, a warning lists them; you can still finish, but the code may not pass the check. Copy a block, download it as an `.html` file, open the full step-by-step instructions, or select **Download everything (.zip)** for all blocks plus an `instructions.txt` file.

Select **Finish** to save the package in the project and return to Schema. You can go back to an earlier step with **Back** or the step names at the top; your entries stay as you move between steps.

## Generate markup for a whole site

Start from a site in Schema: **Fill in and generate everything** in the site summary, **Generate everything ›** on the site's row in the history, or **Generate** in Recommendations. The whole-site generator has four steps.

1. **Scope** — the pages of the site that need work, each with what it is missing (for example "fill in: Phone"). Untick pages you will handle later.
2. **Shared data** — company name, homepage address and logo, plus data that repeats on two or more of the selected pages, such as a phone number or address. You enter each once.
3. **Data per page** — one section per page with only the fields its missing types need. Values from step 2 are already filled in and marked **from shared data**; changing one on a page changes it for that page only.
4. **Deployment** — one file per page. Organization, LocalBusiness and WebSite markup is collected once into `homepage.html` for the homepage; every other page gets a file named after its address, for example `services-solar.html` for `/services/solar`. The same replace and empty-field notes as in the single-page generator appear here. Download everything as a ZIP with instructions, or copy and download files one by one.

**Finish** saves the package as the site's package. If every page of the site is already valid, the generator tells you there is nothing to fill in and points you to the current package instead.

## After you finish

The saved package appears in the page details (single page) or the site summary (whole site), with **Download package (.zip)**, earlier versions, and **Generate again**. Generating again opens the generator with the data from the latest package, so you only change what is different; select **Start from scratch** to clear it. PromptEye keeps the latest package and five earlier versions for each page and site.

Hand the files to whoever maintains the site. Each block goes at the end of the `<head>` section of the page named in the instructions. When it is live, mark the site as deployed in Recommendations, then select **Check again** in [Schema](../schema-check/) to confirm the gaps are gone.

## Choose types that describe the page

The current generator includes:

- **Business:** Organization, LocalBusiness, Person, Service, FinancialProduct
- **Web:** WebSite, BreadcrumbList, SoftwareApplication
- **Content:** Article, BlogPosting, FAQPage, Review
- **Ecommerce:** Product
- **Tourism:** TouristAttraction, TouristDestination, Event

A type being available does not mean it fits every page. Use FAQPage only when the page shows questions and answers, and Product only for the product the page presents. Google no longer shows FAQ rich results for most sites, though the markup still describes the page for other services. For Review, choose what is reviewed (for example a product, a local business or an app); Google does not show review stars for reviews a business publishes about itself.

Some values become nested Schema.org objects in the output: an article author (with an optional author page) becomes a `Person`, an address a `PostalAddress`, an event venue a `Place` with its address, a price an `Offer`, opening hours `OpeningHoursSpecification` entries, profile links a `sameAs` list, FAQ rows `Question` objects under `mainEntity`, and breadcrumb rows numbered `ListItem` objects under `itemListElement`. Review the code in the deployment step to confirm values landed in the right place.

## Required fields and accurate data

The generator does not stop you when a required field is blank; empty fields are left out of the code, so the markup can be incomplete. The deployment step lists the required fields that are still empty. Fill every field marked with an asterisk or **fill in** before you hand the package over. A product needs an image, and a software application needs an average rating (the number of ratings is optional); without them the page fails the schema check. Only add a rating that real users have given. For repeated rows, complete each question-and-answer or name-and-URL pair, and each opening-hours row needs days, an opening time and a closing time.

Use facts that are visible or supported on the page and public URLs. The generator checks the format of addresses, emails and numbers, but it does not check whether a URL exists or a price is current.

## What the generator does not do

It does not read values from your live page, update your CMS, deploy files, merge with markup already on the site, or promise rich results, ranking or AI citations. People with view-only access can download saved packages but cannot generate new ones.

## Use it from an AI assistant (MCP)

The PromptEye MCP server has a `generate_article_schema` tool for articles written in [Content](../content/). It returns Schema.org JSON-LD for one PromptEye article: FAQPage, plus Article for a published article when an author is given. The assistant passes the question-and-answer pairs as plain text, exactly as they appear on the published page, and the author's name. As with the generator, the code is only as accurate as those facts, and pasting it into the page is up to you.

Homepage and project markup, such as Organization, SoftwareApplication, or Product with an Offer, is not generated by this tool. Use the Schema Generator in the app for those.

## Common questions

### Is my work saved if I close the generator?

Only when you select **Finish**. Closing earlier discards the entries. After **Finish**, the package and the data you entered are saved, and **Generate again** starts from them.

### Why does Fill in automatically leave some fields empty?

It only fills the shared name, address and logo from your project settings, and only fields that are still empty. Type-specific facts such as opening hours or prices have to be entered by you.

### Why are some types already ticked?

They are the types the last check found missing on that page. You can untick them or add others.

### Will the new code replace markup already on my page?

No. The generator does not read your page. If the page already has markup of the same type, ask your developer to replace the old script rather than add a second one, then check the page again.

### Why is Organization in the homepage file instead of my page's file?

Organization, LocalBusiness and WebSite describe the whole company or site, so they belong on the homepage once. Repeating them on every page is unnecessary. Everything else, such as breadcrumbs, products or people, stays with its own page.

### Which time zone do event times use?

The time zone set on the computer you generate the code on. If the event happens in another time zone, adjust the offset at the end of `startDate` and `endDate` in the code.

### Do I need a sitemap to use the generator?

No. Only **Collect pages** in Schema reads a sitemap; the generators work from your checks and the data you enter.

## Related guide

- [Schema](../schema-check/)
