{"slug":"article-rewriter","title":"Article Rewriter — Existing Content Improvement Pipeline","tags":["seo","content-rewriting","content-optimization","on-page","editorial"],"agent_summary":"Pipeline for improving existing articles to outrank their current competition: competitive gap analysis per article, entity enrichment, E-E-A-T signal injection, structural improvements, featured snippet engineering, and quality gate before republication.","trigger_phrases":["article rewriter","rewrite article SEO","improve existing content","content improvement pipeline","SEO rewrite","rewrite for SEO","optimize existing articles","content refresh rewrite"],"runnable":true,"markdown":"\n## When to Rewrite vs Refresh vs Create New\n\n**Rewrite:** Article ranks position 5-20 but is losing ground, has clear entity or E-E-A-T gaps, or was written before semantic SEO was the priority. Rewriting reorganizes structure, adds entities, injects experience signals, and re-engineers the featured snippet target.\n\n**Refresh:** Article ranks position 1-5 and has good signals. Only update stale statistics, add new FAQ pairs, update `dateModified`. Do not restructure or rewrite performing content.\n\n**Create new:** Article ranks position 21+ with no impressions, or the existing page targets the wrong intent. Redirect old URL to new page if the new page replaces the old one completely.\n\n## Phase 1: Competitive Analysis (Pre-Rewrite)\n\nBefore changing anything, understand what ranks above you and why.\n\n**Step 1: Pull top 5 URLs for the target keyword.**\n\nVia DataForSEO SERP endpoint or manual SERP check.\n\n**Step 2: Content inventory per competing URL.**\n\nFor each of the top 5, record:\n- Word count (target: match #1 + 10-15%)\n- H2 topics covered (what sub-topics does the competitor address that you don't?)\n- Featured snippet target (does a competitor own a featured snippet? What's their snippet structure?)\n- Schema types present\n- Number of FAQ pairs\n- Internal link structure (how many and where do they link?)\n- Entity declarations (what primary entities appear in H1 and first paragraph?)\n\n**Step 3: Gap matrix.**\n\nBuild a simple table: competitor topic coverage vs your current coverage. Every sub-topic in 3/5 competing pages that your article doesn't address = a critical rewrite target.\n\n## Phase 2: Entity Enrichment\n\nPull the Google NLP API analysis for your article and for the top-ranking competitor article.\n\nCompare entity salience scores:\n- Entities with salience 0.7+ in competitor, below 0.3 in yours = missing primary entity\n- Entities completely absent from yours = entity gap\n\nFor each entity gap:\n- Add a paragraph or sentence where the entity appears in context\n- Ensure the primary business entity appears in H1, first paragraph, and schema\n- Ensure location entities appear in at least 2 H2s for local intent queries\n\n## Phase 3: E-E-A-T Signal Injection\n\nRun `eeat-factor-extractor` on the current article to identify which signals are absent. Then inject:\n\n**Experience signals (minimum 2 per article):**\n- Add a first-person anecdote per section where it fits naturally: \"When we handled [specific scenario] in [location]...\"\n- Add before/after specifics for service businesses\n- Add a case study section with real (anonymized if needed) project data\n\n**Expertise signals:**\n- Verify all technical claims are accurate and use correct terminology\n- Add at least one code section, regulation citation, or technical specification where relevant\n- Update author byline to include specific credentials relevant to the article topic\n\n**Authority signals:**\n- Add 2-3 outbound links to authoritative sources (government data, industry associations, peer-reviewed research)\n- Update or add author bio linking to LinkedIn or other credentials\n- Add publication date + last updated date visible on page\n\n**Trust signals:**\n- Verify NAP is accessible site-wide\n- If pricing content: add date stamp for when price data was verified\n- If regulatory content: cite specific regulation number and agency\n\n## Phase 4: Structural Improvements\n\n**H1 optimization:**\n- If keyword is not in first 5 words of H1, restructure\n- If H1 is a question, convert to declarative unless PAA-targeting is the explicit goal\n\n**H2 restructuring:**\n- Cover all topic gaps identified in Phase 1 competitive analysis\n- Ensure each H2 addresses a distinct sub-topic (no redundant H2s)\n- At least one H2 should be phrased as a question (PAA signal)\n\n**Featured snippet engineering:**\n- Identify the H3 most likely to produce a featured snippet (process question, definition question, or comparative question)\n- Write a 40-60 word answer block directly under that H3: entity name first, declarative sentence, numeric data point, no hedging language\n- Expand below the snippet block to 200-300 words (snippet appears above, content satisfies depth below)\n\n**Internal linking improvements:**\n- Link to the pillar page for this topic cluster from within the article\n- Link to 2-3 closely related spoke pages\n- Link from 2-3 existing related articles to this article using descriptive anchor text\n\n## Phase 5: Technical Formatting\n\n- Verify heading hierarchy: H1 → H2 → H3 (no skipped levels)\n- Convert all bullet lists with 4+ items to either a table or a numbered process list\n- Ensure images have descriptive alt text and WebP format\n- Add FAQPage schema with 4-6 Q&A pairs relevant to the article's topic\n- Verify canonical tag points to the correct URL\n- Update `dateModified` in Article schema after rewrite\n\n## Quality Gate Before Republication\n\nBefore republishing, verify:\n- [ ] Word count matches or exceeds #1 competitor + 10%\n- [ ] All critical topic gaps from Phase 1 addressed\n- [ ] Entity salience gaps from Phase 2 filled\n- [ ] Minimum 2 experience markers present\n- [ ] Featured snippet target H3 + 40-60 word answer block present\n- [ ] FAQPage schema with 4+ Q&A pairs installed\n- [ ] Author byline with credentials visible\n- [ ] At least 2 authoritative outbound links\n- [ ] Internal links to pillar page + 2 related spoke pages\n- [ ] `dateModified` updated in Article schema\n\n## Cross-References\n\n- `eeat-factor-extractor` — signal inventory before Phase 3\n- `koray-content-brief` — brief structure that a rewrite should conform to\n- `featured-snippet-optimizer` — snippet engineering detailed in Phase 4\n- `content-freshness-decay-monitor` — determines which articles need full rewrite vs refresh\n\n#seo-sop #seo #content-rewriting #content-optimization #on-page #editorial\n","html":"<h2>When to Rewrite vs Refresh vs Create New</h2>\n<p><strong>Rewrite:</strong> Article ranks position 5-20 but is losing ground, has clear entity or E-E-A-T gaps, or was written before semantic SEO was the priority. Rewriting reorganizes structure, adds entities, injects experience signals, and re-engineers the featured snippet target.</p>\n<p><strong>Refresh:</strong> Article ranks position 1-5 and has good signals. Only update stale statistics, add new FAQ pairs, update <code>dateModified</code>. Do not restructure or rewrite performing content.</p>\n<p><strong>Create new:</strong> Article ranks position 21+ with no impressions, or the existing page targets the wrong intent. Redirect old URL to new page if the new page replaces the old one completely.</p>\n<h2>Phase 1: Competitive Analysis (Pre-Rewrite)</h2>\n<p>Before changing anything, understand what ranks above you and why.</p>\n<p><strong>Step 1: Pull top 5 URLs for the target keyword.</strong></p>\n<p>Via DataForSEO SERP endpoint or manual SERP check.</p>\n<p><strong>Step 2: Content inventory per competing URL.</strong></p>\n<p>For each of the top 5, record:</p>\n<ul>\n<li>Word count (target: match #1 + 10-15%)</li>\n<li>H2 topics covered (what sub-topics does the competitor address that you don't?)</li>\n<li>Featured snippet target (does a competitor own a featured snippet? What's their snippet structure?)</li>\n<li>Schema types present</li>\n<li>Number of FAQ pairs</li>\n<li>Internal link structure (how many and where do they link?)</li>\n<li>Entity declarations (what primary entities appear in H1 and first paragraph?)</li>\n</ul>\n<p><strong>Step 3: Gap matrix.</strong></p>\n<p>Build a simple table: competitor topic coverage vs your current coverage. Every sub-topic in 3/5 competing pages that your article doesn't address = a critical rewrite target.</p>\n<h2>Phase 2: Entity Enrichment</h2>\n<p>Pull the Google NLP API analysis for your article and for the top-ranking competitor article.</p>\n<p>Compare entity salience scores:</p>\n<ul>\n<li>Entities with salience 0.7+ in competitor, below 0.3 in yours = missing primary entity</li>\n<li>Entities completely absent from yours = entity gap</li>\n</ul>\n<p>For each entity gap:</p>\n<ul>\n<li>Add a paragraph or sentence where the entity appears in context</li>\n<li>Ensure the primary business entity appears in H1, first paragraph, and schema</li>\n<li>Ensure location entities appear in at least 2 H2s for local intent queries</li>\n</ul>\n<h2>Phase 3: E-E-A-T Signal Injection</h2>\n<p>Run <code>eeat-factor-extractor</code> on the current article to identify which signals are absent. Then inject:</p>\n<p><strong>Experience signals (minimum 2 per article):</strong></p>\n<ul>\n<li>Add a first-person anecdote per section where it fits naturally: \"When we handled [specific scenario] in [location]...\"</li>\n<li>Add before/after specifics for service businesses</li>\n<li>Add a case study section with real (anonymized if needed) project data</li>\n</ul>\n<p><strong>Expertise signals:</strong></p>\n<ul>\n<li>Verify all technical claims are accurate and use correct terminology</li>\n<li>Add at least one code section, regulation citation, or technical specification where relevant</li>\n<li>Update author byline to include specific credentials relevant to the article topic</li>\n</ul>\n<p><strong>Authority signals:</strong></p>\n<ul>\n<li>Add 2-3 outbound links to authoritative sources (government data, industry associations, peer-reviewed research)</li>\n<li>Update or add author bio linking to LinkedIn or other credentials</li>\n<li>Add publication date + last updated date visible on page</li>\n</ul>\n<p><strong>Trust signals:</strong></p>\n<ul>\n<li>Verify NAP is accessible site-wide</li>\n<li>If pricing content: add date stamp for when price data was verified</li>\n<li>If regulatory content: cite specific regulation number and agency</li>\n</ul>\n<h2>Phase 4: Structural Improvements</h2>\n<p><strong>H1 optimization:</strong></p>\n<ul>\n<li>If keyword is not in first 5 words of H1, restructure</li>\n<li>If H1 is a question, convert to declarative unless PAA-targeting is the explicit goal</li>\n</ul>\n<p><strong>H2 restructuring:</strong></p>\n<ul>\n<li>Cover all topic gaps identified in Phase 1 competitive analysis</li>\n<li>Ensure each H2 addresses a distinct sub-topic (no redundant H2s)</li>\n<li>At least one H2 should be phrased as a question (PAA signal)</li>\n</ul>\n<p><strong>Featured snippet engineering:</strong></p>\n<ul>\n<li>Identify the H3 most likely to produce a featured snippet (process question, definition question, or comparative question)</li>\n<li>Write a 40-60 word answer block directly under that H3: entity name first, declarative sentence, numeric data point, no hedging language</li>\n<li>Expand below the snippet block to 200-300 words (snippet appears above, content satisfies depth below)</li>\n</ul>\n<p><strong>Internal linking improvements:</strong></p>\n<ul>\n<li>Link to the pillar page for this topic cluster from within the article</li>\n<li>Link to 2-3 closely related spoke pages</li>\n<li>Link from 2-3 existing related articles to this article using descriptive anchor text</li>\n</ul>\n<h2>Phase 5: Technical Formatting</h2>\n<ul>\n<li>Verify heading hierarchy: H1 → H2 → H3 (no skipped levels)</li>\n<li>Convert all bullet lists with 4+ items to either a table or a numbered process list</li>\n<li>Ensure images have descriptive alt text and WebP format</li>\n<li>Add FAQPage schema with 4-6 Q&#x26;A pairs relevant to the article's topic</li>\n<li>Verify canonical tag points to the correct URL</li>\n<li>Update <code>dateModified</code> in Article schema after rewrite</li>\n</ul>\n<h2>Quality Gate Before Republication</h2>\n<p>Before republishing, verify:</p>\n<ul>\n<li>[ ] Word count matches or exceeds #1 competitor + 10%</li>\n<li>[ ] All critical topic gaps from Phase 1 addressed</li>\n<li>[ ] Entity salience gaps from Phase 2 filled</li>\n<li>[ ] Minimum 2 experience markers present</li>\n<li>[ ] Featured snippet target H3 + 40-60 word answer block present</li>\n<li>[ ] FAQPage schema with 4+ Q&#x26;A pairs installed</li>\n<li>[ ] Author byline with credentials visible</li>\n<li>[ ] At least 2 authoritative outbound links</li>\n<li>[ ] Internal links to pillar page + 2 related spoke pages</li>\n<li>[ ] <code>dateModified</code> updated in Article schema</li>\n</ul>\n<h2>Cross-References</h2>\n<ul>\n<li><code>eeat-factor-extractor</code> — signal inventory before Phase 3</li>\n<li><code>koray-content-brief</code> — brief structure that a rewrite should conform to</li>\n<li><code>featured-snippet-optimizer</code> — snippet engineering detailed in Phase 4</li>\n<li><code>content-freshness-decay-monitor</code> — determines which articles need full rewrite vs refresh</li>\n</ul>\n<p>#seo-sop #seo #content-rewriting #content-optimization #on-page #editorial</p>\n"}