# Event website SEO: page and evidence worksheet

Editable working copy (English). Replace prompts with confirmed information. This sheet does not promise indexing, search placement, clicks, or ticket sales.

## 1. State the visitor task

| Item | Confirmed answer | Source / approver | Last checked |
| --- | --- | --- | --- |
| Event edition and public name | [Name and edition] | [Approved program] | [Date] |
| Intended audience and format | [Who / what happens] | [Program owner] | [Date] |
| Date, time, and time zone | [Published value] | [Schedule owner] | [Date] |
| Venue / online access | [Published value] | [Venue or stream owner] | [Date] |
| Ticket or registration destination | [Exact URL and label] | [Sales owner] | [Date] |
| Help route | [Email, form, or contact page] | [Support owner] | [Date] |

Visitor questions this page must answer:

1. [Named-event question, such as: When and where is this edition?]
2. [Topic-discovery question, such as: Is this workshop for a beginner?]
3. [Action question, such as: Which ticket or form should I use?]

## 2. Map public pages to distinct questions

| Public page / exact URL | Visitor question | Approved facts source | Page owner | Next action / destination | Why a separate page? |
| --- | --- | --- | --- | --- | --- |
| [Main event page] | [What, when, where, for whom?] | [Source] | [Owner] | [Ticket URL] | Primary maintained answer |
| [Agenda, if needed] | [Which sessions and times?] | [Program] | [Owner] | [Main page or ticket] | [Distinct detail] |
| [Arrival page, if needed] | [How do I find the entrance?] | [Venue] | [Owner] | [Main page] | [Distinct detail] |

Remove rows for pages that do not answer a separate question. Do not create near-identical pages just to repeat a query phrase.

## 3. Release the visible page

| Check | Result / evidence | Fix owner | Status |
| --- | --- | --- | --- |
| Page title and first visible heading identify this event | [Copy or screenshot reference] | [Name] | [Pass / fix] |
| Summary explains format and audience | [Copy] | [Name] | [Pass / fix] |
| Date, time, zone, place and access match source | [Source link + live URL] | [Name] | [Pass / fix] |
| Main and supporting pages link to each other usefully | [Clicked links] | [Name] | [Pass / fix] |
| Images with information have useful alternatives; crucial facts are text | [Image/alt review] | [Name] | [Pass / fix] |
| Phone view exposes facts and the next action | [Device and date] | [Name] | [Pass / fix] |
| Ticket handoff lands on the intended current event | [Signed-out URL test] | [Name] | [Pass / fix] |
| Site navigation leads to this public URL | [Live route] | [Name] | [Pass / fix] |

Published URL: [ ]  Review date: [ ]  Reviewer: [ ]  Decision: [publish / fix / hold]

## 4. Record search and markup evidence

Only use controls that the site owner actually has. Search Console requires an appropriate verified property.

| Question | Observation | Evidence and date | Owner / next step |
| --- | --- | --- | --- |
| Which exact URL was inspected? | [URL] | [Search Console / browser] | [Name] |
| What indexing status did URL Inspection report? | [Reported state, not prediction] | [Date] | [Name] |
| Is public access blocked or `noindex` unintended? | [Observed result] | [Live check] | [Name] |
| Does any Event markup match visible approved facts? | [Yes / no / no access] | [Rich Results Test or site owner] | [Name] |
| Are any old campaign URLs misdirected? | [Tested URL] | [Browser] | [Name] |

An indexing request is a request for crawling, not a guarantee. A structured-data test is not a promise of a special result.

## 5. Keep a short change and observation log

| Date | Trigger / visitor problem | Approved source change | Public surfaces changed | Live path retested | Search observation | Owner / status |
| --- | --- | --- | --- | --- | --- | --- |
| [Date] | [Example: venue changed] | [Source record] | [Main page, ticket page, partner link] | [Phone and signed-out path] | [If available] | [Name / done] |
| [Date] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |

At close, note whether the edition page becomes a dated recap, a clear archive, or an intentional removal. Record the decision separately from the stable series page.