AI Search Is Eating Web Traffic: What Developers and Agencies Need to Do About It

The deal web publishers had with Google was simple: create content, get traffic. Google indexed it, ranked it, and sent visitors. That deal is changing.

Google AI Overviews answer informational queries directly in search results, pulling from indexed pages without necessarily sending traffic to them. Perplexity builds answers from cited sources but keeps users inside its interface. ChatGPT’s web search mode answers questions with brief citations at the bottom. The query gets answered, but the click that used to follow doesn’t always happen.

This isn’t speculation anymore. Publishers across verticals have reported meaningful changes in referral traffic from search for informational content. The pattern is specific: tutorial-style content (“how to do X”), definition content (“what is X”), and listicle content (“best tools for X”) are seeing the sharpest impact. Opinionated takes, case studies, and data-backed analyses are holding better.

For agencies and developers who run content programs, this is a shift worth understanding clearly.

What’s Actually Happening

Three separate things are happening simultaneously, and it helps to separate them.

AI Overviews in Google Search appear above organic results for queries Google classifies as informational. They’re generated from web content but don’t always trigger a click through to the source. Google has stated it prioritizes sources for overviews, but citation doesn’t guarantee traffic.

Perplexity and ChatGPT Search are alternative search interfaces that a growing slice of users choose over Google for research queries. These tools typically cite sources more explicitly than Google AI Overviews, and some portion of their users do click through, though the user base is smaller than Google’s.

Zero-click rates were already rising before AI Overviews, driven by featured snippets, Knowledge Panels, and People Also Ask. AI Overviews accelerate an existing trend rather than starting a new one.

The net effect is concentrated on the middle of the funnel: informational content that used to drive awareness and early consideration is generating fewer visits from organic search.

What Still Works

Not all traffic is declining equally. Content that doesn’t get swept up in AI-generated answers still drives visits.

Specificity defeats the overview. AI Overviews handle general questions well. “How does JWT authentication work?” gets summarized. “How do I configure Auth.js v5 with Drizzle ORM and a Next.js App Router project?” is specific enough that a direct, detailed answer exists in one place, and a user with that problem will click through to find it.

The practical implication: go narrower. Instead of “how to optimize a PostgreSQL query,” write “how to diagnose an n+1 query in Django with django-debug-toolbar.” The specific answer doesn’t fit in a summary box.

Opinion, experience, and case studies. AI tools can summarize claims, but they can’t generate original experience. A post titled “We migrated from Prisma to Drizzle and here’s what we learned” contains first-person data that doesn’t exist anywhere else. It can’t be replaced by a synthesis.

Recency for fast-moving topics. A post published the week Bun 2.0 ships, or the day a framework releases a security patch, is faster than any AI knowledge cutoff. Time-sensitive content gets traffic before the AI tools catch up.

Tool comparisons with current pricing. AI Overviews use training data with cutoff dates. Pricing tables, benchmark comparisons, and feature matrices go stale. A detailed comparison of Vercel vs Cloudflare Pages pricing from last week isn’t in any AI’s training data.

Content that readers want to save, share, or reference. Long-form guides, checklists, and reference materials get bookmarked and linked. That link signal still matters for rankings, and bookmarked content gets revisited regardless of search.

How AI Search Decides What to Cite

Understanding how Perplexity and ChatGPT Search select sources helps you write content that gets cited rather than ignored.

Structured, factual claims. AI citation algorithms favor content with clear, specific claims stated directly. “Fastify handles approximately 70,000 requests per second on a standard Node.js benchmark” is more citeable than “Fastify is very fast.”

Clean HTML structure. AI crawlers parse your page the same way screen readers do: headings, paragraphs, lists, and tables. Dense prose with few semantic markers is harder to extract. Use <h2>, <h3>, <ul>, and <table> deliberately.

Authoritative signals. Domain authority still matters. Being cited once by a high-authority source creates a feedback loop. If Perplexity cites you in an answer, users who click through to your site may link to you, which improves your ranking in traditional search results, which improves your chance of being cited again.

Freshness. AI search tools crawl frequently and often prioritize recent content. Dates in your frontmatter matter. A post with a 2024 publish date loses to a 2026 equivalent on queries where recency matters.

Structured Data for AI Discoverability

Schema.org markup doesn’t directly affect AI Overviews, but it improves how Google understands and classifies your content, which indirectly affects which pages get included in AI-generated answers.

For technical blog posts, Article schema is the baseline:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "Fastify in 2026: The Node.js API Framework That Stayed When Everyone Left",
  "datePublished": "2026-06-14",
  "dateModified": "2026-06-14",
  "author": {
    "@type": "Person",
    "name": "Anurag Verma"
  },
  "publisher": {
    "@type": "Organization",
    "name": "CoderCops"
  },
  "description": "..."
}
</script>

For FAQ-style content, FAQPage schema makes the Q&A structure explicit:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "When should I use Fastify instead of Express?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Use Fastify when you need schema-based validation, automatic OpenAPI documentation generation, or are building a high-throughput API where JSON serialization speed matters."
      }
    }
  ]
}
</script>

Note: Google’s documentation explicitly states that FAQ schema doesn’t guarantee a featured snippet or AI Overview inclusion. It’s one signal among many.

What to Track Now

The standard metric, organic sessions from Google, is becoming a lagging indicator. It captures clicks but not impressions or citations.

Add to your tracking:

• Google Search Console impressions (not just clicks). If impressions hold but clicks drop, that’s an AI Overview pattern: your content is being seen in summaries but not clicked.
• Referral traffic from Perplexity, ChatGPT, and other AI search tools. These show up as referral sources in your analytics when users do click through.
• Direct traffic changes. Some AI-cited content drives brand searches and direct visits, not tracked as organic.
• Branded search volume. If your brand name appears in AI answers as a citation, branded search typically increases.

Stop optimizing for:

• Keyword density. AI Overviews don’t care about keyword repetition; they care about clear, accurate answers.
• Exact-match anchor text. The link graph still matters, but anchor text optimization is increasingly irrelevant.
• Thin pages targeting long-tail keywords. These were already losing to featured snippets; AI Overviews accelerate that.

The Agency Angle

For agencies running content programs for clients, the conversation is shifting from “get on page one” to “get cited in AI answers.”

Those are related but different goals. Page one requires backlinks and authority at scale. Getting cited in an AI answer requires being the clearest, most specific, most structured source on a topic.

That means:

Depth over breadth. Ten well-researched, specific posts beat a hundred thin ones. The specific posts get cited; the thin ones get absorbed.

Update discipline. A post with accurate current information beats a better-written post with stale facts. Building in a quarterly review of high-traffic posts to update pricing, version numbers, and statistics is now table stakes.

Original data. Surveys, benchmarks, case studies, and analysis of proprietary data are the formats least replaceable by AI summaries. If your agency runs a survey of 200 clients about their AI budgets, that data exists nowhere else and will get cited.

The underlying point: the content that’s always worked (genuinely useful, specific, authoritative, kept current) works better than ever. What’s changing is that generic SEO content, written to rank rather than to help, is getting competed away by AI systems that are very good at generic answers. The bar for what earns traffic has moved up.

That’s uncomfortable for content programs built on volume. It’s straightforward for teams that were already writing things worth reading.