Blog Writing

Verified against Perplexity · 2026-07-29

Run a competitive gap analysis on the ranking pages before writing a word

Audits the pages currently ranking for a target keyword to separate table-stakes coverage from genuine gaps, and gives an honest verdict on whether the keyword is even winnable before a draft gets commissioned.

ChatGPTClaudePerplexity5 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

You are running a competitive gap analysis on a target keyword before any drafting starts. The goal is an honest verdict on what a new post would actually need to include to compete, and whether competing for this keyword is realistic at all given who already ranks — not a reflexive "here's how to beat them" without checking if that's true.

TARGET KEYWORD
how to calculate customer acquisition cost

COMPETITOR PAGES AND NOTES
Top 3 are from HubSpot, a well-known finance-SaaS blog, and a VC firm — all include a formula, a worked example, and a downloadable calculator; none address CAC specifically for usage-based pricing models.

UNIQUE ASSETS AVAILABLE
Access to a real anonymized dataset of CAC benchmarks across 40 usage-based SaaS companies from an internal survey.

SEARCH INTENT
Informational with a calculation need — they want the formula and a way to apply it to their own numbers, not a product pitch.

CONTEXT
Considering a new post; the company has no existing page targeting this keyword today.

ANALYSIS RULES
Catalog what's common across most of the ranking pages first — the subtopics, format elements, and depth level that appear in the majority of them. This is the table-stakes baseline: a new post missing any of it will read as thinner than the competition on a direct side-by-side comparison, regardless of how good its unique material is elsewhere. Separately catalog what's inconsistent or missing across the set — subtopics only one or two pages cover, angles nobody has taken, data nobody cites. This is where a genuine gap might exist, but confirm it's an actual gap and not just something every ranking page correctly judged unnecessary; not every omission is an opportunity. Check for a format mismatch: if most ranking pages use a table, a specific tool, an interactive element, or video, and the planned new post would be plain prose, name that mismatch explicitly, since matching table-stakes content while ignoring a format signal the query itself seems to reward is still a losing bet. Assess how current the competing pages actually are — outdated statistics, references to a deprecated product version, pricing that's since changed — since a specific, well-timed update can be a genuine advantage that has nothing to do with writing quality. Evaluate the ranking domains' evident authority for this specific topic, not just their general size — a page from a much larger site can still be beatable if it's clearly not the site's core subject area, while a page from a smaller but deeply specialized site can be a genuinely hard target to unseat regardless of how good a new post is. Give an honest verdict: state plainly whether this keyword looks winnable with the unique assets actually available, winnable but only with a specific format or authority investment beyond just better writing, or not realistically winnable right now — don't default to "yes, write a better post" as a reflexive answer when the notes don't actually support it.

OUTPUT FORMAT
1. Table-stakes checklist: what any competitive post here must include.
2. Genuine gaps found, each with a note on why it's a real opportunity and not a correctly-skipped non-issue.
3. Format or authority mismatches, if any.
4. The honest winnability verdict, stated in one direct paragraph.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

Separating table-stakes coverage from genuine gaps addresses a common and expensive planning mistake: treating every subtopic the current top-ranking pages skip as an opportunity, when in reality most ranking pages skip the same things for the same good reason — they're out of scope, low-value, or actively confusing to include — and a differentiation angle built on a non-gap produces a section nobody wanted, dressed up as originality. Requiring a check on format mismatch, not just content depth, matters because a query's dominant ranking format is itself a signal about what that specific query rewards: if the pages ranking for a calculation-heavy keyword mostly ship an interactive calculator alongside their text, a well-written prose-only competitor is trying to win a fight it structurally can't win no matter how good the writing is, since it's competing on an axis — interactivity — that the format gap analysis exists specifically to surface before the writing investment gets made rather than after. The requirement for an honest winnability verdict, including the explicit permission to conclude a keyword isn't realistically winnable right now, targets a specific bias in how this kind of analysis usually gets requested: someone commissioning a competitive analysis has usually already decided to write the post, and a model that reflexively confirms winnability regardless of what the actual competitive notes show isn't doing analysis, it's providing cover for a decision that was made before the analysis started — naming the domains' evident topical authority as a real factor, separate from raw site size, gives the model a concrete basis for a negative verdict instead of an unfalsifiable one. Checking currency of competing pages as its own explicit factor is what surfaces a genuinely low-effort, high-confidence opportunity that a pure content-gap read would miss entirely: a page that's structurally excellent but cites three-year-old pricing or a deprecated product version can sometimes be beaten primarily by being current, which is a fundamentally different and often faster win than trying to out-write or out-research a well-built competing page from scratch.

Verified against

Perplexity Sonar Pro · 2026-07-29

Claude Claude Sonnet 5 · 2026-08-03

Changelog

  • 2026-07-29 Initial publish, verified against Perplexity (Sonar Pro) and Claude (Claude Sonnet 5).

Need this built into your business?

If a prompt isn't enough — SEO, built and maintained for you — that's Scult's day job.

EXPLORE SEO
All Blog Writing prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY