SaaS SEO Case Study: How Teal Ranks for 893K Keywords

Q: How is Teal using AI for SEO automation?

Teal uses Claude Desktop with the Playwright MCP to automate SERP analysis. Their automation fires up a headless browser, searches Google for a keyword, crawls each organic result, and extracts title tags, meta descriptions, H1-H6 headings, link counts, schema markup, and images. It then generates a competitive analysis report. They also vectorize all their content in Pinecone for automated internal linking recommendations.

TL;DR: TealHQ ranks for 893,000 keywords and gets roughly 1 million organic clicks per month. This saas seo case study breaks down how they got there — long-tail programmatic content, a 3-million-page job board, and AI-powered SERP analysis built in 20 minutes with Claude. But it also covers what went wrong: launching the job board tanked their highest-value resume keywords because Google shifted their topical authority. The lessons here apply to any SaaS company scaling content.

Source: This case study is based on a public podcast interview with David Fano, founder and CEO of TealHQ (tealhq.com), on The Edward Show (Episode 921). All data points are sourced directly from that conversation.

The Company: TealHQ

Teal is a consumer SaaS company that builds job search automation software. Their core product is an AI resume builder — a freemium tool where roughly 90% of the functionality is free. They also offer cover letter generators, job tracking tools, and a job search engine with 3 million listings.

The numbers (as of the interview):

Metric	Value
Organic keywords	893,000
Monthly organic clicks	~1,000,000
Ahrefs Domain Rating	72-73
Moz Domain Authority	46
Resume-related pages	~20,000-30,000
Job board pages	~3,000,000
Team size	Small (founder-led SEO)
Time in market	6 years

Teal's website runs on Webflow for the marketing site, with a custom React application for the product. They use Cloudflare reverse proxies to serve their job board pages on the main domain while keeping the marketing site on Webflow's hosting.

Strategy: Long-Tail First, Volume Second

Teal's SEO strategy was deliberately long-tail focused from the start. Their head terms — "resume builder," "AI resume builder" — are among the most competitive keywords in consumer SaaS. Established players with decades of domain authority and massive ad budgets dominate those SERPs.

Instead of fighting for head terms early, Teal targeted thousands of long-tail variations:

"HR cover letter"
"interest to put on resume"
"electrician certifications"
"cover letter for executive assistant"
"director of administration job description"

This worked because the resume and career space has enormous search volume spread across thousands of specific queries. A person searching "cover letter for executive assistant" has a specific, immediate need — and a tool that solves it right there converts well.

The long-tail approach built organic traffic and domain authority over years, giving Teal the foundation to eventually compete for higher-volume terms. Their information architecture reflects this: subfolders like /cover-letter-examples/ and /certifications/ organize programmatic content into clean collection structures on Webflow.

What Went Right: The ChatGPT Resume Play

One of Teal's biggest SEO wins came from pattern recognition, not keyword tools.

Three years ago — before custom GPTs existed, before OpenAI had a competitive domain presence — David Fano published a blog post targeting "ChatGPT resume." Every SEO tool showed zero search volume. Ahrefs said zero. Semrush said zero.

But Fano understood the zeitgeist. ChatGPT had just launched. People were going to use it for resumes. It was obvious to anyone paying attention — and Teal moved first.

The results:

Ranked number one for "ChatGPT resume"
Thousands of organic visitors per day
20% conversion rate to free signups
Months of first-mover traffic before competitors caught up

Eventually, OpenAI started ranking for the term themselves (as they should — it's their product name). But the window of opportunity generated substantial revenue for Teal.

The lesson for SaaS teams: SEO tools report historical search volume. They can't predict emerging demand. If you understand your customers deeply enough to anticipate what they'll search for next, you can capture terms before anyone else even targets them. This is one of the saas seo mistakes most companies make — being too dependent on tools and not enough on customer intuition.

What Went Wrong: 3 Million Pages That Broke Everything

This is the most instructive part of the saas seo case study, and the most relevant for any SaaS company planning to scale content.

Teal launched a job board with 3 million publicly indexed job pages. Each page was enhanced with AI — jobs were structured for readability, metadata was extracted (education requirements, benefits, ATS type), and Job Schema markup was implemented for Google Jobs indexing.

The job board worked. Pages ranked quickly. Traffic grew fast. From a product perspective, it made perfect sense — job seekers need jobs, and Teal helps them apply with better resumes.

But then something unexpected happened: Teal's resume-related rankings started declining.

They didn't change any resume pages. No content updates. No technical issues. The resume pages themselves were identical. But their rankings for "resume builder" and adjacent terms — the keywords that actually generate revenue — dropped.

Why It Happened: Topical Authority Dilution

Fano's theory, supported by conversations with SEO adviser David Quaid: Google recalculated Teal's topical authority based on page composition.

Before the job board: Teal had ~20,000-30,000 resume-related pages. Google understood them as a resume tool company.

After the job board: Teal had ~3,000,000 job pages and ~20,000-30,000 resume pages. The ratio flipped to roughly 100:1 in favor of jobs.

Google's interpretation shifted. Teal went from "resume tool" to "job site" in Google's entity graph. And since their domain is tealhq.com (not resumebuilder.com or resumesite.com), there was no domain-level signal anchoring them to the resume topic.

This mirrors what happened to HubSpot when Google cracked down on topical authority. HubSpot had been ranking for keywords completely unrelated to their CRM — quotes, random how-to articles — because their domain authority was so high. Google's topical authority updates changed that, and HubSpot lost rankings for off-topic content.

Teal's situation was subtler — jobs and resumes are adjacent topics. But adjacent isn't the same as identical. Google drew a boundary between the two.

The Missing Middle Layer

The root cause went deeper than just page ratio. Teal's content architecture was missing what Fano calls the "pillar middle" — intermediate hub pages between the head terms and the thousands of long-tail pages.

Their structure looked like this:

Homepage
  ├── Resume Builder (head term)
  │     └── 20,000+ long-tail resume pages
  └── Job Board
        └── 3,000,000 job pages

What it should have looked like:

Homepage
  ├── Resume Builder (head term)
  │     ├── Resume Examples (pillar)
  │     │     └── 200+ specific examples
  │     ├── Resume Format (pillar)
  │     │     └── Related format guides
  │     ├── Cover Letters (pillar)
  │     │     └── 500+ cover letter templates
  │     └── Certifications (pillar)
  │           └── Industry-specific guides
  └── Job Board
        ├── Jobs by Role (pillar)
        ├── Jobs by Location (pillar)
        └── Jobs by Industry (pillar)

Without that middle layer, Fano said, "we go from one to one to 500." Like organizational span of control: a manager shouldn't have 500 direct reports. A head term shouldn't have 500 long-tail pages hanging directly off it with no intermediary pillar to organize the hierarchy.

How They're Fixing It

Teal is now focused on three recovery strategies:

1. Building content bridges between jobs and resumes. If someone lands on a job page for "Senior Product Manager in Miami," that page now links to resume content: "How to write a resume for a senior product manager," "Resume bullets for product management," "How to prepare for a PM interview." This contextually connects the two topic areas rather than letting them exist as isolated silos.

2. Consolidating internal links to pillar pages. Working with SEO consultant Jonathan Boshoff, they identified a link equity dilution problem: pages had 30-50 internal links each, spreading authority too thin. The fix was consolidating. What was previously 30 unique links to 30 individual resume example pages became one link to a single "Resume Examples" pillar page with anchor navigation. The authority now flows to one strong page that distributes it downstream. (If you're evaluating whether to hire a specialist for this kind of architectural work, our best saas seo agencies guide covers what to look for.)

3. Building the missing pillar middle. Instead of adding more long-tail pages (which would fan out the architecture further), Fano is focused on creating intermediate pillar pages for terms like "resume format" (500K monthly searches) that Teal doesn't currently rank for. These pillars create the organizational structure Google needs to understand the topical hierarchy.

Keyword Cannibalization: One Page or Two?

Teal faced a classic keyword cannibalization challenge with their two highest-value terms: "resume builder" (high volume) and "AI resume builder" (one-tenth the volume).

Their existing page at /tools/resume-builder ranked for both terms. Fano wanted dedicated pages for each.

What they tried: Launched a separate /ai-resume-builder page. Changed all internal links on the site. Spent three months trying to get Google to send traffic to the new page.

What happened: Google refused. Every search for "AI resume builder" still landed on the original /tools/resume-builder page.

Why: As David Quaid explained, the existing page already had PageRank for both phrases. Google had it in its "memory" as the ranking page for those terms. To get Google to change its mind, Teal would essentially need to delete the existing page from the index and start from scratch — which was unacceptable for their main revenue page.

To validate whether the keywords were truly different, Fano built an automated SERP analysis tool (more on that below). His system analyzed SERP overlap on a 0-100 scale: below 50 means definitely create two pages, 50-80 means they're related (your call), above 80 means Google sees them as the same keyword. For "resume builder" vs "AI resume builder," the overlap was high — only Canva ranked highly for both with separate pages, and Canva started with two pages from the beginning.

The takeaway: Get your information architecture and keyword mapping right from day one. Retrofitting is exponentially harder once Google has already assigned PageRank to specific URLs.

SEO Automation: SERP Analysis in 20 Minutes

This is where the saas seo case study gets tactical. Fano built an AI-powered SERP analysis system using Claude Desktop, the Playwright MCP (Model Context Protocol), and a headless browser. The entire tool took 20 minutes to build.

What it does:

Takes a target keyword as input
Fires up a headless Chrome browser
Searches Google for the keyword
Crawls each organic result on page one
Extracts from each page: title tag, meta description, all H1-H6 headings, number of internal/external links, images present, schema markup implemented
Generates a competitive analysis report comparing all ranking pages

What he uses it for:

Determining whether Google sees keyword variations as the same or different (SERP overlap scoring)
Analyzing competitors' on-page optimization patterns
Identifying whether a keyword should target a listicle, landing page, or editorial piece based on what's actually ranking
Checking whether schema markup correlates with ranking position in specific verticals

Beyond SERP analysis, Teal vectorizes their entire content library in Pinecone (a vector database) so that content writing and brief-building agents can semantically search existing content, find internal linking opportunities, and avoid creating redundant content.

CRO vs. SEO: When Your Money Page Serves Two Masters

Teal's resume builder page is simultaneously their highest-traffic organic landing page and their primary conversion page. This created constant tension.

The SEO side wanted: Keywords in the H1. Internal links in the hero section. Long-form content below the fold. FAQ sections for featured snippets.

The CRO side wanted: A clean, distraction-free conversion page. An H1 optimized for on-page clarity, not keyword density. No competing links drawing users away from the signup flow.

Fano acknowledged this: "We had SEO blinders. We were putting links in the hero, and that's not great for CRO. This is a page that is your main money page landing page. It's not just a blog page."

What they learned: The title tag and H1 can serve different purposes. The title tag is for Google CTR ("Free AI Resume Builder 2025"). The H1 is for on-page conversion ("The best free AI resume builder"). The meta description is for search intent matching. These don't all need to carry the same keyword density.

For most SaaS companies in a saas seo context, the cleaner solution is separating SEO landing pages from product/conversion pages entirely. But when a single page already has significant PageRank and ranking history, you're often forced to make it work as both.

Key Takeaways for SaaS Teams

1. Long-tail works — until it doesn't. Long-tail SEO builds traffic and authority over time, but without intermediate pillar pages organizing the hierarchy, you end up with an unmanageable flat structure that confuses Google's topical classification.

2. New content sections can damage existing rankings. If you're launching a programmatic section (job board, directory, integration pages) that dwarfs your existing content, pre-plan the internal linking architecture before publishing. Teal's biggest regret was the startup-MVP mindset of "whatever, we'll fix it later." With SEO at scale, you can't.

3. Google remembers. Once a URL has PageRank for a keyword, Google is reluctant to reassign that ranking to a new URL. Get your information architecture and keyword-to-URL mapping right from the start.

4. Entity SEO is topical authority. What Google "thinks" your brand is about — based on the sum total of your content, backlinks, and off-site mentions — directly affects which keywords you can rank for. If 97% of your pages are about topic A and 3% are about topic B, Google will deprioritize topic B.

5. SERP analysis beats tool analysis. SEO tools aggregate historical data. The SERP tells you what Google actually values right now. Automating SERP analysis with AI agents (Claude + browser MCPs) gives you the depth of manual research at machine speed.

6. Anticipate demand, don't just measure it. Teal's "ChatGPT resume" play generated a 20% conversion rate from a keyword that every SEO tool said had zero volume. Understand your customers well enough to predict what they'll search for, not just react to what they already search for.

Frequently Asked Questions

How does Teal rank for nearly 900,000 keywords?

Teal's keyword footprint comes from a combination of long-tail programmatic content across ~20,000-30,000 resume-related pages and a job board with 3 million indexed pages. They target thousands of resume and career-related long-tail variations — "HR cover letter," "electrician certifications," "interest to put on resume" — and use Job Schema markup to get job pages indexed in Google Jobs. Their strategy was long-tail first: instead of competing for head terms against established players, they built volume and domain authority (Ahrefs DR 72-73) through thousands of specific queries.

What happened when Teal launched their job board?

Teal's resume-related rankings declined after launching 3 million job pages, even though the resume pages themselves were unchanged. The sheer volume of job content — outnumbering resume pages roughly 100:1 — shifted Google's perception of Teal's topical authority from "resume tool" to "job site." This is a direct manifestation of Google's topical authority algorithm: when the majority of your content is about topic A, Google deprioritizes your rankings for the less-represented topic B.

Can you rank for two similar keywords with one page?

It depends on SERP overlap. Teal tried creating separate pages for "resume builder" and "AI resume builder" but Google refused to send traffic to the new page after three months of effort — including changing all internal links site-wide. Because the existing page already had PageRank for both terms, Google wouldn't reassign rankings to a new URL. SEO adviser David Quaid explained that the only way to force the split would be to delete the existing page from Google's index and start fresh — which was too risky for Teal's primary revenue page.

How is Teal using AI for SEO automation?

Teal's CEO David Fano uses Claude Desktop with the Playwright MCP (Model Context Protocol) to automate SERP analysis. The system fires up a headless browser, searches Google for a target keyword, crawls each organic result on page one, and extracts title tags, meta descriptions, H1-H6 headings, link counts, schema markup, and images. It generates a competitive analysis report in minutes — a process that previously required hours of manual copy-pasting. They also vectorize all their content in Pinecone for automated internal linking recommendations and content gap analysis.

Want to build SEO content that targets the right keywords and avoids topical authority dilution? Alfa generates keyword-targeted, properly structured articles with internal linking built in — so your content strengthens your topical hierarchy instead of fragmenting it. Get 5 free articles →