Schema Generator
Use Schema Generator to prepare Schema.org structured data for a page. You choose the kind of information to describe, enter facts that match the page, and copy the generated JSON-LD script. The generator prepares code only: it does not add it to your website, save a project copy, or confirm that a search engine will show a rich result.
Generate and copy a script
Section titled “Generate and copy a script”Open Schema Generator from the sidebar. The form starts with Organization selected. Choose a schema type, fill in details that are true for the page, and review the preview as you type. For types with repeatable items, such as FAQ questions or breadcrumb entries, use Add to create a row and the remove control to delete one.
The preview contains the JSON-LD data inside a complete <script type="application/ld+json"> element. Choose Copy HTML to copy that script to your clipboard, then ask whoever maintains the site to add it to the page’s HTML <head> section. If you want to check the deployed page afterward, use Check schema.
The form is not prefilled with your project’s brand or domain; enter every value yourself, in the language of the page it describes. The preview cannot be edited directly: change the form fields to change the code. Schema Generator keeps the current form in the open page only. It has no save, history, or download action. Changing the schema type clears the form, so copy anything you want to keep before switching types. If you leave or reload the page, the form values are not restored.
Choose a type that describes the page
Section titled “Choose a type that describes the page”Types are grouped in the selector so you can choose a description that fits the real subject of the page. The current generator includes:
- Business: Organization, LocalBusiness, Person, Service, FinancialProduct
- Web: WebSite, BreadcrumbList, SoftwareApplication
- Content: Article, BlogPosting, FAQPage, Review, Speakable
- Ecommerce: Product, Offer
- Tourism: TouristAttraction, TouristDestination, Event
These are the types implemented in the current form. A type being available does not mean it is appropriate for every page or that it qualifies the page for a particular search feature. For example, use FAQPage only when the page actually contains question-and-answer content, and use Product or Offer only when the details describe the product or offer presented to visitors.
Some values become nested Schema.org objects in the output rather than plain text fields. For example, an article author becomes a Person, a business address becomes a PostalAddress, a product price can become an Offer, FAQ rows become Question objects under mainEntity, and breadcrumb rows become numbered ListItem objects under itemListElement. The preview shows the structure the form produces; use it to confirm the values landed in the right place.
Required fields and accurate data
Section titled “Required fields and accurate data”An asterisk marks required fields. The generator does not stop you from copying when one of them is blank: empty single-value fields are left out of the output. Check the preview and fill required facts before you hand the code to a developer. For repeatable sections, add complete items where the page needs them; an empty FAQ or breadcrumb list is omitted. If a repeated row has one value but another is blank, the row is still included with the blank value, so complete every question-and-answer pair or breadcrumb name-and-URL pair before copying.
Use facts that are visible or otherwise supported on the page. Keep URLs public and point them to the correct page or image. Use the date format shown in the example placeholders, and use Schema.org availability values such as InStock when the field asks for availability. The generator assembles code from your entries; it does not verify whether a URL exists, whether a price is current, or whether each value matches the page.
Review the preview before copying. This catches common mistakes such as a wrong page URL, a blank required value, an availability value that does not match the expected form, or an FAQ answer attached to the wrong question. After the code is added to the website, run Check schema on that public URL to confirm PromptEye can detect the deployed markup.
What the generator does not do
Section titled “What the generator does not do”The generator is a code helper, not a publishing integration or a complete standards validator. It does not update your CMS, deploy changes, fetch your existing page, merge with markup already on the site, or save a reusable schema. It also does not check the rules of every search engine or promise a rich result, better ranking, indexing, or AI citation.
The separate Check schema page inspects markup found on a public page. It is useful after deployment, but its result also does not guarantee how a search service will use the data. If the checker finds no schema after installation, confirm the code is on the exact public URL, is valid JSON-LD or supported Microdata, and is present in the HTML the page returns.
If you cannot open the schema tools
Section titled “If you cannot open the schema tools”The sidebar disables project workspace items when you do not have access to an active project workspace. A missing XML sitemap or missing Schema.org code does not hide Schema Generator or Check schema. A sitemap is not used by these two tools. If the items are disabled, select a project you can access or ask an owner to grant project access.
Common questions
Section titled “Common questions”Does the generator save my schema?
Section titled “Does the generator save my schema?”No. The values remain in the open form while you work. Copy the script before changing type or leaving the page.
Does Copy HTML copy only JSON?
Section titled “Does Copy HTML copy only JSON?”It copies the full HTML script element containing the JSON-LD, ready for a developer to place in the page source.
Why can I copy the result when a required field is blank?
Section titled “Why can I copy the result when a required field is blank?”The asterisk is guidance; the form does not enforce completion. Blank values are omitted, so the output can be incomplete. Review the preview and fill the facts the chosen schema needs before using it.
Why do I not see all of my site’s schema types in the generator?
Section titled “Why do I not see all of my site’s schema types in the generator?”The generator offers a fixed set of types and fields. It does not import markup from your site or support every Schema.org type. Use the checker to inspect deployed markup, or ask your site developer to implement a type the form does not provide.
Do I need a sitemap XML file to use Schema Generator?
Section titled “Do I need a sitemap XML file to use Schema Generator?”No. Schema Generator builds code from the values you enter. Check schema checks a URL directly. Neither tool reads a sitemap.
My page needs more than one type. What do I do?
Section titled “My page needs more than one type. What do I do?”Generate each type separately and copy each script. A page can contain several structured-data scripts, for example one for Organization and one for FAQPage. Copy the first script before switching type, because switching clears the form.
Will the new script replace markup already on my page?
Section titled “Will the new script 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 run Check schema to confirm what the page now exposes.
Does Generate schema from Check schema fill in the form for me?
Section titled “Does Generate schema from Check schema fill in the form for me?”No. That link opens the separate generator. It does not carry the checked URL or report values into the form, so enter the page’s facts again.