# Product pages for AI search: state the product, fit and proof clearly. - working worksheet

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

## Decision to make

Make a B2B product page understandable to search and AI systems

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

## Buyer questions

- [ ] Should a product page contain an FAQ?
- [ ] Can product claims be placed only inside screenshots?
- [ ] Does Product schema guarantee AI citation?

## Evidence-led work plan

### 1. What should appear above the fold?

Use a direct category and outcome, a short explanation of the mechanism and one clear action.

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

### 2. Which details reduce evaluation friction?

Explain ideal customer, supported workflows, integrations, setup, pricing path, security boundaries and limitations.

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

### 3. How should structured data be used?

Use Organization, SoftwareApplication or Product markup only when it accurately represents visible content and follows current search-engine rules.

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

### 4. Run the five-question product-page test

A buyer or retrieval system should be able to answer five questions from the page alone: what the product is, who it is for, which job it completes, what evidence supports the claim and where it does not fit.

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

## Source ledger

- [ ] Google: AI features and your website: https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- [ ] Google: helpful, reliable, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- [ ] 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

## 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.