GSC Coverage vs Performance: What Each Report Shows

Google Search Console splits two jobs that beginners often merge: whether Google can index and show a URL versus how that URL performs in search results after it appears. The Page indexing area (successor to what many guides still call “Coverage”) tracks indexed, not indexed, and excluded reasons. Performance → Search results tracks clicks, impressions, click-through rate, and average position.

Mixing those reports creates expensive mistakes—rewriting meta descriptions while the URL is still excluded, or requesting indexing on a post that already earns impressions but sits on page four.

Cluster owners to open first: GSC Pages tab vs Queries tab, GSC Not found (404) after deletes, and GSC impressions without clicks. This page is indexing vs Performance literacy. It is not a canonical troubleshooting owner. It is not an organic CTR playbook for snippets that already rank.

Direct answer: Use Page indexing when the question is “Can Google use this URL?” Use Performance when the question is “What search demand is this URL seeing?” Fix eligibility before you optimize snippets on the same URL.

Official starting points: Page indexing report, Performance report overview, URL Inspection tool.

Disclosure: Educational SEO. We do not invent penalties, traffic lifts, or earnings from Console screenshots.

Table of contents

1. Two reports, two questions
2. What Page indexing actually measures
3. What Performance actually measures
4. How data flows from crawl to clicks
5. Which report to open for common jobs
6. Scenario: new affiliate post with no Performance row
7. Misreads that send you to the wrong report
8. FAQ
9. Match the report to the job

Two reports, two questions

Page indexing is a status ledger grouped by reason: indexed, crawled but not indexed, duplicate without user-selected canonical, blocked by robots.txt, not found (404), and other documented buckets. Performance is a behavior ledger for search appearances: how often URLs from your site showed in results, how often searchers clicked, and at what average position—for the date range you pick.

If I were auditing a small blog tonight, I would not open Performance first for a URL that returns 404. I would confirm the HTTP response and indexing reason, then decide redirect, restore, or intentional removal—using the 404 after deletes owner when the spike follows a cleanup.

Conversely, if Performance shows thousands of impressions and near-zero clicks on an indexed money page, Page indexing being green does not solve the problem. You need Performance dimensions—especially Pages vs Queries—and intent-specific FIX work, not another “Validate fix” click on a healthy index state.

What Page indexing actually measures

Google’s indexing reports summarize eligibility and selection after crawls. A URL can be crawled, return 200, and still land in “Crawled – currently not indexed” because Google chose not to store it for retrieval yet—or because quality signals did not justify inclusion.

Mechanisms worth internalizing:

Page indexing is property-wide pattern detection. It helps you notice a template accidentally noindexed, a migration that left orphan parameters, or a batch delete that produced Not found spikes. It is weaker as a daily “how is my best post doing?” dashboard—that is Performance filtered to one URL.

URL Inspection complements Page indexing for one URL’s live story: last crawl, indexing state, referring sitemap, and enhancement checks. Use Inspection after you ship a fix; use Page indexing to see whether the fix class of problem repeats across many URLs.

What Performance actually measures

Performance counts search result interactions for your verified property. The chart at the top is typically property-level for the range you select. Tables slice by Queries, Pages, Countries, Devices, Search appearance, and Dates.

Important limitations Google documents:

• Query tables omit some anonymized rare queries; chart totals may exceed visible row sums.
• Property-level query rows aggregate multiple URLs; page-level rows attribute metrics to one URL.
• Impressions mean an appearance in search results for a user—not a guarantee the URL was indexed at that instant for every row context.

Performance answers demand and visibility questions: which posts earn impressions, which queries trigger them, whether mobile CTR diverges from desktop, and whether a date comparison shows a real shift. It does not replace Crawl Stats for server health or Page indexing for exclusion reasons.

When impressions exist but clicks do not, read impressions without clicks before you assume indexing failure. Often the URL is indexed and visible—just not compelling or not high enough for the query mix.

How data flows from crawl to clicks

Thinking in order reduces circular fixes:

1. Discovery and crawl — Googlebot fetches URLs (sitemaps, links, queues). Failures and redirects show up in crawl-related tools and sometimes in Page indexing reasons.
2. Indexing decision — Google stores or excludes a URL. Page indexing and URL Inspection describe this stage.
3. Ranking and appearance — Eligible URLs compete for queries. Performance records impressions and clicks when your result is shown.
4. User click — CTR is clicks divided by impressions for the chosen slice—not a site-wide “quality score.”

A break at stage 2 never fixes stage 4 with title rewrites alone. A healthy stage 2 with weak stage 4 still needs Performance analysis—not resubmitting the sitemap daily.

Which report to open for common jobs

Keep canonical and duplicate-URL work on canonical owners when Page indexing shows duplicate or alternate rows. This article only points you there—it does not retarget canonical as the primary lesson.

Scenario: new affiliate post with no Performance row

You ship a 1,400-word review on a long-tail tool. After five days, Performance shows nothing for that URL; Page indexing says “Discovered – currently not indexed.”

Sensible sequence:

1. URL Inspection on the live URL—confirm 200, no accidental noindex, canonical points to self.
2. Check internal links from an indexed hub—not orphan click depth alone.
3. Wait a reasonable window; indexing lag is normal. Avoid hammering Request indexing unless Inspection shows a clear error you fixed.
4. Once Page indexing shows indexed and Performance shows impressions, shift to query and snippet questions—not before.

If instead Performance already shows impressions with zero clicks, skip resubmit loops. Filter Pages to the review URL and continue the cluster path for weak CTR on indexed URLs.

Misreads that send you to the wrong report

“Green indexing means SEO is done.” Indexed is table stakes. Performance still decides whether anyone clicks.

“Performance dropped, so indexing broke.” Query mix, seasonality, and losing one high-click query can drop clicks while indexing counts stay stable.

“I will fix CTR in Page indexing.” Snippet optimization does not live in indexing reports.

“404 rows always mean disaster.” After intentional deletes, Not found can rise while the site is healthier—see the 404 owner.

“One URL Inspection snapshot overrides Performance trends.” Inspection is a point in time; Performance is aggregated behavior.

FAQ

See frontmatter for schema-ready pairs; the section mirrors those answers for on-page readers.

Match the report to the job

Page indexing tells you whether Google is willing to store and serve a URL. Performance tells you what happens when search results include that URL. Small blogs grow faster when editors know which question they are asking before they open Search Console—then reach for the sibling owners that own CTR, 404 cleanup, and tab reading without duplicating those playbooks here.

Next practical step: pick one URL you care about. If you are unsure it is indexed, start with URL Inspection and Page indexing. If it is indexed and already shows impressions, open Performance → Pages and continue with the Pages vs Queries and impressions-without-clicks guides—not title experiments on a URL that is not eligible to appear.