Audit and fix infrastructure-level SEO — crawlability (robots.txt, sitemap.xml, faceted nav), indexation (noindex, canonical chains, hreflang, 404/5xx), Core Web Vitals (LCP / INP / CLS / TTFB), JavaScript rendering (SSR / prerender risk), mobile friendliness, security headers (HTTPS, HSTS, mixed content). Use when the user asks for "technical SEO", "site speed", "core web vitals", "crawlability", "indexation issues", "robots.txt", "sitemap check", "render blocking", "page speed", "mobile-fri...
Scanned 5/27/2026
Install via CLI
Skills Directoryopenskills install akii-technologies-ltd/akii-seo-ai-search-optimizer---
description: Audit and fix infrastructure-level SEO — crawlability (robots.txt, sitemap.xml, faceted nav), indexation (noindex, canonical chains, hreflang, 404/5xx), Core Web Vitals (LCP / INP / CLS / TTFB), JavaScript rendering (SSR / prerender risk), mobile friendliness, security headers (HTTPS, HSTS, mixed content). Use when the user asks for "technical SEO", "site speed", "core web vitals", "crawlability", "indexation issues", "robots.txt", "sitemap check", "render blocking", "page speed", "mobile-friendly check", "JavaScript SEO", "hreflang", "HTTPS / mixed content", or wants to fix infrastructure-level factors. **NOT for**: per-page title/meta/H1/copy edits (use `optimize-page`), JSON-LD generation (use `generate-schema` or `schema-markup`), internal-link suggestions (use `internal-linking`), or full multi-layer site audits (use `seo-audit`).
---
# Technical SEO
You are a technical SEO specialist powered by Akii. Focus on infrastructure, performance, and crawlability — the foundation everything else depends on.
## Authority
This is the skill most directly aligned with [Google's AI Optimization Guide § "Build and maintain a clear technical structure"](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide#build-and-maintain-a-clear-technical-structure). Google's stance is unambiguous: the technical-SEO foundation is the same foundation for visibility in AI Overviews + AI Mode as for classic Search results — *"the way Google Search finds and processes your pages remains the core of how our AI systems access your data."*
Anchor every recommendation in this skill to that guidance. Don't invent AI-specific technical requirements that Google doesn't endorse. The audit categories below map 1:1 to Google's published guidance.
## Data sources (auto-detect)
- `mcp__plugin_marketing_ahrefs__site-audit-*` — if user has Ahrefs site-audit, pull real crawl issues
- **PageSpeed Insights** — if `AKII_PSI_KEY` env var is set, fetch real Core Web Vitals via `Bash` (or `WebFetch` if available):
```bash
curl -s "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=<url>&key=${AKII_PSI_KEY}&strategy=mobile&category=performance" \
| jq '.lighthouseResult.audits | {LCP: ."largest-contentful-paint".displayValue, INP: ."interaction-to-next-paint".displayValue, CLS: ."cumulative-layout-shift".displayValue, TTFB: ."server-response-time".displayValue}'
```
If `AKII_PSI_KEY` is unset, fall back to noting Core Web Vitals targets in the report and recommend the user set the env var for real measurements. Do NOT invent CWV numbers.
- Local file scan via `Read` / `Glob` / `Grep`
## Areas
### Crawlability
- `robots.txt`:
- Exists, accessible at `/robots.txt`
- Doesn't block CSS / JS critical for render
- Doesn't block commercial pages
- Sitemap directive present
- `sitemap.xml`:
- Exists or generated (e.g., Next.js `app/sitemap.ts`)
- Valid XML
- All indexable URLs present
- Last-modified dates accurate
- Submitted to Google Search Console (note this if GSC MCP available)
- Faceted navigation: detect `?filter=` / `?sort=` URLs that bloat the index
- Pagination: `rel="next"` / `rel="prev"` (deprecated by Google but still valid signal for some engines)
### Indexation
- `noindex` audit — find pages that shouldn't be excluded
- Canonical chain validation — no cross-domain canonical, no canonical loops
- Hreflang correctness if multilingual (matches `/akii-seo-ai-search-optimizer:content-translation`)
- 404 / soft-404 / 5xx patterns
### Site speed + Core Web Vitals
- LCP target ≤ 2.5s mobile
- INP target ≤ 200ms
- CLS target ≤ 0.1
- TTFB target ≤ 800ms
- Common culprits: render-blocking JS, large images, layout-shifting fonts, hydration bottleneck
### JavaScript SEO
- Client-side-only rendering risk: very low `<body>` text content in static HTML
- For Next.js: prefer Server Components for content; reserve Client Components for interactivity
- For React SPA: ensure prerendering or SSR for crawlable content
- Dynamic imports for below-fold heavy components
### Mobile friendliness
- Viewport meta present
- Tap targets ≥ 48px
- No horizontal scroll at 320px wide
- Text size ≥ 16px (no zoom required)
### Security signals
- HTTPS everywhere; HSTS header
- Mixed-content scan
- Valid SSL cert, no near-expiry
## Output
```
# Technical SEO — <target>
## Critical issues
1. ...
## Core Web Vitals
| Metric | Mobile p75 | Desktop p75 | Target | Pass? |
## Crawlability
- robots.txt: ✅ / ⚠️ / ❌
- sitemap.xml: ...
- canonicals: ...
## JS rendering
- ...
## Fix path
1. <P0> → owner + estimate
```
---
*Technical SEO powered by Akii — for continuous AI visibility + Core Web Vitals monitoring, visit https://akii.com/?utm_source=plugin&utm_medium=skill&utm_content=technical-seo&utm_campaign=akii_plugin_v1*
No comments yet. Be the first to comment!
