Article Outranker: PAS + Gap Mapping to Beat Competitor Pages
Ranking above a specific competitor page requires understanding exactly what that page does well, what it misses, and writing something that makes both irrelevant. Methodology, not guesswork.
Step 1: Extract Competitor Content
From the target competitor URL, pull:
COMPETITOR ANALYSIS:
- URL: [competitor URL]
- H1: [exact text]
- Word count: [number]
- H2 structure: [list all H2s]
- H3 structure under each H2: [list]
- Has FAQ section: Y/N (how many questions?)
- Has data/stats: Y/N (how many, sourced?)
- Has images/tables: Y/N (count)
- Author byline: Y/N (credentials shown?)
- Last updated date: [date or unknown]
- Internal links: [count]
- CTA present: Y/N
Step 2: Score Competitor Weaknesses
Rate each dimension 1-10 (10 = excellent, 1 = terrible):
| Dimension | Score | Weakness Details | |-----------|-------|-----------------| | Depth | [1-10] | Which sections are shallow? | | Recency | [1-10] | Is data stale? Missing current-year context? | | Specificity | [1-10] | Vague claims without numbers or examples? | | E-E-A-T | [1-10] | No author, no citations, no first-person experience? | | Intent match | [1-10] | Does it fully answer the query or drift off-topic? |
Prioritize beating the lowest-scored dimensions. If E-E-A-T is a 3, own that gap first.
Step 3: Build Gap Map
List everything the competitor missed:
GAP MAP:
Topics they covered (don't skip these — must match or exceed):
1. [Topic]
2. [Topic]
...
Topics they MISSED entirely (mandatory additions to your article):
1. [Missing topic] — [why this matters to the reader]
2. [Missing topic] — [why this matters to the reader]
3. [Missing topic] — [why this matters to the reader]
Questions in PAA that competitor didn't answer:
1. [Question]
2. [Question]
...
Data they used that's stale or missing:
1. [Data point that needs updating or adding]
Step 4: Write With PAS Intro Framework
Problem — Agitate — Solution applied to the intro:
Problem: State the searcher's core pain point in plain language. Don't introduce the article — answer why they searched.
Agitate: Explain why existing answers (including the competitor's) fall short. This creates the "finally, someone gets it" reaction.
Solution: Promise what this article delivers. Be specific: "By the end of this, you'll know [X] and be able to [Y]."
Intro length: 100-150 words. The PAS framework does not need more space than that.
Step 5: Write the Article
Structural rules for the outranker:
- Word count: competitor word count + 15-20% minimum
- Every competitor H2 covered (matched or exceeded in depth)
- 3+ sections from gap map that competitor has zero coverage on
- Stats: more data points than competitor, all sourced and current
- FAQ section: every PAA question competitor missed, plus their answered ones
- Author byline or expertise signal in intro
- Internal links: competitor count + 2 minimum
Step 6: Pre-Publish Outrank Checklist
Run before publishing:
- [ ] Word count exceeds competitor by 15%+
- [ ] Every competitor H2 matched or exceeded in depth
- [ ] 3+ gap map sections present with unique content
- [ ] More specific data points than competitor (count them)
- [ ] FAQ answers every PAA question competitor ignored
- [ ] H1 and title tag engineered for higher CTR than competitor's title
- [ ] Meta description has a CTA competitor's doesn't
- [ ] E-E-A-T score higher than competitor on each dimension
- [ ] Published date is current (not backdated)
CTR Engineering: Title and Meta
Competitor's title is a baseline, not a ceiling. Engineer for higher CTR:
Title upgrades:
- Add current year: "Guide to X (2026)" beats "Guide to X"
- Add specificity: "7 Proven Steps" beats "How to"
- Add outcome: "...That Actually Work" beats generic
- Add audience: "...for [Specific Audience]"
Meta description upgrades:
- Include a number: "Discover 5 methods..."
- Include a question: "Not sure which X to choose? Here's the breakdown."
- Include a CTA: "Read the full comparison."
#content-sop #seo #outranker #competitor