<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Outfit:wght@600;700;800&family=Plus+Jakarta+Sans:wght@400;500;600;700&display=swap">
🔍 SEO guide

Google Search Console for Beginners: Setup, Performance and Indexing Reports

Set up Google Search Console, read clicks, impressions, CTR and position correctly, understand indexing statuses, and use URL Inspection to fix problems.

📅 Published 2026-11-15⏱️ 5 min read🛠️ 5 free tools

Google Search Console is the only place where Google tells you directly how your site performs in its search results: which queries show your pages, how often people click, which pages are indexed and which are not, and why. It is free, and it is the first tool to set up for any site that wants search traffic.

The reports are dense and some of the numbers are easy to misread. This guide walks through choosing and verifying a property, reading the Performance report without falling into the averages trap, what the most common indexing statuses actually mean, and how to use URL Inspection and the Core Web Vitals report.

Domain property or URL-prefix property

Search Console offers two property types, and the choice affects what data you see.

  • Domain property (example.com): covers every subdomain and protocol together, so http, https, www, blog. and shop. are all included. It can only be verified with a DNS TXT record at your domain registrar or DNS provider. This is the best default for most sites.
  • URL-prefix property (https://www.example.com/): covers only URLs that start with that exact prefix. It can be verified by DNS, an HTML file upload, a meta tag, Google Analytics or Google Tag Manager. Useful when you only control part of a domain, or want separate reports for a section such as /blog/.
  • You can have both. Many teams add a Domain property for the full picture and URL-prefix properties for key sections or subdomains.
  • Verification must stay in place. If the TXT record or meta tag is removed, you lose access after a while.
  • Add teammates with the lowest permission they need. A restricted user can view reports; only owners can add users or remove the property.

Reading the Performance report

The Performance report shows four metrics for up to 16 months of history, broken down by query, page, country, device, search appearance and date. Data arrives with a delay of about two days.

  • Impressions: how many times a URL from your site appeared in a result the user saw, or at least loaded. A result on page 2 that the user never reached does not count.
  • Clicks: clicks that took the user to your site. Clicks on a result that opened something inside Google do not count.
  • CTR: clicks divided by impressions. Compare CTR between pages at similar positions; CTR always falls with position.
  • Average position: the average of your topmost position for each impression. It is weighted by impressions, so a page ranking 3 for one query and 40 for a high-volume one can show 30.

Avoiding the common misreadings

Averages hide most of what matters. Always filter to one query or one page before drawing conclusions from position or CTR. A falling site-wide CTR often means you started ranking for new, broader queries, which add many impressions at low positions; clicks may be rising at the same time.

Totals on the query tab are lower than totals on the page tab, because Google hides rare queries for privacy. The table is also capped at 1,000 rows in the interface; for more, use the API or an export.

The most useful filters for finding work: queries in positions 4 to 20 with meaningful impressions (pages close to the top that a better answer could move), and pages with many impressions but a CTR well below others at similar positions (often a title or description problem). Compare date ranges of equal length and the same days of the week, and remember seasonality before calling a drop a penalty.

The Pages report and what the statuses mean

The Pages report (formerly Coverage) lists how many known URLs are indexed and groups the rest by reason. Not indexed is not automatically a problem: many of those URLs should not be indexed. Read each reason and decide whether it matches your intent.

  • Crawled - currently not indexed: Google fetched the page and chose not to index it, for now. Usually a quality or duplication signal: thin pages, near-duplicates, or pages with little unique value. Improve or consolidate the content rather than requesting indexing repeatedly.
  • Discovered - currently not indexed: Google knows the URL but has not crawled it yet. Common on new or large sites; often caused by weak internal linking or crawl capacity limits.
  • Duplicate without user-selected canonical, or Duplicate, Google chose different canonical than user: Google sees the page as a copy of another and picked its own preferred version. Check that your canonical tags agree with your internal links and sitemap.
  • Alternate page with proper canonical tag: expected for pages that point a canonical elsewhere, such as parameter variants. No action needed.
  • Excluded by noindex tag, Blocked by robots.txt, Page with redirect, Not found (404): expected if intentional. A surprise here is often a template or deployment mistake.
  • Soft 404: the page returns 200 but looks empty or like an error page, for example an out-of-stock listing with no content. Return a real 404, or give the page useful content.

URL Inspection and Core Web Vitals

URL Inspection shows what Google knows about one URL: whether it is indexed, the canonical Google selected, when it was last crawled, whether it is in a submitted sitemap, and any structured data it found. Test Live URL fetches the page now and shows the rendered HTML and screenshot, which is the quickest way to confirm that content loaded by JavaScript is visible to Google. Request Indexing asks Google to recrawl one URL; it has a daily quota and does not guarantee indexing, so use it for important new or fixed pages, not as a routine.

The Core Web Vitals report groups URLs with similar performance and labels them good, needs improvement or poor for mobile and desktop, based on field data from real Chrome users. URLs only appear when they have enough traffic. After fixing an issue, use Validate Fix; the validation runs over 28 days because the underlying data is a 28-day rolling window.

A weekly routine with Neemtools

The Neemtools Search Console Analyzer connects to your property with read-only access and organises the same performance data into quick-win queries, low-CTR pages and ranking movers, so you can spend the review on fixing pages rather than building filters. Pick two or three pages from those lists each week.

For each page, check speed with the Page Speed Checker, which shows lab metrics alongside the field data behind the Core Web Vitals report. When you have a list of URLs to review, for example everything in a "Crawled - currently not indexed" export, paste it into the Multiple URL Opener to open them in batches and spot the pattern they share. Then check indexing changes in the Pages report a few weeks after your fixes.

More guides you might like

Ready to try it?

Open the free Search Console Analyzer and apply what you just read. No sign-up, nothing uploaded.

Open Search Console Analyzer →

← All guides