> ## Documentation Index
> Fetch the complete documentation index at: https://docs.athenahq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Live content check (delivery verification)

> Shows whether a manually-applied Site Health page edit actually matches what's live, field by field, with an option to retry the live check or return to Page edits.

<Card title="Open in AthenaHQ" icon="arrow-up-right-from-square" href="https://app.athenahq.ai/site-health/optimizations/verification" horizontal>
  `app.athenahq.ai/site-health/optimizations/verification`
</Card>

## Purpose

When a customer manually applies an approved Site Health SEO optimization to their website, Athena schedules a live check to verify that the changes were published correctly. The Live content check page displays the results of this verification. It highlights exactly which fields match the approved draft and which ones differ, allowing the customer to correct any copy-paste mistakes in their CMS and retry the check.

## What's on the page

**Page header**
Displays the page title and a **Back to Page edits** button to return to the optimizations board.

**Live check result card**
Summarizes the overall status of the verification check.

* **Title**: Shows the current status, such as "Confirmed live", "Live content differs", "Could not check the live page", or "Waiting for the live check".
* **URL**: A clickable link to the live page on the customer's website.
* **Version info**: Displays the version and revision numbers of the draft, along with the date and time (in UTC) when the live check was completed.
* **Status description**: A brief explanation of the status. For example, if there is a mismatch, it states how many fields differ. If the check is waiting, it states when the check is scheduled.
* **Action buttons**: Options to retry the check, open the draft, or navigate back to other Site Health views.

**Field comparison cards**
Four collapsible cards that compare specific elements of the page:

* **Page title**
* **Meta description**
* **Main content**
* **Structured data**

Each card header indicates whether the field **Matches**, **Differs**, or is **Not checked**.

### Drilldowns

* **Field comparison cards**: Clicking a field card expands it to show a side-by-side comparison. The left column shows the **Approved version** (what Athena drafted), and the right column shows the **Observed live page** (what Athena found on the website). If a field has no content, it displays "Empty".

## What you can do here

* **Return to Page edits**: Click **Back to Page edits** in the top right to return to the optimizations board. If the verification data includes a URL, the board will be pre-filtered to that specific page.
* **Retry the check**: Click **Retry live check** to queue a fresh live check. This button only appears if the status is "failed" or "mismatch", and only if you have content-editing permissions. A "Live check queued" toast appears on success.
* **Open the draft**: Click **Open the page in Site Health** to jump directly to the draft review screen for this optimization run.
* **Go back**: Click **Back to source** or **Back to Site Health** to return to the referring page or the main Issues view.
* **See results**: Click the **See results** link to navigate directly to the Site Health Results view.
* **Compare differences**: Click any field card marked "Differs" to expand it and read exactly where the live website diverges from the approved draft.

## Data shown

The page displays the approved content for a specific SEO draft and compares it against the text Athena extracted from the live website during its last verification crawl.

## Common workflows

**Fixing a content mismatch**

1. You arrive on the page and see the status is "Live content differs".
2. Click the field comparison cards marked **Differs** to expand them.
3. Compare the **Approved version** text against the **Observed live page** text to see what was missed or mistyped when the changes were applied to your CMS.
4. Update your CMS to perfectly match the approved text and publish the page.
5. Click **Retry live check** to prompt Athena to crawl the page again and confirm the fix.

## Linked from / links to

* **Linked from**: The Site Health Page edits board (optimizations view) after a manual delivery is recorded and a verification event is scheduled.
* **Links to**:
  * **Back to Page edits** goes to `/site-health/optimizations`.
  * **Open the page in Site Health** goes to the draft review page (`/site-health/optimize/[runId]`).
  * **Back to Site Health** goes to the Issues view (`/site-health?view=issues`).
  * **See results** goes to the Results view (`/site-health?view=results`).
  * The live URL link opens the customer's live web page in a new browser tab.

## Common support questions

**Why does the page say "Waiting for the live check" when I already applied the changes?**
Athena schedules the first automated live check for 24 hours after you record the changes as manually applied. Until that time passes, the status remains waiting. If you haven't recorded an applied date yet, the status description will ask you to record it on the Page edits board.

**Why don't I see the "Retry live check" button?**
The retry button only appears if the check resulted in a failure or a mismatch. If the page is already "Confirmed live" or still waiting for its scheduled check, you cannot manually retry it. Additionally, you must have content-editing permissions on your account to trigger a retry.

**Does "Confirmed live" mean my SEO issues are fixed?**
Not entirely. "Confirmed live" only means that the text on your live page now perfectly matches the approved draft. To verify that the underlying SEO issue is completely resolved and impacting your score, you must run a fresh site audit. Performance results use a separate measurement window.

**What does "Could not check the live page" mean?**
This means Athena tried to visit your live URL to verify the content, but the page could not be read. This usually happens if the page is unpublished, blocked by a firewall, or returning an error code. You should check that the page is publicly accessible and then retry the live check.
