Why Search Console, Not Just Analytics
Analytics tells you what happened after someone landed on your site. Search Console tells you what happened before that: whether Google can find your pages, whether it chose to index them, what queries actually surfaced them, and where it silently dropped a page you never noticed was missing. If you only run analytics, you're blind to the entire discovery step, which is exactly where most SEO problems actually live.
Setting Up The Property
Use a domain property, not a URL-prefix property, if you can. A domain property covers every subdomain and protocol (http, https, www, non-www) under one roof. A URL-prefix property only covers the exact prefix you entered, so https://example.com and https://www.example.com end up as two separate properties with split data unless you set both up. Domain properties need DNS verification instead of a file upload or meta tag, which is a small extra step most registrars support in a couple of minutes.
Verify with a method you'll still have access to in a year. A meta tag in your <head> is the easiest option for most projects since it lives in code you already control and ships with every deploy. In this codebase specifically, that's the commented-out verification: { google: "" } line in the root metadata (app/layout.tsx): drop the token in once you generate it in Search Console, and it goes out with the next deploy.
Submit your sitemap immediately after verifying. Go to Sitemaps in the left nav and submit sitemap.xml. If your site generates its sitemap dynamically from your actual content source (the way app/sitemap.ts here pulls straight from getAllCaseStudies() and getAllBlogPosts()), this is a one-time step: new pages get picked up automatically without you touching Search Console again.
The Reports That Actually Matter
Performance. Queries, clicks, impressions, average position, filterable by page and by query. This is where you find out what you're already ranking for that you didn't deliberately target, which is often a better content idea generator than any keyword tool.
Pages (formerly Coverage). Shows what's indexed, what's excluded, and why. "Crawled, currently not indexed" on a page you care about is the single most useful debugging signal Search Console gives you: it means Google saw the page and decided it wasn't worth indexing, usually because the content is thin, near-duplicate, or the page isn't getting enough internal links pointing to it.
URL Inspection. Paste a specific URL and get its exact indexing status, the last crawl date, and a live test against how Googlebot renders it right now. Use this after publishing anything you want indexed fast, and use the "Request Indexing" action sparingly. It's a nudge, not a guarantee, and spamming it on pages Google has already decided not to index won't change the decision.
Core Web Vitals. Field data from real Chrome users, not a lab simulation, grouped into good/needs improvement/poor buckets per URL group. This is the report that tells you whether the performance work you did (image optimization, reduced JS, avoiding layout shift) actually moved the needle for real visitors, not just in a synthetic test.
Enhancements. Shows how your structured data is actually being read: which schema types Google recognized, and any errors in a specific page's JSON-LD. If you've added BlogPosting, Article, or Service schema and want to confirm Google parsed it correctly rather than silently ignoring a malformed field, this is where you check.
What To Check In The First Month
Set a recurring reminder, not a one-time glance. New sites and new sections take a few weeks to fully crawl and settle into their indexing state.
- ▸Coverage errors. Fix anything marked as an error immediately; these are pages Google tried and failed to index, not pages it chose to skip.
- ▸Mobile usability. A layout issue here means a real chunk of your traffic is looking at a broken page, since mobile-first indexing means Google evaluates your site as a mobile user would.
- ▸Manual actions. Under Security & Manual Actions. Should be empty. If it isn't, nothing else in this list matters until it's resolved.
- ▸Which queries you're already ranking for on page 2. Sort Performance by impressions with low clicks and a position between 11 and 20. These are the fastest wins available: content that's already relevant enough to rank, just not polished enough to rank higher.
The Mistake We See Most
Treating Search Console as a one-time setup step instead of a monitoring habit. A property verified once and never opened again catches nothing: not the sitemap that silently stopped updating, not the page that got deindexed after a redesign, not the schema that broke when a component got refactored. The setup takes twenty minutes. The value comes from actually looking at it.
Related posts
How To Do SEO Properly
Most "SEO tips" are either outdated or actively risky. Here's the version we actually use on client sites: technical foundations, content structure, and local SEO for businesses in Delhi NCR, laid out in the order that matters.
Google Analytics, Without The Noise
GA4 ships with more reports than any team actually needs. Here's what to set up first, what to ignore, and how to read the numbers without fooling yourself.