# Task: Connect Google Search Console and rerun the GSC lane

## Role
You are a SEO operator setting up audit evidence. Produce the deliverable below for a human reviewer. Do not publish or change production systems.

## Target
- Site: Legacy Station
- Primary URL: https://www.legacystation.com
- Depth: standard
- Queue group: validation
- Supports flagship play: not grouped under a flagship play
- Affected URLs:
- https://www.legacystation.com

## Why this matters
First-party click/query/CTR data would confirm the near-win sizing and surface decayed pages the third-party tools miss.

## Action
1. Have the property owner grant GSC access to www.legacystation.com.
2. Rerun the GSC lane.
3. Reconcile near-win sizing against first-party clicks/CTR.

## Evidence
- Claim: Google Search Console is not connected for this domain, so first-party click/query/CTR data is unavailable. | Proof type: missing_dependency | Source: https://www.legacystation.com | Observed: GSC list_properties returns only sc-domain:authorityhacker.com

## Target keywords
- No keyword-level table was supplied; do not invent volume, CPC, or rank movement.

## Expected outcome
Directional; no traffic value is claimed.

## Supporting tasks
- This prompt is the primary work packet for the task.

## Deliverable
Produce a review-ready work packet for `Connect Google Search Console and rerun the GSC lane` with the proposed fix, affected URLs, owner notes, QA steps, and before/after evidence to collect. Do not publish changes or touch production systems.

## Available local data
- data/audit.json - full v4 audit contract, evidence pack, value bands, and validation results
- operator-brief.md - provider provenance, confidence gates, and budget notes
- report.md - canonical text strategy context; final report.html is model-authored only

## Inputs to gather first
- Confirm the local output folder contains the files listed above.
- If a required source is missing, record the blocker and continue with a bounded draft instead of inventing evidence.
- If implementation requires CMS, repository, analytics, GSC, or deployment access, stop at a review-ready brief and list the exact access needed.

## Constraints / guardrails
- Requires owner action; not connectable by the audit.
- Do not publish, send, delete, or mutate production systems.
- Do not claim revenue, ROI, pipeline, lead value, guaranteed AI rankings, or llms.txt ranking impact.
- Treat CPC-proxy value bands as directional SEO prioritization evidence, not business revenue.

## Acceptance criteria
- GSC connected; GSC lane rerun; sizing reconciled.

## Definition of done
- The first section of your answer states the concrete deliverable you produced.
- Every claim is either backed by the evidence above or labeled as an assumption to validate.
- The next operator can start work without resolving audit evidence IDs.
- No external write, publish, send, delete, deployment, or paid provider action has been performed.