# My website first-read record

The website first-read record preserves what you know, what you've inferred, and what a real visitor still needs to test.

## Intended visitor and situation

**Product or service:**

**Customer group:**

**User, buyer, and approver:**

**Problem and the moment it becomes urgent:**

**Customer result:**

**Product mechanism:**

**Positioning:**

**Price and what the customer pays for:**

**Proof I have:**

**Primary action:**

**Where visitors will come from:**

## The six visitor questions

1. What is this?

2. Is it for somebody in my situation?

3. What would change for me?

4. Why should I believe that?

5. How much does it cost?

6. What can I do next?

## Current page jobs

Identify the five to seven narrative jobs the page currently attempts. Use that range as a planning prompt only.

1.
2.
3.
4.
5.
6.
7.

## Page plan

| Visitor question | Section job | Information to include | Evidence or asset |
| --- | --- | --- | --- |
| Is this for me? | Opening | | |
| Why would I change now? | Problem and trigger | | |
| How does it work? | Mechanism | | |
| What would I get? | Result or use case | | |
| Why should I believe you? | Proof | | |
| What does it cost? | Offer | | |
| What happens next? | Action | | |

## Claim-to-proof ledger

| Claim | Proof available | Source and date | Limit | Where it appears |
| --- | --- | --- | --- | --- |
| [Exact claim] | [What supports it] | [Public or internal source] | [What the evidence can't establish] | [Page section] |
| | | | | |
| | | | | |
| | | | | |
| | | | | |

## Primary action and route test

**Main action test:** [what I tested, device, date, and result / not tested]

**Keyboard test:** [what I tested, date, and result / not tested]

**Mobile test:** [device or viewport, date, and result / not tested]

**Accessibility or performance results:** [tool, date, exact result / none]

## Accessibility and mobile review

### Static checks

- [ ] Descriptive title
- [ ] Declared language
- [ ] One main heading
- [ ] Sensible heading order
- [ ] Text alternatives for meaningful images
- [ ] Labels for form fields
- [ ] Descriptive links
- [ ] Mobile viewport

### Manual tests

- [ ] Keyboard operation, focus order, visible focus, and escape from menus or overlays
- [ ] Screen-reader names, roles, states, announcements, and reading order
- [ ] Text and component contrast
- [ ] Reflow and zoom
- [ ] Mobile collisions, clipping, and task-blocking overflow
- [ ] Touch-target size and spacing
- [ ] Motion or overlays that hide the main task

## Search, GEO, and agent-readiness baseline

- [ ] Clear answers to real buyer questions
- [ ] Headings that describe those questions and answers
- [ ] Specific claims with the source, date, method, and limit nearby
- [ ] Accurate titles, descriptions, canonicals, and structured data that agrees with the visible page
- [ ] Crawlable internal links to relevant product information, proof, and next steps
- [ ] An intentional index policy and a sitemap for the public pages
- [ ] An owner or author plus an update date where the information can become stale

## AI-pattern copy and visual review

### Copy tells

- [ ] Familiar phrase clusters and abstract nonsense
- [ ] Claims that could move to a competitor unchanged
- [ ] Repeated section scaffolding and duplicated headings
- [ ] Paragraphs with the same length and cadence
- [ ] Confident explanations with no first-hand detail
- [ ] Prose with no named buyer, object, constraint, action, or consequence

### Visual tells

- [ ] Inter used indiscriminately
- [ ] Purple-to-blue gradients
- [ ] Cards inside cards
- [ ] Gray text on colored backgrounds
- [ ] Rounded-square icon tiles above each heading
- [ ] Tiny uppercase labels
- [ ] Decorative images where the page needs product or proof

## Observations, hypotheses, and unknowns

| Observation | Hypothesis | Unknown |
| --- | --- | --- |
| | | |
| | | |
| | | |

## Three changes to make first

| Change | Done when |
| --- | --- |
| | |
| | |
| | |

## Done when

- [ ] The intended visitor can recognize their situation
- [ ] The customer result and product mechanism are understandable
- [ ] The important claims have nearby proof or a visible limit
- [ ] One main action explains and completes the next step
- [ ] The main route works on mobile and by keyboard
- [ ] Serious contrast, reflow, labeling, and overflow problems have been addressed
- [ ] The public pages are crawlable and described accurately

## Next review

**Date:**