agileflow 3.3.0 → 3.4.1

package/src/core/commands/seo/references/eeat-framework.md

@@ -0,0 +1,110 @@
+# E-E-A-T Scoring Framework
+
+Reference data for content quality analysis. Updated February 2026.
+
+---
+
+## Scoring Weights (100-point scale)
+
+| Factor | Weight | Description |
+|--------|--------|-------------|
+| **Trustworthiness** | 30% | Transparency, contact info, HTTPS, no deception |
+| **Expertise** | 25% | Credentials, accuracy, technical depth |
+| **Authoritativeness** | 25% | Citations, media features, industry standing |
+| **Experience** | 20% | First-hand knowledge, original content, case studies |
+
+---
+
+## Signal Detection
+
+### Trustworthiness (30%)
+
+| Signal | Present | Absent |
+|--------|---------|--------|
+| HTTPS | +5 | -10 |
+| Contact page / About page | +5 | -5 |
+| Privacy policy | +3 | -3 |
+| Terms of service | +2 | -2 |
+| Physical address | +3 | 0 |
+| Clear editorial policy | +4 | 0 |
+| No deceptive patterns (dark UX) | +5 | -10 |
+| Transparent affiliate disclosure | +3 | -5 |
+
+### Expertise (25%)
+
+| Signal | Present | Absent |
+|--------|---------|--------|
+| Author bylines with credentials | +5 | -3 |
+| Cited sources / references | +5 | -3 |
+| Technical accuracy (no factual errors) | +5 | -5 |
+| Industry-specific terminology (appropriate use) | +3 | 0 |
+| Depth of coverage (not surface-level) | +4 | -2 |
+| Peer review / editorial review mentioned | +3 | 0 |
+
+### Authoritativeness (25%)
+
+| Signal | Present | Absent |
+|--------|---------|--------|
+| Backlinks from authoritative domains | +5 | 0 |
+| Mentioned in media / press | +4 | 0 |
+| Industry awards / certifications | +3 | 0 |
+| Wikipedia reference | +4 | 0 |
+| Featured on Reddit / YouTube / forums | +3 | 0 |
+| Brand search volume indicators | +3 | 0 |
+| Consistent NAP (Name, Address, Phone) | +3 | -2 |
+
+### Experience (20%)
+
+| Signal | Present | Absent |
+|--------|---------|--------|
+| First-person accounts / case studies | +5 | -2 |
+| Original photography / screenshots | +4 | -1 |
+| Specific data / metrics from real usage | +4 | -2 |
+| User reviews / testimonials (authentic) | +3 | 0 |
+| Step-by-step from personal experience | +4 | -1 |
+
+---
+
+## Content Quality Minimums by Type
+
+| Page Type | Min Words | Unique Content % | Internal Links |
+|-----------|-----------|------------------|----------------|
+| Homepage | 500 | 100% | 5-10 |
+| Service pages | 800 | 60% | 3-8 |
+| Blog posts | 1,500 | 100% | 2-5 |
+| Product pages | 300-400 | 40% | 3-6 |
+| Location pages | 500-600 | 40% | 3-5 |
+| About page | 400 | 100% | 2-4 |
+| FAQ page | 600 | 80% | 2-5 |
+
+---
+
+## AI Content Rules
+
+- AI content is acceptable IF it demonstrates genuine E-E-A-T
+- Red flags for AI-generated content:
+  - Generic phrasing without specifics
+  - No original insights or data
+  - Fabricated first-person experiences
+  - Lack of cited sources
+  - Cookie-cutter structure across pages
+
+---
+
+## Critical 2025-2026 Updates
+
+| Date | Update | Impact |
+|------|--------|--------|
+| Dec 2025 | E-E-A-T applies to ALL queries (not just YMYL) | Affiliate traffic -71%, health -67% |
+| Feb 2026 | Experience signals weighted more heavily | Differentiator vs AI-generated content |
+
+---
+
+## Score Interpretation
+
+| Score | Rating | Action |
+|-------|--------|--------|
+| 80-100 | Strong E-E-A-T | Maintain, optimize further |
+| 60-79 | Adequate | Improve weakest factor |
+| 40-59 | Weak | Significant improvements needed |
+| 0-39 | Critical | Major content overhaul required |

package/src/core/commands/seo/references/quality-gates.md

@@ -0,0 +1,91 @@
+# SEO Quality Gates
+
+Reference data for programmatic SEO and content quality thresholds. Updated February 2026.
+
+---
+
+## On-Page Elements
+
+### Title Tag
+- **Length**: 30-60 characters
+- **Requirements**: Unique per page, keyword-forward, no truncation
+- **Flags**: Missing, duplicate, too short (<30), too long (>60), keyword-stuffed
+
+### Meta Description
+- **Length**: 120-160 characters
+- **Requirements**: Unique per page, natural keywords, includes CTA
+- **Flags**: Missing, duplicate, too short (<120), too long (>160)
+
+### Headings
+- **H1**: Exactly 1 per page, contains primary keyword
+- **H2-H6**: Logical hierarchy (no skipping levels), keyword-relevant
+- **Flags**: Missing H1, multiple H1s, skipped heading levels
+
+### Alt Text
+- **Length**: 10-125 characters
+- **Requirements**: Descriptive, not filename-based, contextually relevant
+- **Flags**: Missing, filename-based (IMG_001.jpg), too long, keyword-stuffed
+
+### Internal Links
+- **Target**: 2-10 per page (varies by content type)
+- **Requirements**: Descriptive anchor text, no broken links, logical structure
+- **Flags**: Orphan pages (0 internal links in), excessive links (>100)
+
+---
+
+## Programmatic SEO Thresholds
+
+| Metric | Warning | Hard Stop |
+|--------|---------|-----------|
+| Pages without audit | 100+ | 500+ |
+| Unique content per page | < 40% | < 20% |
+| Location pages created | 30+ | 50+ |
+| Thin pages (< 300 words) | 10+ | 50+ |
+| Duplicate title tags | 5+ | 20+ |
+| Duplicate meta descriptions | 10+ | 30+ |
+| Pages with no internal links in | 5+ | 20+ |
+| 404 errors | 5+ | 20+ |
+| Redirect chains (3+ hops) | 3+ | 10+ |
+
+---
+
+## Content Uniqueness Requirements
+
+| Page Type | Min Unique % | Template Allowed % |
+|-----------|-------------|-------------------|
+| Core pages (home, about, services) | 100% | 0% |
+| Blog posts / articles | 100% | 0% |
+| Product pages | 40% | 60% |
+| Location pages | 40% | 60% |
+| Category pages | 30% | 70% |
+
+---
+
+## URL Quality Standards
+
+- **Format**: Lowercase, hyphens (not underscores), no special characters
+- **Length**: Under 75 characters preferred, max 2048
+- **Depth**: Max 3-4 levels from root (e.g., /category/subcategory/page)
+- **Flags**: Uppercase, underscores, parameters without canonical, double slashes
+
+---
+
+## Crawl Budget Indicators
+
+| Metric | Healthy | Warning | Critical |
+|--------|---------|---------|----------|
+| Crawl rate (pages/day) | Stable/growing | Declining >10% | Declining >30% |
+| Index coverage errors | < 1% | 1-5% | > 5% |
+| Soft 404s | 0 | 1-10 | > 10 |
+| Blocked resources (CSS/JS) | 0 | 1-5 | > 5 |
+
+---
+
+## Priority Framework
+
+| Priority | Criteria | Examples |
+|----------|----------|----------|
+| **Critical** | Blocks indexing or causes penalties | noindex on key pages, robots.txt blocking, manual action |
+| **High** | Direct ranking impact | Missing title tags, slow LCP, broken canonical chains |
+| **Medium** | Optimization opportunity | Thin content, missing schema, suboptimal alt text |
+| **Low** | Nice-to-have improvement | Trailing slashes inconsistency, suboptimal URL structure |

package/src/core/commands/seo/references/schema-types.md

@@ -0,0 +1,102 @@
+# Schema Markup Types Reference
+
+Reference data for JSON-LD structured data validation. Updated February 2026.
+
+---
+
+## Actively Recommended Types
+
+These schema types are actively supported by Google and can generate rich results:
+
+| Type | Use Case | Required Properties |
+|------|----------|-------------------|
+| **Organization** | Business identity | name, url, logo |
+| **LocalBusiness** | Physical businesses | name, address, telephone, openingHours |
+| **Product** | E-commerce products | name, image, offers (price, availability, priceCurrency) |
+| **Article** | News/blog content | headline, image, datePublished, author |
+| **BlogPosting** | Blog content | headline, image, datePublished, author |
+| **Review** | Product/service reviews | itemReviewed, reviewRating, author |
+| **Event** | Events | name, startDate, location |
+| **JobPosting** | Job listings | title, description, datePosted, hiringOrganization |
+| **Course** | Educational content | name, description, provider |
+| **VideoObject** | Videos | name, description, thumbnailUrl, uploadDate |
+| **BroadcastEvent** | Live streams | isLiveBroadcast, startDate |
+| **ProfilePage** | Author profiles | mainEntity (Person) |
+| **ProductGroup** | Product variants | name, productGroupID, hasVariant |
+| **WebSite** | Site-level (sitelinks search) | name, url, potentialAction (SearchAction) |
+| **BreadcrumbList** | Navigation | itemListElement |
+| **FAQPage** | FAQs (restricted - see below) | mainEntity (Question + acceptedAnswer) |
+
+---
+
+## Restricted Types (Limited Use)
+
+| Type | Restriction | Details |
+|------|-------------|---------|
+| **FAQPage** | Government/healthcare only | Since August 2023, Google restricted FAQ rich results to government and health authority websites. Commercial sites should NOT use FAQPage schema. |
+
+---
+
+## Deprecated Types (Never Use)
+
+These types no longer generate rich results or have been explicitly deprecated:
+
+| Type | Deprecated Since | Replacement |
+|------|-----------------|-------------|
+| **HowTo** | Aug 2023 | None (removed from search features) |
+| **SpecialAnnouncement** | 2024 | None (COVID-era, sunset) |
+| **CourseInfo** | 2024 | Use Course instead |
+| **EstimatedSalary** | 2024 | Use JobPosting.estimatedSalary |
+| **LearningVideo** | 2024 | Use VideoObject |
+| **ClaimReview** | 2024 | Limited to approved fact-checkers |
+| **VehicleListing** | 2024 | Merchant API only |
+| **PracticeProblem** | 2024 | None |
+| **Dataset** | 2024 | Dataset Search only (not main SERP) |
+
+---
+
+## Critical Validation Rules
+
+| Rule | Details |
+|------|---------|
+| **@context** | Must use `https://schema.org` (HTTPS, not HTTP) |
+| **returnPolicyCountry** | Mandatory for Product schema (since March 2025) |
+| **ISO 8601 dates** | All date fields must use ISO 8601 format |
+| **Required properties** | All required properties must be present |
+| **Valid URLs** | All URL fields must be valid, accessible URLs |
+| **No empty values** | Properties must have meaningful values |
+| **Merchant API** | Product structured data must migrate to Merchant API by August 18, 2026 |
+
+---
+
+## Implementation Format
+
+- **Preferred**: JSON-LD in `<script type="application/ld+json">` (head or body)
+- **Acceptable**: Microdata, RDFa
+- **Recommendation**: Always use JSON-LD; it's easiest to maintain and Google's preferred format
+
+---
+
+## Common Validation Errors
+
+| Error | Severity | Fix |
+|-------|----------|-----|
+| Missing @context | Critical | Add `"@context": "https://schema.org"` |
+| HTTP in @context | High | Change to HTTPS |
+| Missing required property | High | Add the required property with valid value |
+| Deprecated type | Medium | Remove or replace per table above |
+| Invalid date format | Medium | Convert to ISO 8601 |
+| Missing returnPolicyCountry | High | Add to Product/Offer schema |
+| Nested errors in offers | Medium | Validate Offer sub-schema |
+
+---
+
+## Business Type to Schema Mapping
+
+| Business Type | Primary Schema Types |
+|--------------|---------------------|
+| **SaaS** | Organization, WebSite, Product, Article, FAQPage (if applicable) |
+| **Local Business** | LocalBusiness, Organization, Product/Service, Review, Event |
+| **E-commerce** | Product, ProductGroup, Organization, BreadcrumbList, Review |
+| **Publisher** | Article, BlogPosting, Organization, WebSite, ProfilePage |
+| **Agency** | Organization, LocalBusiness, Service, Review, Article |

package/src/core/commands/seo/schema.md

@@ -0,0 +1,183 @@
+---
+description: Schema markup validation, deprecated type detection, and ready-to-use JSON-LD generation for rich results
+argument-hint: "URL [GENERATE=true]"
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:seo:schema - Schema markup analysis"
+    - "Detect existing JSON-LD, Microdata, RDFa on the page"
+    - "Validate against current Google standards (2025-2026)"
+    - "Flag deprecated types (HowTo, SpecialAnnouncement, etc.)"
+    - "If GENERATE=true, produce ready-to-use JSON-LD snippets"
+  state_fields:
+    - target_url
+    - generate
+    - schema_found
+---
+
+# /agileflow:seo:schema
+
+Detect, validate, and generate schema markup (structured data) for rich results in Google Search.
+
+---
+
+## Quick Reference
+
+```
+/agileflow:seo:schema https://example.com                    # Detect and validate existing schema
+/agileflow:seo:schema https://example.com GENERATE=true       # Also generate missing JSON-LD
+/agileflow:seo:schema https://example.com/product             # Analyze product page schema
+```
+
+---
+
+## Arguments
+
+| Argument | Values | Default | Description |
+|----------|--------|---------|-------------|
+| URL | Any valid URL | Required | Page to analyze |
+| GENERATE | true, false | false | Generate ready-to-use JSON-LD for missing schema |
+
+---
+
+## Process
+
+### STEP 1: Fetch and Detect
+
+Use WebFetch to retrieve the page. Extract all structured data:
+- `<script type="application/ld+json">` blocks (JSON-LD)
+- Elements with `itemscope`/`itemtype`/`itemprop` (Microdata)
+- Elements with `typeof`/`property` (RDFa)
+
+### STEP 2: Validate Existing Schema
+
+For each schema block found, check:
+
+**Format**:
+- Valid JSON syntax (for JSON-LD)
+- `@context` uses `https://schema.org` (HTTPS, not HTTP)
+- `@type` is a recognized type
+
+**Required Properties** (per type - see schema-types.md reference):
+- Organization: name, url, logo
+- Product: name, image, offers (price, priceCurrency, availability)
+- Article: headline, image, datePublished, author
+- LocalBusiness: name, address, telephone
+- etc.
+
+**Current Rules**:
+- `returnPolicyCountry` mandatory for Products (March 2025)
+- ISO 8601 dates required
+- Merchant API migration by August 18, 2026
+
+### STEP 3: Flag Deprecated/Restricted Types
+
+**Deprecated (remove immediately)**:
+- HowTo, SpecialAnnouncement, CourseInfo, EstimatedSalary
+- LearningVideo, ClaimReview, VehicleListing, PracticeProblem, Dataset
+
+**Restricted (use only if eligible)**:
+- FAQPage: Only government/healthcare sites since August 2023
+
+### STEP 4: Identify Missing Opportunities
+
+Based on page content, recommend schema that should be present:
+
+| Page Contains | Recommended Schema |
+|--------------|-------------------|
+| Business info | Organization or LocalBusiness |
+| Products | Product with Offer |
+| Blog articles | Article or BlogPosting |
+| Events | Event |
+| Job listings | JobPosting |
+| Videos | VideoObject |
+| Breadcrumbs | BreadcrumbList |
+| Site search | WebSite with SearchAction |
+| Reviews | Review with Rating |
+
+### STEP 5: Generate JSON-LD (if GENERATE=true)
+
+For each missing schema, generate a ready-to-use JSON-LD snippet with placeholder values filled from the actual page content:
+
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Organization",
+  "name": "[extracted from page]",
+  "url": "[page URL]",
+  "logo": "[detected logo URL]",
+  "sameAs": [
+    "[detected social links]"
+  ]
+}
+```
+
+### STEP 6: Output Report
+
+```markdown
+# Schema Analysis: {URL}
+
+## Existing Schema
+
+| # | Type | Format | Valid | Issues |
+|---|------|--------|-------|--------|
+| 1 | Organization | JSON-LD | Yes | None |
+| 2 | FAQPage | JSON-LD | No | Restricted type (commercial site) |
+
+## Validation Results
+
+### Schema 1: Organization (Valid)
+```json
+{existing schema}
+```
+All required properties present.
+
+### Schema 2: FAQPage (Invalid)
+- Issue: FAQPage restricted to government/healthcare since Aug 2023
+- Action: Remove FAQPage schema from commercial pages
+
+## Missing Schema Opportunities
+
+| Type | Why | Rich Result |
+|------|-----|-------------|
+| BreadcrumbList | Page has breadcrumb nav | Breadcrumb trail in SERP |
+| WebSite | Homepage, has search | Sitelinks search box |
+
+## Generated JSON-LD (if requested)
+
+[Ready-to-use code blocks]
+
+## Schema Score: X/100
+```
+
+### STEP 7: Offer Next Steps
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Schema analysis: {found} types detected, {valid} valid, {issues} issues, {missing} opportunities.",
+  "header": "Next steps",
+  "multiSelect": false,
+  "options": [
+    {"label": "Generate missing JSON-LD (Recommended)", "description": "Create ready-to-use schema for {missing} opportunities"},
+    {"label": "Fix {issues} validation errors", "description": "{top_error_summary}"},
+    {"label": "Test in Rich Results Test", "description": "Validate generated schema at search.google.com/test/rich-results"},
+    {"label": "Run full SEO audit", "description": "/agileflow:seo:audit {domain}"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+---
+
+<!-- COMPACT_SUMMARY_START -->
+## Compact Summary
+
+**Command**: `/agileflow:seo:schema` - Schema markup validation and generation
+
+**Usage**: `/agileflow:seo:schema URL [GENERATE=true]`
+
+**What It Does**: Detect existing schema → Validate against Google standards → Flag deprecated types → Identify missing opportunities → Generate JSON-LD
+
+**Key References**: schema-types.md (recommended, restricted, deprecated types)
+<!-- COMPACT_SUMMARY_END -->

package/src/core/commands/seo/sitemap.md

@@ -0,0 +1,97 @@
+---
+description: XML sitemap validation, URL coverage analysis, quality gate enforcement, and sitemap generation assistance
+argument-hint: "URL [GENERATE=true]"
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:seo:sitemap - Sitemap validation"
+    - "Deploy seo-analyzer-sitemap for comprehensive sitemap audit"
+    - "Check existence, structure, coverage, quality gates"
+    - "If GENERATE=true, help create or fix the sitemap"
+  state_fields:
+    - target_url
+    - generate
+    - sitemap_found
+---
+
+# /agileflow:seo:sitemap
+
+Validate XML sitemap structure, assess URL coverage, enforce quality gates, and optionally generate or fix sitemaps.
+
+---
+
+## Quick Reference
+
+```
+/agileflow:seo:sitemap https://example.com                   # Validate existing sitemap
+/agileflow:seo:sitemap https://example.com GENERATE=true      # Also generate improvements
+```
+
+---
+
+## Arguments
+
+| Argument | Values | Default | Description |
+|----------|--------|---------|-------------|
+| URL | Any valid URL (domain) | Required | Site to analyze |
+| GENERATE | true, false | false | Generate or fix sitemap XML |
+
+---
+
+## Process
+
+### STEP 1: Deploy Sitemap Analyzer
+
+```xml
+<invoke name="Task">
+<parameter name="description">Sitemap validation analysis</parameter>
+<parameter name="prompt">TASK: Validate XML sitemap comprehensively.
+
+TARGET URL: {url}
+
+Check:
+1. Locate sitemap: robots.txt Sitemap: directive, /sitemap.xml, /sitemap_index.xml
+2. Structure: Valid XML, correct namespace, proper elements
+3. URL quality: Status codes, canonical match, not noindexed, HTTPS
+4. Coverage: Important pages included, no orphans
+5. Quality: lastmod dates present and valid, under 50k URLs / 50MB
+6. robots.txt: Sitemap declared in robots.txt
+
+Quality gates:
+- Non-200 URLs: Warning >5%, Critical >15%
+- Missing lastmod: Warning >20%, Critical >50%
+- Stale lastmod (>1 year): Warning >30%, Critical >60%
+- Duplicate URLs: Any = Warning
+
+OUTPUT: Sitemap Score X/100 with detailed findings.</parameter>
+<parameter name="subagent_type">seo-analyzer-sitemap</parameter>
+</invoke>
+```
+
+### STEP 2: Present Results and Optionally Generate
+
+If GENERATE=true and issues found, help create a corrected sitemap or generate one from scratch based on discovered pages.
+
+---
+
+## Quality Gates
+
+| Metric | Warning | Critical |
+|--------|---------|----------|
+| Non-200 URLs | > 5% | > 15% |
+| Missing lastmod | > 20% | > 50% |
+| Stale lastmod | > 30% | > 60% |
+| Not in robots.txt | Always | - |
+| No sitemap at all | - | Always |
+
+---
+
+<!-- COMPACT_SUMMARY_START -->
+## Compact Summary
+
+**Command**: `/agileflow:seo:sitemap` - XML sitemap validation
+
+**Checks**: Existence, XML structure, URL coverage, lastmod quality, robots.txt reference
+
+**Usage**: `/agileflow:seo:sitemap URL [GENERATE=true]`
+<!-- COMPACT_SUMMARY_END -->

package/src/core/commands/seo/technical.md

@@ -0,0 +1,100 @@
+---
+description: Deep technical SEO analysis - crawlability, indexability, security headers, URL structure, mobile-friendliness, and rendering
+argument-hint: "URL [FOCUS=crawl|index|security|urls|mobile|rendering|all]"
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:seo:technical - Technical SEO deep-dive"
+    - "Deploy seo-analyzer-technical agent for comprehensive assessment"
+    - "8 categories: crawl, index, security, urls, mobile, rendering, international, performance"
+  state_fields:
+    - target_url
+    - focus
+    - tech_score
+---
+
+# /agileflow:seo:technical
+
+Deep technical SEO analysis covering crawlability, indexability, security headers, URL structure, mobile-friendliness, JavaScript rendering, and international signals.
+
+---
+
+## Quick Reference
+
+```
+/agileflow:seo:technical https://example.com                 # Full 8-category assessment
+/agileflow:seo:technical https://example.com FOCUS=crawl      # Crawlability only
+/agileflow:seo:technical https://example.com FOCUS=security   # Security headers only
+/agileflow:seo:technical https://example.com FOCUS=mobile     # Mobile-friendliness only
+```
+
+---
+
+## Arguments
+
+| Argument | Values | Default | Description |
+|----------|--------|---------|-------------|
+| URL | Any valid URL | Required | Site to analyze |
+| FOCUS | crawl, index, security, urls, mobile, rendering, international, all | all | Narrow to specific area |
+
+---
+
+## Process
+
+### STEP 1: Deploy Technical Analyzer
+
+```xml
+<invoke name="Task">
+<parameter name="description">Technical SEO deep-dive</parameter>
+<parameter name="prompt">TASK: Perform a deep technical SEO analysis.
+
+TARGET URL: {url}
+FOCUS: {focus or "all 8 categories"}
+
+Analyze all 8 categories in depth:
+1. Crawlability: robots.txt, meta robots, canonicals, redirect chains, crawl budget
+2. Indexability: noindex directives, orphan pages, sitemap coverage, crawl depth
+3. Security: HTTPS, HSTS, X-Content-Type-Options, CSP, X-Frame-Options, Referrer-Policy
+4. URL Structure: Cleanliness, hierarchy, parameters, consistency, depth
+5. Mobile: Viewport, responsive design, tap targets, font sizes, no horizontal scroll
+6. JavaScript Rendering: Client-side content, JS-dependent elements, hydration
+7. International: hreflang, language tags, geo-targeting, content localization
+8. Performance Indicators: TTFB, render-blocking, resource hints, compression
+
+For each category, provide specific findings with evidence and a category score out of 100.
+
+OUTPUT: Technical SEO Score X/100 with category breakdown.</parameter>
+<parameter name="subagent_type">seo-analyzer-technical</parameter>
+</invoke>
+```
+
+### STEP 2: Present Results
+
+Show the technical assessment with category scores and offer targeted fixes.
+
+---
+
+## 8 Categories
+
+| Category | Weight | Key Checks |
+|----------|--------|-----------|
+| Crawlability | 25% | robots.txt, canonicals, redirects |
+| Indexability | 20% | noindex, orphans, sitemap coverage |
+| Security | 15% | HTTPS, HSTS, CSP, security headers |
+| URL Structure | 15% | Clean URLs, hierarchy, consistency |
+| Mobile | 15% | Viewport, responsive, tap targets |
+| JS Rendering | 5% | Client-side content visibility |
+| International | 3% | hreflang, language declarations |
+| Performance | 2% | TTFB, resource hints, compression |
+
+---
+
+<!-- COMPACT_SUMMARY_START -->
+## Compact Summary
+
+**Command**: `/agileflow:seo:technical` - Deep technical SEO analysis
+
+**8 Categories**: Crawlability, Indexability, Security, URLs, Mobile, JS Rendering, International, Performance
+
+**Usage**: `/agileflow:seo:technical URL [FOCUS=category]`
+<!-- COMPACT_SUMMARY_END -->