Missing From Your Notes Is Not Absent From Their Site

Here’s a sentence that appears, in one form or another, in a great many competitor teardowns: “None of our competitors have a pricing page.” Or “Competitor B doesn’t publish case studies.” Or “Nobody in this space is using video.”

Sometimes it’s true. Often, what’s actually true is narrower: the person doing the research didn’t find it, didn’t look or didn’t write it down. The pricing page lives under “Plans.” The case studies are called “Stories.” The videos are embedded on product pages nobody opened.

This is the most common and most consequential error in competitor research: treating missing-from-your-notes as absent-from-their-site. It’s tempting, it’s invisible and it can point a whole strategy at an opportunity that doesn’t exist.

Why is this mistake so easy to make?

Because absence feels like a finding. When you scan a competitor’s site and don’t see something, the brain records “not there,” not “not seen.” And in a teardown, absence is exciting. A gap in the market is the most actionable thing research can find. Everyone wants to discover the thing nobody else is doing.

The bias compounds in groups. One person’s “I didn’t see a FAQ” becomes the deck’s “no FAQ,” which becomes the strategy’s “we’ll be the only one with a FAQ,” which becomes a project. Nobody re-checks, because the claim now has the authority of a slide.

What does history say about declaring things absent?

Some of the best-known reversals in science and exploration came from confident claims of absence.

Black swans. For centuries, Europeans used “black swan” as a figure of speech for something that couldn’t exist. In 1697, the Dutch explorer Willem de Vlamingh’s expedition recorded black swans in Western Australia. The “absence” had only ever been an absence of observation.

The coelacanth. Known from the fossil record, the coelacanth was long thought to have died out tens of millions of years ago. In 1938, a living one was found in a fishing catch off South Africa, identified with the help of museum curator Marjorie Courtenay-Latimer. Absent from the record of living species was not the same as absent from the ocean.

“Absence of evidence.” The phrase “absence of evidence is not evidence of absence” has been used by many scientists, and Carl Sagan helped popularize it. It’s a reminder that not finding something is only meaningful if you looked properly.

A competitor’s FAQ page isn’t a coelacanth. The logic is the same.

How does the error distort strategy?

In three ways, each costly.

False opportunities. You build something to fill a gap that isn’t a gap. The “only pricing page in the market” launches into a market where three competitors already have one, under a different label.

Misread positioning. If you believe competitors lack something, you may position against a weakness they don’t have. Prospects who compare carefully notice.

Lost credibility. When a client or colleague later finds the “missing” page in thirty seconds, every other finding in the research becomes suspect.

How do you prevent it?

With a simple vocabulary that forces honesty. When comparing competitors, record presence with one of six codes:

Yes: verified present.
No: verified absent, after a deliberate check.
Partial: present in some form, but limited.
Missing-in-notes: your notes don’t cover it.
Unknown: you tried to verify and couldn’t.
N/A: doesn’t apply.

The power is in Missing-in-notes and Unknown. They give you an honest place to put what you don’t know, so it doesn’t get rounded to No. And they create a to-do list: every Missing-in-notes cell is a check you haven’t done yet.

What counts as a deliberate check for “No”?

Before marking something as truly absent, run a quick, documented check. A reasonable standard:

Check the navigation and footer, including menus that open on hover.
Search the site, using its own search or a site-restricted web search, with several synonyms.
Try likely URLs, such as /pricing, /plans, /faq, /case-studies or /stories.
Check a few deep pages, like product or service pages, where the element might be embedded.
Note the date and method in your evidence log.

If all of that comes up empty, “No” is defensible, with a date. If you skipped it, the honest code is Missing-in-notes.

What does an honest evidence entry look like?

Compare two versions of the same note.

Weak: “Competitor C — no case studies.”

Strong: “Competitor C — case studies: No. Checked main nav, footer, site search for ‘case study,’ ‘stories,’ ‘work’ and ‘clients,’ and tried /case-studies and /work. Accessed [date]. Observation.”

The strong version takes perhaps a minute longer to write. It also survives scrutiny. Anyone who doubts the finding can see what was checked and when, and can repeat the check. If the competitor adds case studies next month, the date explains why your note and their site disagree.

Now a third version, equally honest:

Also strong: “Competitor C — case studies: Missing-in-notes. Didn’t check this pass.”

There’s no shame in that line. It’s accurate, and it tells the next person exactly what to do.

How do you run a re-check pass?

Before research informs a decision, take a short, focused pass over the cells that matter:

Filter the Comparison sheet to the rows relevant to the decision at hand.
List every Missing-in-notes and Unknown in those rows.
Run the deliberate check for each Missing-in-notes, and record the result as Yes, No, Partial or Unknown.
Retry Unknowns with a different method, such as a deep page or a site-restricted search.
Update dates for anything re-verified.
Re-read your experiments to see whether any depended on a gap that just turned out to be filled.

Step six is the one that saves projects. It’s much cheaper to drop an experiment at this stage than after it’s been built, launched and compared against a competitor who had the same thing all along.

Does this apply to your own site too?

Yes, and it’s surprisingly common. Teams sometimes claim “we don’t have X” about their own site when it exists in an old section nobody remembers. When your own row in a comparison shows Missing-in-notes, re-check before claiming absence. It’s an awkward thing to discover in a client meeting, especially when the client is the one who finds it. A five-minute audit of your own site, using the same deliberate check you’d apply to a competitor, prevents the moment entirely and often surfaces useful pages worth linking more prominently.

Why does this make research more useful, not less?

You might think admitting unknowns weakens research. It does the opposite. When every No has been deliberately checked and every gap is labeled honestly, the findings that remain are trustworthy. Readers can act on them. And the genuine gaps, the verified Nos where most competitors fall short, become far more valuable, because you know they’re real.

Honest research also turns into better experiments. Instead of “we’ll be the only one with X,” you write “most comparators answer X on their service pages; we’ll test our own version on ours.” That’s an original experiment grounded in verified observations, not a race to fill an imaginary gap.

What else goes wrong in teardowns?

Missing-versus-absent is the biggest error, but it travels with relatives:

Inferences written as observations. “They’re targeting enterprise” is a conclusion. Record what you saw that led you there.
Undated findings. Sites change. A finding without an access date can’t be trusted next month.
Unrepresentative comparators. Comparing yourself only to the largest brands produces distorted gaps.
Copying instead of experimenting. A competitor’s solution is evidence, not a template.
Assuming traffic or revenue. You can see what’s on a page. You can’t see its performance.
No question. Without one, everything looks like a finding.

How does the workbook enforce this?

The Competitor Research-to-Action Workbook builds the distinction into its structure. Its Comparison tab uses the six presence codes, including Missing-in-notes and Unknown, so there’s always an honest option. Its Evidence Log labels every finding as Observation, Inference or Unknown, with the URL and access date. And its Experiments tab turns verified findings into original tests for your own site, prioritized with Impact × (4 − Effort), and marked Incomplete until both ratings exist.

The fictional Riverglass walkthrough shows the method in action, including a comparator whose schema markup is logged as Unknown rather than assumed, and a reminder that missing-in-notes on your own page means re-check before claiming absence.

Quick answers

Isn’t “Unknown” just a lazy answer?

Not when it’s honest. Unknown says you tried and couldn’t verify. It’s far more useful than a confident No that turns out to be wrong.

How many Missing-in-notes cells are acceptable?

Some are normal. Before the research drives a decision, convert the ones that matter to that decision into Yes, No or Unknown.

Should I share Unknowns with clients?

Yes. It signals rigor and tells them exactly where more research would change the picture.

Check before you claim

The most exciting finding in competitor research is a gap. That’s exactly why it deserves the most skepticism. Before you build strategy on “nobody does this,” make sure nobody really doesn’t, and label honestly when you’re not sure.

Get the Competitor Research-to-Action Workbook and run your next teardown with presence codes that keep Missing-in-notes apart from No. Your findings will be smaller in number and much larger in value.

You’ll find the Workbook, presence codes and all, on Content & SEO Workflows.