How We Use AI to Run a 4,400-Page Editorial Engine

We manage 12+ websites and 4,400 pages with one human and one AI agent. Here's the exact system: how we use OpenClaw, Claude Opus 4.6, Google Search Console data, and Google Analytics to find opportunities, fix underperforming pages, publish news, and build interactive tools — all in a single session.

The Stack

Here's what we run:

• OpenClaw — an open-source AI agent runtime that connects Claude to our tools, files, and APIs via WhatsApp. We talk to it like a coworker. It reads files, runs scripts, deploys to Cloudflare, and manages sub-agents.
• Claude Opus 4.6 — Anthropic's most capable model. Handles strategic analysis, content creation, and code generation. Sub-agents run on Sonnet for parallel page building.
• Google Search Console API — pulls impression, click, position, and CTR data for every page and query across all our domains.
• Google Analytics 4 API — pulls session counts, bounce rates, session duration, and pages per session.
• Ahrefs — keyword research exports that feed our build queue with volume, keyword difficulty, and CPC data.
• Cloudflare Pages + Workers — hosts everything. Deploy in under 30 seconds.
• Astro — static site generator. All 4,400 pages build in ~35 seconds.

Step 1: Pull the Data

Every editorial session starts the same way. The AI agent pulls three data sources and cross-references them:

Google Search Console: What Google sees

GSC tells us which pages are getting impressions (showing up in search results) and at what position. The key insight: impressions without clicks means Google thinks our page is relevant, but searchers aren't choosing it.

We pull:

• Pages ranked by impressions (descending)
• Click-through rate (CTR) for each page
• Average position
• Query-level data: which exact searches trigger our pages

Google Analytics: What visitors actually do

GA tells us what happens after someone clicks. The critical metrics:

• Bounce rate — did they leave immediately?
• Session duration — how long did they stay?
• Pages per session — did they explore?

The pattern is clear: interactive pages retain visitors. Static data dumps don't. Buyback leaders (sortable table, search, charts) has 9% bounce. Debt-to-equity (75KB static HTML, zero JavaScript) has 100% bounce. Same data quality, completely different engagement.

Ahrefs: What to build next

Ahrefs keyword exports feed our build queue — a ranked list of keywords by a custom score combining search volume, keyword difficulty, and commercial intent. We maintain queues per domain so each site gets topically relevant content.

Step 2: Diagnose — Find the Leaks

Before building anything new, we fix what's broken. The framework:

Real example: the meta description purge

We discovered that 9 of our highest-impression pages had template meta descriptions: "Free [keyword] data and analysis. Updated regularly." These were auto-generated during the initial build and never reviewed.

The fix took 10 minutes — rewrite each description with specific data points and a compelling hook:

Real example: the null data discovery

Our cap-rates page on firemaths.info had 1,296 monthly impressions at position 11.8 (just below page 1) with zero clicks. When we inspected the page, we found every single data field for all 50 cities was null. The page had a working interactive framework — search, sort, filter — but literally no data to display. It was an empty shell that had been live for weeks.

Populating it with real data was a 2-minute sub-agent task. The page now shows cap rates from 3.8% (San Jose) to 9.2% (Detroit) across 51 US markets.

Step 3: Upgrade — Make Pages Interactive

The data consistently shows that interactive pages outperform static ones by 10x on engagement. Our best-performing page (buyback-leaders, 9% bounce) has sortable tables, search, bar charts, and sector filters. Our worst (debt-to-equity, 100% bounce) was 75KB of static HTML cards.

The upgrade playbook:

1. Add a calculator or tool — something users interact with. Our dividend aristocrats page went from a static list to having an income calculator ("pick a stock, enter investment amount, see 10-year income projection").
2. Add context visualizations — our S&P 500 P/E ratio page got a percentile gauge ("current CAPE is higher than X% of all historical readings"), decade averages, and a distribution histogram.
3. Make tables sortable and filterable — every data page should have search + column sort at minimum.
4. Add multiple view modes — our API directory got a Cards/Table toggle because developers want to scan quickly.

Step 4: Publish News That Links to Tools

This is where it comes together. Instead of treating news articles and evergreen tools as separate workstreams, every page upgrade ships with a news article.

The news article:

• Covers a timely event (market selloff, supply chain disruption, policy change)
• Uses real sources (BBC, Al Jazeera, Google Finance, official data)
• Links directly to the upgraded tools and data pages
• Provides context that makes the tools relevant right now

Example from this session:

The news article drives timely search traffic. The tools catch and retain it. The internal links pass authority. Everything reinforces everything.

Step 5: Internal Linking

With 4,400 pages, internal linking is the single highest-leverage SEO action. Google discovers and ranks pages partly based on how many internal links point to them.

After every batch of upgrades, we run an internal linking pass:

• Identify top 10 pages by traffic (GA data)
• Check which ones link to new/upgraded pages
• Add contextual "Related Tools" sections at the bottom
• Add inline links within content sections (more valuable than footer links)

In one session, we added related links from 8 high-traffic pages to our new dividend tools. This immediately helps Google discover and rank the new pages.

Step 6: Deploy and Verify

Our deploy pipeline:

1. npm run build — Astro builds all 4,400 pages in ~35 seconds
2. wrangler pages deploy — pushes to Cloudflare Pages in ~30 seconds
3. Regenerate sitemaps so Google discovers new pages
4. Verify pages return 200 status codes

Total time from code change to live: under 2 minutes.

The Parallel Workflow

OpenClaw can spawn sub-agents — separate AI instances that work in parallel. While the main agent analyzes data and makes editorial decisions, sub-agents build pages simultaneously.

A typical session flow:

Results: One Morning Session

In a single ~90-minute session, we:

The math: if fixing meta descriptions alone gets 2% CTR on existing impressions, that's ~400 new clicks per month from zero new content. Add the interactive upgrades reducing bounce rates, the new tools attracting new queries, and the news articles driving timely traffic — and a single morning's work compounds for months.

The Framework (TL;DR)

1. Pull data — GSC impressions/clicks/position + GA bounce/duration + Ahrefs keywords
2. Fix the leaks — meta descriptions, broken pages, null data, non-interactive tools
3. Upgrade top pages — add calculators, sortable tables, visualizations
4. Publish news — timely articles that link to upgraded tools
5. Wire the network — internal links from high-traffic pages to new/upgraded ones
6. Deploy + verify — build, ship, regenerate sitemaps
7. Repeat — next session, pull fresh data and start again

The key insight: the traffic is already there. 20,000+ monthly impressions across our network. The bottleneck was never "build more pages" — it was "make existing pages worth clicking on and staying at." Fix the leaks before turning on more faucets.

Tools mentioned: OpenClaw (open-source AI agent runtime), Claude Opus 4.6 (Anthropic), Google Search Console, Google Analytics 4, Ahrefs, Cloudflare Pages, Astro. Our sites: westmountfundamentals.com, firemaths.info, siliconbased.dev, and gab.ae.