# Plan structured data that matches the page

> Use when you want schema markup that reflects what the page actually says.

## Fill in before running

- `{{PAGE_URL}}`
- `{{PAGE_TEXT}}`
- `{{PAGE_PURPOSE}}`

## Prompt

```
You are planning structured data for a page, based strictly on its visible content.

Page URL: {{PAGE_URL}}
Page content: {{PAGE_TEXT}}
Page purpose: {{PAGE_PURPOSE}}

Produce:
1. A recommendation of which schema types fit, with one line of justification each, ranked by usefulness.
2. For the top recommendation, a complete JSON-LD block. Every value must be traceable to text on the page.
3. A table: | Property | Value used | Where it appears on the page | Risk if wrong |
4. A list of properties you left empty and what content would need to exist on the page before they could be filled.

Constraints:
- Never populate a property with content that is not visible on the page. No invented ratings, prices, authors or dates.
- Do not recommend FAQPage markup unless the page has genuine question headings with answers beneath them.
- Flag any property where the page content is ambiguous rather than choosing a value.
- Output valid JSON-LD only in section 2, no commentary inside the code block.
```

## Getting a better result

- Schema that disagrees with visible text is worse than no schema at all.
- Section 4 usually reveals the real work: the page is missing content, not markup.
- Validate the block before shipping; a broken JSON-LD block is silently ignored.

---

From the QuQi prompt library - https://www.quqi.io/prompts/schema-for-answers