# Schema markup for AI search: clarify entities without inventing facts. - working worksheet

Reviewed alongside the Eli guide: https://hireeli.io/resources/schema-markup-for-ai-search

## Decision to make

Choose accurate schema markup for an AI-search website

Owner: ____________________
Review date: ____________________
Canonical page or destination: ____________________

## Buyer questions

- [ ] Does schema guarantee inclusion in AI answers?
- [ ] Can FAQ schema be used on every page?
- [ ] Should an author have a separate profile page?

## Evidence-led work plan

### 1. Which types are usually useful?

Use Organization for the company, Person for real authors, Article for editorial pages, SoftwareApplication or Product for the visible offer and BreadcrumbList for navigation.

Evidence or artifact: ____________________
Status: [ ] not started  [ ] working  [ ] verified  [ ] blocked

### 2. What causes schema trust problems?

Common problems include contradictory names, prices hidden from users, review ratings without source evidence, multiple canonical entities and markup that survives after visible copy changes.

Evidence or artifact: ____________________
Status: [ ] not started  [ ] working  [ ] verified  [ ] blocked

### 3. How should markup be verified?

Validate syntax, compare every property with the rendered page and monitor search reports for errors.

Evidence or artifact: ____________________
Status: [ ] not started  [ ] working  [ ] verified  [ ] blocked

### 4. Validate claims before adding markup

Build structured data from visible page facts and assign an owner to each changeable field.

Evidence or artifact: ____________________
Status: [ ] not started  [ ] working  [ ] verified  [ ] blocked

## Source ledger

- [ ] Google: structured data guidelines: https://developers.google.com/search/docs/appearance/structured-data/sd-policies
- [ ] Schema.org: vocabulary documentation: https://schema.org/docs/documents.html
- [ ] Google: helpful, reliable, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content

## Measurement boundary

Baseline date and exact context: ____________________
7-day observation: ____________________
14-day observation: ____________________
30-day observation: ____________________
Known limitations: ____________________

Keep technical eligibility, citations, recommendations, visits, leads and revenue as separate evidence. This worksheet does not guarantee an external ranking or commercial result.