CTR After SGE: Testing Schemas, FAQs, and Comparisons So AI Overviews Still Send Your Blog Clicks

Google’s AI Overviews (formerly SGE) have turned the classic SEO game on its head.

You can do everything “right”:

• Rank on page one
• Earn a featured snippet
• Build a solid backlink profile

…and still watch clicks flatten because an AI summary answers the query right on the results page.

If your blog is a key acquisition channel, that’s not a small problem. It’s the difference between:

• A compounding traffic engine that feeds pipeline
• A content budget that’s suddenly hard to justify

The good news: you’re not powerless.

AI Overviews still need sources. They still surface links. And they still reward sites that:

• Structure content clearly
• Answer questions directly
• Offer rich, trustworthy information that’s easy to parse

This post is about how to do exactly that—so your content isn’t just “included” in AI Overviews, but actually earns the click.

We’ll dig into three levers you can control:

1. Schemas: making your content machine-readable
2. FAQs: aligning with how people actually ask questions
3. Comparisons: giving AI Overviews a reason to show (and prefer) your content

And we’ll talk about how an AI-powered platform like Blogg can help you test and scale all of this without turning your week into a schema science project.

---

Why CTR After AI Overviews Is Its Own Problem

Before AI Overviews, SEO was mostly about ranking. If you could break into the top 3, your click-through rate (CTR) was fairly predictable.

Now, you can:

• Rank in the top 3
• Still appear in the AI Overview citations
• And yet get fewer clicks than you did a year ago

Why?

Because the job of the AI Overview is to reduce the need to click.

So your new job is to:

Make your content the best possible next step after the overview.

That means:

• Rich, structured answers that are easy for Google’s systems to parse and trust
• Specificity that goes beyond what a summary can reasonably include
• Formats (tables, comparisons, workflows, calculators, checklists) that give a clear reason to visit your site

If you’ve read our post on the “Question Cloud” technique, you’ve already seen a version of this: you win by becoming the most complete, most structured resource around a problem.

AI Overviews just raise the bar.

---

Step 1: Use Schemas to Make Your Content AI-Legible

Schemas (structured data) were already important for rich results. With AI Overviews, they become your API contract with Google.

The Schemas That Matter Most for CTR

You don’t need every schema type under the sun. Focus on the ones that:

• Clarify what the page is
• Clarify who it’s for
• Clarify how it compares to alternatives

For most B2B and SaaS blogs, that means:

• Article / BlogPosting: baseline for blog content
• FAQPage: for pages with clear question–answer sections
• HowTo: for step-by-step guides
• Product and Offer: for product or pricing pages
• ItemList: for comparison or roundup pages

You’re not adding schema “for Google.” You’re adding schema so that AI systems can see the same structure you see.

A Simple Schema Testing Workflow

You don’t have to refactor your entire blog in one go. Treat this like an experiment.

1. Pick a test cluster
   Choose 3–5 posts that:

   • Already get impressions from queries likely to trigger AI Overviews
   • Are high-intent (commercial or problem-aware queries)

2. Add or upgrade schema

   • Mark the page as Article or BlogPosting
   • Add FAQPage schema for any FAQ sections
   • Use HowTo for clear step-by-step tutorials

3. Validate

   • Use Google’s Rich Results Test
   • Fix any errors and warnings

4. Monitor CTR deltas
   In Google Search Console:

   • Filter to those URLs
   • Compare CTR before and after implementation (give it at least 4–6 weeks)

5. Scale what works
   If you see improved CTR or more impressions for AI-Overview-prone queries, roll the same pattern out to the rest of your content.

This is exactly the kind of repetitive, structured work that an AI engine like Blogg can help standardize. Once you’ve defined your schema patterns, you can bake them into your templates so every new post ships with the right structure.

---

Step 2: Turn Real FAQs into AI-Friendly Answer Blocks

AI Overviews are, at their core, answer engines.

If you want to show up as a cited source—and earn the click—you need content that:

• Mirrors the way people actually ask questions
• Provides concise, quotable answers up top
• Offers depth and nuance underneath

Where to Find the Right Questions

Your best FAQ material rarely comes from keyword tools alone. It comes from:

• Support tickets
• Sales call transcripts
• NPS comments and surveys
• Live chat logs

If you’ve read our post on turning NPS data into SEO themes, you know how powerful this is: From NPS Comments to Content Calendar.

Those sources give you:

• The exact phrasing customers use
• The real objections they care about
• The context around each question

Perfect raw material for AI-friendly FAQs.

How to Structure FAQs for AI Overviews

For each key question:

1. Use the question as a subheading

   • H2 or H3: How does X compare to Y for [use case]?

2. Lead with a 1–3 sentence answer

   • Direct
   • Neutral in tone
   • Specific

3. Follow with depth

   • Bullet points
   • Short paragraphs
   • Visuals or tables where helpful

4. Mark it up with FAQ schema

   • Use FAQPage JSON-LD for the main Q&A pairs

This gives AI Overviews two reasons to pick your content:

• The structure makes it easy to parse and quote
• The clarity makes it a safe, trustworthy answer

Turn FAQs into a Content Flywheel

Once you have a strong FAQ corpus, you can:

• Spin individual FAQs into full posts
• Group related FAQs into pillar pages
• Use AI (or Blogg) to:
  • Cluster questions
  • Draft answers
  • Suggest related content

If you want a deeper walkthrough of this idea, check out our post on building a question-first content engine. It’s essentially the same strategy—but now tuned for an environment where AI Overviews are the first reader.

---

Step 3: Use Comparisons to Create “Next-Step” Clicks

AI Overviews are great at summarizing. They’re worse at:

• Nuanced tradeoffs
• Edge-case scenarios
• Context-specific recommendations

That’s where comparison content shines.

Why Comparison Pages Are CTR Magnets

When someone searches:

• “X vs Y for enterprise teams”
• “Best alternatives to X for small businesses”
• “X pricing vs Y pricing”

They’re not just information-seeking. They’re decision-seeking.

AI Overviews may summarize the landscape, but users still need:

• Deeper breakdowns
• Real examples
• Use-case-specific guidance

If your comparison content is the most structured, most balanced resource in the set, you’re far more likely to:

• Be cited in the overview
• Earn the click from users who want to go deeper

How to Structure Comparison Content for AI Overviews

For each comparison page:

1. Start with a neutral summary

   • 2–3 sentences that fairly describe both options
   • Avoid obvious bias in the opening; save your opinion for later

2. Use consistent, scannable sections
   For example:

   • Overview
   • Core features
   • Pricing
   • Best for
   • Limitations

3. Include a structured comparison table

   • Columns: Product A, Product B (and maybe yours)
   • Rows: Key criteria (pricing, implementation time, integrations, support, etc.)

4. Add scenario-based recommendations

   • “Choose X if…”
   • “Choose Y if…”

5. Mark up with ItemList or Product schema where appropriate

The goal is to make your page the canonical explainer that AI systems can safely lean on—because it’s clear, balanced, and deeply structured.

This is also a perfect place to connect back to jobs-to-be-done thinking. Your comparison content should map to the jobs buyers are trying to get done, not just feature lists. Our post on the “Jobs, Not Journeys” content map goes deeper on how to frame content around real tasks.

---

Measuring Whether Your AI-Overview CTR Work Is Actually Working

All of this effort—schemas, FAQs, comparisons—only matters if it moves the numbers.

You don’t need a giant dashboard. You do need a focused scorecard that answers:

Are AI Overviews hurting our CTR, and are our experiments clawing that back?

The Core Metrics to Watch

In Google Search Console, focus on:

• CTR by query
  • Especially for queries likely to trigger AI Overviews
• CTR by page
  • Before and after adding schema or restructuring content
• Average position
  • To make sure CTR changes aren’t just ranking changes
• Impressions for long-tail, question-based queries
  • To see if FAQs and structured answers are increasing visibility

If you want a simple framework for turning these into a recurring report, our post on metrics that actually matter walks through a lightweight scorecard you can reuse.

How AI Can Help You Iterate Faster

A platform like Blogg can help you:

• Identify posts with falling CTR despite stable rankings
• Suggest schema types based on the content structure
• Generate FAQ blocks from existing copy and support data
• Propose comparison sections where they’re currently missing

Instead of manually auditing 200+ posts, you can:

• Define your schema and FAQ patterns once
• Let AI scan your archive for candidates
• Ship updates in batches

That’s how you keep up with an environment that’s changing faster than any human-only workflow can match.

---

Putting It All Together: A Practical 30-Day Plan

If you want to protect (and grow) CTR in the era of AI Overviews, here’s a simple 30-day plan you can follow.

Week 1: Baseline and Prioritization

• Export top 100–200 queries from Search Console
• Flag queries that are:
  • Question-based
  • Comparison-focused
  • Likely to trigger AI Overviews
• Identify 10–15 URLs that:
  • Drive meaningful traffic
  • Map to those high-risk queries

Week 2: Schema and FAQ Upgrades

For those 10–15 URLs:

• Add or refine Article / BlogPosting schema
• Add FAQPage schema for any Q&A sections
• Convert suitable posts into HowTo where it makes sense
• Tighten headings and intro paragraphs to be answer-first

Week 3: Comparison and Depth Enhancements

• Identify 3–5 comparison or “X vs Y” opportunities
• For each:
  • Add a neutral summary
  • Create a structured comparison table
  • Add scenario-based recommendations
  • Mark up with ItemList or Product schema where relevant

Week 4: Review, Measure, and Systematize

• Compare CTR for target URLs vs. your baseline (accept that you may need 4–6 weeks for full effect)
• Note which patterns correlate with:
  • Higher CTR
  • More impressions for question-based queries
• Turn those patterns into templates and checklists so every new post ships AI-Overview-ready by default

This is where having Blogg as your publishing engine pays off: once the pattern is clear, you can encode it into your workflows so every future post:

• Ships with the right schema
• Includes AI-friendly FAQ blocks
• Uses comparison and structure to give AI Overviews a reason to send you clicks

---

Summary: AI Overviews Don’t Have to Be a Traffic Tax

AI Overviews change the mechanics of search, but they don’t change the fundamentals:

• People still have jobs to be done
• They still need depth, nuance, and context
• They still click when a result clearly promises “the next step” they need

To keep your CTR healthy, focus on:

• Schemas: Make every important post machine-readable with the right structured data types.
• FAQs: Turn real customer questions into clear, answer-first sections that AI systems love to quote.
• Comparisons: Build balanced, structured comparison content that turns AI summaries into clicks for you, not just complete answers on the SERP.

Do this consistently and your blog doesn’t just survive AI Overviews—it becomes one of the sources those overviews depend on.

---

Where to Go From Here

If you’re already juggling product launches, sales support, and a lean marketing team, keeping up with AI Overviews can feel like “one more thing.”

It doesn’t have to be.

Start small:

• Pick 5–10 high-value posts
• Add the right schemas
• Layer in real FAQs
• Tighten your comparisons

Then, once you see what works, let AI handle the repetition.

Platforms like Blogg exist so you can:

• Set your topics and preferences
• Encode your schema and FAQ patterns once
• Have new, SEO-optimized posts—and refreshed older ones—publish on schedule

While you stay focused on running the business, your blog can stay:

• Structured for AI
• Helpful for humans
• And ready to earn the click, even when the first answer shows up before anyone leaves Google.

If you’re serious about keeping your blog visible and valuable in an AI-shaped search experience, this is the moment to start.

Take the first step: pick those 5–10 posts, run the schema and FAQ play, and see what happens. Then decide whether you want to keep doing it by hand—or let an engine like Blogg do the heavy lifting while you set the strategy.