seo-technical
Technical SEOagricidaniel/claude-seoskills.sh ↗
Installs
5,236
deduplicated, at the last sync
Since we started
+2.6%
40 readings, about 2 hours apart. Not a live curve.
Our category
Technical SEO
ours
Last read
Sep 3, 2026
from the directory
Our brief
oursThis skill performs a comprehensive technical SEO audit across nine categories, including crawlability, indexability, security, mobile optimization, Core Web Vitals, structured data, JavaScript rendering, and the IndexNow protocol [2]. It also audits for agent-friendly page characteristics by analyzing the accessibility tree to ensure semantic HTML usage and proper label associations [1], [2].
- Technical SEO audit report across 9 categories
- Agent-UX score (0-100) plus itemized issues
- Accessibility tree findings
- URL to audit
not detected
The provided evidence does not contain information regarding required payments or API costs.
not detected
The provided evidence does not mention any user registration requirement.
The skill provides technical audit checks and guidance but cannot guarantee ranking success, nor can it verify the real-time effectiveness of implemented fixes. It also relies on specific commands like `claude-seo run agent_ux_check.py` to perform detailed audits [2].
Evidenceskills/seo-technical/references/agent-friendly-pages.md:1-65skills/seo-technical/SKILL.md:1-195
# Agent-friendly pages — audit reference (June 2026) The next wave of AI search is not summarization — it's **agents** acting on the user's behalf (search, compare, buy, book). Google's AI optimization guide and the linked web.dev article describe three channels through which agents interpret your site: 1. **Screenshots + vision model** — interprets visual hierarchy, button prominence, layout. Slow and token-expensive. 2. **Raw HTML / DOM** — nesting, IDs, classes, data attributes. 3. **The accessibility tree** — the browser-native semantic distillation (roles, names, states). The cleanest signal of the three. Modern agents combine all three. Optimizing for the **accessibility tree** is the single highest-leverage move; if your accessibility tree is broken, no amount of visual polish saves you. **Primary sources:** - Google AI optimization guide: https://developers.google.com/search/docs/fundamentals/ai-optimization-guide - web.dev (referenced from the guide above): article on building agent-friendly websites ## Audit checklist ### 1. Use real interactive elements | Pass | Fail | |---|---| | `<button>` for actions | `<div onclick="...">` | | `<a href="...">` for na
--- name: seo-technical description: > Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers". user-invocable: true argument-hint: "[url]" license: MIT metadata: author: AgriciDaniel version: "2.2.5" category: seo --- # Technical SEO Audit ## Categories ### 1. Crawlability - robots.txt: exists, valid, not blocking important resources - XML sitemap: run `claude-seo run sitemap_discovery.py <url> --json`; require a valid entry in `found`, and report stale or unsafe robots.txt declarations separately from working fallback locations - Noindex tags: intentional vs accidental - Crawl depth: important pages within 3 clicks of homepage - JavaScript rendering: check if critical content requires JS execution - Crawl budget: for large sites (>10k pages), efficiency matters - Googlebot **fetch limits**: Googlebot fetches the first **2MB of HTML** and first **64MB of a PDF** (uncompressed; 15MB is the broader crawler-infra default)
Read 2 of 2 text files in the skill.
Installfrom the directory
npx skills add https://github.com/agricidaniel/claude-seoInstalling happens there, not here. We are an index with an opinion, not a mirror.
What is inside itfrom the directory
3 files — names only. The directory does not report sizes.
What the auditors foundfrom the directory
A skill is instructions your agent will follow and scripts it may run, so who checked it matters as much as how many people installed it.
Installs, reading by readingours
Axis starts at 5.1k, not zero — the range is 5.1k to 5.2k.
Asked out loudspoken, not typed
The same skill in the words people use speaking to an assistant rather than typing into a box. Each one carries the situation it came from, and each answer says only what the skill's own files support.
You can provide the skill with a URL to analyze. Alternatively, you can use specific commands like `claude-seo run agent_ux_check.py <url> --json` for detailed checks [2].
Yes, the documentation includes sections on managing various known AI crawlers via robots.txt rules, such as GPTBot and ClaudeBot [2].
The evidence does not specify if payment is required for running the technical SEO audits or checks.