SEO

Schema markup generator

Use when you need valid structured data for a specific page and want no invented fields.

schema-markup-generator.md

Download .md

You are generating JSON-LD structured data.

Page URL: {{PAGE_URL}}
Page type: {{PAGE_TYPE}}
Page content or key facts: {{PAGE_FACTS}}
Organization name and URL: {{ORG}}

Produce:
1. The recommended schema type or types, with one line explaining why each applies.
2. A complete JSON-LD block ready to paste into the head, using only facts present in {{PAGE_FACTS}}.
3. A list of recommended properties you could not fill, with the exact information needed to fill each.
4. A validation checklist of things to confirm before publishing.

Rules:
- Never invent ratings, review counts, author names, dates, prices or availability. If it is not in the supplied facts, leave the property out and list it in section 3.
- Every value in the markup must correspond to something visible on the page. Say so explicitly if any supplied fact is not visible.
- Do not add schema types that the page does not genuinely qualify for, even if they trigger rich results.
- Output the JSON-LD in a single code block with no commentary inside it.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{PAGE_URL}}
{{PAGE_TYPE}}
{{PAGE_FACTS}}
{{ORG}}

Getting a better result

Paste the visible page copy, not a description of it, so every property maps to real on-page text.
Run the output through the Rich Results Test before deploying - the model cannot validate for you.
Section 3 is the useful part: it tells you what content the page is actually missing.

Questions about this prompt

When should I add structured data to a page?

When the page has facts that a search engine would otherwise have to infer, and when the type you are marking up still earns something in the results. Breadcrumbs, products and reviews remain worth it. Note that FAQ and How-to rich results were restricted in 2023, so marking those up no longer earns the snippet it once did.

What should I paste in?

The visible page copy, not a description of it. Every property in valid structured data has to map to something a user can actually see on the page. Marking up facts that are not on the page is the definition of the spam case Google penalises.

Can I trust the output is valid?

Run it through the Rich Results Test before deploying. The model cannot validate its own output, and a subtly malformed block is worse than none because it can suppress the enhancement you were trying to earn.

What is the most useful part of the output?

The section that tells you what the page is missing. If the markup cannot be completed without inventing a field, that is usually a sign the page itself is missing information a visitor would want, and fixing the page is worth more than fixing the schema.