%20(1).jpg)
Google Discover Traffic Down 2026? Blogger-Specific Fix
If your Blogger site's Discover traffic collapsed sometime after February 2026 and you went looking for a fix, you've probably run into the same problem everyone else has: every guide assumes you're on WordPress with a plugin that handles your Open Graph tags, image markup, and robots directives automatically. Blogger has none of that. Here's what actually changed in Discover this year, and the specific, no-plugin fixes for a Blogger theme.
What Actually Happened to Discover in 2026
Two separate events explain most of the traffic swings publishers have seen this year. First, Google rolled out a Discover-focused algorithm update in February 2026 that weighted content freshness, topical depth, and engagement signals more heavily than before — some sites lost around 40% of impressions almost overnight, while others gained traffic they'd never seen. Second, a serving bug in March 2026 caused separate 60–80% impression drops for thousands of publishers, unrelated to content quality; Google acknowledged the bug but didn't commit to a fixed resolution timeline. If your drop happened specifically in that window, it may be at least partly the bug rather than something you did — but the technical checklist below is worth working through either way, since it addresses both.
Step 1: Check Your Discover Report Before Changing Anything
In Search Console, go to Performance → Discover. If you don't see this report at all, your site hasn't had meaningful Discover traffic yet, which is a different problem than a drop. If you do see it, check whether impressions cratered specifically in February or March 2026 — that timing tells you whether you're likely dealing with the algorithm update, the serving bug, or a separate site-specific issue.
Step 2: Add the Large-Image Preview Directive (Blogger Skips This by Default)
Discover's large image card — the format that actually drives clicks — requires the max-image-preview:large directive in your robots meta tag. Blogger's default theme output does not include this. Add it manually inside your theme's <head> section:
<meta content='max-image-preview:large' name='robots'/>
Without this line, Google can still show your content in Discover, but typically only as a small thumbnail — which converts to clicks at a meaningfully lower rate than the large card format.
Step 3: Fix Your Featured Image Requirements
Discover's large card has minimum image requirements that a lot of free Blogger templates don't meet by default: at least 1200px wide, and enabled for indexing (not blocked via robots or noindex on the image itself). In your post's HTML, confirm your featured image tag looks like this, with real width and height attributes rather than being left to CSS alone:
<img src="your-image-url.jpg" width="1200" height="675" alt="descriptive alt text" />
A 16:9 or 4:3 aspect ratio is the safest choice — Discover tends to crop unusual ratios in ways that cut off important parts of the image.
Step 4: Verify Open Graph Tags Are Actually Correct
Blogger auto-generates some Open Graph metadata, but it's not always reliable — particularly og:image, which can default to your blog's favicon or a random inline image if your theme isn't explicitly setting it. Add this explicitly in your theme's head section, tied to your post's featured image data tag:
<meta expr:content='data:blog.postImageUrl' property='og:image'/> <meta expr:content='data:blog.pageTitle' property='og:title'/>
Test the result on individual post URLs using Facebook's Sharing Debugger or a similar Open Graph validator — it will show you exactly what image and title Discover-adjacent systems are actually reading, which is often different from what you assume your theme is outputting.
Step 5: Article Schema — Don't Duplicate What You've Already Set Up
Article schema and author E-E-A-T signals matter for Discover the same way they matter for AI Overview citations. If you haven't already implemented this on your Blogger theme, don't rebuild it from scratch here — we've already covered the full JSON-LD implementation, including Blogger's no-head-injection workaround, in How to Rank in Google AI Overviews With a Blogger. The same schema block serves both purposes.
Step 6: Stop Publishing Across Random Topics on One Blog
This is the fix most Blogger-specific guides miss entirely. Discover uses a domain-level publisher identity model — it evaluates your blog's overall publishing history and topic consistency, not just individual post quality, before deciding whether to trust it as a Discover source. A Blogger site that jumps between, say, tech news, recipes, and travel diaries under one URL sends a weaker consistency signal than a site that stays within one or two clearly related topic clusters. If your Blogger site has historically been a mixed-topic personal blog, this is worth knowing before you assume a technical fix alone will solve a Discover drop — the fix in that case is editorial, not code.
Step 7: Rule Out Core Web Vitals as a Contributing Factor
Slow LCP and layout shift limit Discover distribution the same way they limit regular Search visibility. Blogger themes — especially free ones — commonly have render-blocking scripts and unoptimized ad loading that hurt this. If you haven't audited this recently, our guide on why your Blogger page speed is low covers the specific script and image issues that show up most often on Blogger templates.
Step 8: Avoid Clickbait Titles Specifically Now
The February 2026 update is reported to penalize title-and-content mismatches more aggressively than before. On Blogger, it's easy to let your post title (used for both the URL slug and Discover's headline) drift toward something punchier than what the article actually delivers. Keep the Discover-facing headline declarative and accurate — front-load the actual value rather than teasing it.
Bottom Line
Most "why did my Discover traffic drop" guides are written assuming a plugin handles half of this automatically. On Blogger, none of it is automatic — but none of it requires custom development either. Work through the robots meta tag, image dimensions, Open Graph tags, and topic consistency in that order, give it two to four weeks (Discover fluctuations often self-correct on that timeline once the technical issues are fixed), and check the Discover report in Search Console weekly rather than daily to avoid reacting to normal day-to-day noise.
