Google Search Console Gets New Features: Recommendations and Site-Wide Signals

Google Quietly Made Its Most Useful Free Tool Better — And Almost Nobody Noticed

Search Console is the only place Google tells you, in its own words, how your site performs in its own results. It is free, it is first-party, and most business owners open it twice a year — once when a developer asks them to verify a property, and once when traffic drops and a panic sets in. The rest of the time it sits unused while people pay for tools that estimate, from the outside, the data Search Console hands you for nothing from the inside.

Over the back half of 2025, Google rolled a set of changes into the platform that are worth a second look. The headline addition is a Recommendations surface — Search Console now points at specific things on your site worth acting on, rather than leaving you to find them. Alongside it came performance-data improvements: fresher, more granular numbers, and a steady consolidation of insights so the useful signals are less buried. None of this is revolutionary. All of it is the kind of incremental sharpening that makes the difference between a tool you check and a tool you actually work in.

This is a practitioner's read on what changed and, more importantly, on the workflows that were always there and almost nobody runs. The recommendations are the news. The performance report is the gold, and it has been the gold the whole time. We'll cover both, and we'll be honest about the edges where Search Console still can't see — because knowing the blind spots is what separates using the tool from trusting it blindly.

The New Recommendations: Helpful Nudges, Not a Strategy

The Recommendations feature does what the name says. Instead of presenting raw reports and trusting you to interpret them, Search Console now surfaces cards that say, in effect, here is something on your site worth your attention, and here is the report that proves it. A recommendation might flag a query you already rank for on page two and could realistically push onto page one, a page collecting impressions for a topic you haven't fully covered, or a structured-data opportunity on a template that qualifies for richer results.

The value here is triage, not insight. Everything a recommendation points at was already discoverable in the performance and enhancement reports — the feature's job is to shorten the distance between data and action for people who would never have gone digging. For an owner who logs in, sees three cards, and clicks into one, that's a real upgrade over a blank dashboard.

The honest framing is that recommendations are a starting point and nothing more. They are pattern-matched suggestions, not a prioritized plan that knows your margins, your sales cycle, or which keyword actually converts. A recommendation to chase a near-page-one query is only worth acting on if that query brings buyers; Search Console has no idea whether it does. So treat the cards as a prompt to open the underlying report, then apply your own judgment about which ones are worth the work. Used that way, they're a genuinely good front door. Followed blindly, they're a to-do list that optimizes for movement over money.

The Performance Report Is the Whole Game — Here's How to Mine It

If you only ever learn one thing in Search Console, make it the performance report. It shows you the exact queries people typed to reach your site, which pages they landed on, your average position for each, your impressions, your clicks, and your click-through rate. That is the closest thing to ground truth about your organic visibility that exists, and it comes straight from the search engine.

Start with the queries tab and sort by impressions. These are the searches where Google already considers you relevant enough to show. Now layer in position and click-through rate. A query with thousands of impressions, a position of 8, and a near-zero CTR is telling you something specific: Google shows you, and nobody clicks, because you're sitting at the bottom of page one where almost no clicks live. That's not a content problem — that's a ranking-improvement target.

Switch to the pages tab and you get the mirror image: which URLs earn impressions and clicks, and which ones Google shows but users skip. A page pulling impressions with a weak CTR often has a title and meta description that don't match what searchers want — a rewrite you can ship in an afternoon, no new content required. Then combine the two. Click a single page and Search Console shows every query that page ranks for. This is where you discover that one article is quietly ranking for a dozen searches you never targeted, several of which deserve their own section or their own page entirely.

The whole report runs on filters and comparisons, and that's the part people skip. Filter to a single page, a single query pattern, a country, a device. Sort by the metric that matches your goal. Five minutes of this most weeks tells you more about your real SEO position than any third-party rank tracker, because it isn't an estimate — it's what happened.

Striking-Distance Keywords: The Fastest Wins in Organic Search

There is a specific, repeatable play hiding in the performance report, and it is the highest-return SEO work most sites never do. The term for it is striking distance: queries where you already rank on the edge of page one or the top of page two — roughly positions 5 through 20 — that a focused push could move into the clickable zone.

These are gold because the hard part is already done. Google has crawled the page, indexed it, judged it relevant, and decided it belongs near the front. You're not begging for a seat at the table; you're asking to move up a few chairs. Moving a query from position 12 to position 6 can multiply its clicks several times over, because click-through rate climbs steeply as you approach the top of the first page. Starting a brand-new page from nothing to compete for that same query is months of work with no guarantee. The striking-distance version is often a week.

To find them, filter the performance report to positions in that 5-to-20 band and sort by impressions, so you're working on terms with real demand behind them. For each candidate, open the page that ranks and ask the obvious questions: does it fully answer the query, or does it mention it in passing? Is the query in the title, or only the body? Does the page have the depth and internal links that the results above it have? The fixes are usually unglamorous — expand the relevant section, sharpen the title, add a couple of internal links from stronger pages, refresh a date-sensitive detail. Then note the position, make the change, and check back in a few weeks. Search Console is both the place you find the opportunity and the place you measure whether the fix worked.

Index Coverage: Diagnosing the Pages Google Refuses to Rank

A page that isn't indexed cannot rank, cannot earn an impression, and cannot appear anywhere in the performance report. So before you optimize anything, it's worth confirming Google has actually accepted the pages you care about — and the indexing report, formerly called Coverage, is where you check.

The report sorts your URLs into indexed and not-indexed, and the not-indexed reasons are where the diagnosis happens. Two states cause the most confusion and deserve the most attention. "Discovered — currently not indexed" means Google knows the URL exists but hasn't bothered to crawl it, often a signal that it doesn't see enough value to prioritize, or that the page is buried too deep in your site's structure. "Crawled — currently not indexed" is sharper: Google came, looked, and declined to index it — almost always a quality, thinness, or duplication judgment rather than a technical switch you can flip.

Other states are more mechanical and faster to resolve. "Duplicate without user-selected canonical" or "Duplicate, Google chose different canonical than user" means Google folded the page into another and picked the winner itself. "Excluded by noindex tag" means a tag is doing exactly what it says, which is great if intended and a quiet disaster if not. "Soft 404" flags pages returning a success status with nothing useful on them.

The one tool to know alongside the report is URL Inspection. Paste any URL and Google tells you whether it's indexed, when it was last crawled, which canonical it chose, and whether it's eligible to appear. If a page should rank and doesn't, this is the first place to look — and once you've fixed the cause, it's where you request a fresh crawl. Most "my page disappeared from Google" emergencies resolve in this one report, and resolve fast once you stop guessing and read what Google is plainly telling you.

Fresher Data and Date Comparisons: Reading the Effect of an Update

One of the quieter improvements has been around data freshness and granularity. Search Console has moved toward more timely performance numbers, including views with finer time resolution — closer to hour-by-hour rather than waiting days to see whether yesterday mattered. For a news site, a product launch, or anyone watching a campaign land, shrinking that lag from days to near-real-time changes how quickly you can react.

The feature that turns this freshness into insight is the date-range comparison, and it's the right way to read whether something actually moved your site. When Google rolls out a core update, instead of staring at a single line and convincing yourself it dipped, set the report to compare the weeks after the update against the equivalent weeks before. Now you can see it plainly: did total clicks fall, and if so, was it across the board or concentrated in specific pages and queries? A site-wide drop and a drop confined to one content cluster are completely different problems with completely different fixes.

The comparison view is just as useful without an update in the picture. Compare this quarter to last to see which pages are trending up and which are quietly fading. Compare year-over-year to separate genuine decline from normal seasonality — a contractor's traffic falling in winter isn't a penalty, it's January. Compare before and after you shipped a change to a page, which is the only honest way to know whether your work helped, did nothing, or hurt.

This is also where the new freshness pays off in practice. The faster the data arrives, the sooner a comparison stops being a postmortem and starts being a steering input — you catch the wrong-direction move while there's still time to course-correct, instead of explaining it after the quarter closes.

What Search Console Still Can't Tell You

For all of this, Search Console has real blind spots, and using it well means knowing them rather than discovering them the hard way.

The query data is sampled and anonymized. Google withholds queries that are too rare to report without risking identifying an individual searcher, which means the clicks and impressions in your performance report rarely sum to your true totals — a chunk of your long-tail visibility is folded into an unlabeled remainder you'll never see itemized. The data is directional and extremely useful, but it is not a complete census, and you shouldn't treat the numbers as penny-accurate.

There's a hard time limit, too. Performance data only goes back 16 months. There is no way to pull a three-year trend or compare against a year that's now out of range, so if you want history beyond that window, you have to export and store it yourself, on a schedule, before it ages out. Plenty of teams learn this the day they go looking for a comparison that no longer exists.

The most consequential gap right now is the newest one. As Google leans harder into AI-generated answers at the top of the results, Search Console offers no clean, separate view of how often your content is cited or summarized inside those answers, or what that does to your clicks. You may see impressions hold while clicks erode — the fingerprint of an answer that satisfied the searcher before they ever reached you — but the tool won't hand you a tidy "AI citations" report to confirm it. That visibility doesn't exist yet, and any tool claiming to measure it precisely is estimating.

None of this is a reason to trust Search Console less. It's a reason to read it for what it is: the best free, first-party signal you have, accurate in direction, incomplete in detail, and blind in a few specific places worth keeping in mind.

Turning Search Console Into a Monthly Habit

The features only matter if you open the tool, so here's a routine that takes about half an hour a month and beats most of what agencies bill for under the heading of reporting.

Start with the new recommendations — read the cards, dismiss the ones that don't fit your business, and click into one or two that point at real money. Next, the performance report: compare the last 28 days to the prior 28 and scan for pages and queries that moved meaningfully in either direction, because both the climbers and the slippers are telling you something. Then run the striking-distance filter — positions 5 to 20, sorted by impressions — and pick one or two genuine opportunities to act on before next month. Finally, glance at the indexing report for any spike in not-indexed pages, which is the early-warning siren for a technical problem worth catching before it spreads.

That's the whole loop, and the point of it isn't completeness — it's consistency. A site checked this way every month rarely gets blindsided. You see the core update in the comparison view instead of in a revenue report two months later. You catch the de-indexed template the week it happens. You ship a handful of small, compounding wins a year instead of one big panic-driven overhaul.

The new recommendations and fresher data lower the bar to doing this, which is the real story. Google has made its most useful free tool a little easier to act on. The agencies that already live in this report — SearchPod among them — will tell you the same thing: the leverage was never in fancy software. It was in opening the one tool that tells you the truth, and actually using it.