DEV Community: Apex Stack

Most Ad Audits Miss 5 of 7 Critical Dimensions. Here's the Framework I Built to Fix That.

Apex Stack — Tue, 07 Apr 2026 13:15:35 +0000

Most ad campaign audits are shallow. They check ROAS, maybe creative performance, and call it a day.

But after auditing dozens of campaigns across Meta, Google, TikTok, and LinkedIn, I noticed the same pattern: the problems that bleed the most budget are hiding in dimensions nobody checks. Audience overlap silently inflates CPMs. Bid strategies contradict campaign objectives. Conversion tracking gaps make every other metric unreliable.

So I built a structured 7-dimension audit framework, packaged it as a Claude Skill, and started using it on every campaign I touch. Here's how it works — and why most audits only scratch the surface.

The Problem: Partial Audits Lead to Partial Results

A typical ad audit looks like this: export your Meta Ads Manager report, sort by ROAS, kill the losers, scale the winners. Maybe check frequency if you're thorough.

That approach misses five critical dimensions that often have more impact on profitability than ROAS alone:

Audience overlap — Are your ad sets bidding against each other? I've seen accounts where 40%+ of audiences overlap, artificially inflating CPMs by 15-30%.
Conversion tracking integrity — If your Meta Pixel isn't paired with Conversions API (CAPI), you're likely underreporting conversions by 20-30% post-iOS 14.5. Every decision built on that data is compromised.
Bid strategy alignment — A cost-cap bid on a campaign getting 15 conversions/week will spend erratically. The algorithm needs 50+ weekly conversions to optimize properly.
Landing page experience — A 5-second load time on mobile kills conversion rates, but the ad platform doesn't flag this. Your "low-performing" ad might actually have a landing page problem.
Budget allocation efficiency — Equal budget across unequal performers is the most common waste pattern. Marginal ROAS analysis often reveals 20-30% of spend is better allocated elsewhere.

The 7-Dimension Campaign Health Framework

After systematizing audits across different platforms and verticals, I settled on 7 dimensions that together give a complete picture of campaign health. Each is scored 1-10, giving a total health score out of 70.

Dimension 1: Creative Performance & Fatigue
CTR trends over time, frequency thresholds, creative variant count, hook rates for video. The key insight: frequency above 3.0 almost always correlates with declining CTR. Most advertisers wait until frequency hits 5.0+ before refreshing — by then, you've wasted 2-3 weeks of budget on exhausted creatives.

Dimension 2: Audience Quality & Overlap
Audience definition mapping, overlap estimation between ad sets, conversion rates by segment. The "overlap tax" — wasted spend from self-competition — is invisible in standard reporting. I've calculated it at 10-25% of total spend in poorly structured accounts.

Dimension 3: Budget Allocation & Pacing
Marginal ROAS analysis, CBO vs. ABO appropriateness, dayparting opportunities, budget headroom testing. The question isn't "which campaign has the best ROAS?" — it's "where does the next dollar generate the most return?"

Dimension 4: Conversion Tracking & Attribution
Pixel + CAPI implementation, Event Match Quality scores, UTM consistency, cross-platform attribution conflicts. This dimension is the foundation — if your measurement is broken, every other optimization is built on sand.

Dimension 5: Bid Strategy & Campaign Structure
Bid strategy matching to objectives, campaign consolidation score, Learning Limited status, ad set feeding levels. Meta's algorithm needs 50+ conversions per ad set per week to optimize properly. Most accounts have fragmented structures with ad sets getting 5-10 conversions weekly.

Dimension 6: Landing Page & Post-Click Experience
Load time, message match between ad and page, mobile optimization, CTA clarity, form friction. This is where ad audits traditionally stop — but the post-click experience determines whether clicks become conversions.

Dimension 7: ROAS & Profitability Analysis
Blended vs. marginal ROAS, break-even calculation, new vs. returning customer splits, contribution margin per campaign. The final dimension ties everything together — are you actually making money, or is retargeting revenue masking a prospecting problem?

What a Full Audit Output Looks Like

Here's the structure the skill generates from your campaign data:

## Campaign Audit: [Brand Name]
### Overall Score: 48/70 (69%) — Needs Attention

| Dimension                        | Score | Priority | Top Action                           |
|----------------------------------|-------|----------|--------------------------------------|
| Creative Performance & Fatigue   | 6/10  | 🟡       | Refresh 3 creatives above freq 4.0  |
| Audience Quality & Overlap       | 5/10  | 🔴       | Merge 2 overlapping ad sets (38%)   |
| Budget Allocation & Pacing       | 7/10  | 🟡       | Shift $200/day from Campaign C → A  |
| Conversion Tracking              | 8/10  | 🟢       | Add CAPI for Purchase event         |
| Bid Strategy & Structure         | 6/10  | 🟡       | Consolidate ad sets in Learning Ltd |
| Landing Page Experience          | 4/10  | 🔴       | Fix mobile load time (4.2s → <3s)   |
| ROAS & Profitability             | 7/10  | 🟡       | Separate new vs returning reporting |

### Top 5 Priority Actions
1. Fix landing page mobile speed → Est. +18% conversion rate
2. Merge overlapping audiences → Est. -22% CPM savings
3. Refresh exhausted creatives → Est. +12% CTR recovery
4. Consolidate underfed ad sets → Exit Learning Limited
5. Implement CAPI for Purchase → +15% conversion attribution

The skill generates this from raw campaign exports — CSV data, pasted tables, or even a manual description of your setup. No API keys needed. No subscriptions.

The Benchmark Problem (and How I Solved It)

One of the biggest challenges in ad auditing is knowing what "good" looks like. A 1.2% CTR on Meta Feed might be excellent for B2B finance ($3.89 avg CPC) but mediocre for eCommerce ($1.12 avg CPC).

The paid version includes industry benchmarks compiled from WordStream, Databox, Revealbot, and Varos data for 2025-2026. Here's a sample:

Platform	Metric	Average	Good	Excellent
Meta (Feed)	CTR	0.90%	1.5%+	2.5%+
Meta	CPC	$1.72	<$1.20	<$0.70
Google Search	CTR	3.17%	5%+	8%+
TikTok	Hook Rate (3s)	30%	45%+	60%+
LinkedIn	CPC	$5.26	<$4.00	<$2.50

Without benchmarks, you're scoring in a vacuum. A 2.0x ROAS sounds decent until you realize your break-even ROAS at 50% gross margin is... 2.0x. You're not making money — you're treading water.

The break-even formula: Break-Even ROAS = 1 / Gross Margin %. At 70% margin, you break even at 1.43x. At 30% margin, you need 3.33x just to cover COGS. Most advertisers I've worked with don't have this number memorized — and they should.

Why a Claude Skill Instead of a SaaS Tool?

The existing landscape for ad auditing tools is dominated by monthly SaaS subscriptions. Madgicx runs $44-166/month. Revealbot is $99+/month. Adzooma has a free tier but upsells aggressively.

These tools are powerful, but they're overkill for many advertisers who need periodic audits, not always-on monitoring. A Claude Skill gives you the audit framework, the benchmarks, and the structured analysis — for a one-time $19 purchase. Run it whenever you need it. No recurring fees.

The skill also covers what SaaS tools often skip: qualitative assessment of campaign structure, bid strategy alignment, and creative pipeline health. These require judgment, not just data aggregation.

Specialized Modules Beyond the Core Audit

The full skill includes six focused modules that go deeper on specific problems:

Creative Fatigue Detector — Feed it time-series creative data and it classifies each ad into lifecycle stages (Fresh → Mature → Fatiguing → Exhausted) with specific refresh recommendations.

Audience Overlap Analyzer — Maps audience definitions across ad sets, estimates overlap percentages, and calculates the "overlap tax" in wasted spend.

Budget Allocation Optimizer — Calculates marginal ROAS per campaign to find the optimal spend distribution with expected impact projections.

Scaling Readiness Assessment — Evaluates six criteria (ROAS stability, CPA variance, Learning Limited status, frequency, conversion volume, creative freshness) to determine which campaigns can absorb more budget safely.

Weekly Performance Brief — Generates a stakeholder-ready report with WoW comparisons. Saves 30-60 minutes of manual reporting every week.

Try It: Free Lite Version Available

The lite version covers 3 of 7 dimensions (Creative Fatigue, Budget Allocation, ROAS & Profitability) — enough to find the biggest problems in most accounts.

Free lite version: Ad Performance Auditor Lite on GitHub

Full 7-dimension version ($19): Ad Performance Auditor on Gumroad

If you're building a financial data product and want to see programmatic SEO at scale, check out how I'm analyzing stock performance data across 8,000+ tickers — the same data-driven methodology applies to ad campaign analysis.

What's Next

The Ad Performance Auditor pairs well with two other tools in the Apex Stack lineup:

Landing Page Copywriter & CRO Auditor — Ads drive the traffic, but landing pages convert it. This skill handles Dimension 6 (post-click experience) in depth.
Content Pipeline Builder — If you're running content-driven acquisition campaigns alongside paid, this keeps your organic funnel organized.

Performance marketing isn't just about spending more on what works. It's about systematically finding and fixing the leaks across all seven dimensions — creative, audience, budget, tracking, structure, post-click, and profitability.

The framework is public. The benchmarks are in the skill. The question is whether you'll keep running partial audits or start catching the problems hiding in the dimensions nobody checks.

Built by Apex Stack — tools and frameworks for builders who ship.

My Site Has 8,000 Pages and Zero Real Backlinks. Here's the Claude Skill I Built to Fix That.

Apex Stack — Tue, 24 Mar 2026 13:12:18 +0000

My Site Has 8,000 Pages and Zero Real Backlinks. Here's the Claude Skill I Built to Fix That.

Eight thousand pages. Twelve languages. Two and a half years of data. And Google has indexed exactly 1,335 of them.

I spent weeks debugging the problem — thin content, crawl budget, hreflang issues. Fixed them all. Then Bing Webmaster Tools told me the real answer in three words: not enough inbound links.

No backlinks. Zero. Not one domain pointing at StockVS with any authority. Google doesn't trust a site nobody else trusts. It's that simple, and that brutal.

The fix is obvious: build backlinks. The execution is where everyone stalls.

Why Link Building Dies on the To-Do List

I know the playbook. Find guest post opportunities. Research resource pages. Spot broken links. Draft personalized outreach. Follow up. Repeat.

I also know why it never gets done.

To find 10 good link-building targets, you need to:

Google "write for us" + your niche across 20 variations
Check each site's DA, traffic, and editorial quality
Confirm they're still accepting submissions (half these pages are dead)
Find the right contact — editor email, submission form, Twitter DM
Write a personalized pitch that doesn't sound like every other cold email they ignore
Do this for 10 targets minimum before you see any response

That's 4–6 hours of manual work for a pipeline that may produce one accepted pitch. Most people do it once, get discouraged, and go back to writing more content that still won't rank.

I did it too. I set up a scheduled task that ran twice a week to research targets and draft pitches. It worked — I've now got 27 targets identified and several pitches ready to send. But it took weeks to tune, and the logic was buried in a custom agent prompt that nobody else could reuse.

So I packaged it.

What the Backlink Prospector & Outreach Drafter Does

The Backlink Prospector & Outreach Drafter is a Claude Skill that turns the entire link-building research-and-outreach workflow into a 10-minute session instead of a 4-hour grind.

Here's what it actually does when you run it:

1. Niche-Targeted Opportunity Research

You give it your domain, your niche, and your target audience. It runs structured searches across the high-value opportunity types that actually move the needle:

Guest post targets — blogs and publications accepting contributor content in your space
Resource page links — curated lists that link to tools, guides, and data sites like yours
Broken link reclamation — pages linking to dead content you could replace
Directory submissions — niche and general-purpose directories with real DA

For each target it finds, it evaluates:

Domain authority / trust signals
Whether submissions are currently open (not just a zombie "write for us" page)
The right contact method (form, email, Twitter — whatever's live)
Whether your content genuinely fits their audience

You get a prioritized list, not a dump of 50 targets you'd need to manually vet.

2. Personalized Outreach Drafts — Not Templates

This is the part that usually takes the most time. Generic cold pitches go straight to the trash. The skill drafts outreach that's specific to each target:

References a recent article or topic they published (shows you actually read the site)
Proposes a specific angle that fits their audience — not just "I'd love to write for you"
Matches the tone of the publication (technical blogs get technical pitches; indie hacker communities get builder-to-builder framing)
Includes your credentials in context — what makes you qualified to write this piece for their audience

Here's a real example from my StockVS outreach campaign. Instead of sending:

"Hi, I'd love to contribute a guest post about SEO to your blog..."

The skill drafted something like:

"Hi — I noticed your recent piece on programmatic content strategies. I'm building StockVS, an 8,000-page stock data platform in 12 languages, and I've been documenting the indexing and crawl budget challenges at scale. Happy to write a detailed piece on multilingual hreflang implementation for large sites — it's a gap in your existing content and something your readers building content sites would find immediately useful."

The second pitch gets responses. The first one doesn't.

3. A Tracker You'll Actually Use

Every session outputs a clean prospect tracker — status (researched / pitched / accepted / published), DA, contact info, angle proposed, and a follow-up date. It appends to a running outreach file so you never lose track of where each pitch stands.

Real Numbers From My StockVS Campaign

Since I've been running the underlying workflow for a few weeks, here's what the numbers actually look like:

27 targets identified across guest posts, resource pages, and directories
5 pitches submitted (freeCodeCamp, SitePoint, GrowthHackers, Envato Tuts+, Smashing Magazine)
6 outreach drafts ready to send
1 HackerNoon article drafted (DA 82 — with direct deep-links to StockVS pages)
Time per research session: ~15 minutes with the skill vs. 3–4 hours manually

Zero accepted links yet — link building is a long game and most pipelines take 4–6 weeks to produce results. But the pipeline is built. Without the skill, I'd still be on target #3.

Who This Is For

If any of these describe you, this skill will save you real hours:

Indie site builders — you have content, you need authority, you hate cold outreach
SEO professionals — you're doing this for clients and need to 10x your prospecting volume
Solopreneurs — you know link building matters but it always falls to the bottom of the list
Small agencies — you can't justify $99/mo for Ahrefs just for prospecting; this does the research layer for $19 one-time

The skill works best for content sites, SaaS tools, developer tools, and any niche where guest posts and resource pages are the primary link-building vector.

What You Get

Paid version ($19):

Full opportunity research across all 4 target types (guest posts, resource pages, broken links, directories)
Personalized pitch drafts with site-specific research baked in
Prioritized prospect scoring (DA, fit, effort-to-reward)
Running outreach tracker with follow-up dates
Pitch templates for cold email, Twitter DM, and web forms

Free lite version (GitHub):

Guest post prospecting only (1 of 4 target types)
Basic outreach template (not personalized)
Good for testing the workflow before committing

The Math

A single accepted guest post on a DA 70+ site can move your domain rating by 3–5 points. A few of those and Google starts trusting your site enough to crawl deeper. With 8,000 pages sitting in "Discovered - not indexed," that crawl trust is the only thing standing between me and actual search traffic.

The skill doesn't guarantee placements — nothing does. But it removes the friction that makes link building the task that never gets started.

Get the full version: apexstack.gumroad.com/l/backlink-prospector — $19, one-time

Try the free lite first: github.com/apex-stack-ai/backlink-prospector-lite

Building StockVS in public — follow along on Dev.to for weekly updates on what's working and what isn't.

Google Isn't the Only Search Engine That Matters Anymore. Here's How I Optimize for All of Them.

Apex Stack — Fri, 20 Mar 2026 13:12:46 +0000

Last month, I checked where my site's traffic was actually coming from. Google Search? Sure — a few clicks. But here's what caught my attention: people were finding my pages through Perplexity, ChatGPT Browse, and Bing Copilot. Not by ranking in blue links — by being cited in AI-generated answers.

The shift hit me hard. I'd spent weeks optimizing title tags, meta descriptions, and keyword density. Classic SEO. But the game has changed. AI search engines don't show you a list of 10 links. They synthesize an answer and cite their sources. If your content isn't structured for citation, you're invisible in the fastest-growing search channel.

The Problem: Traditional SEO Doesn't Get You Cited

Here's what I mean by "the new invisible." I run StockVS, a financial data platform with 8,000+ stock analysis pages across 12 languages. Google has indexed about 1,580 of them. Impressions are slowly climbing. Classic SEO is working — slowly.

But AI search engines play by different rules. When someone asks Perplexity "What is AAPL's dividend yield?" or Bing Copilot "Compare tech sector stocks," these engines don't just rank pages. They extract specific facts, quote sentences, and cite sources. If your content has the answer buried in paragraph 14 of a wall of text, the AI skips you entirely.

I tested this with my own pages. I asked Perplexity about stocks I knew I had detailed analysis for. Result? Not cited. The data was there, but it was wrapped in narrative paragraphs that no AI engine would bother to extract.

Traditional SEO tools couldn't help here. Ahrefs tells me about backlinks. Semrush shows keyword rankings. Neither of them can tell me whether my content is citable by an AI engine. That's a completely different optimization problem.

What Actually Makes Content AI-Citable

After weeks of research and hands-on testing across my 8,000+ pages, I identified 8 specific dimensions that determine whether AI search engines will cite your content:

Direct Answer Density — How many standalone, quotable facts exist per section? AI engines extract concise statements, not paragraphs.
Structured Data Signals — Schema markup (JSON-LD), heading hierarchy, semantic HTML. AI crawlers rely on these to understand what your page is about.
Source Authority Signals — Author credentials, outbound links to authoritative sources, editorial policies. The E-E-A-T dimension, but for machines.
Query-Intent Alignment — Does your first paragraph answer the query? AI engines check the first 100 words before deciding to cite you.
Freshness & Temporal Signals — dateModified in schema, "Last updated" on the page, current-year references. AI engines weight recency heavily.
Multimodal Richness — Tables, charts, comparison data with proper alt text. AI engines increasingly process structured visuals.
Semantic Depth — Topical coverage completeness. Does your page cover all subtopics an expert would expect?
Competitive Citation Position — Are competitors already being cited for your target queries? What are they doing that you're not?

I turned this framework into a scoring system: each dimension gets a 1-10 score, and the total tells you how AI-citable your content is. Below 40/80? Your content is essentially invisible to AI search. Above 65? You're in strong citation territory.

How the GEO Optimizer Works in Practice

Let me show you what this looks like on a real page. I ran the audit on my stock analysis page for AAPL (stockvs.com/en/stock/aapl):

GEO Audit Results: stockvs.com/en/stock/aapl
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Direct Answer Density:    7/10  ✅ Strong — financial data is naturally factual
Structured Data Signals:  8/10  ✅ JSON-LD schema present, good heading hierarchy
Source Authority:         4/10  ⚠️ No author byline, few outbound links
Query-Intent Alignment:   6/10  ⚠️ Answer not in first paragraph
Freshness Signals:        8/10  ✅ dateModified present, data refreshed weekly
Multimodal Richness:      7/10  ✅ Tables for financials, comparison data
Semantic Depth:           5/10  ⚠️ Missing analyst ratings, earnings timeline
Competitive Position:     3/10  ❌ Not cited yet — competitors dominating
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TOTAL: 48/80 — Moderate citability. Key gaps: authority + competitive.

The audit immediately flagged what I'd been missing. My data was accurate and fresh, but I had no authority signals (no author bio, no editorial policy) and my content didn't lead with the answer. A human scanning the page could find what they needed. An AI engine extracting quotes? It was bouncing.

The skill then generates specific rewrites. For example, it took my opening paragraph:

Before: "Apple Inc. (AAPL) is a technology company headquartered in Cupertino, California. The company designs, manufactures, and markets consumer electronics..."

And produced:

After: "Apple (AAPL) trades at $198.42 with a market cap of $3.04T as of March 2026. The stock's dividend yield is 0.49% ($0.96/share annually), and its trailing P/E ratio is 32.7. AAPL is the largest holding in the Technology sector, representing 7.2% of the S&P 500."

The second version is packed with extractable facts. Every sentence can stand alone as an AI answer. That's what Perplexity and ChatGPT Browse want to cite.

Beyond content rewrites, the skill generates schema templates tailored to your page type — FAQPage markup for question-based content, HowTo schemas for guides, and proper Article schemas with dateModified that AI crawlers prioritize when deciding freshness.

The Results on My Own Site

I applied GEO optimization to 50 of my highest-impression stock pages. Here's what changed:

Direct Answer Density went from an average of 4.2/10 to 7.8/10 after restructuring content with facts-first paragraphs
Schema scores improved across the board after adding FAQPage markup and dateModified to every page
Query-Intent Alignment jumped when I added "Key Facts" boxes and TL;DR sections at the top of each page

The checklist approach is what makes it repeatable. Before publishing any page now, I run through the GEO quick reference: first paragraph answers the primary query, every statistic has a date, FAQ section at the bottom, schema markup present, outbound links to authoritative sources. It takes 10 minutes per page instead of hoping AI engines notice you.

I'm also using it to monitor which AI crawlers are hitting my pages — the skill includes a reference table of all major AI engine user agents (PerplexityBot, ChatGPT-User, ClaudeBot, Bingbot) so you know who's actually crawling your content.

Who This Is For

If you're running a content site, a SaaS marketing blog, an affiliate site, or any web property that depends on search traffic — GEO is no longer optional. AI search is already pulling traffic from traditional results, and it's accelerating.

The GEO Optimizer is especially useful if you're doing programmatic SEO (hundreds or thousands of similar pages) because you can audit one page template and apply the fixes across your entire site.

Try the free version first: The lite edition runs the 8-dimension audit and gives you a citability score. It shows you exactly where your content falls short.

👉 Get the free lite version on GitHub

Want the full toolkit? The paid version ($19) includes the content rewriter, schema template generator, competitive GEO analysis, and the monthly monitoring checklist — everything you need to systematically optimize your entire site for AI search.

👉 Get GEO Optimizer on Gumroad — $19

I'm building a portfolio of online businesses and sharing everything I learn along the way. Follow me for more on programmatic SEO, AI automation, and building in public.

Stop Checking 5 Dashboards Every Morning. I Built an AI Agent That Does It for Me.

Apex Stack — Tue, 17 Mar 2026 13:12:30 +0000

Every morning, my routine looked like this: open Google Search Console, check indexing numbers, switch to Google Analytics, pull session data, hop to Gumroad for sales metrics, check Dev.to stats for article performance, then Yandex Webmaster for international crawl data. Five tabs, five logins, forty-five minutes — before I’d written a single line of code or published anything.

I’m building stockvs.com, a programmatic SEO site serving stock analysis across 8,000+ tickers in 12 languages. I also sell Claude Skills on Gumroad. Between the two properties, the number of metrics I need to track every day was eating my entire morning.

So I built an AI agent to do it for me.

The Real Cost of Dashboard Hopping

If you’re running even one side project, you probably know the drill. Google Search Console takes 2-3 minutes to load and navigate. Google Analytics has a new UI every quarter that moves everything around. Gumroad’s analytics are behind a few clicks. And if you’re cross-posting content to Dev.to, Medium, and Hashnode, that’s three more dashboards to check.

Here’s what it actually costs:

45 minutes per day on metric checking alone (not acting on the data — just collecting it)
Context switching tax — by the time you’ve checked everything, you’ve lost your focus for deep work
Decision paralysis — you see 15 metrics but don’t know which one matters today
Missed patterns — you check each dashboard in isolation, so you never spot cross-platform trends

For solopreneurs and small teams, this is death by a thousand tabs. You built a product to escape the 9-5, and now you spend your mornings doing data entry.

What If Your AI Assistant Already Knew the Numbers?

I wanted something dead simple: tell Claude “morning briefing” and get back a consolidated view of every property, every channel, every metric that matters — with the top 3 things I should actually do today.

That’s what Revenue Agent Pro does. It’s a Claude Skill that turns your Claude session into a daily business operations assistant. Instead of you going to the data, the data comes to you.

Here’s what a daily briefing looks like:

# Daily Growth Briefing — March 17, 2026

## Priority Actions Today
1. Fix sectors 403 error on DO Spaces — blocking Google from
   indexing sector hub pages (est. impact: +200 indexed pages)
2. Publish cross-post of Article 7 to remaining platforms —
   content is written, just needs distribution
3. Check Gumroad conversion funnel — 7 articles live with CTAs
   but 0 store visits, diagnose the CTA placement

## Metrics Snapshot
| Property      | Yesterday | 7-Day Avg | Trend |
|---------------|-----------|-----------|-------|
| StockVS (GSC) | 36 imp    | 5.1/day   | up    |
| Gumroad       | 0 views   | 0/day     | flat  |
| Dev.to        | ~70 views | ~10/day   | up    |

## Revenue Progress
- MTD: $0 / $200 target (0%)
- Pace: Behind — need first sale this week

No tab switching. No login juggling. Just: here’s what happened, here’s what matters, here’s what to do about it.

The Seven Capabilities That Replace Your Dashboard Routine

Revenue Agent Pro isn’t just a briefing generator. It’s a full operations layer:

1. Daily Growth Briefing — The morning summary shown above. Pulls from your revenue data, content calendar, and SEO metrics to generate a prioritized action plan.

2. Revenue Dashboard — Multi-property income tracking with a Python-based RevenueTracker class. Log revenue by property, channel, and date. Get monthly summaries, channel breakdowns, and trend analysis that tells you if you’re growing, flat, or declining.

tracker = RevenueTracker()
tracker.add_property("StockVS", ["ads", "affiliate"])
tracker.add_property("Gumroad", ["products"])
tracker.log_revenue("Gumroad", "products", 29.00, "2026-03-15")
print(tracker.monthly_summary())

3. Content Calendar — Plan publication dates, track cross-posting schedules, and never forget which platform still needs this week’s article. I run 3 platforms (Dev.to, Medium, Hashnode) and publish 2-3 articles per week — without a calendar, things slip through the cracks.

4. SEO Monitor — Track pages indexed, crawl health, traffic trends, and keyword positions over time. It calculates your index health score automatically and flags when something goes wrong (like my indexing regression from 2,246 to 1,917 pages — a decline I caught early because the agent flagged it).

5. Promotion Scheduler — Set up recurring promotions on a rotation. Product A gets promoted on Monday, Product B on Wednesday, Product C on Friday. The scheduler tells you what’s due today so no product goes stale.

6. Competitor Watch — Log competitor moves and get alerted when positioning changes. Useful when you’re in a crowded niche and need to react fast.

7. Weekly Review Generator — Every Monday, get an automated performance summary: wins, revenue trends, content published, SEO progress, and next week’s priorities. This is the one I use most — it forces accountability.

Before vs. After: What Changed for Me

Before Revenue Agent Pro:

45 minutes every morning checking dashboards
Decisions based on whichever metric I looked at last
Missed cross-platform patterns (like Dutch pages driving all my GSC impressions, but English content getting all my Dev.to traffic)
Weekly reviews took 2 hours to compile manually

After:

5 minutes: read the briefing, confirm priorities, start working
Decisions based on consolidated data with trend arrows
Cross-property insights surfaced automatically
Weekly reviews generated in seconds

The math is simple. At 40 minutes saved per day, that’s over 4.5 hours per week back for building, writing, and shipping. Over a month, that’s nearly 20 hours — essentially a half-time employee’s worth of data analysis, for a one-time $19 purchase.

It’s Built From Real Operations, Not Theory

Most productivity tools are built by people who’ve never actually run a multi-property online business. Revenue Agent Pro came directly from the operational workflows I built for managing StockVS (100K+ pages across 12 languages) and an Apex Stack digital product store with 6 live products.

Every template, every tracking class, every briefing format was tested against real data — real GSC numbers, real Gumroad analytics, real content calendars with real deadlines.

The daily routine, weekly routine, and monthly routine automations aren’t aspirational. They’re what I actually run.

Try It Free, Then Go Pro

The free lite version gives you daily briefings, basic revenue tracking, and the priority action framework — enough to replace your morning dashboard routine immediately.

Try Revenue Agent Lite free on GitHub

When you’re ready for multi-property dashboards, SEO monitoring, content calendars, promotion scheduling, and automated weekly reviews:

Get Revenue Agent Pro — $19 on Gumroad

Install it as a Claude Skill, say “morning briefing,” and take your mornings back.

Built by Apex Stack — from real experience growing online properties from $0 to revenue.

I'm Optimizing 100,000 Pages for AI Search Engines, Not Just Google. Here's My Playbook.

Apex Stack — Sat, 14 Mar 2026 14:32:51 +0000

Google AI Overviews now appear in more than 1 out of every 4 search results. For long-tail queries — the exact type that programmatic SEO sites target — that number jumps above 50%.

I run StockVS.com, a programmatic SEO site with 100,000+ pages covering stock analysis, sector breakdowns, and ETF data across 12 languages. When I started building it, I optimized exclusively for traditional Google rankings. Page titles, meta descriptions, schema markup, internal linking — the standard playbook.

That playbook is no longer enough. AI search engines like Google's AI Overviews, ChatGPT with browsing, Perplexity, and others are reshaping how people find information. They don't just rank pages — they synthesize answers. And if your content isn't structured to be cited by these systems, you're invisible in the new search landscape.

Here's how I'm adapting 100,000 pages for a world where AI does the reading first.

The Problem: AI Overviews Eat Your Click

Here's what happens now when someone searches "NVDA stock analysis 2026":

Google shows an AI Overview at the top — a synthesized answer pulling from multiple sources
Below that, maybe some People Also Ask boxes
Then the traditional blue links

The AI Overview answers the question well enough that many users never scroll down. For programmatic SEO sites that depend on long-tail traffic, this is an existential shift. You can rank on page 1 and still get zero clicks because the AI summary already gave the user what they needed.

I noticed this pattern in my own Search Console data. Impressions were climbing in certain query buckets, but click-through rates were declining. People were seeing my pages in search results but not clicking through — because the AI Overview had already answered their question.

GEO: The New Optimization Layer

The SEO community has started calling this "Generative Engine Optimization" or GEO. It's the practice of structuring your content so that AI systems are more likely to cite it when generating answers.

This isn't about tricking AI. It's about making your data so clear, so structured, and so authoritative that when an AI needs to answer a financial question, your page becomes the obvious source to cite.

Here's what I've changed across my 100,000+ pages.

1. Structured Data Becomes Non-Negotiable

I was already using schema markup — FinancialProduct, FAQPage, BreadcrumbList. But for AI search, I've gone deeper.

Every stock page on StockVS now includes:

{
  "@type": "FinancialProduct",
  "name": "AAPL Stock Analysis",
  "description": "Apple Inc. stock analysis with key financials, valuation metrics, and sector comparison",
  "provider": {
    "@type": "Organization",
    "name": "StockVS"
  },
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  }
}

But I've also added explicit dateModified timestamps to every page, author markup linking to the site's editorial policy, and about schema connecting each stock page to its sector and industry.

Why? AI systems use structured data as a trust signal. When Perplexity or Google's AI Overview needs to decide which source to cite for "NVDA P/E ratio," the page with clean, machine-readable schema wins.

2. Direct-Answer Formatting

AI Overviews pull from content that directly answers questions. I restructured every stock page to lead with key metrics in a scannable format before diving into analysis.

Instead of:

"Apple Inc. (AAPL) is a technology company that designs, manufactures, and markets smartphones..."

I now start with:

AAPL Key Metrics (March 2026)

Market Cap: $3.2T

P/E Ratio: 28.4

Dividend Yield: 0.54%

52-Week Range: $169.21 – $260.10

Sector: Technology

Then the analysis follows. This formatting makes it trivial for AI systems to extract and cite specific data points. Every page becomes a structured data card that AI can pull from.

3. FAQ Sections That AI Actually Cites

I've always had FAQ schema on my pages, but I reworked the questions to match how people actually query AI assistants.

Old approach:

"What is the P/E ratio of AAPL?"
"Is AAPL a good investment?"

New approach:

"How does AAPL's valuation compare to the Technology sector average?"
"What are the key risks for Apple stock in 2026?"
"Should I buy AAPL at its current price?"

The difference: the new questions match how people phrase queries to ChatGPT, Perplexity, and Google's conversational search. When an AI system encounters these questions in your FAQ schema, it's more likely to cite your answer in its generated response.

4. Unique Data Points as Citation Magnets

Here's the biggest insight: AI systems preferentially cite pages that contain unique, quantitative data that other sources don't have.

Every stock page on StockVS generates unique analysis using financial data from yfinance combined with a local Llama 3 model. This means my AAPL page doesn't just repeat the same data as Yahoo Finance — it includes proprietary analysis, custom comparisons within the sector, and valuation assessments that exist nowhere else on the web.

For AI citation, unique data is the moat. If your page says the same thing as 50 other pages, the AI has no reason to cite you specifically. If your page contains a unique analysis or data point, the AI must cite you to reference that information.

5. Cross-Language as an AI Advantage

One of the most underappreciated aspects of AI search: multilingual content creates citation opportunities across language barriers.

When someone asks ChatGPT about a stock in German, the AI pulls from German-language sources. Most financial analysis sites are English-only. StockVS covers stocks, sectors, and ETFs across 12 languages — and in several of those languages, we're one of very few sources with comprehensive financial analysis.

My Search Console data confirms this: Dutch and German pages consistently generate more impressions per page than English ones. In AI search, this advantage compounds — there are simply fewer high-quality German-language financial analysis pages for AI to cite.

The Technical Implementation

Here's what the pipeline looks like for optimizing 100,000 pages for AI search:

Data Layer (Supabase PostgreSQL)
→ 8,000+ ticker records with live financial data from yfinance
→ Sector/industry/ETF relationship mappings
→ Historical price data and calculated metrics

Content Generation (Local Llama 3)
→ Template-based analysis with unique data-driven insights per ticker
→ FAQ generation matching conversational search patterns
→ Cross-language content with localized financial terminology

Schema Layer (Astro Static Build)
→ JSON-LD structured data generated at build time
→ FinancialProduct, FAQPage, BreadcrumbList, Organization
→ dateModified auto-updated per data refresh cycle

Delivery (Cloudflare CDN)
→ Sub-second page loads globally
→ Edge-cached static HTML — no JavaScript rendering required
→ This matters because AI crawlers heavily penalize slow or JS-dependent pages

What I'm Measuring

Traditional SEO metrics don't capture the full picture anymore. Here's what I'm tracking:

CTR at position — If I'm ranking position 5-10 and CTR drops, it likely means an AI Overview is absorbing clicks
Impression-to-click ratio by query type — Long-tail financial queries vs. branded queries
Schema validation rate — Percentage of pages passing Google's Rich Results test
AI citation monitoring — Searching key queries in Perplexity and ChatGPT to check if StockVS pages are cited
Language-specific AI visibility — Checking AI responses in German, Dutch, Polish for stock queries

I don't have a perfect measurement system for AI citations yet — nobody does. But directionally, I can see which optimizations move the needle.

What's Not Working

Transparency time: some things I've tried haven't panned out.

Aggressive FAQ expansion didn't help as much as I expected. Adding 20 FAQs per page didn't increase AI citations — having 5 really well-structured, data-rich FAQs performed better.

Trying to "game" AI Overviews by stuffing exact-match questions into headings backfired. The content felt unnatural and the quality signals degraded.

Over-optimizing meta descriptions for AI was a waste. AI systems read the full page content, not just the meta description. The meta description matters for traditional CTR, not for AI citation.

The Playbook Summary

If you're running a programmatic SEO site, here's the minimum viable GEO stack for 2026:

Schema everything — dateModified, author, about, domain-specific types. Make your data machine-readable.
Lead with data — Put key facts and metrics above the fold in scannable formats. AI extracts from the top of your content first.
Match conversational queries — Rewrite FAQs to match how people ask AI assistants, not how they type into Google.
Generate unique analysis — Original data points are your citation moat. If your page says what everyone else's says, AI won't cite you.
Go multilingual — Non-English AI search is wide open. If your data works in other languages, translate and localize it.
Measure AI visibility — Check Perplexity, ChatGPT, and Google AI Overviews manually for your key queries. The tools for automated tracking are coming but aren't reliable yet.

What's Next

I'm building automated monitoring that checks whether StockVS pages appear in AI-generated answers for a rotating set of financial queries across all 12 languages. It's basically an "AI SERP tracker" — and I'll share the results when I have enough data.

The shift from "rank on page 1" to "get cited by AI" is the biggest change to SEO since mobile-first indexing. For programmatic SEO at scale, it's both a threat and an opportunity. The sites that adapt their content structure for AI consumption first will have a massive head start.

I'm building StockVS and documenting the entire journey. If you're into programmatic SEO, AI-powered content generation, or building data-driven web properties, I write about the real numbers — what works, what fails, and what the data actually says.

Resources I've built:

📘 Programmatic SEO Blueprint — The complete framework for building data-driven SEO sites at scale
🔍 Programmatic SEO Auditor — Claude skill that audits your pSEO site for indexing, content quality, and technical issues
📊 Financial Data Analyzer — Claude skill for pulling live stock data and running analysis

Google Only Indexed 2% of My 100,000-Page Site. Here's What I'm Doing About It.

Apex Stack — Fri, 13 Mar 2026 17:36:03 +0000

I've been building StockVS, a multilingual stock analysis platform with over 100,000 pages covering 8,000+ US tickers across 12 languages. It's a programmatic SEO play — templatized pages generated from financial data and local LLM analysis.

Here's the problem: Google has only indexed about 1,920 of those pages. That's roughly 2%.

And it's getting worse.

The Numbers Don't Lie

Every few days I check Google Search Console and pull the indexing report. Here's what I'm looking at right now:

Status	Pages	What It Means
Crawled — not indexed	51,061	Google visited, read the page, and said "no thanks"
Discovered — not indexed	28,016	Google knows the URL exists but won't even bother crawling it
Indexed	1,920	The 2% that made the cut
Redirects	2,648	Pages I intentionally removed

The most painful line is "Crawled — not indexed." That means Googlebot actually spent its crawl budget visiting 51,000 pages, processed them, and decided they weren't worth indexing. That's not a discovery problem. That's a quality problem.

Even worse: my indexed count dropped from 2,246 to 1,920 in one week. Google is actively de-indexing pages it previously accepted.

Why Google Is Rejecting 98% of My Pages

After months of analyzing GSC data and reading every Google documentation page about indexing, I've identified three root causes.

1. Thin Content Signals

My stock pages were originally 200-300 words of templated analysis. For a site with zero authority, that's not enough to convince Google that each page adds unique value. When Google's AI-first indexing systems see thousands of pages with similar structure and shallow content, it treats the whole domain as low-quality.

I've since expanded pages to 600-800 words with more specific financial analysis per ticker, but the reputation damage takes time to reverse.

2. Zero Domain Authority

Here's a stat that surprised me: one audit I read about described a site with 8 million discovered pages but only 650,000 indexed. The reason? Google scales its indexing generosity with your domain's trust signals. No backlinks, no authority, no index.

StockVS has zero backlinks registered in any tool I've checked. I've published five articles across Medium, Dev.to, and Hashnode to start building links, but that's a drop in the ocean compared to what's needed.

3. Crawl Budget Economics

Google allocates crawl budget based on a site's perceived importance. When you have 100,000+ URLs competing for attention on a domain Google doesn't trust yet, you're burning crawl budget on pages Google will never index. It's a vicious cycle: low authority means less crawling, which means fewer indexed pages, which means less traffic, which means less authority.

What I'm Actually Doing About It

I'm not giving up on programmatic SEO. The math still works — if even 10% of my pages start ranking, that's 10,000 pages of organic traffic. But the approach has to change.

Strategy 1: Kill the Weakest Pages

I already removed all comparison pages — they were the thinnest content on the site and were actively diluting crawl budget. Those 2,648 redirects in my GSC report are the evidence. Sometimes the best SEO move is subtraction.

The principle: fewer, better pages > more pages.

Strategy 2: Thicken Content Where It Matters

I'm adding unique sections to every stock page that aren't just reformatted data points. Things like related news, analyst ratings, earnings timelines, and market context sections that actually require specific data per ticker.

The goal is to make Google's quality classifiers see each page as a legitimate analysis rather than a data table with a paragraph bolted on.

Strategy 3: Internal Linking Architecture

Programmatic SEO sites often have flat architecture where every page is equally connected (or disconnected). I'm building internal linking widgets — "Related Stocks," "Popular in This Sector," cross-links between stock pages, sector pages, and ETF pages.

This helps Google understand the topical relationships between pages and distributes whatever authority the domain has more effectively.

Strategy 4: Build Backlinks Through Content Marketing

Five articles are live across three platforms. Each one tells part of the StockVS story and naturally links back to the site. I'm planning more — the key is writing about the journey of building a large-scale site, which resonates with the developer and SEO communities.

This article you're reading is part of that strategy.

Strategy 5: Focus on What's Working

Here's an interesting signal from my GSC data: non-English pages are getting more impressions than English ones. Dutch pages lead impressions, followed by German and Polish. The competition for "[ticker] analyse" in Dutch is dramatically lower than "[ticker] analysis" in English.

This validates the multilingual approach. Instead of fighting for English keywords against sites with DR 70+, I can win in languages where the SERP is wide open.

The Uncomfortable Truth About Programmatic SEO in 2026

Google's indexing bar has never been higher. Their AI-first systems are more aggressive about filtering out content that doesn't demonstrate unique value. If you're generating thousands of pages, each one needs to earn its place in the index individually.

The old playbook of "spin up 100k pages, submit sitemap, wait for traffic" doesn't work anymore. You need:

Content depth that goes beyond what any template can auto-generate
Authority signals (backlinks, brand searches, engagement metrics) that tell Google your domain is trustworthy
Technical hygiene — clean sitemaps, proper canonicals, fast load times, no crawl traps
Patience — Google's re-evaluation cycle for domains isn't fast, especially when you're recovering from thin content signals

What's Next

I'm tracking this weekly. Every GSC report tells me whether the content thickening and backlink building is moving the needle. The leading indicators I'm watching:

Crawled-not-indexed count — if content quality is improving, this should decrease
Indexed page count — the north star metric
Impressions on non-English pages — the multilingual arbitrage play
Domain Rating in Ahrefs — currently zero, need to see movement

If you're building a programmatic SEO site and hitting the same indexing wall, I'd love to hear what's working for you. The old "just build more pages" approach is dead. In 2026, it's about building pages that deserve to be indexed.

I write about building large-scale SEO sites, AI-powered content generation, and the tools I use to manage it all. If you're into programmatic SEO, check out my Programmatic SEO Blueprint — it covers the architecture, data pipelines, and multilingual strategy I use for StockVS.

For AI-powered SEO workflows, I've also built a set of Claude Skills that handle everything from content auditing to cross-platform publishing.

Agentic SEO Is Here: How I Use AI Agents to Manage a 100,000-Page Website

Apex Stack — Thu, 12 Mar 2026 16:22:27 +0000

Everyone's talking about AI agents replacing DevOps engineers and writing code. But nobody's talking about what happens when you point AI agents at SEO.

I run StockVS.com, a programmatic SEO site with over 100,000 pages covering 8,000+ stock tickers across 12 languages. Managing a site this size manually is impossible. So I built an agentic workflow that handles everything from content generation to cross-platform publishing to technical auditing.

Here's exactly how the system works, what surprised me, and where AI agents still fall short.

What "Agentic SEO" Actually Means

There's a difference between using AI to write a blog post and using AI agents to operate an SEO pipeline.

Traditional AI-assisted SEO looks like this: you open ChatGPT, ask it to write an article, copy-paste it into WordPress, and manually optimize it. That's AI as a tool.

Agentic SEO is different. You define the workflow once — data collection, content generation, quality checks, publishing, monitoring — and agents execute the entire pipeline autonomously. You shift from being the operator to being the architect.

For StockVS, that pipeline looks like this:

Data Layer:     yfinance API → Supabase PostgreSQL (8,000+ tickers)
Content Layer:  Local Llama 3 → 600-800 word analysis per ticker
Build Layer:    Astro static site → 12 language variants
Distribution:   Cloudflare CDN → Digital Ocean Spaces
Monitoring:     Google Search Console → Custom dashboards
Publishing:     AI skill → Dev.to + Medium + Hashnode simultaneously

Each layer runs with minimal manual intervention. That's the shift.

Agent 1: Content Generation at Scale With a Local LLM

The backbone of StockVS is a local Llama 3 instance generating unique stock analysis for every ticker. Not generic filler — each page includes valuation metrics, financial health indicators, sector positioning, and a forward-looking assessment.

I covered this in detail in a previous article, but the key insight is cost. Running Llama 3 locally means generating 100,000+ pages of content costs exactly $0 in API fees. The tradeoff is compute time and the work of building the pipeline, but once it's running, the marginal cost of adding a new ticker is near zero.

What I'd do differently: I initially generated 300-400 word pages. Google flagged most of them as thin content (50,000+ pages "crawled but not indexed" in Search Console). After expanding to 600-800 words with more unique data points per page, the quality signal improved significantly.

Lesson: AI agents are only as good as the quality bar you set for them. An agent that generates fast but shallow content will scale your problems, not your results.

Agent 2: Cross-Platform Publishing in Under a Minute

Writing articles is half the battle. The other half is getting them in front of people across multiple platforms without spending 30 minutes copy-pasting and reformatting.

I built a publishing agent that takes a markdown article and pushes it to Dev.to, Hashnode, and Medium simultaneously. It handles:

Platform-specific formatting differences
Canonical URL management (so Google doesn't see duplicate content)
Tag optimization per platform
Frontmatter translation

A single command takes an article from draft to live on three platforms. The same article, properly formatted for each platform's quirks, with canonical URLs pointing back to the primary source.

Before this, publishing a single article across three platforms took 25-30 minutes of manual work. Now it takes under 60 seconds.

The Blog Cross-Publisher is available as a Claude skill if you want to try this workflow yourself.

Agent 3: Programmatic SEO Auditing

When you have 100,000+ pages, you can't manually check each one for SEO issues. You need an agent that crawls your own site, identifies problems, and prioritizes fixes.

My auditing agent checks for:

Missing or duplicate meta descriptions
Thin content pages (under word count threshold)
Broken internal links
Missing schema markup
Hreflang consistency across 12 languages
Canonical tag mismatches (Google flagged 297 pages for this)
Orphaned pages with no internal links

The output is a prioritized list of issues sorted by impact. Fix the top 10 items and you move the needle more than fixing 1,000 random pages.

This is where agents genuinely outperform humans. No person can audit 100,000 pages for hreflang consistency. An agent does it in minutes.

The Programmatic SEO Auditor is the skill I packaged from this workflow.

Agent 4: Financial Data Analysis

StockVS pages need actual financial data, not just AI-generated text. Each stock page pulls live data through yfinance: price history, P/E ratios, dividend yields, revenue growth, debt levels, and more.

An analysis agent processes this raw data and generates the narrative sections — "AAPL is trading at 28x earnings, above its 5-year average of 24x, suggesting the market is pricing in continued growth from its services segment."

This is where combining structured data with LLM reasoning gets interesting. The agent isn't hallucinating numbers — it's reading real financial data from a database and generating contextual analysis around verified facts.

I open-sourced a lite version of this as the Financial Data Analyzer skill.

The Hard Truth: What Agents Can't Do (Yet)

After 6 months of building agentic SEO workflows, here's where agents still struggle:

1. Editorial judgment. Agents can generate content that's technically accurate and well-structured, but they can't tell you if a page is interesting. The difference between a page that ranks #3 and one that ranks #30 is often the quality of insight, not the quality of grammar.

2. Link building. This is still fundamentally a human relationship activity. Agents can identify link opportunities and draft outreach emails, but the actual relationship — the "hey, I noticed your resource page" conversation — requires human nuance. My site has zero backlinks despite 100K+ pages, and no agent has solved that yet.

3. Strategic pivots. When Google's indexing data showed 50,000+ pages as "crawled but not indexed," the decision to remove comparison pages entirely and double down on stock analysis pages was a strategic call. Agents can surface the data, but the judgment to cut 200,000 pages requires understanding Google's signals in context.

4. Understanding Google's mood. Google's indexing behavior is partially opaque. Why did my Dutch pages get more impressions than English ones? Why did a copper industry page get a click before any individual stock page? Agents can track these patterns, but interpreting them still requires human pattern recognition.

The Real Numbers

Transparency matters more than hype, so here's where things actually stand:

Metric	Current
Total pages	100,000+ across 12 languages
Pages indexed by Google	2,246 (2.1%)
Search clicks (3 months)	3
Impressions (3 months)	2,180
Average position	52.5
Backlinks	0
Revenue	$0

Those numbers are humbling. And they're real.

The indexing rate is the critical blocker. Google has crawled 50,000+ pages and rejected them, and another 51,000+ pages it discovered but won't even crawl yet. Until the site builds authority through backlinks and proves content quality, the agentic pipeline is generating pages that Google isn't serving.

But here's why I'm still optimistic: the pipeline is built. When indexing improves — through backlink building, content quality signals, and time — the system can scale instantly. I don't need to manually write 100,000 pages. The agent infrastructure is ready.

How to Start With Agentic SEO

If you want to experiment with agentic SEO workflows, start small:

Step 1: Automate your publishing pipeline first. Cross-posting is the lowest risk, highest time-savings entry point.

Step 2: Build a site auditing agent. Even for a 50-page site, automated auditing catches things you'd miss manually.

Step 3: Add data-driven content generation for one content type. Don't try to automate everything at once.

Step 4: Monitor Google Search Console data programmatically. Build alerts for indexing drops, crawl errors, and ranking changes.

The goal isn't to remove humans from SEO. It's to let humans focus on strategy and relationships while agents handle the repetitive execution at scale.

What's Next

I'm currently focused on three things:

Content thickening — adding related news, analyst ratings, and earnings data to each stock page to increase the quality signal
Internal linking — building cross-references between stock, sector, and ETF pages so Google can better understand site structure
Backlink building — the one thing agents can't automate, and the biggest blocker to indexing

If you're building something similar, or if you've cracked the indexing challenge at scale, I'd love to hear about it in the comments. What's your experience with using AI agents for SEO tasks?

I build tools for programmatic SEO and AI-powered content workflows. Check out the Apex Stack collection of Claude skills for SEO, publishing, and financial analysis.

5 Claude Skills Every SEO Professional Needs in 2026

Apex Stack — Wed, 11 Mar 2026 20:40:46 +0000

The SEO landscape shifted dramatically when AI coding agents went mainstream. Tools like Claude, Codex, and ChatGPT aren't just chatbots anymore — they're autonomous agents that can run scripts, analyze data, and execute complex workflows.

But here's what most SEO professionals are missing: skills (also called custom instructions or agent configurations) turn these general-purpose AIs into specialized SEO machines. Instead of explaining your workflow from scratch every session, a skill gives the agent pre-loaded context, proven frameworks, and ready-to-run scripts.

I've been running a programmatic SEO site with 100,000+ pages across 12 languages. Over the past few months, I've built and battle-tested a set of Claude skills that handle everything from content generation at scale to backlink strategy. Here are the five that changed my workflow the most.

1. Programmatic SEO Auditor

If you're running a programmatic site — or thinking about building one — this is the skill you install first.

The Programmatic SEO Auditor analyzes your site architecture for the specific patterns that make or break programmatic SEO: template quality scoring, internal linking coverage, schema markup completeness, crawl budget optimization, and content uniqueness across generated pages.

What makes it different from generic SEO audit tools? It understands programmatic sites. Most audit tools flag every templated page as "duplicate content." This skill knows the difference between a well-structured template with unique data and actual thin content. It scores your templates on data richness, contextual uniqueness, and information gain.

What it does:

Scores page templates for content quality and uniqueness
Maps internal linking gaps across your page taxonomy
Validates schema markup (JSON-LD) for every page type
Identifies crawl budget waste from low-value URLs
Generates a prioritized fix list with estimated impact

I originally built this to diagnose why Google was only indexing 2% of my pages. The audit identified that my comparison pages were dragging down the entire domain's quality signals. After removing them based on the audit findings, my index rate started climbing.

Try it: A free lite version is on GitHub with basic auditing capabilities. The full version ($19) adds multi-language support, crawl budget analysis, and generates a complete action plan.

2. Content Pipeline Builder

Generating one article with AI is easy. Generating 10,000 pages with consistent quality, proper data integration, and multi-language support? That's an engineering problem.

The Content Pipeline Builder skill encodes the entire system I use to generate programmatic content at scale. It's not a collection of prompts — it's an architecture pattern that includes template design, data source integration, LLM prompting strategies, quality scoring, and output validation.

What it covers:

Template system design with variable injection patterns
Data pipeline architecture for pulling from APIs and databases
LLM prompt engineering for consistent, factual output
Quality scoring to catch hallucinations and thin content before publishing
Multi-language content generation with cultural adaptation
Scaling patterns that work from 100 to 100,000 pages

The key insight baked into this skill is that content quality at scale isn't about better prompts — it's about better systems. The skill includes a pipeline_runner.py script that orchestrates the full generation → validation → output cycle, plus a template-patterns.md reference covering the most effective template architectures I've tested.

Get it: This one is $25 on Gumroad with no free version — it's a complete system with production-tested code and architecture docs.

3. Blog Cross-Publisher

Content marketing drives backlinks. Backlinks drive rankings. But cross-posting the same article to Medium, Dev.to, and Hashnode manually — while managing canonical URLs correctly — eats an hour every time.

The Blog Cross-Publisher skill automates the entire process. Feed it a markdown article, and it publishes to all three platforms with proper canonical URL attribution, platform-specific tag mapping, and formatting that respects each editor's quirks.

The tricky part it handles for you: Medium deprecated their API for new users in 2023. Most automation tools simply don't work with Medium anymore. This skill includes a browser automation fallback that uses insertText commands to work with Medium's editor directly — and it handles the gotchas like editor state sync that break most automation attempts.

What it does:

Publishes to Dev.to via REST API (instant)
Publishes to Hashnode via GraphQL API (instant)
Publishes to Medium via browser automation (2-5 min)
Manages canonical URLs across all platforms
Maps tags to each platform's format and limits

I used this skill to publish the three articles that currently drive traffic to my projects. What used to take an hour per article now takes minutes.

Try it: Free lite version on GitHub handles Dev.to publishing. The full version ($12) adds Medium, Hashnode, and canonical URL management.

4. Financial Data Analyzer

This one is for SEO professionals working in the finance niche — and there are a lot of you, because finance keywords have some of the highest RPMs in display advertising.

The Financial Data Analyzer pulls stock data via yfinance (no expensive API subscriptions), generates analysis reports, compares tickers, and visualizes performance. If you're building content around stock analysis, dividend tracking, or sector comparisons, this skill turns Claude into a financial research assistant.

What it does:

Pulls real-time and historical stock data via yfinance
Generates comprehensive ticker analysis reports
Compares multiple stocks with side-by-side metrics
Tracks dividend history and calculates yield metrics
Visualizes price trends, sector performance, and earnings data

I built this to power the data pipeline behind my stock analysis site. Every stock page pulls fresh data, runs it through analysis frameworks, and generates unique content that Google actually values — because it's based on real numbers, not generic summaries.

Try it: Free lite version on GitHub with basic stock lookup. The full version ($15) adds sector analysis, dividend tracking, portfolio comparison, and charting.

5. Revenue Agent

Here's a skill I didn't plan to build — it emerged from my own daily routine.

Running multiple web properties means tracking revenue across platforms, monitoring search rankings, managing content calendars, scheduling promotions, and doing weekly reviews. The Revenue Agent skill consolidates all of this into a single daily briefing system.

What it does:

Generates a daily growth briefing with key metrics
Maintains a revenue dashboard across multiple platforms
Manages your content calendar with publishing deadlines
Monitors SEO performance and flags ranking changes
Schedules and tracks promotions across properties
Produces a weekly review with trends and action items

The skill includes Python classes (RevenueTracker, ContentCalendar, SEOMonitor, PromotionScheduler) that you can extend for your specific setup. It's designed for solo operators managing a portfolio of sites — the people who don't have a team but still need the systems.

Try it: Free lite version on GitHub with basic daily briefing. The full version ($19) adds multi-platform tracking, Python classes, and weekly review generation.

Why Skills Beat Prompts

You might be wondering: can't I just write good prompts and get the same result?

You can, for one-off tasks. But skills are fundamentally different because they include persistent context. A skill carries reference files, scripts, and domain knowledge that would take thousands of tokens to re-explain every session. My Programmatic SEO Auditor skill, for example, includes reference docs on crawl budget optimization patterns, schema markup templates for 15+ page types, and internal linking formulas — none of which would fit in a prompt.

Skills also include executable code. The Content Pipeline Builder doesn't just tell Claude how to generate content — it includes a Python script that actually runs the pipeline. The Blog Cross-Publisher includes API integration code for three different platforms. That's the difference between instructions and infrastructure.

The Stack Effect

These five skills work best together. The Content Pipeline Builder generates your pages. The Programmatic SEO Auditor validates quality. The Blog Cross-Publisher distributes your content marketing. The Financial Data Analyzer powers your data pipeline. And the Revenue Agent tracks whether any of it is actually making money.

That's the workflow I run daily, and it's all available as installable skills you can drop into Claude (or any compatible AI agent) and start using immediately.

All the free lite versions are available on GitHub under the Apex Stack account. Full versions with advanced features are on Gumroad.

I'm building in public — follow along as I scale a portfolio of online businesses using AI, programmatic SEO, and too much coffee. More articles on the systems behind it coming soon.

My Site Has 287,000 Pages and Zero Backlinks. Here's My Plan to Fix That.

Apex Stack — Tue, 10 Mar 2026 14:43:38 +0000

There's a brutal truth about programmatic SEO that nobody talks about when they're selling you on the dream: Google doesn't care how many pages you have if nobody links to you.

I built a stock comparison engine with 287,000 pages across 12 languages. The tech stack works. The content pipeline runs. Pages render fast on a static Astro site behind Cloudflare. Every page has structured data, clean URLs, and unique AI-assisted analysis.

Google has indexed about 2,500 of those 287,000 pages. That's 0.9%.

The reason is simple. Domain authority is zero. Backlink count is zero. In Google's eyes, my site is a ghost.

So I'm fixing it. Here's exactly what I'm doing, what's working, and what I'd skip if I started over.

Why Backlinks Still Matter in 2026

Every year someone declares backlinks are dead. Every year the data says otherwise. Ahrefs, Semrush, and Moz have all published studies showing strong correlations between referring domains and organic rankings. In Google's own leaked documentation, link signals remain part of the ranking system.

For programmatic SEO sites this matters even more than usual. When you're generating thousands of pages from templates, Google needs external trust signals to justify crawling and indexing all that content. Without backlinks, your crawl budget stays low and most of your pages sit in the "discovered but not indexed" bucket indefinitely.

That's exactly where I was.

Phase 1: Directory Submissions (Week 1-2)

I started with the lowest effort, highest certainty plays. Directory submissions aren't glamorous, but they establish a baseline of referring domains that tells Google your site exists and is real.

Here's what I targeted:

General web directories — places like BOTW, Jasmine Directory, and a handful of curated niche directories that still pass value. I looked for directories that have editorial review, not the ones that accept anything.

Tech and startup directories — Product Hunt (as a discussion post, not a formal launch), BetaList, SaaSHub, AlternativeTo. These have real traffic and decent domain authority.

Finance-specific directories — niche directories for financial tools, stock screeners, and investment resources. Smaller audience but highly relevant.

Developer tool directories — since the site is built with Astro and uses programmatic SEO, it fits in directories that list developer tools and open-source projects.

Total time investment: about 4 hours across two days. Expected result: 15-25 referring domains within a month as submissions get reviewed and approved.

The key insight: don't submit to 200 directories in one day. Spread it out. A sudden spike of low-quality directory links looks unnatural.

Phase 2: Content Marketing (Week 2-4)

This is where the real leverage is. I started writing about the process of building this site — the technical decisions, the failures, the data — and publishing on platforms where my target audience already hangs out.

Medium — long-form technical articles. Medium has strong domain authority and articles can rank in Google independently. Each article links back to the site naturally within the context of the story.

Dev.to — developer-focused platform. Great for technical breakdowns of the stack, code examples, and architecture decisions. The community is engaged and articles get syndicated through their newsletter.

Hashnode — another developer blogging platform with good domain authority. Cross-posting here with canonical URLs pointing back to Medium ensures the content gets maximum distribution without duplicate content issues.

The strategy isn't to write thinly veiled ads. Every article needs to stand on its own as genuinely useful content. The backlink comes from naturally referencing the project within an article that teaches something real.

My first two articles covered the architecture behind building a 287k-page site and how I use a local LLM for content generation. Both got solid engagement from the developer community because they shared specific, actionable details — not vague "10 tips" fluff.

Phase 3: Community Engagement (Ongoing)

Reddit, Indie Hackers, and Hacker News are goldmines for early traffic and backlinks — but only if you do it right.

The wrong way: Drop a link to your site in every relevant thread. Get downvoted. Get banned.

The right way: Be genuinely helpful. Answer questions in detail. Share your experience when it's relevant. Build a reputation in subreddits like r/SEO, r/SideProject, r/juststart, and r/webdev. When someone asks about programmatic SEO or scaling content, share what you've learned. The link to your site becomes a natural citation, not spam.

I spend about 20 minutes per day browsing these communities and contributing where I actually have something useful to say. Some days I don't link to anything. Some days someone asks a question where my project is the perfect case study.

The compounding effect is real. After a few weeks of genuine engagement, people start recognizing your username and upvoting your content by default.

Phase 4: Guest Posts (Month 2-3)

Once you have some published articles and community presence, guest posting becomes much easier. You're not a random person pitching from nowhere — you're someone with a track record of writing useful technical content.

I'm targeting SEO blogs that cover programmatic approaches, developer blogs that feature case studies, indie hacking newsletters that showcase side projects, and finance/fintech blogs that cover stock analysis tools.

The pitch is simple: I have a unique story (287k-page site, one person, local LLM pipeline) and I can write a detailed technical breakdown that their audience would find valuable. In exchange, I get a contextual backlink in the author bio or within the article.

Acceptance rate for cold guest post pitches is typically 5-10%. With a portfolio of published articles to show, that jumps to 20-30%.

What I'd Skip

Paid links. Too risky for a new domain. Google's spam detection has gotten aggressive, and if your first batch of backlinks are obviously paid, you're starting your site's life with a penalty.

PBN networks. Same problem, worse execution. Private blog networks are increasingly easy for Google to detect and the penalty is site-wide.

Link exchanges. "I'll link to you if you link to me" is the most common pitch in SEO, and it's also the least effective. Google explicitly targets reciprocal linking patterns.

HARO/Connectively. These journalist-response platforms used to be great for earning high-DA links. But response volumes have exploded, acceptance rates have cratered, and many publishers have moved behind paywalls. Still worth trying, but don't build your strategy around it.

The Math

Here's my realistic timeline:

Month 1: 15-25 referring domains from directories + content platforms. Domain Rating moves from 0 to maybe 5-8.

Month 3: 50+ referring domains. Guest posts start landing. DR reaches 15+. Index rate climbs from 0.9% to 10-15%.

Month 6: 100-200 referring domains. Community reputation established. DR hits 25-30. Index rate above 30%.

The relationship between backlinks and indexing isn't linear — it's more like a step function. There's a threshold where Google suddenly decides your site is worth crawling properly. Based on what I've seen from other programmatic SEO sites, that threshold is somewhere around DR 15-20 with 50+ unique referring domains.

The Takeaway

Building backlinks for a new domain isn't complicated. It's just slow. The temptation is to look for shortcuts, but every shortcut in link building carries risk that could sink your entire project.

The sustainable playbook is: create content worth linking to, distribute it where your audience already is, and engage authentically in communities. It takes months, not days. But once domain authority starts building, every one of your programmatic pages benefits from the rising tide.

I'll report back on the results. If you want the full technical breakdown of how I built the programmatic SEO pipeline behind this site — the data architecture, templates, AI integration, and deployment — I put everything into a guide: Programmatic SEO Blueprint.

Building in public at Apex Stack. Follow for more on programmatic SEO, side project economics, and building online businesses as a solo developer.

How I Use a Local LLM to Generate SEO Content for 10,000+ Pages

Apex Stack — Tue, 10 Mar 2026 01:37:03 +0000

There's a lot of hype about using AI for content. Most of it is about writing blog posts faster. That's fine, but it misses the bigger opportunity: using AI as a component in a programmatic content pipeline that generates thousands of unique pages.

I run a stock comparison site with 287,000 pages across 12 languages. Every page has AI-generated narrative sections — not generic filler, but analysis that's specific to each stock pair. The AI doesn't write the page. It writes the parts of the page that need to feel human, while structured data handles everything else.

Here's how the system works and what I've learned about making AI content that Google actually accepts.

Why Local LLM (and Why Llama 3)

First question everyone asks: why not just use the OpenAI API?

Cost. At 287,000 pages with roughly 500-800 tokens of AI-generated content per page, even at GPT-3.5 prices you're looking at $200-400 just for the initial generation. Then factor in regeneration when you update templates, multilingual variants, and iterative improvements. It adds up fast.

Speed. API rate limits mean generating content for 287k pages would take days of queued requests. With a local Llama 3 instance running on a decent GPU, I can generate content for thousands of pages per hour without worrying about rate limits or API outages.

Control. I can fine-tune prompts, adjust generation parameters, and rerun entire batches without worrying about cost. This matters more than you'd think — I went through about 15 iterations of my prompt templates before landing on output that consistently passed quality checks.

Privacy. Financial data flowing through a third-party API isn't ideal. Running locally means all data stays on my machine.

That said, cloud APIs absolutely have their place. For one-off content, complex reasoning tasks, or when you need the best possible quality on a small number of pages, GPT-4 or Claude is better. But for batch generation at scale, local is the way to go.

The Template + AI Hybrid

The key concept: AI doesn't write the entire page. It writes specific sections within a structured template.

A stock comparison page has roughly this structure:

[Header — ticker names, logos, prices] ← Structured data
[Key Metrics Table — P/E, market cap, etc.] ← Structured data
[AI Comparison Summary — 2-3 paragraphs] ← AI generated
[Dividend Analysis] ← Mix of data + AI narrative
[Growth Metrics Chart] ← Structured data
[AI Investment Considerations] ← AI generated
[FAQ Section] ← AI generated from data
[Schema Markup] ← Auto-generated

Maybe 60-70% of each page is structured data rendered by the template. The AI fills in the 30-40% that needs natural language — summaries, analysis, and FAQs.

This hybrid approach solves two problems at once:

Uniqueness. Every page has different data AND different narrative, so Google doesn't flag it as duplicate content.
Accuracy. The AI generates text based on actual financial data passed in the prompt, not from its training data. This means the content is factually grounded, not hallucinated.

The Prompt Architecture

I can't share my exact production prompts (those are in the full blueprint), but here's the general approach.

Context injection. Every prompt starts with the actual data for that specific stock pair. The AI isn't generating from scratch — it's analyzing and narrating data it's been given.

You are analyzing {STOCK_A} vs {STOCK_B}.

Here is the current financial data:
- {STOCK_A} P/E: {pe_a}, Market Cap: {mcap_a}, Dividend Yield: {div_a}
- {STOCK_B} P/E: {pe_b}, Market Cap: {mcap_b}, Dividend Yield: {div_b}

Write a 2-paragraph comparison focusing on...

Variation instructions. To prevent all pages from reading the same way, I include randomized style directives: vary sentence length, alternate between starting with stock A or stock B, use different comparison frameworks (value vs growth, income vs appreciation, etc.).

Output constraints. Word count limits, formatting requirements, and explicit instructions about what NOT to include (no financial advice disclaimers in the body text, no "as an AI" self-references, no generic filler phrases).

Quality gates. After generation, every piece of content runs through automated checks: minimum uniqueness score against other generated pages, readability score, factual consistency against the source data, and keyword density checks.

What Google's Helpful Content Update Means for This

Google's official stance: AI-generated content isn't automatically bad. Low-quality content is bad, regardless of how it's made.

In practice, here's what I've observed across my 287k pages:

Pages that get indexed tend to have: Unique data points, specific analysis tied to that data, proper schema markup, and they answer a real search query that a human would type.

Pages that DON'T get indexed tend to have: Generic narrative that could apply to any stock pair, thin analysis that just restates the numbers in sentence form, and patterns that are too similar across pages.

The lesson: the AI content needs to actually say something specific. "Stock A has a higher P/E than Stock B" is thin. "Stock A's P/E of 35 suggests the market expects significant growth, which makes sense given their 40% revenue increase last quarter, while Stock B's P/E of 12 reflects a more mature business with stable but slower growth" — that's useful analysis.

Getting the AI to consistently produce the latter instead of the former is the core challenge. It's solvable with good prompts, but it took me 15+ iterations.

Multilingual Generation

One of the biggest advantages of programmatic SEO is going multilingual cheaply. Here's how I handle it:

Template strings (headers, labels, button text) are translated once by a human translator and stored in locale files. This is maybe 200-300 strings per language.

AI narrative sections are generated in the target language directly, not translated from English. This produces more natural-sounding content than translation. The prompt is in English, but I instruct the model to output in the target language with the data injected.

Data stays the same. Numbers, ticker symbols, percentages — these are universal. The template handles formatting (date formats, number separators) based on locale.

Result: 12 languages with minimal per-language effort. The heavy lifting is in building the system. Each additional language is maybe 2-3 days of work.

Cost Breakdown

For anyone wondering about the economics:

Item	Cost
Local GPU (one-time, used RTX 3090)	~$700
Electricity for generation runs	~$5/batch
Supabase (free tier + small paid)	$25/mo
Hosting (DigitalOcean Spaces)	$5/mo
Cloudflare CDN	Free tier
Domain	$12/year
Monthly recurring	~$30/mo

Compare that to paying for API calls at scale or hiring writers. The local LLM pays for itself after generating content for maybe 5,000-10,000 pages.

Mistakes I Made

Starting with too many pages. I generated content for 287k pages before validating that Google would index them. Should have started with 5k, gotten indexed, then scaled.

Not enough variation in prompts. My first generation pass used identical prompt structures for every page. The output was technically unique but structurally identical. Google noticed. Second pass included randomized style directives and it made a big difference.

Ignoring readability. Early AI output was dense and clinical. Real financial analysis writing varies between technical detail and accessible explanations. I had to explicitly prompt for this variation.

No quality gate initially. I generated everything in batch and published it all. Should have implemented automated quality checks before publishing. Catching the bottom 10% of AI output before it goes live saves you from thin content flags.

The System Today

After iterating, my current pipeline looks like this:

Data refresh — Pull latest financial data via yfinance (daily cron job)
Content generation — Run Llama 3 on pages with stale or missing narrative (weekly)
Quality check — Automated scoring: uniqueness, readability, factual accuracy
Build — Astro generates static HTML for all pages
Deploy — Push to CDN

The whole thing runs on a single machine. Total human time per week: about 2 hours of monitoring and occasional prompt tweaking.

If you want the full technical details — the exact prompt templates, the quality scoring system, the Astro project structure, and the complete deployment pipeline — I wrote it all up in the Programmatic SEO Blueprint. It includes the MIT-licensed code examples you can adapt for your own projects.

Follow for more on building AI-powered content systems at scale.

I Built a 287,000-Page Website. Here's What I Learned About Programmatic SEO.

Apex Stack — Tue, 10 Mar 2026 01:37:02 +0000

Most SEO advice boils down to the same thing: pick a keyword, write an article, wait three months, repeat. If you want 10x the traffic, you write 10x the content. That math doesn't work if you're one person.

About a year ago I started experimenting with a different approach. Instead of writing articles one by one, I built a system that generates pages programmatically — one template, one data pipeline, thousands of output pages. Each page targets a specific long-tail keyword. The effort goes into building the machine, not feeding it.

The site I built is a stock comparison engine. You type in two tickers and get a side-by-side breakdown: financials, dividends, growth metrics, the works. Simple concept, but at scale it covers every meaningful stock pair — across 12 languages.

287,000 pages. One person. No content team.

Here's what actually happened.

The Stack

Nothing exotic. Astro for static site generation — fast, SEO-friendly, handles thousands of routes without breaking. Supabase PostgreSQL for the data layer. yfinance API for pulling financial data. A local Llama 3 instance for generating the narrative sections on each page.

Total monthly cost: under $50.

The key insight was separating data from presentation. The database holds structured financial data for 8,000+ tickers. The templates define how that data gets rendered into comparison pages. The AI fills in the gaps — generating human-readable analysis that's unique to each pair.

I won't go deep on the code here, but the architecture looks like this:

Data Layer (Supabase PostgreSQL)
    ↓
ETL Pipeline (Python + yfinance)
    ↓
Content Generation (Llama 3 local)
    ↓
Static Site Generator (Astro)
    ↓
CDN (Cloudflare)

Each layer is independent. If I want to swap Astro for Next.js, the data layer doesn't care. If I want to switch from Llama 3 to Claude, the templates don't change. This modularity ended up being really important when I needed to iterate fast.

What Worked

Long-tail coverage is insane. When your site has a page for literally every stock pair, you're catching searches nobody else bothers to target. "[Random small-cap] vs [other random small-cap]" has almost zero competition. Volume per page is tiny. Volume across 287,000 pages adds up.

Multilingual was easier than expected. Once you have the template and data pipeline, translating to 12 languages is mostly a matter of translating the template strings and regenerating. The data — numbers, tickers, percentages — stays the same. I used AI translation for the initial pass, then cleaned up the most important pages manually.

Schema markup at scale pays off. Every page gets FinancialProduct schema, FAQ schema, and BreadcrumbList markup. Programmatic means you write the schema once, it applies everywhere. This is one of those things that would be insane to do manually across 287k pages but is trivial when it's built into the template.

The build pipeline is surprisingly stable. I expected constant breakdowns with this many pages. But because everything is static and generated from structured data, there's very little that can go wrong at runtime. The site just serves HTML files. No server-side processing, no database queries on page load, nothing to crash.

What Didn't Work

Here's the thing nobody warns you about with programmatic SEO: Google doesn't want to index 287,000 pages from a brand new domain with zero backlinks.

Out of 287k pages, Google indexed about 2,500. That's a 0.9% index rate. Brutal.

The root causes were obvious in hindsight:

No domain authority. New domain, no backlinks, no brand recognition. Google had no reason to allocate crawl budget to my site when established financial sites exist.

Content similarity. While each page had unique financial data, the narrative sections followed similar patterns. Google's helpful content system flagged some pages as thin — not because they lacked information, but because the structure was too uniform across pages.

Crawl budget is real. Google physically will not crawl 287k pages on a new domain. I was watching Search Console and seeing Googlebot visit maybe 200-500 pages per day. At that rate, it would take years to crawl everything — and Google's not going to crawl pages it doesn't think are worth indexing anyway.

The Fix (What I'm Doing Now)

The solution is counterintuitive: fewer pages, not more.

1. Cut pages ruthlessly. I'm going from 287k down to 5,000-30,000 pages per language. Only keeping comparison pairs that have real search demand — validated with Search Console data and keyword research tools. If nobody searches for "[obscure penny stock] vs [other obscure penny stock]," that page doesn't need to exist.

2. Thicken remaining pages. Each surviving page needs genuine unique value beyond plugging different numbers into the same template. I'm adding sector context, historical trend analysis, dividend deep-dives, and custom AI-generated insights that are actually specific to each stock pair. The goal is that every page could stand on its own as a useful resource.

3. Build backlinks. There's no shortcut here. I started with directory submissions (boring but necessary), moved to industry-specific directories, and I'm now doing targeted outreach. The goal is DR 15+ within 6 months.

4. Optimize crawl budget. Better sitemap strategy — instead of one massive sitemap, I broke it into smaller topic-based sitemaps. Improved internal linking so Googlebot can discover important pages through the site structure, not just the sitemap. Removed low-value pages from the index with noindex tags.

The Numbers

Let me be transparent about where things stand:

Metric	Current
Total pages	287,000
Pages indexed	~2,500
Index rate	0.9%
Domain Rating	0
Backlinks	0
Monthly revenue	$0
Monthly cost	~$50

Not pretty. But here's why I'm still bullish on this approach:

The infrastructure works. The data pipeline works. The content generation works. The site loads fast, passes Core Web Vitals, and has proper schema markup on every page. The only thing broken is Google's trust — and that's a solvable problem with time and backlinks.

Once indexing improves, the growth should compound quickly. Each indexed page targets keywords that virtually nobody else is competing for. And with 12 languages, the addressable market is massive.

Lessons If You're Considering This

Start smaller than you think. If I could do it over, I'd launch with 5,000 pages instead of 287,000. Get those indexed, prove the model works, then scale up. Launching with hundreds of thousands of pages on a new domain is just asking Google to ignore you.

Your data source is your moat. Anyone can build a template. The hard part is finding a data source that's both comprehensive and accessible. Financial data via yfinance was a good choice because it's free, structured, and covers thousands of entities. Think about what data you can get that's hard for others to replicate at scale.

The template + AI hybrid is the sweet spot. Pure template-based pages (just plugging in data) get flagged as thin. Pure AI-generated pages are expensive and inconsistent. The hybrid — structured data rendered by templates with AI-generated narrative sections — hits the balance of unique content at scale.

Budget for backlink building from day one. I made the mistake of assuming great content would earn links naturally. It doesn't when you have zero domain authority. Build backlink acquisition into your launch plan, not as an afterthought.

Programmatic SEO is a patience game. This isn't a "launch and rank tomorrow" strategy. It's an infrastructure play. You're building a machine that compounds over time. The first 6 months will feel slow. That's normal.

What's Next

I'm documenting everything as I go — the full technical architecture, every prompt I use for content generation, the monetization roadmap, and all the mistakes so you don't repeat them.

I've packaged it all into a guide called the Programmatic SEO Blueprint. It covers niche selection, data architecture, AI content generation, the Astro/Next.js implementation, SEO infrastructure, the indexing problem and how to solve it, and monetization strategy. All code examples are MIT licensed.

If you're thinking about building something like this, I'd say go for it. Just start smaller than I did.

If you found this useful, follow me for more on building programmatic SEO sites. I'll be posting updates as the indexing situation improves.