Zero-volume keywords: what 184 impressions taught us

A zero-volume keyword is a query that a keyword tool reports at zero or in its smallest volume bucket. The label is an estimate, not proof that nobody searches. At Popupsmart, “php popup” showed 0–10 US searches in Ahrefs but earned 184 Google impressions and 56 clicks in 28 days.

That result does not mean every zero-volume keyword deserves a page. It means search volume should be treated as one forecast among several. The better decision combines first-party demand, search intent, business value, the live results page, and what your team can add that no generic article can.

Author experience. I’m Emre Elbeyoglu. I’ve worked in SEO and growth for 15 years and co-founded Popupsmart in 2019. This article draws on the Ahrefs and Search Console snapshots my team saved while working on Popupsmart’s organic growth. I separate what those screenshots show from what they cannot prove.

What does “zero search volume” actually mean?

Zero search volume is a measurement label, not an observation of zero human demand. Each research product builds its number from a different dataset, date range, location, and grouping method. A zero may mean the query fell below a reporting threshold, was grouped with close variants, was absent from the tool’s database, or genuinely received almost no searches.

Google’s own products show why the distinction matters. Keyword Planner describes monthly searches as estimates, while Google Trends says low-volume terms can appear as “0” because Trends displays a sampled, normalized view of search interest.

I still use “zero-volume keyword” as shorthand. I read it as “unmeasured or very small demand,” not “nobody has ever searched this.”

What did I learn from our “php popup” example?

I use our Popupsmart example to show that a query in a tool’s lowest bucket can produce measurable search activity. In April 2024, Ahrefs reported 0–10 monthly US searches for “php popup.” Our saved query-level Google Search Console snapshot for April 12 to May 9 recorded the following:

My team and I had a natural reason to cover the query. Popupsmart sells popup software, and the PHP popup tutorial lets a reader either build the interaction with code or use the product. The topic sits close to our product, answers a specific task, and gives the page a sensible next step.

The comparison has limits. Ahrefs used US settings, while the Search Console screenshot does not show a country filter. An impression is not a unique person, and the two tools do not use identical date ranges or definitions. The page can also appear for related queries. The numbers therefore do not prove that the phrase receives 184 monthly US searches.

What can I say with confidence? The two snapshots show why the “0–10” bucket was not enough to make our publishing decision. More importantly, the page earned clicks because we had product fit and a useful answer, not because the keyword carried a zero label.

Are zero-volume keywords usually hidden traffic winners?

No. Most zero-volume keywords remain small, and page traffic is often mistaken for traffic from one exact query. A page may target an obscure phrase yet earn visits from dozens of better-known variations. Crediting all page traffic to the original keyword inflates the result.

Ahrefs tested low- and zero-volume queries for which its blog ranked in the top five. In that small study, fewer than 1% produced more than 100 monthly impressions, and the average query produced 11.3 impressions. Ahrefs also warns that a low-volume phrase may be an uncommon wording of a competitive parent topic.

Three popular assumptions should therefore be rejected:

• A zero-volume keyword is not automatically easy to rank for.
• A specific query is not automatically commercial.
• A page’s total organic traffic is not the same as traffic from its target query.

My goal is not to collect zeroes. I look for neglected customer problems where weak volume data might otherwise stop my team from publishing a useful, commercially relevant answer.

How do zero-volume, low-volume, and long-tail keywords differ?

Zero-volume, low-volume, and long-tail describe related but different ideas. “Zero” and “low” refer to a tool’s reported demand. “Long-tail” refers to the large set of individually uncommon queries beyond the most popular head terms. A long-tail query can contain two words, and a long phrase can still have substantial volume.

Do not create separate pages just because the wording differs. Search both the candidate and its broader parent query. If four or five of the same URLs dominate both result sets, Google is probably treating them as one intent. Add the missing answer to the stronger existing page instead of creating a competing URL.

When is a zero-volume keyword worth targeting?

A zero-volume keyword is worth targeting when the expected business or audience value justifies the cost of producing the best answer. Reported volume matters, but product fit, first-party evidence, standalone intent, and your ability to show real work matter more.

I use this ten-point score before commissioning a new page. The score is a prioritization aid, not a Google ranking model.

Interpret the total like this:

• 8–10: A standalone page is defensible. Define a conversion goal and publish the evidence.
• 5–7: Test the idea as a section on an existing page, a support answer, or a small paid-search campaign.
• 0–4: Skip it unless the query is strategically necessary, such as documentation for a new feature.

The score prevents two expensive errors: dismissing a high-value customer question because a tool says zero, and producing hundreds of thin pages because zero-volume keywords sound easy.

How can you find zero-volume keyword candidates?

The best candidates come from customer language and product activity before they come from an SEO database. I start with places where a real person has already expressed a need, then use keyword tools to size and group the opportunity.

1. Export queries from Google Search Console

I open the Search results report, select at least three months, and export the query and page dimensions. I look for terms that have impressions but little or no reported volume in my research tool. Then I group them by landing page and intent before deciding whether any query needs new content.

Google documents that some Search Console queries are omitted for privacy and that the report shows only its most important rows. Search Console is strong first-party evidence, but it is not a complete list of everything people searched.

2. Listen to sales, support, and on-site search

Sales calls, support tickets, chat logs, demo notes, and on-site searches expose the words customers use before those words appear in a keyword database. Count repeated problems, record the customer stage, and remove personal information before sharing examples with a content team.

At Popupsmart, I sat close to product and support conversations. That made technical patterns such as platform names, integrations, and implementation questions easier to spot. I value that context more than a generated list because it explains who asked, what they were trying to do, and what happened next.

3. Search product-shaped patterns

High-value B2B and SaaS queries often follow repeatable structures:

• [feature] + [platform]
• [product] + [integration]
• [error code] + fix
• [competitor] alternative for [industry or team]
• how to [task] without [constraint]
• [software category] for [specific workflow]

I generate these combinations from the actual product, integrations, customer segments, and error logs. I use a template only when each resulting query maps to a real need. A pattern is not permission to publish a page for every combination.

4. Use Autocomplete and related questions as evidence, not volume

Google says Autocomplete predictions reflect real searches, along with language, location, trends, and a user’s past searches. Predictions are also filtered, so their presence supports demand but does not reveal how often a phrase is searched.

I repeat the check in the target market and note whether the same language appears in related searches, People Also Ask, forums, videos, or product communities. I treat one isolated suggestion as weak evidence. The same problem repeated across independent sources is stronger.

5. Watch releases, regulations, and new terminology

New product names, API changes, regulations, error messages, and industry events can create demand before historical-volume tools catch up. Google Trends can show direction for larger emerging topics, but it should not be used to validate tiny queries. Google states that Trends uses a sample, normalizes results to 0–100, and displays very low-volume terms as zero.

I sometimes use an LLM to expand a verified pattern into possible phrasings. It cannot tell me whether anyone searched them. I treat generated keywords as hypotheses and validate them with the sources above.

How do you validate a candidate before writing?

I validate a zero-volume keyword by checking the task, result set, demand evidence, business value, and correct content format. My initial review takes about 15 minutes and can prevent weeks of work on a page that should have been one paragraph.

1. Write the searcher’s task in one sentence. If you cannot explain what the person wants to accomplish, the query is not ready.
2. Compare the live results. Search the exact phrase and its broader wording in the target country. Record result types, repeated domains, freshness, and whether the top pages actually solve the task.
3. Check the intent overlap. When the same pages answer both queries, improve the existing parent page. When the result sets and required answers differ, a standalone page may be justified.
4. Collect two demand signals. Prefer Search Console, customer conversations, on-site search, product logs, or an exact-match Google Ads test. Autocomplete and community discussions can support the case.
5. Define the payoff. Decide what a qualified visit can do: start a trial, request a demo, use a free tool, subscribe, or complete a support task. A few valuable visits may beat thousands of irrelevant ones.
6. Choose the smallest useful format. The answer might be a product-doc section, comparison row, integration page, video, tool, or blog post. Do not default to a 2,000-word article.

For a trend-led query with no first-party data, set a review date before publishing. If the page remains indexed with no impressions and no customer use after 60 to 90 days, merge it into a stronger page or remove it.

How should you create content for a zero-volume keyword?

I build one strong page for one search intent, then answer close variations within that page. The main risk is not insufficient keyword repetition. It is creating a thin URL that adds nothing beyond the current results.

A useful page should:

• Answer the task in the first 40–60 words.
• Show the workflow with original screenshots, code, data, or a named example.
• State the product, market, and date behind every measured result.
• Cover the related questions needed to finish the task.
• Link from a relevant parent page and to the next useful action.
• Explain limitations, failed approaches, and cases where the advice does not apply.

The Popupsmart PHP page works as a concept because we can connect a technical implementation question to a real popup product. Publishing unrelated zero-volume topics would weaken that connection. In my account of Popupsmart’s 60% SEO traffic drop, I explain why I now give topical fit a harder look in content decisions.

Avoid swapping a keyword into a fixed template and publishing hundreds of near-duplicate pages. If every page would give the same answer, the site needs one guide with useful filters or a real programmatic product experience, not a folder of search-doorway pages.

How should you measure the result?

I measure a zero-volume page with first-party outcomes, not a later change in a keyword tool’s estimate. I record a baseline, annotate the publication date, and review Search Console and conversion data after the page has had enough time to be crawled and tested.

I track impressions, clicks, qualified conversions, revenue or pipeline when available, and support outcomes for documentation content. I report query-level and page-level performance separately. That distinction stops me from presenting a page with broad traffic as proof that one zero-volume phrase became popular.

What should you do next?

I recommend starting with ten queries your customers already use. Compare them with your keyword tool, score any zero-volume candidates, and inspect the live results. I update an existing page when the intent overlaps. I create a new page only when the query represents a distinct task and I can contribute evidence or experience that the current results lack.

Zero-volume keywords are not a shortcut around competition. They are a reminder that a forecast is not the market. The useful work is deciding which small signals point to a real customer problem, then solving that problem better than the available alternatives.