“Good” in Search Console's Core Web Vitals report describes loading, responsiveness and layout stability for a URL group. It does not certify the quality of an article or promise search traffic. A page can provide a good measured experience while still having limited relevant impressions, few clicks, or poor business results.
Start by identifying the report, date, device category and URLs behind the label. An old page-experience screenshot, a current Core Web Vitals status and a third-party SEO score are different observations. The process below is for investigating low search traffic when Core Web Vitals already look good.
What the Good status actually covers
The Core Web Vitals report uses real-user CrUX data, separates mobile and desktop, and groups URLs with similar experiences. When the reporting-data requirements are met, the worst-performing metric determines the group's status for that device category.
| Metric | Experience being assessed | Good range |
|---|---|---|
| LCP | How promptly the main content appears | 2.5 seconds or less |
| INP | Responsiveness to clicks, taps and keyboard interactions | 200 milliseconds or less |
| CLS | Unexpected layout movement | 0.1 or less |
Interpret these ranges with the report's 75th-percentile measurements and trailing 28-day window. One local test is not a substitute for that field history. A representative URL is not proof that every page in its group has been individually reviewed, and missing data is not automatically a poor result. See the LCP, INP and CLS measurement guide for the diagnostic distinctions.
The report does not check whether you wrote 1,500 words, placed a keyword near the beginning, or stayed below a supposed text-similarity threshold. Google's page-experience guidance explicitly says good scores do not guarantee top rankings. Perfecting a score may be less useful than addressing the next genuine obstacle.
Identify what “no traffic” means
| Observation | First investigation |
|---|---|
| The important URL is not indexed | Inspect access, indexing reasons and the selected canonical |
| The URL is indexed but has few relevant impressions | Review demand, page purpose and the actual search results |
| There are impressions but few clicks | Compare queries, devices, positions and search presentation |
| Search Console clicks exceed analytics visits | Check measurement scope, channel, timing and tracking behavior |
| There are visits but few useful inquiries | Check audience fit, the offer and the actual contact journey |
Check the current URL and reporting scope
Use URL Inspection for the exact page you care about. Record the stored indexing result, last crawl and Google-selected canonical. A live test shows present accessibility; it does not prove indexing. An earlier Core Web Vitals observation also cannot replace checking the URL's current state. For an indexing obstacle, use the submitted-but-not-indexed checklist.
Then open the Search results performance report. Confirm the property covers the intended domain and path, and inspect the date range, search type, page, country and device filters. Do not compare one URL's latest partial day with the whole site's previous month. If Google has selected another canonical, investigate where the data is attributed.
Separate brand demand from non-brand demand and articles from commercial pages. A query missing from your site's visible data does not establish zero market demand. Average position is also an aggregate for the selected scope, not a fixed rank seen by every searcher.
Indexed but barely visible: review the page's job
Choose an important page and describe the reader's task in one sentence. Does the query call for a product category, a comparison, a troubleshooting procedure or a definition? Inspect representative results in the intended language and market, preserving the observation conditions. A fast company-history page may still be a poor answer to a product-selection query.
Look for the actual missing information: specifications, selection criteria, limitations, steps or evidence. Add what helps the reader complete the task, rather than expanding every page to a fixed length. The five-area content review helps turn a vague “improve quality” instruction into paragraph-level work.
Use target-keyword and page planning to connect demand with suitable pages. Keyword tools can inform that work, but their volume and difficulty figures depend on the tool, market and date. They are not Google's eligibility scores or probabilities that your page will rank.
Visible but rarely clicked: compare like with like
Inspect the queries, devices and countries behind the impressions, then look at the real results. Does the title describe what the page supplies? Does a comparison guide pretend to be a purchase page? Does a promised template actually exist? Resolve the mismatch before making the wording more dramatic.
Record the surrounding result formats as well: products, images, videos or other features can change how the result is presented. A change in aggregate CTR can also reflect a different query or device mix. There is no universal 5% CTR threshold that makes every title defective. Judge comparable groups and the actual page promise.
Visits without business results need a separate investigation
Google explains that Search Console clicks and Analytics sessions are calculated differently. Align dates, landing pages, countries, devices and Google organic-search scope when comparing their patterns. Check tracking delivery and consent behavior before calling a discrepancy lost traffic. Do not mix Search Console clicks with Analytics sessions as if they were the same denominator.
Complete the intended journey on a phone: read the specification table, use the main action, and send a safe test inquiry. Verify that it reaches the responsible team, not just that the interface shows a success message. Short engagement can mean a quick answer or a usability problem; one duration does not establish a ranking penalty.
If images are genuinely slow, blurred or unstable, follow the image compression and delivery checks. Converting every image to WebP solely because clicks are low is not a diagnosis. Identify the resource or interaction responsible and verify the repair.
Keep a useful follow-up record
For each target page, save the report scope, observed problem, change, publication date, verification result and next observation period. Confirm the technical fix first; then monitor comparable impressions and clicks; finally examine qualified inquiries. If traffic used to be healthy and fell suddenly, Google's traffic-drop guide also covers migrations, technical problems, seasonality and search changes.
The next task is to identify the unresolved stage. The three-area ranking checklist connects content, technical access and measured outcomes without treating a green status as a complete SEO result.