Scaling Content: From 45 Pages to 1,000

On this page

• Stage 1: Launch (1-50 Pages)
• AutoFix at Stage 1
• Stage 2: First Data (50-100 Pages, Month 2-3)
• The First Overlap
• Stage 3: Growth (100-200 Pages, Month 4-6)
• AutoFix at 150 Pages
• CompareStack at 200 Pages
• Stage 4: Scale (200-500 Pages, Month 7-9)
• The Resume Pattern
• Newsweek Reports
• Stage 5: Maturity (500-1,000 Pages, Month 10-12)
• Cost at Scale
• What Changes at Each Stage

Content sites follow a predictable growth curve. Each stage introduces problems the previous stage did not have. Wire's commands map directly to these stages. You use different commands as your site grows.

This guide follows two sites through their first year: AutoFix München (45 to 200 pages, local service business) and CompareStack (200 to 1,000 pages, SaaS comparison site). Both are fictional but based on real growth patterns.

Stage 1: Launch (1-50 Pages)

AutoFix launches with 45 pages: 15 service pages (bremsen, oelwechsel, inspektion), 12 location pages (schwabing, pasing, sendling), and 18 blog posts.

Problems at this stage:

• Pages are thin (200-400 words, written quickly to launch)
• No search data yet (needs 2-4 weeks to populate)
• Internal linking is sparse (pages do not reference each other)
• No styleguide (Wire uses the built-in defaults)

What to run:

python -m wire.build                    # Build and verify structure
python -m wire.chief audit              # Baseline health check
python -m wire.content create services/zahnriemen   # Add missing service pages

Token usage: Minimal per page created, covered by your AI subscription. See pricing.

What NOT to run: data, reword, deduplicate, enrich. These need search data that does not exist yet. Running them produces "no search data" warnings and wastes time.

AutoFix at Stage 1

The audit shows mostly structural issues:

HEALTH: services (15 pages)
  - No search data
  + No dead pages
  + Titles OK
  + Descriptions OK
  - 8 thin page(s) (< 200 words)
  - 5 underlinked page(s)

The fix is content, not optimization. Write better pages. Expand thin ones. Add internal links manually or wait for Stage 2 when crosslink becomes useful.

Stage 2: First Data (50-100 Pages, Month 2-3)

Google has indexed AutoFix. Search data shows results for 30 of the 45 original pages. 15 pages get zero impressions.

Problems at this stage:

• First keyword overlaps appear (bremsen-reparatur and bremsen-wechsel share 5 keywords)
• Some pages rank on page 2 for valuable keywords
• Blog posts cannibalize service pages (a blog post about "Bremsen quietschen" outranks the service page)
• Location pages are thin and identical in structure

What to run:

python -m wire.chief data               # Pull search metrics
python -m wire.chief audit services     # Full SEO analysis
python -m wire.chief deduplicate services    # Merge/differentiate overlapping pages
python -m wire.chief enrich services    # Improve pages with search data

Token usage: data and audit are free. deduplicate and enrich use minimal AI tokens per page.

The First Overlap

The audit reveals:

ACTION: services
  Merge (hard overlap, ratio > 0.4):
    bremsen-reparatur + bremsen-wechsel
    4 shared keywords, ratio 0.80, bremsen-reparatur gets 85%

This is classic keyword cannibalization. Two pages about brakes split Google's attention. Wire merges the weaker page into the stronger one, archives the donor, and creates a redirect. One strong page replaces two weak ones.

Before merge: bremsen-reparatur ranks position 14, bremsen-wechsel ranks position 18. Neither page 1.

After merge: the combined page has more content, more keywords, and no internal competition. Typical result: position moves from 14 to 7-9 within 4-6 weeks.

Stage 3: Growth (100-200 Pages, Month 4-6)

AutoFix expanded from services into blog content. CompareStack has reached 200 vendor profiles.

Problems at this stage:

• Cross-topic cannibalization (blog posts compete with service pages)
• News staleness (vendor pages reference year-old product updates)
• Source concentration (5 vendor pages cite only ADAC)
• Content gaps appear (search data shows demand for "TÜV Vorbereitung München" but no page exists)

What to run:

python -m wire.chief audit              # Cross-topic audit (no topic arg = all topics)
python -m wire.chief news services      # Gather fresh news for service pages
python -m wire.chief refine services    # Integrate news into pages
python -m wire.chief crosslink services # Add internal links to underlinked pages
python -m wire.chief sanitize           # Fix any broken links

Token usage: news, refine, and crosslink each use minimal AI tokens per page.

AutoFix at 150 Pages

Monthly costs stabilize:

Data, audit, and sanitize are free. The monthly token usage for a 150-page site is minimal, covered by your AI subscription. See pricing.

CompareStack at 200 Pages

CompareStack hits different problems at the same page count. With 200 vendor profiles, keyword overlap is everywhere:

HEALTH: vendors (200 pages)
  + Search data loaded (12,400 keywords)
  - Cannibalization: 47 overlap pairs (3+ shared keywords)
  - 12 dead page(s) below threshold
  - 8 pages with source concentration

47 overlap pairs means 47 pairs of pages fighting each other for the same keywords. Wire classifies each:

• 8 hard overlaps (merge the weaker page)
• 23 soft overlaps (differentiate both pages)
• 16 minor overlaps (report only, no action)

Running deduplicate resolves the 31 actionable pairs: 8 merges and 23 differentiations, all with minimal token usage. A one-time cleanup that would take a human editor weeks.

Stage 4: Scale (200-500 Pages, Month 7-9)

CompareStack adds comparisons. Every vendor pair generates a comparison page. 200 vendors produce up to 19,900 possible comparisons, but only ~80 have search demand.

Problems at this stage:

• Comparison pages cannibalize vendor pages (the "Acme vs Rossum" comparison steals traffic from both vendor pages)
• The batch pipeline matters now (running commands one page at a time is too slow)
• Resume becomes essential (a 200-page enrich run takes 2 hours; interruptions happen)
• Newsweek reports become valuable (weekly market intelligence across all vendors)

What to run:

python -m wire.chief enrich vendors --resume    # Resume interrupted run
python -m wire.chief newsweek --from 2026-03-03 --to 2026-03-10
python -m wire.chief reword vendors             # Tiered: top 20% full SEO, next 30% light

The Resume Pattern

At scale, batch commands run for hours. The --resume flag tracks progress in .wire/progress-{command}-{topic}.json:

# Start enrich on 200 vendor pages
python -m wire.chief enrich vendors
# ... processes 87 pages, then your laptop sleeps

# Resume from page 88
python -m wire.chief enrich vendors --resume

Progress files are cleaned up on successful completion. If a run crashes, delete the progress file to start fresh, or use --resume to continue.

Newsweek Reports

With 200+ vendor pages, Wire has enough news to produce weekly market intelligence reports:

python -m wire.chief newsweek --from 2026-03-03 --to 2026-03-10

This runs a three-phase pipeline: extract news from all topics, synthesize into a thematic report, and optionally review for quality. Token usage: moderate per full report. Output: a publication-ready markdown page at docs/news/2026-03-10-news.md.

Stage 5: Maturity (500-1,000 Pages, Month 10-12)

CompareStack at 800 pages. AutoFix at 200 pages with strong local rankings.

Problems at this stage:

• Dead pages accumulate (vendor companies shut down, products are discontinued)
• The audit becomes the primary workflow tool (not individual commands)
• Content gaps drive new page creation (search data reveals keywords nobody owns)
• Cost optimization matters (not every page deserves a full enrich pass)

The Monthly Workflow at Scale:

# Week 1: Data + Audit
python -m wire.chief data --force
python -m wire.chief audit

# Week 2: Fix problems the audit found
python -m wire.chief deduplicate
python -m wire.chief sanitize

# Week 3: Improve content
python -m wire.chief enrich vendors --resume
python -m wire.chief enrich guides --resume

# Week 4: News + Report
python -m wire.chief news vendors
python -m wire.chief refine vendors
python -m wire.chief newsweek --from ... --to ...

Cost at Scale

Wire's token usage scales linearly with page count, but stays minimal per page for every command. Compare to manual alternatives: a content editor costs $4,000-8,000/month. A junior SEO analyst costs $3,000-5,000/month. Wire at 1,000 pages runs on your AI subscription and never calls in sick. See pricing.

Wire's analysis, audit, build, and lint commands use zero AI tokens. Only content generation calls Claude.

What Changes at Each Stage

Wire's commands are designed for this progression. You do not need all of them on Day 1. Use what your current stage requires and ignore the rest until the problems appear.

See the Guides overview for all Wire documentation. Related: SEO reference, workflow guide. Source: Zyppy title tag study.