What to do after connecting Google Search Console

Google Search Console is the most useful free SEO tool that exists, and also the most abandoned. Most people connect it, look at the performance graph twice, and never open it again — because it reports what happened and stops there. Nothing in it says what to do next.

This is the missing instruction manual: the order to work through it, and what each report is actually for.

What should I check first in Search Console?

Start with indexing, not performance. Open Pages (under Indexing) and look at the "Why pages aren't indexed" table. Performance data is meaningless for pages Google hasn't indexed, and most sites are surprised by what's missing.

The reasons worth acting on:

• "Crawled – currently not indexed" — Google saw the page and declined it. This is usually a quality or duplication signal: thin pages, near-duplicates, or pages with no internal links pointing at them.
• "Discovered – currently not indexed" — Google knows the URL exists but hasn't bothered fetching it. Usually an internal-linking or crawl-priority problem.
• "Excluded by 'noindex' tag" — fine if intentional. An emergency if a template accidentally noindexed real pages. Check any page you care about with a free SEO check.
• "Duplicate without user-selected canonical" — you have near-identical pages and never told Google which one counts. Add canonical tags.

Which performance numbers actually matter?

Open Performance and ignore the default view. Total clicks going up or down tells you that something changed, never why. The two views that produce actions:

1. Queries where you rank 4–20. Filter by average position. Anything between 4 and 20 is "striking distance": Google already believes you're relevant, you're just not winning. Moving position 8 → 3 routinely multiplies clicks by five or more, because click-through rate falls off a cliff below the top results. This one filter is so valuable we built an entire feature around it — but you can do it manually: sort by impressions, filter position 4–20, and improve those pages first.

2. Pages with high impressions and terrible CTR. These pages are being shown and not clicked, which usually means the title and meta description are losing the argument on the results page. Check what searchers actually see with a meta tag checker and rewrite the snippet to answer the query.

How do I know if my sitemap is working?

Open Sitemaps, submit yours if you haven't, and then read the number it reports against what you expect. If you publish 200 pages and the sitemap shows 40 discovered, your sitemap generation is broken. If it shows 200 discovered and 90 indexed, revisit the indexing section above. Validate the file itself with a sitemap checker — malformed XML fails silently more often than you'd think.

How often should I check Search Console?

Weekly is plenty for most sites. The productive loop looks like this:

1. Check Pages for new indexing errors (2 minutes).
2. Pull the position 4–20 queries and pick one page to improve (10 minutes).
3. Fix that page: content, title, internal links pointing at it.
4. Next week, check whether its position moved.

That last step is the one everyone skips, and it's the only one that tells you whether anything you did mattered. SEO without a feedback loop is superstition.