# GEO Evidence & Experiment Register

Use this working register to keep platform controls, research findings, hypotheses, observations, and business outcomes separate. Duplicate the tables for each market or experiment.

## 1. Program record

| Field | Entry |
|---|---|
| Business / property | |
| Owner | |
| Review window | |
| Priority market(s) and language(s) | |
| Priority products / services | |
| Decision date | |

## 2. Evidence-class legend

| Class | Meaning | How to use it |
|---|---|---|
| Documented control | First-party platform documentation describes the requirement, control, or report | Follow the current documentation and record the verification date |
| Published research | A study reports a finding within a disclosed benchmark or sample | Preserve the study's scope; do not turn its maximum result into a guarantee |
| Operational hypothesis | A plausible practice to test in your own environment | Define the expected outcome and stop rule before implementation |
| Observed result | A repeated measurement from your own protocol | Record conditions, variance, and downstream impact |

## 3. Prompt cohort

| ID | Exact prompt | Intent | Platform / mode | Country | Language | Session state | Competitors | Baseline date |
|---|---|---|---|---|---|---|---|---|
| P-01 | | | | | | Fresh / signed-in | | |

For each run, capture the response date, brand mention, owned citation, cited URL, prominence, factual accuracy, competing sources, and notes. Do not compare runs that silently changed prompt wording, market, language, or session state.

## 4. Crawler and delivery policy

| User agent / system | Job | Intended policy | robots.txt verified | CDN / WAF verified | Server-log evidence | Last checked |
|---|---|---|---|---|---|---|
| Googlebot | Search crawling | | | | | |
| OAI-SearchBot | ChatGPT Search crawling | | | | | |
| ChatGPT-User | User-initiated fetching | | N/A / note | | | |
| GPTBot | Potential model-training crawl | | | | | |
| PerplexityBot | Perplexity search crawling | | | | | |
| Perplexity-User | User-requested fetching | | N/A / note | | | |

## 5. Priority-page technical gate

| URL | 200 status | Canonical | Index status | Snippet eligible | Primary content in rendered HTML | Mobile usable | Owner | Fix date |
|---|---|---|---|---|---|---|---|---|
| | | | | | | | | |

## 6. Source and claim register

| Claim ID | Claim | Owning URL | Evidence / source | Source date | Scope or conditions | Review date | Status |
|---|---|---|---|---|---|---|---|
| C-01 | | | | | | | Draft / verified / revise / retire |

## 7. Entity consistency register

| Entity / fact | Canonical value | Owned locations checked | External profiles checked | Conflict found | Owner | Resolved date |
|---|---|---|---|---|---|---|
| Company name | | | | | | |
| Product / service name | | | | | | |
| Market / availability | | | | | | |
| Price / policy / contact | | | | | | |
| Named expert and role | | | | | | |

## 8. External corroboration

| Claim / topic | Relevant independent source | Why it is credible | Relationship disclosed | Status | Published URL | Date |
|---|---|---|---|---|---|---|
| | | | Yes / N/A | Planned / pitched / published | | |

## 9. Experiment definition

| Field | Entry |
|---|---|
| Experiment ID and owner | |
| Target URL(s) | |
| Evidence class | |
| Single primary change | |
| Hypothesis | |
| Baseline window | |
| Release date | |
| Prompt cohort IDs | |
| Technical recrawl / index check | |
| Primary outcome | |
| Downstream business metric | |
| Confounders | |
| Minimum observation window | |
| Scale / iterate / stop rule | |

## 10. Outcome path: baseline vs. post-change

| Stage | Definition | Baseline | Post-change | Confidence / sample note | Decision |
|---|---|---|---|---|---|
| Discovered | Page is accessible and eligible in the relevant system | | | | |
| Mentioned | Brand appears in sampled answers | | | | |
| Cited | An owned URL is linked or named as a source | | | | |
| Accurately used | The answer represents the source claim correctly | | | | |
| Visited | A measurable referral reaches the site | | | | |
| Converted | The visit contributes to a qualified outcome | | | | |

## 11. 90-day cadence

| Phase | Required output | Complete | Decision / notes |
|---|---|---|---|
| Days 1–15 | Baseline, crawler policy, technical gate, claim inventory | [ ] | |
| Days 16–45 | Priority source upgrades and entity repair | [ ] | |
| Days 46–75 | First-party evidence and credible distribution | [ ] | |
| Days 76–90 | Repeated cohort, attribution review, scale / iterate / stop decision | [ ] | |

## Final decision record

**Decision:** Scale / iterate / stop

**Evidence supporting the decision:**

**What remains uncertain:**

**Next review date and owner:**