@@ −19 +21 @@
- Implementing on-page SEO for a specific page — use **seo-geo**
- Technical SEO issues are blocking indexing — fix those first with **technical-seo-audit**
- Content is purely for AI search — use **ai-citability** for GEO-specific optimization
+
+## Signals & changes (short)
+
+- Google launched “Web Guide” (Search Labs experiment) that groups links by topic using a Gemini model; it can change how users discover content on the Web tab and may expand to other tabs (Google Blog, Jul 24, 2025). Optimize for clear structure, summaries, and strong citations.
+- Google’s guidance: AI-generated content is not automatically disallowed — Google rewards helpful, high-quality content regardless of production method (Google Search Central, Feb 2023). Focus on usefulness, accuracy, and human oversight.
+- Search Console had a logging error that over-reported impressions from May 13, 2025; fixes rolled out in early Apr 2026 — expect impression drops in Performance reports (Search Engine Land summary of Google notice, Apr 3, 2026). Monitor clicks and other metrics; clicks were unaffected by the bug.
+- Practitioners (Ahrefs, Mar 2026) recommend treating AI features as a new surface: structure content for retrieval (clear headings, summaries, FAQs) and preserve authoritative signals (citations, authorship, E-E-A-T).
## Core concepts
@@ −32 +41 @@
| Content lifecycle | Creation → publish → optimize → refresh → prune/consolidate |
| Topical authority | Google's assessment of your site's expertise on a topic, built through cluster coverage |
| Content decay | Gradual decline in organic traffic for aging content |
+| AI-organized SERPs | New result surfaces (Web Guide, AI Overviews) that rely on retrieval, summarization, and citation. Optimize structure and extractable summaries to increase visibility in these surfaces. |
## Workflow
### Step 1: Define topic clusters from keyword research
−Use keyword clusters from the **keyword-research** skill as the foundation:
+Use keyword clusters from the **keyword-research** skill as the foundation. Map intent and prioritize pages that serve distinct user problems (informational, transactional, navigational).
−
−```text
−Topic Cluster: API Security
−├── Pillar: "Complete Guide to API Security" (primary: "api security", vol: 8,200)
−├── Cluster: "API Authentication Methods" (primary: "api authentication", vol: 3,400)
−├── Cluster: "OAuth 2.0 Implementation" (primary: "oauth 2.0 tutorial", vol: 2,800)
−├── Cluster: "API Rate Limiting" (primary: "api rate limiting", vol: 4,800)
−├── Cluster: "JWT Security Best Practices" (primary: "jwt security", vol: 2,100)
−└── Cluster: "API Key Management" (primary: "api key management", vol: 1,600)
−```
### Step 2: Create the pillar page structure
A pillar page should:
+- Cover the broad topic comprehensively (2,500–5,000 words for competitive topics) and include a clear table-of-contents and short summaries of cluster pages
+- Link to each cluster page with descriptive anchor text and contextual placement
+- Include short, extractable summary paragraphs (40–120 words) at the start of each subtopic so AI retrieval systems can easily summarize and cite your content (practical adaptation for Web Guide / AI Overviews)
−- Cover the broad topic comprehensively (2,500-5,000 words)
+- Target the highest-volume keyword in the cluster and document secondary keywords in the brief
−- Include an overview of every subtopic (cluster page)
−- Link to each cluster page with descriptive anchor text
−- Serve as a table-of-contents style entry point for the topic
−- Target the highest-volume keyword in the cluster
−```markdown
+### Step 3: Build a content brief template
−# Complete Guide to API Security
−## Introduction
+Add fields that reflect the new search landscape:
−[Overview of why API security matters — 200-300 words]
+- Primary and secondary keywords + intent
+- Target length
+- Required sections and specific extractable summary for each section (recommended 2–3 sentence summary)
+- Structured data required (Article, FAQ, HowTo where relevant)
+- Citations & authoritative sources required (list of URLs to cite)
+- E-E-A-T notes (author bio, date, data sources)
−## Authentication Methods
+- Monitoring tags (GSC property, Analytics view, experiment tag)
−[Summary of authentication approaches — 300-400 words]
−→ Read more: [API Authentication Methods Deep Dive](/blog/api-authentication)
−## OAuth 2.0
+Example brief additions (extractable summary + citations):
−[OAuth overview with key concepts — 300-400 words]
−→ Read more: [OAuth 2.0 Implementation Guide](/blog/oauth-tutorial)
+- **Extractable summary**: "Rate limiting prevents API abuse by limiting requests per key or IP..." (40–80 words)
−## Rate Limiting
+- **Required citation**: Link to RFC or authoritative docs for any protocol or standard
−[Rate limiting overview — 300-400 words]
−→ Read more: [API Rate Limiting Best Practices](/blog/api-rate-limiting)
−[Continue for each cluster page...]
+### Step 4: Implement internal linking (updated)
−```
−### Step 3: Build a content brief template
+Rules and additions for 2026:
+| Link type | Rule |
+|-----------|------|
+| Pillar → Cluster | Every pillar links to its cluster pages using descriptive anchor text and short intro text (helps AI-organized SERPs find context) |
+| Cluster → Pillar | Every cluster page links back to its pillar with a clear contextual sentence near the top |
+| Cluster → Cluster | Cross-link related clusters where it improves user flow and topical depth |
+| Anchor text | Use descriptive anchors. When linking for AI retrieval, include a short phrase around the link that explains the link target (not only the anchor) |
+| Link placement | Prefer in-body contextual links over footer menus; top-of-content links increase discoverability for snippet-generation |
