# Task: Expand the FasTrack layout-plan library

## 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: Turn the guide engine into a category-ranking machine
- Read the parent play brief first for the full strategy frame (donor/target logic, complete page set): `prompts/plays/01-internal-link-engine.md`
- Affected URLs:
- https://www.legacystation.com/fasttrack-plans-and-layouts
- https://www.legacystation.com/lionel-fastrack-guide

## Why this matters
Layout-plan pages (by size, theme, train count) each rank #1-2 and are a proven, low-competition format that feeds internal links to category pages.

## Action
1. Mine layout-plan long-tail (4x8, Christmas, O27, 2-train) in Ahrefs.
2. Draft new layout pages mirroring the top performers.
3. Link each new page to relevant track/product categories.

## Evidence
- Claim: The site's informational guide/layout pages rank #1-4 and drive meaningful traffic, proving a repeatable content format. | Proof type: provider_metric | Source: https://www.legacystation.com/fasttrack-plans-and-layouts | Observed: /fasttrack-plans-and-layouts #1 (27 kw, 170 visits/mo); /lionel-fastrack-guide #4 (18 kw, 95 visits/mo); /slang/ #1-6; /blog/choosing-lionel-transformer/ #4

## Target keywords
- lionel fastrack layouts 4x8 | volume: 80 | CPC: unknown | current: 1 | target: 1 | URL: https://www.legacystation.com/fasttrack-plans-and-layouts-page2

## 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 `Expand the FasTrack layout-plan library` 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
- No publishing without approval.
- 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 new layout page targets a real long-tail term and links to >=1 product category.

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