Article Page Generator
When the user wants to create, optimize, or audit a single article/post page (not the blog index). Also use when the user mentions "article page," "blog post page," "single post," "post template," "article structure," "post optimization," "competitor article analysis," "optimize based on top-ranking articles," "analyze ranking articles," "optimize article for SEO," or "article schema." For writing article body copy, use article-content. For blog listing/index page, use blog-page-generator.
- Skill ID
- kostja94/marketing-skills/article-page-generator
- Publisher
- kostja94
- Repository
- marketing-skills
- Installs
- 0
- Files
- 1
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
kostja94/marketing-skills/article-page-generatorInstalls these files- SKILL.md
What this skill tells the agent
Pages: Article (Single Post)
Guides structure, SEO, and UX for individual article pages — layout, metadata, schema, technical. For article body content (intro, body, conclusion, writing), see article-content. Distinct from blog-page-generator, which covers the blog index/listing page.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Output workflow: Always output in order: 0. Research Phase (keywords, search intent, competitors) → 1. Intent Analysis → 2. Content Analysis → 3. Recommendations. Do not skip steps. When Research Phase was performed via web search, show the search results and findings.
Optimization Foundation: Four Inputs
Article analysis and creation rest on four inputs. Gather or infer them before outputting recommendations:
| Input | Purpose | Source |
|---|---|---|
| Product | Product connection, features, use cases, CTA placement | project-context (Sections 1–4, 9–11); article content; web search |
| Keywords | Target keyword, primary/secondary placement | project-context Section 6; keyword-research; article |
| Article intent | Informational, commercial, transactional, navigational; drives structure, CTA, SEO depth | project-context Section 6 (target intent); article orientation; content type |
| Competitor articles | Structure to adopt, content gaps, length target, keyword opportunities | User-provided URLs; project-context Section 11; web search |
When any input is missing: Proactively ask or search. For article analysis: perform Research Phase (keyword search, search intent, competitor articles) by default — see Research Phase section. For product/keywords/intent, infer from article or prompt user to add project-context.
Before Analysis: Gather Context
1. Product / company context
Use available context to give tailored analysis:
| Source | Use for |
|---|---|
| project-context.md | Keywords (Section 6), competitors (Section 7), content strategy (Section 11), product connection |
| Article content | Extract product name, features, URLs; infer target keyword and audience |
| Web search | When analyzing a known brand: search for "[product] features", "[product] vs competitors", company positioning — use to validate product connection, suggest missing features/use cases, and improve competitor gap analysis |
If no project-context exists, infer from the article and optionally search for company/product info to enrich recommendations.
Research Phase: Keyword, Search Intent, Competitor (Required for Article Analysis)
Lightweight research for article analysis. When analyzing or auditing an article, perform searches and output the results in Section 0. Skip only if user explicitly asks to skip (e.g. "skip search").
- Keyword: Extract from article (title, H1, H2s, first 100 words); search for opportunities — see keyword-research (extract from article method)
- Search intent: Informational / Commercial / Transactional / Navigational — see keyword-research Search Intent
- Competitor articles: Fetch 2–3 top-ranking pages; analyze structure, gaps, length target — see competitor-research (Competitor Article Fetch Workflow)
Output format: See Output Format Section 0 below.
Scope
- Single article page: One post, one URL (e.g.
/blog/how-to-optimize-seo) - Not the blog index, category pages, or archive pages — see blog-page-generator for those
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for topics, audience, keywords, and Section 11 (Content/Blog/Article Strategy).
Identify:
- Product connection: How does this article support the product? (educate on problem, introduce features, nurture leads)
- Keyword basis: Target keyword from product context or keyword research — see keyword-research
- Content type: Blog post, guide, tutorial, news, evergreen
- Length: Short (<1,000 words), medium (1,000–2,500), long (2,500+)
- Intent: Informational, commercial, problem-aware
Product-linked content: Articles should tie to the product (problem it solves, features, use cases). Avoid purely generic content with no product relevance. Link to product/feature pages naturally in conclusion or when context fits.
Article Orientations
Choose structure, SEO depth, and schema based on orientation. See content-marketing for full Article Orientations (Funding/PR, Product update, Guide, News, Evergreen), SEO-driven vs non-SEO-driven, Evergreen vs Timely.
Intent Analysis output: Orientation, primary goal, SEO vs non-SEO, Evergreen vs timely — see Output Format Section 1.
Article Page Structure
| Section | Purpose |
|---|---|
| Hero/Header | Title (H1), author, single date (see schema-markup Date display for CTR), reading time (word count ÷ 200; round up), featured image, share buttons |
| TL;DR or Key Takeaways | See article-content for content; placed after intro; supports GEO/AI citation |
| Introduction | See article-content for hook, length, keyword placement |
| Body | See article-content for QAE, paragraph length, scannability |
| Conclusion | See article-content for summary, CTA, product connection |
| Related posts | 3–6 contextual links; end-of-article recommendations |
| Author bio | E-E-A-T; credentials, photo, link to author page — see eeat-signals |
Featured Image
See image-optimization (Article / Blog hero). Same image for Schema, Open Graph, Twitter Cards; min 1200px wide, absolute URL. See open-graph, twitter-cards.
Social Sharing
- Add share buttons (X, LinkedIn, Facebook, etc.) — see social-share-generator
- Place after intro and/or end of article; sticky sidebar for long-form
- Requires Open Graph and Twitter Cards for rich previews when shared
GEO / AI Optimization
See article-content for TL;DR, Key Takeaways, QAE pattern, answer-first; generative-engine-optimization for full GEO strategy.
Long-Form (1,000+ words)
- Add table of contents (TOC) after intro — see toc-generator
- Use jump links for major sections
- Break text with images, lists, definition boxes, mini-FAQs
SEO Best Practices
Title & Meta
| Element | Guideline |
|---|---|
| Title | 55 chars; primary keyword near start; power words |
| Meta description | 150–160 chars; CTA; primary keyword |
| H1 | One per page; matches title; primary keyword naturally |
Keyword Placement
- Title: 1× primary keyword
- First 100 words: 1× primary keyword
- Body: 2–3× naturally; avoid stuffing
- At least one H2: Include primary or related keyword
Content Quality
See article-content for readability, depth, originality, word count by type. E-E-A-T: Author bio, citations, changelog, expert quotes — see eeat-signals.
Common Mistakes to Avoid
- Multiple H1s; skipping heading levels (H2→H4); keyword stuffing in headings
- Neglecting conclusion or CTA; no internal links to related content
- Walls of text; generic "click here" anchors
URL
Use url-slug-generator for slug creation. Key rules:
- Slug: 3–5 words; under 60 chars; primary keyword; lowercase, hyphens
- Example:
/blog/ai-people-searchnot/blog/ai-search-engine-finding-people-speed-discovery-outreach - Avoid: Date in path (
/blog/2025/01/15/article-title); copy-pasting full title
Date Display
See schema-markup (Date display for CTR): show only one visible date; prefer dateModified.
Schema & Open Graph
More from kostja94
Use this skill in a project
Open any RiverX project, search the Skills panel for kostja94/marketing-skills/article-page-generator, and install it in one click.
