--- license: Apache-2.0 name: seo-content-blogging description: Writing informational blog posts that rank in search -- genuine technical content that serves humans AND search engines. Covers topic research, keyword mapping, content structure for featured snippets, technical blog templates (tutorial, comparison, deep-dive, case study), internal linking strategy, meta tags, schema markup, content freshness cycles, and measuring ROI. Activate on 'SEO blog', 'blog post SEO', 'content strategy', 'keyword research', 'technical blog', 'blog ranking', 'search optimization', 'content calendar', 'featured snippets', 'schema markup'. NOT for social media or launch tactics (use tech-launch-channels) or general product announcements (use product-announcement-craft). allowed-tools: Read,Write,Edit,Glob,Grep,WebSearch,WebFetch metadata: category: Marketing & Launch tags: - seo - blogging - content-strategy - technical-writing - keyword-research - developer-blog pairs-with: - skill: seo-visibility-expert reason: Technical SEO auditing and site-level optimization complements content-level SEO - skill: technical-writer reason: Clear technical writing is the foundation of content that ranks and converts - skill: tech-launch-channels reason: Distribute blog content across channels for backlinks and initial traffic category: Content & Marketing tags: - seo - blogging - content-strategy - keywords - organic-traffic --- # SEO Content Blogging Writing technical blog posts that rank in search engines -- not keyword stuffing, but genuinely useful content that also happens to satisfy every signal Google cares about. This skill covers the full lifecycle from topic research to published post to long-term maintenance. ## When to Use **Use for:** - Planning a content calendar for a developer blog - Researching topics and keywords for technical blog posts - Structuring a blog post for both human readers and search engines - Adding schema markup, meta tags, and internal linking to existing content - Auditing existing blog posts for SEO improvement opportunities - Writing new technical content in SEO-optimized formats (tutorials, comparisons, case studies) **Do NOT use for:** - Product announcements or launch posts (use product-announcement-craft) - Social media content or launch channel tactics (use tech-launch-channels) - Paid advertising or SEM campaigns - Link building outreach or off-page SEO (use seo-visibility-expert for technical SEO) --- ## The SEO Content Lifecycle ``` RESEARCH → PLAN → WRITE → OPTIMIZE → PUBLISH → DISTRIBUTE → MEASURE → REFRESH ↑ │ └──────────────────────────────────────────────────────────────────────┘ ``` Content is not "done" when published. The refresh cycle is what separates blogs that compound from blogs that decay. --- ## Step 1: Topic Research and Keyword Mapping ### Finding Topics That Rank Start with problems your audience searches for, not features you want to promote. **Sources for topic ideas:** 1. **Google Autocomplete** -- Type your topic, note the suggestions 2. **People Also Ask** -- The accordion questions in Google results 3. **Reddit and HN comments** -- What questions do people ask repeatedly? 4. **Stack Overflow** -- Most-voted questions in your domain 5. **Competitor blogs** -- What ranks for them? (Use Ahrefs, Semrush, or free tools like Ubersuggest) 6. **Your support inbox** -- Questions customers ask are questions people search for ### Keyword Intent Classification Not all keywords are equal. Understand intent before writing. | Intent | Example | What to Write | Conversion Potential | |--------|---------|---------------|---------------------| | **Informational** | "what is a DAG" | Tutorial / explainer | Low (top of funnel) | | **Comparative** | "Airflow vs Prefect" | Comparison post | Medium | | **Problem-solving** | "how to parallelize AI agents" | How-to guide | Medium-High | | **Tool-seeking** | "best DAG orchestration tool" | Listicle / review | High | | **Transactional** | "windags pricing" | Landing page (not blog) | Highest | ### Keyword Mapping Template ``` Primary keyword: "how to orchestrate AI agents" Search volume: ~1,200/month Difficulty: Medium Intent: Problem-solving Secondary keywords: - "AI agent orchestration framework" - "parallel AI agent execution" - "multi-agent workflow" Long-tail variations: - "how to run multiple AI agents in parallel" - "best way to coordinate Claude agents" - "DAG-based AI workflow tool" People Also Ask: - "What is an AI agent orchestrator?" - "How do AI agents communicate with each other?" - "Can you run multiple AI agents at the same time?" ``` Map each article to ONE primary keyword and 3-5 secondary keywords. Never target the same primary keyword with two different articles (that is keyword cannibalization). --- ## Step 2: Content Structure for Humans and Search Engines ### The Blog Post Anatomy ```html

How to Orchestrate AI Agents with DAGs

AI agent orchestration is the process of coordinating multiple AI agents to execute complex tasks in parallel. This guide shows you how to build DAG-based workflows that...

What Is AI Agent Orchestration?

Why Use DAGs for Multi-Agent Workflows?

Step-by-Step: Building Your First Agent DAG

Common Mistakes and How to Avoid Them

Comparing Agent Orchestration Frameworks

Frequently Asked Questions

``` ### Heading Hierarchy Rules - **H1:** One per page. Contains the primary keyword. Under 60 characters. - **H2:** Major sections. Each should be independently valuable (some readers jump to one section via search). - **H3:** Subsections within an H2. Use for step numbers, sub-topics, or examples. - Never skip heading levels (H1 then H3 with no H2). ### The Featured Snippet Formula Google pulls featured snippets from content that directly answers a question in a structured format. To win snippets: **For definitions:** ```markdown ## What Is [Term]? [Term] is [40-60 word definition that directly answers the question]. ``` **For "how to" queries:** ```markdown ## How to [Do Thing] 1. **Step one** -- [brief description] 2. **Step two** -- [brief description] 3. **Step three** -- [brief description] ``` **For comparisons:** ```markdown ## [Tool A] vs [Tool B] | Feature | Tool A | Tool B | |---------|--------|--------| | Speed | Fast | Faster | | Price | Free | $29/mo | ``` **For lists:** ```markdown ## Best [Category] Tools in 2026 1. **[Tool]** -- [one-line description] 2. **[Tool]** -- [one-line description] ``` --- ## Step 3: Technical Blog Post Templates ### Template 1: The Tutorial (Highest SEO value for dev tools) ```markdown # How to [Achieve Outcome] with [Technology] [2-sentence summary that answers the search query directly] ## Prerequisites - [What the reader needs before starting] ## Step 1: [First Action] [Explanation + code block] ## Step 2: [Second Action] [Explanation + code block] ## Step 3: [Third Action] [Explanation + code block] ## What You Built [Screenshot/demo of the finished result] ## Next Steps [Links to related tutorials, advanced topics] ## FAQ [3-5 questions from People Also Ask, answered concisely] ``` **SEO power:** Tutorials rank for long-tail "how to" queries, which have high intent and low competition. ### Template 2: The Comparison Post ```markdown # [Tool A] vs [Tool B]: Which Should You Use in 2026? [1-paragraph summary with recommendation for the impatient reader] ## Quick Comparison | Criteria | Tool A | Tool B | |----------|--------|--------| | Best for | ... | ... | | Price | ... | ... | | Learning curve | ... | ... | ## [Tool A] Overview [What it is, who it's for, strengths and weaknesses] ## [Tool B] Overview [Same structure] ## Head-to-Head: [Specific Criterion] [Detailed comparison on the dimension people care about most] ## When to Choose [Tool A] ## When to Choose [Tool B] ## FAQ ``` **SEO power:** Comparison queries ("X vs Y") have very high purchase intent. A fair, detailed comparison builds trust. ### Template 3: The Deep-Dive / Architecture Post Structure: Problem Space, Architecture Overview, Component Deep-Dives (with code and diagrams), What We Tried That Didn't Work (honesty earns trust), Performance Characteristics (benchmarks), Lessons Learned. **SEO power:** Architecture posts earn backlinks from other developers referencing your approach. Backlinks are the strongest off-page ranking signal. ### Template 4: The Case Study Structure: The Challenge (specific problem with numbers), The Approach (step by step), The Results (time saved, cost reduced, performance improved), Key Takeaways (3-5 transferable bullet points). **SEO power:** Case studies rank for problem-specific queries and build credibility signals (E-E-A-T). --- ## Step 4: On-Page Optimization ### Meta Tags Checklist Every blog post needs these meta tags: - **Title tag:** Primary keyword near front, brand at end, under 60 chars. Example: `How to Orchestrate AI Agents with DAGs | Windags` - **Meta description:** 150-160 chars, action-oriented, includes primary keyword - **Open Graph tags:** `og:title`, `og:description`, `og:image` (1200x630px), `og:type` = "article" - **Twitter Card:** `twitter:card` = "summary_large_image", `twitter:title`, `twitter:image` ### Schema Markup (Structured Data) Add JSON-LD schema to every blog post for rich results in search. Use the appropriate type: | Content Type | Schema Type | Rich Result | |-------------|-------------|-------------| | Any blog post | `BlogPosting` | Author, date, publisher info | | FAQ sections | `FAQPage` | Expandable Q&A in search results | | Tutorials | `HowTo` | Step-by-step display in search | | Lists | `ItemList` | Numbered items in search | Always include: `headline`, `description`, `author` (Person with name/url), `datePublished`, `dateModified`, `publisher` (Organization with logo), and `mainEntityOfPage`. ### Internal Linking Strategy Internal links pass authority between pages and help search engines understand your site structure. **Rules:** 1. Every blog post links to 3-5 other blog posts on your site 2. Use descriptive anchor text (not "click here" -- use the target page's keyword) 3. Link from high-authority pages to pages you want to rank higher 4. Create "pillar" pages that link to all related content (topic clusters) **Topic Cluster Model:** ``` [Pillar Page] "AI Agent Orchestration" / | \ [Cluster] [Cluster] [Cluster] "DAG Basics" "Parallel "Skill Execution" Matching" ``` The pillar page covers the broad topic and links to each cluster page. Each cluster page links back to the pillar and to sibling clusters. --- ## Step 5: Content Freshness and Measurement Google rewards freshness, especially for technical content where tools and APIs change. ### Update Schedule | Content Type | Update Frequency | What to Update | |-------------|-----------------|----------------| | Tutorials | Every 6 months | Code examples, API changes, screenshots | | Comparisons | Every 3-4 months | Pricing, new features, market changes | | Deep-dives | Annually | Architecture changes, performance data | | "Best of" lists | Every 3 months | New tools, removed tools, updated rankings | When updating: change `dateModified` in schema, add "Updated [date] with [changes]" at top, refresh code examples, re-share on social. ### Measuring Content ROI Track with Google Search Console (free, essential) and Google Analytics 4: | Metric | Target | |--------|--------| | Organic traffic | Growing month-over-month | | Average position | Top 5 for primary keyword | | Click-through rate | Above 3% for page 1 results | | Time on page | Above 3 minutes for tutorials | | Conversions | Track with UTM params per post | **The compound effect:** SEO content grows over time. A post getting 100 visits/month at launch can reach 1,000/month by month 12 as it earns backlinks and authority. This is the opposite of social media, which spikes and dies. --- ## AI-Era SEO: What Has Changed (2025-2026) ### Google's Stance on AI Content Google does NOT penalize content for being AI-generated. They penalize content that is low-quality, regardless of how it was created. The policy: "Content created primarily for people" ranks. "Content created to manipulate rankings" does not. **What this means in practice:** - AI-assisted content that is edited, fact-checked, and genuinely useful ranks fine - Mass-generated thin content with no human review gets filtered - First-person experience and original data are stronger ranking signals than ever (E-E-A-T: Experience, Expertise, Authoritativeness, Trustworthiness) ### AI Overviews and Zero-Click Search Google AI Overviews now answer many queries directly in search results. This changes the game: - **Structure content to be cited by AI Overviews** (clear answers, authoritative tone) - **Target queries AI Overviews cannot fully answer** (nuanced comparisons, code tutorials, architecture decisions) - **Include original data and benchmarks** that AI models will reference ### Multi-Search Optimization People now search Google, ChatGPT, Perplexity, and Bing simultaneously. To be visible across all: - Use clear, structured content that AI models can parse - Include factual claims that can be verified - Publish on your own domain (not just Medium or Dev.to) - Maintain schema markup so AI crawlers understand your content structure --- ## Anti-Patterns ### 1. Keyword Stuffing **Mistake:** Forcing the target keyword into every paragraph, making the content unreadable. **Fix:** Use the primary keyword in the title, H1, first paragraph, and meta description. Use secondary keywords and natural language everywhere else. ### 2. Writing for Bots, Not Humans **Mistake:** Content that reads like an SEO checklist was applied to a blank page. **Fix:** Write for a smart developer first. Optimize for search second. If the content would not be useful without Google, it should not exist. ### 3. Ignoring Search Intent **Mistake:** Writing a product pitch for an informational query ("what is X" answered with "buy our product that does X"). **Fix:** Match content to intent. Informational queries get educational content. Let the reader decide to try your product after being genuinely helped. ### 4. Publish and Forget **Mistake:** Never updating published content. **Fix:** Schedule quarterly reviews. Update outdated examples, refresh screenshots, add new information. A well-maintained post from 2024 outranks a fresh but thin post from 2026. ### 5. No Internal Links **Mistake:** Every blog post is an island with no links to other content. **Fix:** Every post links to 3-5 related posts. Build topic clusters. Create pillar pages. ### 6. Duplicate Content Across Platforms **Mistake:** Publishing the exact same article on your blog, Dev.to, Medium, and LinkedIn. **Fix:** Publish the canonical version on YOUR domain. Cross-post to Dev.to and Medium with canonical URL tags. Syndicate summaries to LinkedIn and Twitter. ### 7. Chasing Vanity Keywords **Mistake:** Targeting "AI" (billions of results, impossible to rank) instead of "how to orchestrate AI agents with DAGs" (specific, rankable). **Fix:** Target long-tail keywords with clear intent. Better to rank #1 for a 500-searches/month term than #50 for a 50,000-searches/month term. --- ## Quality Checklist - [ ] Primary keyword appears in: title, H1, meta description, first paragraph, URL slug - [ ] Meta description is 150-160 characters with a clear value proposition - [ ] H2 sections each target a secondary keyword or People Also Ask question - [ ] Content answers the search query in the first 2 sentences (featured snippet bait) - [ ] At least one table, list, or code block per major section (structured content) - [ ] 3-5 internal links to related content on your site - [ ] Schema markup added (BlogPosting at minimum, FAQPage and HowTo if applicable) - [ ] Open Graph and Twitter Card meta tags set with a custom image - [ ] All images have descriptive alt text (not keyword-stuffed -- genuinely descriptive) - [ ] URL slug is short, descriptive, and contains the primary keyword - [ ] Content is 1,500+ words for tutorials and comparisons (comprehensive coverage) - [ ] The post would be useful to a developer even if search engines did not exist - [ ] Canonical URL is set (especially important for cross-posted content) - [ ] `datePublished` and `dateModified` are accurate in schema markup - [ ] A content refresh date is scheduled (3-6 months from publication)