Site Architecture
AvdLee/RocketSimApp
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
Run a full technical and on-page SEO audit on any website or page.
$ npx skills add OpenClaudia/openclaudia-skills --skill seo-audit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OpenClaudia/openclaudia-skills seo-audit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-audit .claude/skills/seo-audit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "seo-audit" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/seo-audit into .claude/skills/seo-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-audit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/seo-auditType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OpenClaudia/openclaudia-skills --skill seo-audit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OpenClaudia/openclaudia-skills seo-audit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo-audit .agents/skills/seo-audit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "seo-audit" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/seo-audit into .agents/skills/seo-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-audit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenClaudia/openclaudia-skills --skill seo-audit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OpenClaudia/openclaudia-skills seo-audit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo-audit .cursor/skills/seo-audit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "seo-audit" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/seo-audit into .cursor/skills/seo-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-audit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OpenClaudia/openclaudia-skills.git --path skills/seo-audit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OpenClaudia/openclaudia-skills --skill seo-audit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OpenClaudia/openclaudia-skills seo-audit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo-audit .gemini/skills/seo-audit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "seo-audit" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/seo-audit into .gemini/skills/seo-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-audit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OpenClaudia/openclaudia-skills seo-auditInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OpenClaudia/openclaudia-skills --skill seo-audit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo-audit .github/skills/seo-audit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "seo-audit" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/seo-audit into .github/skills/seo-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-audit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenClaudia/openclaudia-skills --skill seo-audit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OpenClaudia/openclaudia-skills seo-audit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo-audit .opencode/skills/seo-audit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "seo-audit" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/seo-audit into .opencode/skills/seo-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-audit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
seo-auditRun a full technical and on-page SEO audit on any website or page.
SEO Audit is an agent skill from OpenClaudia/openclaudia-skills. Run a full technical and on-page SEO audit on any website or page. Use when the user says "audit my site", "SEO check", "technical SEO review", "site health", "check my SEO", "what's wrong with my site", or provides a URL and asks for SEO feedback.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Technical SEO, SEO audit and On-page SEO. The repository describes itself as: 77 open-source marketing skills for Claude Code, Codex, and other AI coding agents. SEO, content, email, ads, analytics, and growth. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 28bf209. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
googleapis.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
SEO Audit loads about 2.2k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 879 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from OpenClaudia/openclaudia-skills at commit 28bf209, republished under its MIT licence (© OpenClaudia). 879 words, ~2,226 tokens.
.claude/skills/seo-audit/SKILL.md (or your agent's skills folder).You are an expert SEO auditor. When given a URL or domain, perform a comprehensive technical and on-page SEO audit. Produce a structured report with scores, issues, and prioritized fix recommendations.
Use the available tools to collect information about the target site:
{domain}/robots.txt{domain}/sitemap.xml (also check robots.txt for sitemap location)https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url={URL}&strategy=mobile and &strategy=desktopIf the user provides a project codebase, also inspect:
next.config.js, app/layout.tsx, middleware.ts<head> contents, Open Graph tagsEvaluate each category below. Score each 0-100 and list specific issues found.
Check these items:
| Check | What to look for | Severity |
|---|---|---|
| robots.txt | Exists, not blocking important pages, allows search engines | Critical |
| XML Sitemap | Exists, valid XML, includes all important URLs, no 404s listed | Critical |
| Canonical tags | Present on all pages, self-referencing, no conflicting canonicals | High |
| Hreflang tags | Present if multi-language, valid language codes, reciprocal tags | Medium |
| Noindex tags | Not accidentally applied to important pages | Critical |
| URL structure | Clean slugs, no excessive parameters, logical hierarchy | Medium |
| Redirect chains | No chains longer than 2 hops, no redirect loops | High |
| 404 pages | Custom 404, no soft 404s, broken internal links | Medium |
| Pagination | rel=prev/next or proper infinite scroll handling | Low |
| Crawl depth | Important pages within 3 clicks of homepage | Medium |
Scoring formula:
| Check | What to look for | Severity |
|---|---|---|
| HTTPS | Site uses HTTPS, no mixed content, proper redirects from HTTP | Critical |
| Mobile-friendliness | Responsive design, viewport meta tag, no horizontal scroll, tap targets 48px+ | Critical |
| Core Web Vitals - LCP | Largest Contentful Paint < 2.5s (good), < 4s (needs improvement) | High |
| Core Web Vitals - FID/INP | First Input Delay < 100ms / Interaction to Next Paint < 200ms | High |
| Core Web Vitals - CLS | Cumulative Layout Shift < 0.1 (good), < 0.25 (needs improvement) | High |
| Page speed - mobile | Performance score > 90 (good), > 50 (needs improvement) | High |
| Page speed - desktop | Performance score > 90 (good), > 50 (needs improvement) | Medium |
| Render blocking resources | Critical CSS inlined, JS deferred/async | Medium |
| Image optimization | WebP/AVIF format, proper sizing, lazy loading below fold | Medium |
| Server response time | TTFB < 200ms (good), < 500ms (acceptable) | High |
| Compression | Gzip or Brotli enabled | Medium |
| HTTP/2 or HTTP/3 | Modern protocol in use | Low |
| JavaScript rendering | Content visible without JS (for search engines) | High |
Scoring: Same formula as Category 1.
For each page analyzed, check:
| Check | What to look for | Severity |
|---|---|---|
| Title tag | Exists, 50-60 characters, includes primary keyword, unique per page | Critical |
| Meta description | Exists, 150-160 characters, includes keyword, compelling CTA | High |
| H1 tag | Exactly one per page, includes primary keyword | Critical |
| Heading hierarchy | Logical H1 > H2 > H3 nesting, no skipped levels | Medium |
| Keyword in first 100 words | Primary keyword appears naturally in opening paragraph | Medium |
| Content length | Adequate for topic (check against SERP competitors) | Medium |
| Internal links | 3-10 relevant internal links per page, descriptive anchor text | High |
| External links | Links to authoritative sources where appropriate | Low |
| Image alt text | All images have descriptive alt text with keywords where natural | Medium |
| URL slug | Includes primary keyword, short, hyphenated, lowercase | Medium |
| Open Graph tags | og:title, og:description, og:image present and correct | Medium |
| Twitter Card tags | twitter:card, twitter:title, twitter:description present | Low |
Scoring: Same formula as Category 1.
Evaluate these qualitative factors:
| Factor | What to assess | Score range |
|---|---|---|
| E-E-A-T signals | Author bios, credentials, about page, contact info, bylines | 0-20 |
| Content freshness | Last updated dates, regular publishing cadence | 0-15 |
| Content depth | Comprehensive coverage vs. thin content, word count vs. competitors | 0-20 |
| Originality | Unique insights, not just rehashed competitor content | 0-15 |
| Readability | Short paragraphs, subheadings, lists, Flesch reading ease 60-70 | 0-15 |
| Media richness | Images, videos, infographics, interactive elements | 0-15 |
Score: Sum of all factors (max 100).
| Check | What to look for | Score range |
|---|---|---|
| Internal linking structure | Logical silo structure, hub pages, orphan pages | 0-25 |
| Anchor text diversity | Natural anchor text distribution, not over-optimized | 0-25 |
| Backlink profile indicators | Links from authoritative domains, relevance, diversity | 0-25 |
| Social signals | Social sharing buttons, engagement indicators | 0-10 |
| Brand mentions | Brand appears consistently, NAP consistent (local) | 0-15 |
Score: Sum of all factors (max 100).
Overall = (Crawlability * 0.20) + (Technical * 0.25) + (On-Page * 0.25) + (Content * 0.15) + (Authority * 0.15)Rating scale:
Format the report exactly as follows:
# SEO Audit Report: {domain}
**Date:** {date}
**Pages Analyzed:** {count}
**Overall Score:** {score}/100 ({rating})
## Score Summary
| Category | Score | Weight | Weighted |
|----------|-------|--------|----------|
| Crawlability & Indexation | {}/100 | 20% | {} |
| Technical Foundations | {}/100 | 25% | {} |
| On-Page Optimization | {}/100 | 25% | {} |
| Content Quality | {}/100 | 15% | {} |
| Authority & Links | {}/100 | 15% | {} |
| **Overall** | | | **{}/100** |
## Critical Issues (Fix Immediately)
1. **{Issue title}** - {Description}
- **Impact:** {What this costs in traffic/rankings}
- **Fix:** {Exact steps to fix}
- **Effort:** {Low/Medium/High}
## High Priority Issues
{Same format as critical}
## Medium Priority Issues
{Same format}
## Low Priority Issues
{Same format}
## Quick Wins (High Impact, Low Effort)
{Numbered list of easy fixes with the biggest impact}
## Detailed Findings
### Crawlability & Indexation
{Detailed findings with evidence}
### Technical Foundations
{Detailed findings with PageSpeed data}
### On-Page Optimization
{Detailed findings per page}
### Content Quality
{Detailed assessment}
### Authority & Links
{Detailed findings}
## Recommended Action Plan
### Week 1: Critical Fixes
{List}
### Week 2-3: High Priority
{List}
### Month 2: Medium Priority
{List}
### Ongoing: Monitoring
{List}© OpenClaudia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/seo-audit of OpenClaudia/openclaudia-skills.
Open the folder on GitHubat commit 28bf209
SEO Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| SEO Audit this skillOpenClaudia/openclaudia-skills | 713 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Site ArchitectureAvdLee/RocketSimApp | 804 | 11 repos | ~3.3k | Automated safety check: Pass | Custom licence | |
| SEO Optimizerailabs-393/ai-labs-claude-skills | 454 | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| SEO Drift MonitorAgriciDaniel/claude-seo | 19k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| SEO Auditfreekmurze/dotfiles | 1k | 34 repos | ~2.2k | Automated safety check: Pass | None | |
| Universal SEO AnalysisAgriciDaniel/claude-seo | 19k | — | ~4.9k | Automated safety check: Pass | MIT |
AvdLee/RocketSimApp
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.
AgriciDaniel/claude-seo
Captures baselines of a page's SEO-critical elements, compares later snapshots against them and flags regressions by severity, like version control for on-page SEO.
freekmurze/dotfiles
When the user wants to audit, review, or diagnose SEO issues on their site.
AgriciDaniel/claude-seo
Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.
artwist-polyakov/polyakov-claude-skills
Crawls a site with Crawl4AI to audit titles, meta tags, H1s, canonicals, navigation and internal links, and to compare landing pages and competitor sites.
OpenClaudia/openclaudia-skills
Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with…
OpenClaudia/openclaudia-skills
Score how hard a keyword is to rank for in the AI-search era — page-level URL Rating of real competitors (not just domain DR), Ahrefs keyword difficulty, and whether a given site already ranks or is…
OpenClaudia/openclaudia-skills
Audit EVERY Google Search Console property at once — rank all sites by clicks and impressions with period-over-period deltas, then diff keywords per site to surface what is newly ranking, rising…
OpenClaudia/openclaudia-skills
Fetch website traffic estimates (monthly visits, traffic sources, top countries, keywords, engagement, ranks) for any domain from SimilarWeb.
OpenClaudia/openclaudia-skills
Manages Ahrefs API usage in Python using ahrefs-python library.
OpenClaudia/openclaudia-skills
Design, plan, and analyze A/B tests with statistical rigor. An agent skill from OpenClaudia/openclaudia-skills.
Categories
Run a full technical and on-page SEO audit on any website or page. SEO Audit is an agent skill from OpenClaudia/openclaudia-skills. Run a full technical and on-page SEO audit on any website or page.
SEO Audit fits situations like: the user says audit my site; technical SEO review; whats wrong with my site; provides a URL and asks for SEO feedback.
Run `npx skills add OpenClaudia/openclaudia-skills --skill seo-audit -a claude-code`. Or copy the skill folder (skills/seo-audit in OpenClaudia/openclaudia-skills) into .claude/skills/seo-audit in your project. Claude Code loads it when a task matches its description.
Run `npx skills add OpenClaudia/openclaudia-skills --skill seo-audit -a codex`. Or copy the skill folder (skills/seo-audit in OpenClaudia/openclaudia-skills) into .agents/skills/seo-audit in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenClaudia/openclaudia-skills --skill seo-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-audit, .gemini/skills/seo-audit, .github/skills/seo-audit and .opencode/skills/seo-audit in your project.
SKILL.md names no scripts, command-line tools or credentials: SEO Audit is instructions for the agent only.
SKILL.md names 1 domain. In commands or code: googleapis.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
SEO Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with SEO Audit: Site Architecture (AvdLee/RocketSimApp, 804 stars), SEO Optimizer (ailabs-393/ai-labs-claude-skills, 454 stars), SEO Drift Monitor (AgriciDaniel/claude-seo, 19k stars) and SEO Audit (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
OpenClaudia (a GitHub organization) maintains it in OpenClaudia/openclaudia-skills, which has 713 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on September 18, 2026.
Source: OpenClaudia/openclaudia-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.