Getting Google Impressions but Few Clicks? How to Diagnose and Improve Your WordPress Site's Performance — and Why AI Answers Are Stealing Your Traffic

TL;DR High impressions with a low CTR is often a SERP problem, not a content problem. The diagnosis runs on two tracks: technical and on-page work on WordPress, plus the AI layer. The order matters: GSC first, then Core Web Vitals and TTFB, then AI visibility, and only then titles and meta. AI Overviews cut position-1 CTR by around 58% (Ahrefs, Dec 2025), and the effect shrinks as you go down the page. Semly measures how your brand shows up in ChatGPT, Gemini, Claude, Grok, Perplexity and Google AI Mode, and you can start with a free report.

You open Google Search Console, see impressions climbing, and then you look at clicks. Flat. Or worse, falling. Your first instinct is to blame the content. Sometimes that is right. But more and more often, the problem is not your page at all. It is the search results page itself, and the AI answers sitting on top of it.

This guide walks you through a simple, repeatable way to figure out which one you are dealing with. You will check your data, your WordPress performance, your AI visibility, and your on-page basics, in that order. No guesswork, no panic.

Impressions but few clicks: what's actually happening

Let's start with the frame. When you see impressions but few clicks, there are really only two places the problem can live.

The first is on your side. Your page ranks, but the title does not match what people want, the page loads slowly, or several of your own URLs compete for the same query. That is a fixable, on-page problem.

The second is in the SERP. Your page ranks fine, but the click never reaches you because someone else took it. That someone is usually an AI Overview, a featured snippet, or a zero-click answer that satisfies the query before anyone scrolls.

CTR in GSC is simply clicks divided by impressions. It is a useful number, but it is not a ranking score. A page can rank first and still get very few clicks. That gap is the whole point of this article.

Here is the uncomfortable part. Even queries without an AI Overview are losing clicks. Seer Interactive found organic CTR for non-AI Overview queries dropped about 41% year over year (Seer, 2025). So this is not only about AI Overviews. It is a broader shift in how people search, including ChatGPT, social, and direct visits.

Watch out: do not assume AI Overviews caused your drop just because the timing feels right. Seer and Semrush both openly question the simple causal story. Semrush even found zero-click rates for the same queries went slightly down, not up, after AI Overviews appeared (Semrush, 2025). Treat the AI explanation as a hypothesis you test, not a fact you assume.

Before you start: what you need and when this guide won't help

This workflow works best when you have a few things ready:

• Access to Google Search Console with at least 3 months of data.
• PageSpeed Insights and CrUX for real-user performance data.
• A list of your top 20 pages by impressions.
• Access to your WordPress setup: hosting, plugins, and page builder.
• An account in a tool that measures AI visibility, so you can check the second track.

Now the honest part. This guide will not help much if:

• Your domain is brand new (under 3 months). You do not have enough data yet.
• You are in the middle of a migration. Fix the migration first.
• You are seeing a seasonal spike or dip. Compare year over year, not month over month.
• You have a manual penalty. That is a different problem with a different fix.

If any of those apply, handle that first. Then come back.

Step 1 — Read your GSC data the right way

Your goal here is simple: separate a content problem from a SERP problem.

1. Open the Queries report in GSC.
2. Sort by impressions, highest first.
3. Look for queries with high impressions and a CTR that feels low for their position.
4. Split branded from non-branded queries. They behave very differently.
5. For your worst offenders, check the live SERP. Is there an AI Overview or a featured snippet?

That last step is where most people stop too early. You need to know whether the click is being taken by a SERP feature or by your own messy setup.

There are two kinds of cannibalization to tell apart:

• URL cannibalization: several of your own pages target the same query. Google picks one, and your clicks scatter.
• SERP feature cannibalization: one page ranks well, but an AI Overview or snippet answers the query and the click never comes.

Same symptom, very different fix.

Watch out: branded and non-branded CTR move in different directions. Advanced Web Ranking data suggests branded desktop CTR actually rose in late 2025, while non-branded and informational queries took the hit (AWR, 2026). Do not average them together and call it a trend.

Step 2 — Check Core Web Vitals and TTFB on WordPress

Now the technical track. Slow pages lose twice: they can rank lower and they get fewer clicks when they do rank.

Where to look:

• PageSpeed Insights for lab and field data.
• CrUX for real-user numbers.
• GSC under Core Web Vitals for a site-wide view.

What to watch: LCP, INP, CLS, and TTFB. Across the web, only about 49.1% of mobile origins pass all three Core Web Vitals (PageSpeed Matters, CrUX May 2026). WordPress does a bit better on desktop than mobile, but its real weak spot is TTFB. Only around 33.2% of WordPress origins have a good TTFB on desktop, and just 24.2% on mobile (Hostingstep, June 2026).

That is the number to remember. WordPress is usually responsive (INP is fine), but slow to start responding. That points at hosting, not at the CMS itself.

Your biggest levers, in order:

1. Hosting. This is the foundation. A weak host caps everything else.
2. Images. Compress and resize. Mobile WordPress pages carry a lot of image weight.
3. Page builder. Some builders pass Core Web Vitals far more often than others.
4. Plugin bloat. Fewer, lighter plugins.
5. Fonts and scripts. Load only what you need.

Checklist:

• Run PageSpeed Insights on your top 5 pages.
• Check TTFB in CrUX or your host's dashboard.
• Compress and resize oversized images.
• Audit plugins and remove unused ones.
• Review your page builder's performance reputation.
• Limit web fonts and third-party scripts.
• Re-test after each change, one at a time.
• Compare GSC CTR before and after.

Fix hosting and images first. Do not start with a "cache plugin" and hope it covers everything.

Step 3 — Measure your visibility in AI answers

This is the track most WordPress owners skip. Classic CTR cannot tell you whether your brand appears in AI answers at all. You can rank well and still be invisible in ChatGPT, Gemini, or Google AI Mode.

So how do you measure something with no ranking? You track prompts, sources, competitors, and sentiment. You look at whether you are mentioned, how often, and in what context. And you separate two things that sound similar but are not:

• Being cited: a model links to your page as a source.
• Being visible: your brand shows up in the answer itself, even without a link.

Semly is built for exactly this. It monitors how your brand appears in ChatGPT, Gemini, Claude, Grok, Perplexity, and Google AI Mode. Its Sources module shows which domains and URLs the models actually cite, so you can see where you are missing. The Leon AI Agent adds a layer of recommendations and content generation on top. And if you want a starting point without spending anything, the free AI visibility report at report.semly.ai gives you a baseline across models in a couple of minutes.

For WordPress and WooCommerce, Semly connects through an application password, so there is no plugin to install or maintain.

Watch out: AI visibility moves slowly. Expect a 2 to 6 week lag between a change and a measurable result, and treat 3 to 4 months as the minimum sensible measurement window (Semly, 2026). Do not judge a fix after one week.

Step 4 — Fix the on-page basics that still move CTR

Only now do you touch titles and meta. Doing this first is the most common mistake, because you are optimizing the wrong layer.

Work in this order:

1. Title and meta description. Match the query intent, not just the keyword.
2. Content-to-query fit. Does the page actually answer what people searched for?
3. Schema markup. FAQ, Product, and Article schema help both search and AI systems understand your page.
4. Internal linking. Point related pages at each other to spread authority.
5. Index hygiene. Clean up index bloat and thin content that drags your site down.

How to measure the effect: use GSC, compare equal periods, and change one thing at a time. A before-and-after example is useful as an illustration, not as a promise. Your results will depend on your niche, your competition, and your starting point.

Step 5 — Make your WordPress site readable for AI crawlers

Here is a quiet problem that can cut your site off from the AI layer entirely.

AI crawlers have three distinct roles, and each has its own token:

• Training: GPTBot, ClaudeBot, Google-Extended.
• AI search indexing: OAI-SearchBot, PerplexityBot, Applebot.
• User-triggered fetch: ChatGPT-User, Perplexity-User.

Blocking "OpenAI" is not one decision. It is several.

The sneaky part is silent blocking. A 403, 429, or 503 response to a bot never shows up in robots.txt. The telltale sign is a page that loads fine in your browser but returns an error to the crawler. Cloudflare, WAF rules, and security plugins like Wordfence are common culprits. Also remember that robots.txt changes can take around 24 hours to propagate (Semly, 2026).

What not to do:

• Do not block Googlebot. It handles classic indexing and feeds AI Overviews. Blocking it costs you normal search traffic.
• Do not treat Google-Extended or Applebot-Extended as crawlers. They are control tokens. They never send a request and will never appear in your logs.
• Do not treat llms.txt as a fix. Current evidence shows no measurable citation impact. It is a nice addition, not a repair.

Common mistakes and how to fix them

• Changing titles without checking intent → Read the live SERP first, then rewrite.
• Optimizing plugins instead of hosting → Fix hosting and images before anything else.
• Mixing branded and non-branded data → Split them in GSC and analyze separately.
• Concluding "AI takes everything" without data → Measure your AI visibility before you decide.
• Blocking bots "just in case" → Check each token's role and block only what you mean to.
• No measurement after changes → Set a baseline and compare equal periods.
• Confusing correlation with causation → Test one variable at a time.
• Judging AI visibility too early → Give it 2 to 6 weeks, and 3 to 4 months for a real read.

What to do next

Here is the sequence that works.

Start with your WordPress fundamentals and on-page basics. In parallel, set up AI visibility measurement so you are collecting data while you fix things. Then, if CTR keeps falling even with good Core Web Vitals and no AI Overviews in sight, dig into query intent and SERP features. That is your signal to look deeper.

And update your KPIs. CTR alone is no longer enough. Add share of voice in AI citations, branded search lift, and assisted conversions next to it. That gives you a fuller picture and something you can actually show your leadership team.

The easiest first step is the free AI visibility report at report.semly.ai. It gives you a baseline across models. From there, you can track prompts and sources over time and see whether your work is moving the needle.

Mini glossary

• CTR: clicks divided by impressions. A ratio, not a ranking.
• Zero-click search: a search that ends without a click to any website.
• AI Overviews: Google's AI-generated summary at the top of some results.
• GEO / AEO: optimizing for visibility in generative and answer engines.
• TTFB: time to first byte. How fast your server starts responding.
• LCP: largest contentful paint. How fast the main content loads.