# From an AI answer to a qualified website visit: design the handoff. - working worksheet

Reviewed alongside the Eli guide: https://hireeli.io/resources/ai-answer-to-qualified-website-visit

## Decision to make

Continue the buyer's question when an AI assistant sends a visit

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

## Buyer questions

- [ ] From an AI answer to a qualified website visit: design the handoff?
- [ ] What should a B2B startup do first to continue the buyer's question when an ai assistant sends a visit?
- [ ] Which evidence shows that continue the buyer's question when an ai assistant sends a visit is working?
- [ ] What is the most common mistake when teams try to continue the buyer's question when an ai assistant sends a visit?

## Evidence-led work plan

### 1. Why this decision appears: the visitor arrives with context

The visitor arrives with context, but a generic homepage makes them restate the problem and search for the relevant proof.

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

### 2. Match high-intent questions to focused pages that answer first, show the relevant evidence and offer one stage-appropriate continuation

Match high-intent questions to focused pages that answer first, show the relevant evidence and offer one stage-appropriate continuation.

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

### 3. Preserve the landing question and source when available, then lead with the direct answer

Preserve the landing question and source when available.

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

### 4. Measure track eligible ai referrals

Track eligible AI referrals, engaged visits, confirmed needs and qualified actions separately.

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

### 5. Do not cross this boundary: referral evidence may be incomplete and should not be treated as verified identity or recommendation intent

Referral evidence may be incomplete and should not be treated as verified identity or recommendation intent.

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

## Source ledger

- [ ] Google Search Central: optimizing for generative AI features: https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- [ ] Google Search Central: people-first content guidance: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- [ ] OpenAI: publishers and developers FAQ: https://help.openai.com/en/articles/12627856-publishers-and-developers-faq
- [ ] Eli AI Visibility Index methodology: https://hireeli.io/ai-visibility-index/methodology

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