antigravity-seo-kit 2.0.0

package/.agent/skills/seo-audit/SKILL.md

@@ -0,0 +1,278 @@
+---
+name: seo-audit
+description: >
+  Full website SEO audit with parallel skill delegation. Crawls up to 500
+  pages, detects business type, activates 10 specialist skills (7 core + 3
+  conditional), generates health score. Use when user says "audit",
+  "full SEO check", "analyze my site", or "website health check".
+---
+
+# Full Website SEO Audit
+
+## Process
+
+1. **Fetch homepage**: use `scripts/fetch_page.py` to retrieve HTML
+2. **Detect business type**: analyze homepage signals per seo orchestrator
+3. **Crawl site**: follow internal links up to 500 pages, respect robots.txt
+4. **Activate specialist skills** (run analysis for each area):
+   - `seo-technical` -- robots.txt, sitemaps, canonicals, Core Web Vitals, security headers
+   - `seo-content` -- E-E-A-T, readability, thin content, AI citation readiness
+   - `seo-schema` -- detection, validation, generation recommendations
+   - `seo-sitemap` -- structure analysis, quality gates, missing pages
+   - `seo-performance` -- LCP, INP, CLS measurements
+   - `seo-visual` -- screenshots, mobile testing, above-fold analysis
+   - `seo-geo` -- AI crawler access, llms.txt, citability, brand mention signals
+   - `seo-local` -- GBP signals, NAP consistency, reviews, local schema, industry-specific local factors (activate when Local Service industry detected: brick-and-mortar, SAB, or hybrid business type)
+   - `seo-maps` -- Geo-grid rank tracking, GBP audit, review intelligence, competitor radius mapping (activate when Local Service detected AND DataForSEO MCP available)
+   - `seo-google` -- CWV field data (CrUX), URL indexation (GSC), organic traffic (GA4) (activate when Google API credentials detected via `python .agent/skills/seo-google/scripts/google_auth.py --check`)
+5. **Score** -- aggregate into SEO Health Score (0-100)
+6. **Report** -- generate prioritized action plan
+7. **Offer PDF report**: "Generate a professional PDF report? Use `/seo-google report full`"
+
+## Crawl Configuration
+
+```
+Max pages: 500
+Respect robots.txt: Yes
+Follow redirects: Yes (max 3 hops)
+Timeout per page: 30 seconds
+Concurrent requests: 5
+Delay between requests: 1 second
+```
+
+## Output Files
+
+- `FULL-AUDIT-REPORT.md`: Comprehensive findings
+- `ACTION-PLAN.md`: Prioritized recommendations (Critical > High > Medium > Low)
+- `screenshots/`: Desktop + mobile captures (if Playwright available)
+
+## Scoring Weights
+
+| Category | Weight |
+|----------|--------|
+| Technical SEO | 22% |
+| Content Quality | 23% |
+| On-Page SEO | 20% |
+| Schema / Structured Data | 10% |
+| Performance (CWV) | 10% |
+| AI Search Readiness | 10% |
+| Images | 5% |
+
+## Report Structure
+
+### Executive Summary
+- Overall SEO Health Score (0-100)
+- Business type detected
+- Top 5 critical issues
+- Top 5 quick wins
+
+### Technical SEO
+- Crawlability issues
+- Indexability problems
+- Security concerns
+- Core Web Vitals status
+
+### Content Quality
+- E-E-A-T assessment
+- Thin content pages
+- Duplicate content issues
+- Readability scores
+
+### On-Page SEO
+- Title tag issues
+- Meta description problems
+- Heading structure
+- Internal linking gaps
+
+### Schema & Structured Data
+- Current implementation
+- Validation errors
+- Missing opportunities
+
+### Performance
+- LCP, INP, CLS scores
+- Resource optimization needs
+- Third-party script impact
+
+### Images
+- Missing alt text
+- Oversized images
+- Format recommendations
+
+### AI Search Readiness
+- Citability score
+- Structural improvements
+- Authority signals
+
+## Priority Definitions
+
+- **Critical**: Blocks indexing or causes penalties (fix immediately)
+- **High**: Significantly impacts rankings (fix within 1 week)
+- **Medium**: Optimization opportunity (fix within 1 month)
+- **Low**: Nice to have (backlog)
+
+## DataForSEO Integration (Optional)
+
+If DataForSEO MCP tools are available, activate the `seo-dataforseo` skill to enrich the audit with live data: real SERP positions, backlink profiles with spam scores, on-page analysis (Lighthouse), business listings, and AI visibility checks (ChatGPT scraper, LLM mentions).
+
+## Error Handling
+
+| Scenario | Action |
+|----------|--------|
+| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess site content. Suggest the user verify the URL and try again. |
+| robots.txt blocks crawling | Report which paths are blocked. Analyze only accessible pages and note the limitation in the report. |
+| Rate limiting (429 responses) | Back off and reduce concurrent requests. Report partial results with a note on which sections could not be completed. |
+| Timeout on large sites (500+ pages) | Cap the crawl at the timeout limit. Report findings for pages crawled and estimate total site scope. |
+
+## Performance Analysis Role
+
+When assessing performance during audits:
+
+You are a Web Performance specialist focused on Core Web Vitals.
+
+## Current Metrics (as of 2026)
+
+| Metric | Good | Needs Improvement | Poor |
+|--------|------|-------------------|------|
+| LCP (Largest Contentful Paint) | ≤2.5s | 2.5s–4.0s | >4.0s |
+| INP (Interaction to Next Paint) | ≤200ms | 200ms–500ms | >500ms |
+| CLS (Cumulative Layout Shift) | ≤0.1 | 0.1–0.25 | >0.25 |
+
+**IMPORTANT**: INP replaced FID on March 12, 2024. FID was fully removed from all Chrome tools (CrUX API, PageSpeed Insights, Lighthouse) on September 9, 2024. INP is the sole interactivity metric. Never reference FID.
+
+## Evaluation Method
+
+Google evaluates the **75th percentile** of page visits, 75% of visits must meet the "good" threshold to pass.
+
+## When Analyzing Performance
+
+1. Use PageSpeed Insights API if available
+2. Otherwise, analyze HTML source for common issues
+3. Provide specific, actionable optimization recommendations
+4. Prioritize by expected impact
+
+## Common LCP Issues
+
+- Unoptimized hero images (compress, WebP/AVIF, preload)
+- Render-blocking CSS/JS (defer, async, critical CSS)
+- Slow server response TTFB >200ms (edge CDN, caching)
+- Third-party scripts blocking render
+- Web font loading delay
+
+## Common INP Issues
+
+- Long JavaScript tasks on main thread (break into <50ms chunks)
+- Heavy event handlers (debounce, requestAnimationFrame)
+- Excessive DOM size (>1,500 elements)
+- Third-party scripts hijacking main thread
+- Synchronous operations blocking
+
+## Common CLS Issues
+
+- Images without width/height dimensions
+- Dynamically injected content
+- Web fonts causing FOIT/FOUT
+- Ads/embeds without reserved space
+- Late-loading elements
+
+## Performance Tooling (2025-2026)
+
+**Lighthouse 13.0** (October 2025): Major audit restructuring with reorganized performance categories and updated scoring weights. Use as a lab diagnostic tool: always validate against CrUX field data for real-world performance.
+
+**CrUX Vis** replaced the CrUX Dashboard (November 2025). The old Looker Studio dashboard was deprecated. Use [CrUX Vis](https://cruxvis.withgoogle.com) or the CrUX API directly.
+
+**LCP subparts** (TTFB, resource load delay, resource load time, element render delay) are now available in CrUX data (February 2025). See `seo/references/cwv-thresholds.md` for details.
+
+## Tools
+
+```bash
+# PageSpeed Insights API
+curl "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=URL&key=API_KEY"
+
+# Lighthouse CLI
+npx lighthouse URL --output json
+```
+
+## Output Format
+
+Provide:
+- Performance score (0-100)
+- Core Web Vitals status (pass/fail per metric)
+- Specific bottlenecks identified
+- Prioritized recommendations with expected impact
+
+## Visual Analysis Role
+
+When performing visual analysis during audits:
+
+You are a Visual Analysis specialist using Playwright for browser automation.
+
+## Prerequisites
+
+Before capturing screenshots, ensure Playwright and Chromium are installed:
+
+```bash
+pip install playwright && playwright install chromium
+```
+
+## When Analyzing Pages
+
+1. Capture desktop screenshot (1920x1080)
+2. Capture mobile screenshot (375x812, iPhone viewport)
+3. Analyze above-the-fold content: is the primary CTA visible?
+4. Check for visual layout issues, overlapping elements
+5. Verify mobile responsiveness
+
+## Screenshot Script
+
+Use the screenshot script (at `.agent/skills/seo/scripts/capture_screenshot.py`) for browser automation:
+
+```python
+from playwright.sync_api import sync_playwright
+
+def capture(url, output_path, viewport_width=1920, viewport_height=1080):
+    with sync_playwright() as p:
+        browser = p.chromium.launch()
+        page = browser.new_page(viewport={'width': viewport_width, 'height': viewport_height})
+        page.goto(url, wait_until='networkidle')
+        page.screenshot(path=output_path, full_page=False)
+        browser.close()
+```
+
+## Viewports to Test
+
+| Device | Width | Height |
+|--------|-------|--------|
+| Desktop | 1920 | 1080 |
+| Laptop | 1366 | 768 |
+| Tablet | 768 | 1024 |
+| Mobile | 375 | 812 |
+
+## Visual Checks
+
+### Above-the-Fold Analysis
+- Primary heading (H1) visible without scrolling
+- Main CTA visible without scrolling
+- Hero image/content loading properly
+- No layout shifts on load
+
+### Mobile Responsiveness
+- Navigation accessible (hamburger menu or visible)
+- Touch targets at least 48x48px
+- No horizontal scroll
+- Text readable without zooming (16px+ base font)
+
+### Visual Issues
+- Overlapping elements
+- Text cut off or overflow
+- Images not scaling properly
+- Broken layout at different widths
+
+## Output Format
+
+Provide:
+- Screenshots saved to `screenshots/` directory
+- Visual analysis summary
+- Mobile responsiveness assessment
+- Above-the-fold content evaluation
+- Specific issues with element locations

package/.agent/skills/seo-competitor-pages/SKILL.md

@@ -0,0 +1,212 @@
+---
+name: seo-competitor-pages
+description: >
+  Generate SEO-optimized competitor comparison and alternatives pages. Covers
+  "X vs Y" layouts, "alternatives to X" pages, feature matrices, schema markup,
+  and conversion optimization. Use when user says "comparison page", "vs page",
+  "alternatives page", "competitor comparison", or "X vs Y".
+---
+
+# Competitor Comparison & Alternatives Pages
+
+Create high-converting comparison and alternatives pages that target
+competitive intent keywords with accurate, structured content.
+
+## Page Types
+
+### 1. "X vs Y" Comparison Pages
+- Direct head-to-head comparison between two products/services
+- Balanced feature-by-feature analysis
+- Clear verdict or recommendation with justification
+- Target keyword: `[Product A] vs [Product B]`
+
+### 2. "Alternatives to X" Pages
+- List of alternatives to a specific product/service
+- Each alternative with brief summary, pros/cons, best-for use case
+- Target keyword: `[Product] alternatives`, `best alternatives to [Product]`
+
+### 3. "Best [Category] Tools" Roundup Pages
+- Curated list of top tools/services in a category
+- Ranking criteria clearly stated
+- Target keyword: `best [category] tools [year]`, `top [category] software`
+
+### 4. Comparison Table Pages
+- Feature matrix with multiple products in columns
+- Sortable/filterable if interactive
+- Target keyword: `[category] comparison`, `[category] comparison chart`
+
+## Comparison Table Generation
+
+### Feature Matrix Layout
+```
+| Feature          | Your Product | Competitor A | Competitor B |
+|------------------|:------------:|:------------:|:------------:|
+| Feature 1        | ✅           | ✅           | ❌           |
+| Feature 2        | ✅           | ⚠️ Partial   | ✅           |
+| Feature 3        | ✅           | ❌           | ❌           |
+| Pricing (from)   | $X/mo        | $Y/mo        | $Z/mo        |
+| Free Tier        | ✅           | ❌           | ✅           |
+```
+
+### Data Accuracy Requirements
+- All feature claims must be verifiable from public sources
+- Pricing must be current (include "as of [date]" note)
+- Update frequency: review quarterly or when competitors ship major changes
+- Link to source for each competitor data point where possible
+
+## Schema Markup Recommendations
+
+### Product Schema with AggregateRating
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Product",
+  "name": "[Product Name]",
+  "description": "[Product Description]",
+  "brand": {
+    "@type": "Brand",
+    "name": "[Brand Name]"
+  },
+  "aggregateRating": {
+    "@type": "AggregateRating",
+    "ratingValue": "[Rating]",
+    "reviewCount": "[Count]",
+    "bestRating": "5",
+    "worstRating": "1"
+  }
+}
+```
+
+### SoftwareApplication (for software comparisons)
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "SoftwareApplication",
+  "name": "[Software Name]",
+  "applicationCategory": "[Category]",
+  "operatingSystem": "[OS]",
+  "offers": {
+    "@type": "Offer",
+    "price": "[Price]",
+    "priceCurrency": "USD"
+  }
+}
+```
+
+### ItemList (for roundup pages)
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "ItemList",
+  "name": "Best [Category] Tools [Year]",
+  "itemListOrder": "https://schema.org/ItemListOrderDescending",
+  "numberOfItems": "[Count]",
+  "itemListElement": [
+    {
+      "@type": "ListItem",
+      "position": 1,
+      "name": "[Product Name]",
+      "url": "[Product URL]"
+    }
+  ]
+}
+```
+
+## Keyword Targeting
+
+### Comparison Intent Patterns
+| Pattern | Example | Search Volume Signal |
+|---------|---------|---------------------|
+| `[A] vs [B]` | "Slack vs Teams" | High |
+| `[A] alternative` | "Figma alternatives" | High |
+| `[A] alternatives [year]` | "Notion alternatives 2026" | High |
+| `best [category] tools` | "best project management tools" | High |
+| `[A] vs [B] for [use case]` | "AWS vs Azure for startups" | Medium |
+| `[A] review [year]` | "Monday.com review 2026" | Medium |
+| `[A] vs [B] pricing` | "HubSpot vs Salesforce pricing" | Medium |
+| `is [A] better than [B]` | "is Notion better than Confluence" | Medium |
+
+### Title Tag Formulas
+- X vs Y: `[A] vs [B]: [Key Differentiator] ([Year])`
+- Alternatives: `[N] Best [A] Alternatives in [Year] (Free & Paid)`
+- Roundup: `[N] Best [Category] Tools in [Year], Compared & Ranked`
+
+### H1 Patterns
+- Match title tag intent
+- Include primary keyword naturally
+- Keep under 70 characters
+
+## Conversion-Optimized Layouts
+
+### CTA Placement
+- **Above fold**: Brief comparison summary with primary CTA
+- **After comparison table**: "Try [Your Product] free" CTA
+- **Bottom of page**: Final recommendation with CTA
+- Avoid aggressive CTAs in competitor description sections (reduces trust)
+
+### Social Proof Sections
+- Customer testimonials relevant to comparison criteria
+- G2/Capterra/TrustPilot ratings (with source links)
+- Case studies showing migration from competitor
+- "Switched from [Competitor]" stories
+
+### Pricing Highlights
+- Clear pricing comparison table
+- Highlight value advantages (not just lowest price)
+- Include hidden costs (setup fees, per-user pricing, overage charges)
+- Link to full pricing page
+
+### Trust Signals
+- "Last updated [date]" timestamp
+- Author with relevant expertise
+- Methodology disclosure (how comparisons were conducted)
+- Disclosure of own product affiliation
+
+## Fairness Guidelines
+
+- **Accuracy**: All competitor information must be verifiable from public sources
+- **No defamation**: Never make false or misleading claims about competitors
+- **Cite sources**: Link to competitor websites, review sites, or documentation
+- **Timely updates**: Review and update when competitors release major changes
+- **Disclose affiliation**: Clearly state which product is yours
+- **Balanced presentation**: Acknowledge competitor strengths honestly
+- **Pricing accuracy**: Include "as of [date]" disclaimers on all pricing data
+- **Feature verification**: Test competitor features where possible, cite documentation otherwise
+
+## Internal Linking
+
+- Link to your own product/service pages from comparison sections
+- Cross-link between related comparison pages (e.g., "A vs B" links to "A vs C")
+- Link to feature-specific pages when discussing individual features
+- Breadcrumb: Home > Comparisons > [This Page]
+- Related comparisons section at bottom of page
+- Link to case studies and testimonials mentioned in the comparison
+
+## Output
+
+### Comparison Page Template
+- `COMPARISON-PAGE.md`: Ready-to-implement page structure with sections
+- Feature matrix table
+- Content outline with word count targets (minimum 1,500 words)
+
+### Schema Markup
+- `comparison-schema.json`: Product/SoftwareApplication/ItemList JSON-LD
+
+### Keyword Strategy
+- Primary and secondary keywords
+- Related long-tail opportunities
+- Content gaps vs existing competitor pages
+
+### Recommendations
+- Content improvements for existing comparison pages
+- New comparison page opportunities
+- Schema markup additions
+- Conversion optimization suggestions
+
+## Error Handling
+
+| Scenario | Action |
+|----------|--------|
+| Competitor URL unreachable | Report which competitor URLs failed. Proceed with available data and note gaps in the comparison. |
+| Insufficient competitor data (pricing, features unavailable) | Flag missing data points clearly. Use "Not publicly available" in comparison tables rather than guessing. |
+| No product/service overlap found | Report that the products serve different markets. Suggest alternative competitors that share feature overlap, or pivot to a category roundup format. |