If you’re asking “how do I get more TOFU traffic?” you’re already asking the wrong question. The teams I see struggling with TOFU aren’t failing to publish. They’re publishing a lot.
The problem is that their TOFU content either doesn’t rank at all, or it ranks and drives zero pipeline. They don’t know which of those to fix first.
The right question is: how do I build TOFU content Google won’t skip, and that makes my BOFU pages easier to rank? Those are actually the same question, and this is the five-step answer.
TL;DR
- Why TOFU fails: Most SaaS teams treat TOFU as a volume play; it’s actually an authority infrastructure play that BOFU pages depend on to rank.
- Step 1 (ICP keywords): Pick TOFU keywords that match how your ICP describes their own problem, not generic category terms.
- Step 2 (Format match): Check what format Google already rewards for each query before writing; format mismatch kills rankings regardless of content quality.
- Step 3 (Depth): After recent Google core updates, shallow TOFU content gets quietly removed from the index, not just demoted. Depth means ICP specificity and a real POV, not word count.
- Step 4 (Internal links): TOFU pages only complete their job when they’re wired into the site’s internal link structure and passing authority to BOFU pages.
- Step 5 (Measurement): Track TOFU by authority signals (backlinks earned, BOFU ranking movement), not traffic.
Why Most TOFU Keyword Strategies Fail for SaaS
Look, I get the logic. Publish high-volume awareness content, build traffic, warm up buyers, and eventually they convert. It sounds right. But in SaaS SEO, it breaks at almost every step.
The traffic-first trap
The assumption behind volume-first TOFU is that traffic equals awareness, and awareness eventually becomes pipeline. That chain only holds if your BOFU pages are actually ranking when those warmed-up buyers go back to search for a solution.
Here’s what actually happens. A SaaS company publishing dozens of TOFU blogs on generic category terms sees traffic grow. The team celebrates. Six months later, their “best [software category]” comparison page is sitting on page 3 and converting nobody. The TOFU content got traffic but didn’t build the topical authority the BOFU pages needed to move.
The sites that rank for competitive BOFU terms aren’t just building good BOFU pages. They’re building depth across the topic so Google trusts them on the high-intent queries too. TOFU content is what creates that depth, but only when it’s the right TOFU content, done the right way.
What TOFU is actually for in SaaS SEO
TOFU’s real job isn’t to generate demos. A blog post about “what is [problem category]” isn’t going to produce trials. When done well, it does three things:
- Earns backlinks from sites that cite genuinely useful, specific content
- Builds topical authority Google uses to rank your site for adjacent queries
- Passes internal link equity down to the BOFU pages that actually convert
We’ve seen BOFU pages stuck mid-page jump into top positions after adding TOFU support content underneath them. The TOFU didn’t drive demos. The TOFU made the BOFU pages rank, and the demos followed.

Step 1: Pick TOFU Keywords That Signal Real ICP Problems
Most TOFU keyword lists are built from keyword tools. The result is a list of generic category terms: “what is project management software,” “employee onboarding best practices,” “what is CRM.” High volume. Broad audience. Almost useless for a SaaS company trying to reach a specific ICP .
Use ICP language, not category language
Your buyers don’t search the way keyword tools think they do. A VP of Engineering at a Series B company doesn’t search “what is sprint planning software.” They search “how to track velocity across three engineering teams,” or “cross-team dependencies in Jira.”
The language your ICP uses to describe their own problem is what you want to target. And you won’t find that in Ahrefs. You’ll find it in:
- Sales call recordings (what words do prospects use when describing the pain?)
- CS tickets and support chats (what problems do existing customers write in?)
- G2 and Capterra reviews, especially the one-star ones (what did the product fail at?)
- Reddit threads and Slack communities where your ICP hangs out
Once you have that language, validate it in a keyword tool. But discovery should come from people, not search volume.
Group by topic, not by keyword
Before building out any TOFU cluster: we group keywords into topics first, not a flat list. “What is GRC,” “GRC components,” and “GRC examples” all map to one topic: one strong pillar page, not three thin articles.
A flat list of 300 TOFU keywords is noise. Seventy topics is a strategy. Topics tell you how many pages you need and which ones can be consolidated. It also makes the internal linking structure obvious, which matters for Step 4.
| Approach | What you get | Problem |
|---|---|---|
| Flat keyword list | Lots of topics | No cluster depth; each page is a dead end |
| Topic-grouped | 70 coherent topics | Authority compounds across the cluster |
Step 2: Match the Format Google Already Rewards for That Query
You can have the right keyword with the right ICP angle and still not rank if the format is wrong. I’ve seen well-written long-form guides sitting on page 4 for queries where Google shows short definitional pieces in the featured snippet. Format mismatch is what’s blocking it, not the content quality.
Read the SERP before you write a single word
Before writing any TOFU piece, put the target keyword into Google and ask:
- What’s the top result? A guide, a definition, a how-to, a listicle, a comparison?
- How long are the top three results roughly?
- Is there a featured snippet? What format is it? A paragraph, a numbered list, a table?
- Are the top results from publications, tools, or practitioners?
The format question isn’t about copying what’s ranking. It’s about understanding the constraint. If Google shows short definitional content for a query, publishing a long-form guide there probably won’t work. Google has already decided that query wants a quick answer.
When to go deeper than what’s ranking
There’s an important exception. If the top results for your target keyword are thin and generic (short, no original perspective, clearly written to rank rather than to help), you can outflank them with genuine depth plus a specific ICP angle.
The trap is thinking more words always wins. They don’t. A tight piece with a real scenario (“here’s how a 50-person fintech team uses X to solve Y”) will outrank a bloated generic guide every time, assuming the format matches what Google wants for that query.

Step 3: Write Depth Google Won’t Deindex
This is the step most guides skip, and it’s the one that matters most right now. After Google’s core updates over the past year, shallow TOFU content isn’t getting penalized with ranking drops. It’s getting quietly removed from the index entirely.
And most teams don’t even know it’s happened.
The deindexation problem
Tip: Open Google Search Console, go to the Pages report, and look at “Not Indexed.” Inside that, look at “Crawled but not indexed” and “Discovered but not indexed.” If those numbers are climbing while you’re publishing more TOFU content, that’s your answer.
Google cleared out pages with no real point of view, no unique insight, and no genuine depth. Recovery isn’t publishing more content. It’s making what’s there worth showing. We started seeing this pattern consistently after the April 2024 update. The fix is always the same: add a real ICP-specific angle, go deeper on the actual problem, then resubmit in Search Console.
Treat TOFU as a credibility signal, not a volume play. Google is.
What depth actually means for TOFU
Depth is not word count. I want to be clear about that. A focused TOFU piece with three specific signals will outperform a bloated generic article. The signals Google rewards are:
- ICP specificity. Name the role, the company size, the specific scenario. “A compliance manager at a Series B fintech company searching for X is dealing with Y” is depth. “Teams struggle with compliance” is not.
- A real point of view. Not “there are pros and cons to X.” An actual position: “Most teams approach X this way, and here’s why that breaks at scale.”
- Fresh framing. Connect the topic to what’s actually happening in the category right now. If there’s a regulation change, a common tool sunset, or a shift in buyer behavior, your TOFU content should reflect it.
None of this requires more words. It requires more thinking before you write.

Step 4: Build Internal Links That Pass Authority to BOFU Pages
Internal links are how TOFU authority reaches your BOFU pages. Without them, the equity dies at the TOFU level. It doesn’t go anywhere. This is one of the most common gaps we see in SaaS content programs. Teams produce strong TOFU content but don’t connect it to the money pages.
Here’s the basic structure that works:
- Every TOFU page should link to at least one relevant MOFU or BOFU page in the body, naturally within context
- Every BOFU page should have TOFU and MOFU pages linking into it from above
- Your site’s main navigation or hub pages should link to BOFU pages directly, not just TOFU
The internal link is the mechanism. It tells Google which pages on your site are important, and it passes link equity from your well-ranking TOFU pages down to the BOFU pages that need it.
One practical note: don’t wait until you have a large TOFU cluster built before internal linking. Link as you publish. Retrofitting links across 60 pages is a project. Doing it as you go is a habit.
Step 5: Measure TOFU the Right Way
Most teams measure TOFU by traffic. That’s how you end up celebrating a 40% organic traffic increase while your pipeline sits flat.
The right metrics for TOFU are authority signals, not traffic signals. Specifically, track:
| Metric | What it tells you | Where to check it |
|---|---|---|
| Backlinks earned (90-day) | Whether other sites find your content worth citing | Ahrefs / GSC Links report |
| BOFU ranking movement | Whether TOFU authority transfer is working | GSC Performance, filtered by BOFU URLs |
| Indexed page count | Whether TOFU pages are actually in Google’s index | GSC Pages report, “Not Indexed” status |
| Average position (rolling 90d) | Cluster-level authority trend | GSC Performance, topic cluster URL filter |
Traffic is a lagging indicator and a noisy one. An AI Overview showing up for one of your TOFU queries can halve your clicks without your ranking changing at all. If you track clicks and they drop, you’ll think your TOFU strategy is failing when actually it’s working. Google just summarized the answer before the click.
Authority is what makes traffic compound. Track it instead.
Common Mistakes That Kill TOFU Rankings
Beyond the five steps above, three specific mistakes trip up SaaS teams consistently.
Cannibalization across TOFU topics. If you’ve grouped keywords into topics (Step 1), you shouldn’t have this problem. But teams that build from flat keyword lists often publish three or four pieces on what is effectively one topic, split across different angles. Google can’t pick a winner, so it shows none of them consistently. Consolidate: pick the strongest piece and fold the others into it.
Publishing TOFU with no internal linking plan. “We’ll add links later” is how pages sit in isolation for a year. Before you publish any TOFU piece, know which BOFU or MOFU page it should link to, and add that link at the time of publishing.
Measuring traffic instead of authority. Already covered in Step 5, but worth repeating because it’s where most reporting goes wrong. If your monthly SEO report leads with sessions or clicks on TOFU content, you’re optimizing for the wrong signal, and you’ll make bad decisions because of it.
Why PipeRocket Digital Helps SaaS Teams Rank TOFU Content
At PipeRocket, we build TOFU content programs designed from day one to support BOFU rankings, not just drive awareness traffic. That means ICP-specific keyword research , format-matched content, depth standards that hold up after core updates, and internal linking wired in at publish time.
If your TOFU content isn’t ranking or isn’t converting into pipeline, reach out to us and we’ll show you what’s breaking. See how we work with SaaS teams at our SaaS SEO agency page .
Frequently Asked Questions
How long does it take for TOFU content to rank for SaaS?
Realistically, three to six months for a new domain or a thin authority site, and four to eight weeks on a domain that already has topical authority in the category. The timeline depends less on the quality of the specific piece and more on whether the site has the authority infrastructure around it.
A strong TOFU piece on a site with good internal linking and a few relevant backlinks will move faster than the same piece sitting in isolation on a site Google doesn’t fully trust yet. No movement after six months usually points to authority or indexation, not content quality.
Should SaaS startups focus on TOFU or BOFU keywords first?
For a brand-new SaaS site , BOFU first.
This is counterintuitive but it’s what the data supports. TOFU keywords on high-volume queries are competitive, and a new site isn’t going to outrank established players on “what is project management software” anytime soon. BOFU keywords (alternatives, comparisons, pricing pages) are lower competition, higher intent, and more likely to produce pipeline from whatever traffic does come in.
Once the BOFU pages are in place and the site has some domain authority , TOFU content starts to compound. Building TOFU first on a new site is how teams end up with lots of traffic and no pipeline.
How do I know if my TOFU pages are being indexed by Google?
Here’s how to check:
-
Open Google Search Console and go to Search Results. Filter by the URL of the page you want to check. If impressions are zero or near-zero and the page is more than four weeks old, it may not be indexed.
-
Go to the Pages report and look at “Not Indexed.” Two statuses matter here: “Crawled but not indexed” means Google visited but decided not to include the page. “Discovered but not indexed” means Google found it but hasn’t gotten to it yet.
-
For “Crawled but not indexed,” the fix is usually content depth. Google decided the page wasn’t worth showing. Add a real ICP-specific angle, deepen the argument, and use the URL Inspection tool to request reindexing after the update is published.