Search Console: the part everyone skips.

Almost every site we inherit has Search Console installed, verified, and abandoned. Sometimes a marketing manager checks it once a quarter and reports 'impressions are up'. That's not what it's for. Search Console is the single best diagnostic tool for any site that depends on organic search — and most teams use less than 10% of it.

Here's the full walk-through of what's actually in there, what to do with it, and the weekly habits that turn it from a vanity dashboard into a real growth lever.

The reports worth your time

What it actually tells you that nothing else can

• 01The exact queries users typed into Google to reach your site, ranked by impressions, clicks, and click-through rate. No third-party tool has access to this.
• 02Which pages Google has crawled, indexed, or quietly refused to index — with the specific reason for each exclusion.
• 03How your site renders to Googlebot, not just to you — including the rendered HTML after JavaScript has executed.
• 04Which Core Web Vitals are failing on specific URLs in the real world (real Chrome User Experience data, not lab synthetic).
• 05When something has gone wrong — a sudden index drop, a manual penalty, a malware flag — usually before you notice in analytics.
• 06Which sites are linking to you, what anchor text they use, and which of your pages they link to most often.
• 07How many users tap your site on mobile vs desktop, and which queries differ between them.

"

Almost every 'why is our organic traffic stuck?' problem has its answer already inside Search Console. The hard part isn't the data. The hard part is having someone whose job it is to look at it every week.

What we set up on every project

• 01Verify the property by DNS TXT record, not by HTML tag — survives platform migrations and never gets accidentally deleted by a CMS update.
• 02Add both www and non-www, both http and https, then 301-redirect everything to the canonical version.
• 03Submit the sitemap explicitly; don't trust auto-discovery.
• 04Wire alert emails to a real address that gets read — not the agency mailbox that nobody monitors.
• 05Tag the URL inspection of every key landing page on launch day, then again at 14 days. If they're not indexed by then, investigate.
• 06Connect Search Console to BigQuery for sites with enough traffic to justify a real data layer.
• 07Create user access for the marketing team, not just engineering — they're the ones who should be looking weekly.

The weekly review we recommend

• 01Performance: look at the top 20 queries by impressions. Identify any with high impressions and low CTR — title or meta-description rewrites usually fix these in two weeks.
• 02Indexing: any new URLs since last week that haven't been indexed? Use URL Inspection to find out why.
• 03Core Web Vitals: any 'needs improvement' or 'poor' URLs? Triage by traffic impact, then fix.
• 04Manual actions: should be empty. If it isn't, drop everything else.
• 05Sitemap: should show recent successful parse. If it shows errors, investigate the new content that broke it.

The mistakes we see most often

• 01Verifying as one user. When that person leaves, nobody has access. Always verify multiple emails.
• 02Submitting a sitemap that includes non-canonical URLs. Confuses crawlers, wastes crawl budget.
• 03Ignoring the 'discovered, not indexed' bucket. These are pages Google knows about but didn't think were worth indexing — the signal is 'your content isn't compelling enough', not 'something is broken'.
• 04Treating impressions as the success metric. CTR is more interesting — low CTR means your title and description aren't earning the click even when you're ranking.
• 05Not segmenting mobile vs desktop. The data is often dramatically different.

If a client's organic traffic is stuck, the answer is almost always already in Search Console. Nobody is reading it. Set up the weekly review. It is the single highest-leverage 30 minutes of marketing work most teams aren't doing.