My page is indexed but gets no traffic: how to make it answer the question
Your page is not missing from Google. It is present and unwanted. Search Console tells you which problem you have: not being shown, or shown and not chosen.

Your page is not missing from Google. It is present and unwanted. Search Console reports queries your page was shown for, how often, and in what position, and those three numbers tell you which of two different problems you have: you are not being shown, or you are being shown and not chosen. The query list is partial, and knowing that before you start matters. Google omits rare queries to protect user privacy, and states that "due to internal limitations, Search Console stores and shows only the most important data rows." Work the queries you can see and treat the rest as unmeasured rather than absent. The two problems need different repairs, and confusing them wastes a week.
What this actually is
Ranking is a matching problem, not a quality contest. Google describes its ranking systems as looking at "many factors and signals about hundreds of billions of web pages and other content in our Search index to present the most relevant, useful results." Useful gets settled by a person mid-search: they type eight words, scan, click, and either stop or come back for another result.
A page that circles the question is a page they come back from.
There are two distinct failure states, and the reframe that makes this tractable is to stop calling both of them "not ranking":
Zero impressions, with the report filtered to the page, means Search Console recorded no appearances for it in that period. The withheld-query caveat does not explain this one away: what gets withheld is which queries are named in the table, not whether the page was counted as shown. Google is not putting the page in front of anyone. The page has no question. It has a topic.
Impressions with no clicks means Google associated it, showed it, and the searcher chose someone else. Your matching is fine. Your title, your description, or your fit to the intent is not.
Google's own guidance for this is blunt: it describes people-first content as "content that's created primarily for people, and not to manipulate search engine rankings," and search-engine-first content as content "primarily made to attract visits from search engines." One of its named warning signs is "Writing to a particular word count because you've heard that Google has a preferred word count." Word count was never the target.
How to check
Open Search Console, pick the property, and go to Performance, then Search results. The default view is "click and impression data for your site in Google Search results for the past three months."
Turn on all four metrics at the top of the chart: Clicks, Impressions, CTR, and Average position. The default gives you clicks and impressions, so CTR and Average position are the two you switch on yourself, and they are the two that tell you whether you are being skipped.
Now filter to the one page. Two routes, and the second is exact by construction. Either click "+ Add filter" above the chart, choose Page, and paste the full URL including the trailing slash into "URLs containing," or switch the table to the Pages tab and click the row for your page, which filters the whole report to that URL with no string for you to get wrong. Everything above and below now describes that page alone.
Switch the table below the chart to the Queries tab, and sort by Impressions descending.
Read the definitions the way Google defines them, not the way they feel. An impression is "How many times your site appeared in Search results." A click is "The number of times a user clicked your site from Google Search results." Average position in the table is "The average position in Search results for the specific URL or grouping dimension shown in the table row," while the position drawn in the chart is "The average position of the topmost result from your entire site." Those are two different numbers and they will not agree. The table row is the one you want.
Then do the part that is not in Search Console. Take the top query by impressions, open a private browsing window, and search it. Read the first ten results end to end. You are not looking for their word count. You are looking for the sub-questions they answer that you do not.
If you need more rows than the table shows, the Search Analytics API takes the same filters and returns up to 25,000 rows per call, with a default of 1,000. It reads the same store, so the same omissions apply. The fullest list Google offers is the bulk data export, which schedules a daily export of your performance data into BigQuery.
What you will see
Four states, four different repairs.
No impressions, page indexed. Google has the page and matches it to nothing. The repair is upstream of everything below: the page needs a question it demonstrably answers, phrased the way people type it.
Impressions, average position above 30. Google matched the page to the query weakly, and put it on page three or worse. You are on-topic and thin. This is a content depth repair.
Impressions, position roughly 5 to 20, clicks near zero. You are on the page a human looked at, and they skipped you. This is a title and description repair first, an intent repair second.
Impressions, clicks, position in the top ten. Nothing to repair here. Go find the next page.
Two footnotes on the data. The newest days are preliminary: Google notes that "The newest data can be preliminary, meaning it's still being collected and might change in the next few hours," shown as a dotted line. And the query list is incomplete by design, twice over: rare queries are omitted to protect user privacy, and Google "stores and shows only the most important data rows," so a page with real traffic can show queries that do not sum to its click total. Google says so itself: "the most complete list of queries can be exported using bulk data exports." Do not read a query's absence from the table as proof nobody searched it.
How to fix
Take one query. One. The repair is per-question, and a page that answers one question completely beats a page that gestures at six.
Classify the intent by reading Google's results, not by guessing. The results page is Google's own answer to "what did this person want," and it is free:
Informational: the top ten are articles, how-to pages, and definitions, usually with People Also Ask boxes.
Commercial investigation: comparisons, "best X" roundups, and review pages.
Transactional: product pages, category pages, booking forms, and shopping results.
Navigational: one brand dominates, usually with sitelinks under its homepage.
If the top ten are all product pages and you wrote a 2,000-word explainer, you did not lose on quality. You entered the wrong race. Rewrite for the intent that is actually there, or pick a different query.
Rebuild the headings around the question. The H1 states the question the way a person asks it. Each H2 is a sub-question, in the order someone would ask them. If a heading is a noun ("Features," "Overview," "Our Process"), it is a label, not a question, and it earns nothing. Google's title documentation notes that "Multiple prominent headings" with unclear hierarchy is one of the conditions that makes it rewrite your title for you.
Write the title tag as the answer, not the category. Google states there is no character limit: "While there's no limit on how long a <title> element can be, the title link is truncated in Google Search results as needed, typically to fit the device width." That is the rule. The practical number comes from Moz, which puts display titles at a 600-pixel width limit and recommends 51 to 60 characters, reporting that under 60 characters about 90% of titles display correctly. Moz also studied 57,832 title tags and found Google rewrote 58% of them. Ouch.
Google's own instruction is "Write descriptive and concise text for your <title> elements," avoid vague descriptors like "Home," avoid boilerplate repeated across pages, and avoid "Foobar, foo bar, foobars, foo bars," which "doesn't help the user."
Write the meta description as the reason to click. Same shape of rule: "There's no limit on how long a meta description can be, but the snippet is truncated in Google Search results as needed." Google uses it "if it might give users a more accurate description of the page than content taken directly from the page," and warns that "Identical or similar descriptions on every page of a site aren't helpful." Moz's working range is 120 to 160 characters, roughly 680 pixels. The description does not rank you. It gets you chosen once you are already there, which is exactly the problem you are fixing when impressions are high and clicks are not.
Cover the question until the reader has no reason to go back. Write down every sub-question the top ten results answer between them. Answer each one on your page, with the specific numbers, prices, hours, steps, and named tools. Then check your page against Google's own self-assessment questions: "Does the content provide original information, reporting, research, or analysis?" "Does the content provide insightful analysis or interesting information that is beyond the obvious?" "Is this content written or reviewed by an expert or enthusiast who demonstrably knows the topic well?" "Does the content have any easily-verified factual errors?"
Do not solve this with volume. Google's spam policies define scaled content abuse as "when many pages are generated for the primary purpose of manipulating search rankings and not helping users," and name "Using generative AI tools or other similar tools to generate many pages without adding value for users" and "Stitching or combining content from different web pages without adding value" as examples. Sites in violation "may rank lower in results or not appear in results at all." Google publishes no pages-per-week number that trips this, so treat any threshold you have been quoted as invented. What the policy names is purpose: many pages generated mainly to move rankings rather than to help the reader. Rewriting one page because you found a question it failed to answer is not that. Generating forty because a tool will produce forty is.
Then ask for a recrawl. URL Inspection, paste the URL, Request Indexing. Google is clear about what that buys you: "there's a quota for submitting individual URLs and requesting a recrawl multiple times for the same URL won't get it crawled any faster," and "Crawling can take anywhere from a few days to a few weeks."
What it costs
Pulling and reading the Search Console data for one page: 30 minutes.
Reading the top ten results properly, and writing down the sub-questions: one hour. This is the step everyone skips and it is the step that decides the outcome.
Rewriting the body to answer them: two to four hours per page, more if you need to go get real numbers.
Title and meta description: 15 minutes, and worth every one of them when position is already under 20.
Then the waiting, which is the expensive part and is not negotiable. Crawling takes days to weeks. After that, Google states: "some changes can take effect in a few days, while others could take several months," and "it may take months before our systems determine that a site is now producing helpful content in the long term. In general, you'll likely want to wait a few weeks to analyze your site in Search Console again."
So set the check date three weeks out, filter to the same page, compare the period against the previous period, and look at average position and CTR rather than raw clicks. Google also states plainly that "there's no guarantee that changes you make to your website will result in noticeable impact in search results." Plan for several pages, not one.
Want the queries your pages already appear for pulled and read against the results Google is actually ranking? Get a web audit.












