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