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

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":

1. Google shows an AI Overview at the top — a synthesized answer pulling from multiple sources
2. Below that, maybe some People Also Ask boxes
3. 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:

1. CTR at position — If I'm ranking position 5-10 and CTR drops, it likely means an AI Overview is absorbing clicks
2. Impression-to-click ratio by query type — Long-tail financial queries vs. branded queries
3. Schema validation rate — Percentage of pages passing Google's Rich Results test
4. AI citation monitoring — Searching key queries in Perplexity and ChatGPT to check if StockVS pages are cited
5. 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:

1. Schema everything — dateModified, author, about, domain-specific types. Make your data machine-readable.
2. Lead with data — Put key facts and metrics above the fold in scannable formats. AI extracts from the top of your content first.
3. Match conversational queries — Rewrite FAQs to match how people ask AI assistants, not how they type into Google.
4. Generate unique analysis — Original data points are your citation moat. If your page says what everyone else's says, AI won't cite you.
5. Go multilingual — Non-English AI search is wide open. If your data works in other languages, translate and localize it.
6. 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