content gap report is the document that lists the topics your site does not cover, scores them, and presents them in an order you can act on. It is the output of a research process and the input to an editorial calendar. Read properly, it turns a vague sense that you should publish more into a short list with reasons attached.
The direct answer to the question most people have when they first see one: read the bottom of the report before the top. The evidence status and the coverage notes tell you which recommendations you can trust, and the ranking only means something once you know that. A content gap report read top to bottom without those checks is a list of suggestions. Read with them, it is a plan.
What is in a content gap report?
A well-built report has seven sections, and they appear in a deliberate order.
The scope. What was checked, when, and against what inventory. If this section is missing, every number below it is unanchored.
The coverage summary. How many topics you already serve, how many you serve partially, and how many you do not serve at all. This is the one-page picture of your site’s shape.
The conflict list. Pages of yours competing for the same intent. These are not gaps, and they get resolved before new articles are commissioned. The procedure for resolving them sits in cannibalization check.
The ranked opportunities. The main table. Each row is a topic with its score, its intent, and its evidence status.
The evidence status report. Which sources returned data and which failed during the run. This is the section that tells you how much to trust the ranking.
The question bank. Reader questions collected during research, grouped by topic. Often the most durable artifact in the whole report. The content gap analysis method explains how these questions are collected in the first place, which is useful if you want to run the research yourself.
The recommended actions. The report’s own shortlist. Useful as a starting point, and never as a final answer, because it does not know your business priorities.
Seven sections, and the reason they are listed in this order is that this is the order to read them in. Most people open a content gap report at the ranked table because it is the most exciting page. That is like reading a medical test result by looking only at the risk percentage and skipping the note about which sample was tested. The scope and the status are what make the numbers mean something.
A content gap report is also a dated document. It records what was true on the day it ran, and the date matters as much as the content. A report from eighteen months ago still tells you something useful about your site’s shape, and its opportunity scores should be treated as history rather than advice.
How do you read the coverage summary?
The coverage summary has four numbers, and each one calls for a different response.
Already covered. Topics where you have a page that genuinely serves the intent. Nothing to do. Take these off the table and stop reopening them.
Partially covered. Topics where a page touches the subject without fully answering it. These are expansion candidates, and they are usually the cheapest wins in the report. You are not starting from nothing, and the URL already has some history.
Not covered. Genuine gaps. Some are worth filling and most are not, which is what the scoring section is for.
Covered more than once. Topics where two or more of your pages compete. These are conflicts rather than gaps.
The ratio between these four numbers tells you what kind of problem you have. A site with a large partially-covered group has an expansion problem, and its fastest gains come from improving existing pages. A site with a large not-covered group and almost nothing in the other three has a publishing problem. A site with a large conflict group has an internal competition problem that no amount of new writing will fix.
Most sites misdiagnose this. The common assumption is that growth requires new articles, and the coverage summary frequently shows that the bigger opportunity sits in pages that already exist. Google’s guidance on creating helpful content puts the emphasis on usefulness to a reader rather than volume of output, which is the same conclusion arrived at from a different direction.
Here is a concrete example. A site with four hundred published pages finds that three hundred and ten are fully covered, sixty are partially covered, twenty-five are uncovered, and five involve two pages competing. The uncovered group is the one everyone wants to discuss, and it is the smallest. The sixty partially covered pages are the real opportunity, because each one already has a URL with some history, some links, and some impressions, and each one is a smaller job than a new article. A content gap report surfaced that in one table. Google’s guidance on creating helpful content supports the same priority from the direction of quality rather than quantity.
How do you read the opportunity scores?
The ranked table is where most readers go first, and it is the section most likely to be misread.
Each row carries a score out of one hundred, built from weighted factors. Relevance and audience fit carry the most weight, because a topic your readers do not care about fails no matter how much demand it shows. Intent quality and demand come next. Gap size and competitor weakness describe how much room exists. Differentiation asks whether you can say something the current results do not. Commercial value, social interest, and conversion potential round it out.
Three score bands matter in practice.
Sixty and above. Act on these. They passed every test and the evidence behind them is strong enough to build on.
Forty to fifty-nine. Keep them on a secondary list. These are topics where one or two factors were weak, and the weak factor is worth naming. A topic held back by competitor weakness needs a different angle. A topic held back by relevance is usually the wrong topic.
Below forty. Monitor. Do not commission. These are the rows that tempt people because the topic sounds interesting, and the score is the report’s way of saying the interesting part is not the same as the useful part.
The bands are useful because they convert a hundred-point range into three decisions. In practice most of the value sits in the middle band, because the top band acts itself and the bottom band is safely ignored. The forty-to-fifty-nine group is where judgement earns its place, and where a content gap report needs a human to read the underlying factors rather than the total.
One more reading note. A score is only comparable within a single report. Comparing a score from this month against a score from six months ago tells you very little, because the competitor set and the demand signals both moved. Compare the ranking, not the number. A topic that climbed from position twenty to position three is a better signal than a topic that scored sixty-one instead of fifty-eight.
Why read the evidence status before the ranking?
Because two rows that look identical can rest on completely different foundations.
Every finding in the report carries a status. Verified means the source returned the data directly. Source-derived means the finding came from that data by a stated method. Inferred means the pipeline reached a conclusion the source did not state. Estimated means a number was modelled rather than observed. Requires live verification flags something that was true under earlier conditions and needs a fresh check. Unknown means the pipeline could not determine the answer. Blocked means the source refused or failed.
The practical consequence is that a high score built on verified evidence and a high score built on an estimate should not be treated the same way, even though they appear in the same table with similar numbers. A content gap report that ranks purely by score without showing status is hiding the most important column.
There is a second check worth running on any row before you commit. Open the top three current results for the topic and read them. If they already answer the question thoroughly, the row is weaker than its score suggests, and no amount of production quality will change that. The scoring formula estimates competitor weakness from signals. Reading the results is how you confirm it.
This is where a content gap report differs from a ranked list produced by volume alone. Volume tells you how many people search. It says nothing about how well the current results serve them. A topic with modest demand and poor existing answers is often a better investment than a topic with large demand and excellent existing answers, and only the report’s structural columns let you see the difference.
The status column also protects you from a subtler mistake, which is treating a blocked source as an empty one. If several adapters failed during the run, the report will contain fewer rows than it should, and the rows it does contain carry more weight than they deserve. A content gap report that honestly reports its own gaps is more trustworthy than one that looks complete.
How do you turn one row into a published article?
Reading a content gap report and acting on it are different skills, and the second one is where the value lands.
Pick one row, not five. The most common failure is trying to act on the whole shortlist at once. Take the highest-scoring row that your team can genuinely execute this month and finish it.
Extract the intent. The row records the intent, and the intent becomes the article’s promise to the reader. Write it as a sentence before writing anything else. If the sentence is vague, the row was vague.
Pull the matching questions from the question bank. These become headings, FAQ entries, and the structure of the answer. Using the reader’s own phrasing improves the match between what you publish and what gets searched.
Check the conflict list first. If the same intent already appears in your conflict rows, the correct action is to fix that page rather than to publish a new one.
Write the brief from the row. The row already contains the score, the intent, and the evidence. A brief built from it takes fifteen minutes and prevents the drift that happens when a writer starts from a title alone.
Recheck the report after publishing. The next run should move the topic from not covered to covered. If it does not, the article did not serve the intent the report identified, and that is worth knowing early.
There is one more step that most teams skip, and it is the one that makes the process compound. Record what you did with each row. Which one you published, which ones you deliberately deferred, and why. Three months later, when the same content gap report is regenerated, that log lets you compare decisions against outcomes instead of guessing.
A worked example. A row scores seventy-two for the intent “how to choose a first running shoe for flat feet”. The brief pulls four reader questions from the question bank, which become four H2 sections. The article publishes. The next run shows the intent fully covered and two adjacent intents new to the list, because the question bank for that topic surfaced follow-up questions nobody had asked before. One row produced one article and two future rows. That is the compounding effect, and it only appears when the report is run on a schedule.
What mistakes do people make with a content gap report?
Five recur often enough to be worth listing.
Treating the top row as an instruction. The ranking reflects the formula’s weights, not your business. A topic can score highly and still be wrong for you this quarter.
Ignoring the conflict list. Publishing into an intent you already compete for makes the site worse rather than better, because it splits the same signals further.
Skipping the question bank. The questions are the most reusable output and the least used. They describe what readers actually want to know, in the words they use, and they stay useful long after the opportunity list is stale.
Acting on the whole list. A shortlist of ten becomes ten half-finished articles. One completed article changes the site.
The reason the evidence column matters this much is the same reason Google’s SEO starter guide tells publishers to write for people rather than for engines. A report is a model of demand, and a model can be wrong in ways that look tidy. Reading the status column is how you keep the model honest before it becomes a publishing decision.
Not re-running the report. A single report is a snapshot. The value compounds when reports are comparable, because the differences between them show which decisions worked.
To those five, add a sixth. Treating the report as a finished research project rather than a working document. A content gap report that sits in a folder is worth nothing. The same report pinned next to the editorial calendar, with rows crossed off and reasons written beside them, becomes the thing that stops the team from re-arguing settled questions every quarter.
The mistakes share a root cause, which is treating a content gap report as an answer rather than an instrument. It measures. It does not decide. The measurement is careful and repeatable, and the decision is still yours, made with context the report cannot see.
FAQ
What is a content gap report in simple terms?
It is a document that lists topics your site does not cover, scores them, shows which of your existing pages conflict, and reports how strong the evidence behind each finding is. A content gap report is the output of research and the input to planning.
How is it different from a keyword list?
A keyword list records terms and often their volume. A content gap report records terms alongside what you already cover, what you conflict on, what the evidence status is, and how each topic ranks against a weighted formula. The list is one stage inside the report.
How many opportunities should a content gap report contain?
Enough to plan a quarter, usually ten to twenty scored rows in a shortlist and a longer appendix. A report with five hundred rows is a research artifact rather than a working document, and nobody will act on it.
Should you always publish the highest-scoring topic?
No. The score measures opportunity against a formula, and the formula does not know your capacity, your seasonality, or your commercial priorities. Use a content gap report to rank a shortlist, then choose the row you can execute well now.
What if a high-scoring topic already ranks for you?
Check the coverage column before acting. If a page already serves the intent, the row describes an expansion or a refresh rather than a new article. Publishing a second page into a served intent creates the conflict the report was meant to find.
How often should you regenerate the report?
Monthly for most sites. Quarterly is enough for slow-moving niches. The reason to keep it regular is comparability, because the useful signal sits in how the ranking changed rather than in any single snapshot.
Can you build one without paid tools?
Yes. A content gap report can be assembled from public demand signals, your own sitemap, and your own performance data. It takes longer and the demand figures are relative rather than absolute, and the decisions it supports are the same decisions.
Who should own the report?
One person, with a named reviewer. A content gap report that belongs to everyone gets read by nobody. The owner runs it on schedule, keeps the decision log current, and brings the shortlist to planning. The reviewer challenges the scores, which is how the formula stays honest.
What is the single most useful section?
The question bank for long-term reuse and the evidence status for short-term trust. If you only have time for one check before acting, read the evidence status, because it tells you whether the ranking in front of you is built on anything solid.
Conclusion
A content gap report is only as good as the reading of it. The scope tells you what was actually checked. The coverage summary tells you whether your problem is new publishing or unfinished existing pages. The conflict list keeps you from making things worse. The scores rank the shortlist, and the evidence status tells you which rows deserve trust.
Read it in that order and a content gap report stops being a list of ideas. It becomes a plan with reasons, and reasons are what let you defend a decision six months later when someone asks why you published that article instead of another one.
Then act on one row. Write the intent as a sentence, pull the matching questions from the bank, brief the piece from the row, and re-run the report once it is live. The comparison between the two reports is where a content gap report starts earning its place in your calendar, because that is the moment you find out whether the research was right. Keep the log, keep the cadence, and the report stops being an annual exercise and becomes the way your site decides what to publish.