← Back to the index
SEO-02 · SEC. 07 SEO & GEO
Generate JSON-LD Schema From Existing Page Content
Feed it a page's content, get back valid JSON-LD structured data ready to embed.
- FORMAT
- prompt
- DIFFICULTY
- beginner
- TIME
- 5 min
- TOOLS
- universal
- MODELS
- any
- COPIES
- 0 so far
When to use this
You have a page live with no structured data, and you want search engines and LLMs to parse its content correctly (rich results, better citations). Use this per page type: article, product, FAQ, how-to.
The pattern
Pastes as plain text
Generate valid JSON-LD structured data for one page from my site: - Pick the single most accurate schema.org type for the content (Article, Product, FAQPage, HowTo, etc.), don't guess a generic type if a specific one fits better - Extract only facts that are actually present in the content I give you, do not invent prices, ratings, dates, or author names that aren't there - Include only properties whose values are supported by the content; omit unknown optional properties - Output a single <script type="application/ld+json"> block ready to paste into the page <head> only when the source supports a valid block - If the most accurate type needs a required value the content does not provide, do not invent it or emit a placeholder block; state the missing fact and ask for it instead Start by asking me in one message for the page URL and the page's full content pasted in, then wait. Don't generate anything until you have both.
Real example output
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Generate an llms.txt File for Your Site",
"step": [
{
"@type": "HowToStep",
"name": "List your key pages",
"text": "Gather URLs and one-line descriptions of your site's most important pages."
},
{
"@type": "HowToStep",
"name": "Generate the file",
"text": "Use an AI prompt to format the list into a structured llms.txt file."
},
{
"@type": "HowToStep",
"name": "Publish at site root",
"text": "Save the file as /llms.txt so crawlers can find it at a predictable path."
}
]
}
</script>
Missing (not in source content): totalTime, author name.Why it works
Schema.org's `@type` vocabulary is precise, and picking the wrong one (Article for a Product page) is worse than no schema at all. Grounding extraction strictly in the pasted content, and flagging gaps instead of filling them with invented data, keeps the output valid and avoids penalties for misleading structured data.