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.
Article analysis and creation rest on four inputs. Gather or infer them before outputting recommendations:
InputPurposeSourceProductProduct connection, features, use cases, CTA placementproject-context (Sections 1–4, 9–11); article content; web searchKeywordsTarget keyword, primary/secondary placementproject-context Section 6; keyword-research; articleArticle intentInformational, commercial, transactional, navigational; drives structure, CTA, SEO depthproject-context Section 6 (target intent); article orientation; content typeCompetitor articlesStructure to adopt, content gaps, length target, keyword opportunitiesUser-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.
1. Product / company context
Use available context to give tailored analysis:
SourceUse forproject-context.mdKeywords (Section 6), competitors (Section 7), content strategy (Section 11), product connectionArticle contentExtract product name, features, URLs; infer target keyword and audienceWeb searchWhen 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.
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").
Output format: See Output Format Section 0 below.
/blog/how-to-optimize-seo)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-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.
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.
SectionPurposeHero/HeaderTitle (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 TakeawaysSee article-content for content; placed after intro; supports GEO/AI citationIntroductionSee article-content for hook, length, keyword placementBodySee article-content for QAE, paragraph length, scannabilityConclusionSee article-content for summary, CTA, product connectionRelated posts3–6 contextual links; end-of-article recommendationsAuthor bioE-E-A-T; credentials, photo, link to author page — see eeat-signals
See image-optimization (Article / Blog hero). Same image for Schema, Open Graph, Twitter Cards; min 1200px wide, absolute URL. See open-graph, twitter-cards.
See article-content for TL;DR, Key Takeaways, QAE pattern, answer-first; generative-engine-optimization for full GEO strategy.
ElementGuidelineTitle55 chars; primary keyword near start; power wordsMeta description150–160 chars; CTA; primary keywordH1One per page; matches title; primary keyword naturally
See article-content for readability, depth, originality, word count by type. E-E-A-T: Author bio, citations, changelog, expert quotes — see eeat-signals.
Use url-slug-generator for slug creation. Key rules:
/blog/ai-people-search not /blog/ai-search-engine-finding-people-speed-discovery-outreach/blog/2025/01/15/article-title); copy-pasting full titleSee schema-markup (Date display for CTR): show only one visible date; prefer dateModified.
See schema-markup for Article/BlogPosting/NewsArticle type selection, required properties, JSON-LD example, and date display. Validate with Rich Results Test.
Use og:type: article for article pages (not website):
html
<meta property="og:type" content="article">
<meta property="og:article:published_time" content="2025-01-15T09:00:00Z">
<meta property="og:article:modified_time" content="2025-02-01T14:30:00Z">
<meta property="og:article:author" content="https://example.com/author/jane">
ElementGuidelineVolume3–5 contextual links in body + 3–6 in Related posts = 6–11 total per articleFirst paragraph1 link to pillar or key related contentBody2–4 contextual links; one per major section when relevantRelated posts3–6 end-of-article links; same topic clusterAnchor textDescriptive (e.g. "SEO checklist for 2025", "how to optimize meta tags"); avoid "click here", "learn more", "read more"VariationMix exact-match, partial-match, branded anchors; avoid over-optimizationOrphan preventionEvery article has ≥1 internal link from hub/pillar or nav
ElementGuidelineVolume2–5 external links per article; cite authoritative sourcesWhen to useStatistics, research, definitions, tool comparisons, expert quotesAnchor textDescriptive (e.g. "Google's Search Quality Guidelines", "SEO study"); link to sourceSame URLCounts once per page for link equity; no need to repeatE-E-A-TExternal links to reputable sources signal trust — see eeat-signals
See article-content for citation format; eeat-signals for E-E-A-T and when to include.
See article-content for AI-assisted content guidance; eeat-signals for E-E-A-T.
When auditing or optimizing an article, apply the Content Audit Checklist. See article-content for full dimensions.
When analyzing or auditing an article, output this section before Intent Analysis. Include search sources and findings. If user asked to skip search, note that and infer from article only.
SectionOutputKeyword SearchPrimary keyword (from article or search), secondary keywords, keyword opportunities (from SERP/competitor analysis). If search was performed: query used, top results observed.Search IntentIntent for primary keyword (Informational/Commercial/Transactional/Navigational), intent for 2–3 secondary keywords, whether article content matches intent. If search was performed: SERP snippet types observed.Competitor ArticlesIf searched: 2–3 URLs, brief structure (word count, H2s), content gaps, length target. If user provided URLs: same. See competitor-research for full methodology. If skipped: "Competitor analysis skipped."
Before any recommendations, output a brief analysis:
DimensionOutputOrientationFunding/PR, Product update, Guide, News, EvergreenPrimary goalBrand, PR, education, product adoption, organic traffic, …SEO vs non-SEOSEO-driven / Non-SEO-driven / HybridEvergreen vs timelyEvergreen / TimelyImplications1–2 sentences: e.g. "Low SEO priority → focus on clarity, shareability" or "SEO-driven → full keyword + GEO optimization"
Apply the Content Analysis table above. Output a brief assessment per dimension (✅ / ⚠️ / ❌ + one-line note).
Assign priority to each item: P0 (critical), P1 (high), P2 (medium), P3 (nice-to-have). Output as table or list with priority prefix.
PriorityUse whenP0Blocks GEO/SEO; missing core element (TL;DR or Key Takeaways, keyword in first 100 words, schema)P1Significant impact on traffic, CTR, or conversion (title length, share buttons, CTA)P2Improves UX or authority (related posts, author bio, internal links)P3Polish (image optimization, readability tweaks)
Example: [P0] Add TL;DR or Key Takeaways — GEO, AI citation