# Task: Add LGB / USA Trains / PIKO garden brand hubs

## Role
You are a SEO content strategist. 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: supporting
- Supports flagship play: Own the garden / G-scale sub-niche
- Read the parent play brief first for the full strategy frame (donor/target logic, complete page set): `prompts/plays/02-garden-hub.md`
- Affected URLs:
- https://www.legacystation.com/g-scale-trains

## Why this matters
Garden buyers search by brand (LGB, USA Trains, PIKO). Brand hub pages capture branded transactional demand and reinforce the garden pillar.

## Action
1. Validate brand search volumes (LGB, USA Trains, PIKO) in Ahrefs.
2. Confirm in-stock inventory per brand.
3. Draft brand hub briefs.

## Evidence
- Claim: The /g-scale-trains category page is the site's strongest non-branded asset, ranking for 54 keywords and ~341 visits/month, #1-2 for the garden-trains cluster. | Proof type: provider_metric | Source: https://www.legacystation.com/g-scale-trains | Observed: 54 keywords, 341 visits/mo; 'garden trains' #1 (vol 200), 'garden train sets' #1 (vol 100), 1,254 words

## 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 `Add LGB / USA Trains / PIKO garden brand hubs` 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
- Validate before building.
- 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
- Each brand hub maps to validated volume and stocked inventory.

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