What does this skill do, and when should you use it?
Technical SEO Checker is the Tune-phase SEO/GEO skill in Aaron Marketing Skills, focused on technical site health. It reviews crawlability, indexability, Core Web Vitals, mobile usability, security, URL structure, structured data, and international SEO. Each audited area receives evidence, issues, fixes, and a score, followed by a prioritized queue and handoff summary. It fits technical SEO diagnostics and migration planning, but not page-level tags or content optimization.
Reads target URLs or domains, robots.txt, sitemaps, PageSpeed/CrUX reports, and reported symptoms; checks crawlability, indexability, Core Web Vitals, mobile-friendliness, HTTPS and security headers, URL patterns, structured data, and hreflang; can run the referenced robots, sitemap, crawl, onpage, and psi Python helpers, plus rendered crawling, W3C Nu validation, certificate-transparency lookups, and gated IndexNow/Baidu push workflows; produces an evidence-backed scorecard, P0 repair priorities, roadmap, monitoring plan, and handoff summary.
- An SEO team needs to diagnose why pages are not being found or indexed by Google.
- A site owner wants to review Core Web Vitals, page speed, and mobile experience.
- An engineering team is preparing a migration between domains or from WordPress to a headless Next.js stack.
- An ecommerce team has many unindexed product pages and needs a pattern-level bulk audit.
- A website team needs to review how robots.txt handles GPTBot, ClaudeBot, or other AI crawlers.
How do you install this skill?
- This is a low-confidence static review only; no connector, crawl, performance test, or indexing submission was executed.
- Before using Firecrawl, Tavily, or other delegated services, confirm that transmitting the target URL to a third party is acceptable and verify mainland-China reachability.
- The skill declares version 18.0.0 while SECURITY.md identifies 17.x as the current supported line; clarify support and maintenance status.
- Robots policies, AI-crawler behavior, search APIs, and performance guidance can change, so production conclusions require date-specific revalidation.
- Shell / CLI
- Network access
- Local filesystem
Python 3curl
In Claude Code, run /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, then /plugin install aaron-marketing@aaron. On a generic Agent Skills-compatible host, run npx skills add aaron-he-zhu/aaron-marketing-skills; you can also use git clone https://github.com/aaron-he-zhu/aaron-marketing-skills. The skill is located at seo-geo/tune/technical-seo-checker/SKILL.md.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/seo-geo/tune/technical-seo-checker" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Provide a URL or domain and enter Perform a technical SEO audit for https://example.com. You can narrow the request with Check Core Web Vitals for https://example.com or Audit crawlability and indexability for example.com. For a migration audit, provide both endpoints and the relevant stacks. AI-crawler audits require choosing default-open, default-closed, or split handling.
What are this skill's strengths and limitations?
- Covers crawling, indexing, speed, security, structured data, and international SEO in one workflow.
- Requires metrics to be labeled Measured, User-provided, or Estimated, and marks unavailable data N/A.
- Produces scores, P0 risk flags, a prioritized repair queue, roadmap, and handoff summary.
- Supports focused checks, bulk audits for 5+ URLs, and pre-migration workflows.
- It needs target URLs, domains, or supplied PageSpeed, robots.txt, and sitemap data; unavailable evidence is not fabricated.
- The SKILL.md references Python, curl, Firecrawl, W3C Nu, and other connector workflows, but does not fully document their deployment in this file.
- It explicitly excludes page-level tags and content optimization; those are directed to on-page-seo-checker.
- External writes such as index pushes are gated, dry-run by default, and require the relevant credentials or tokens.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Technical SEO Checker this page | 60 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
| GEO Technical SEO Audit Skill (geo-technical) | 54 · Use with care | ★ 11k | 21d ago | MIT |
| Technical SEO Auditor | 49 · Use with care | ★ 19k | 22d ago | MIT |
| Unlighthouse Site Audit | 51 · Use with care | ★ 19k | 22d ago | MIT |
| Full-Site SEO Audit | 53 · Use with care | ★ 19k | 22d ago | MIT |
How did FollowSkills review this skill?
The evidence limits the declared tool to WebFetch, treats fetched content as untrusted data, labels metric provenance, asks before saving, and gates indexing mutations behind dry-run plus --live. Five points are deducted because sensitive-data handling, consolidated data-flow disclosure, and confirmation boundaries remain incomplete; some delegated fetch paths may transmit target URLs to third parties.
The skill provides structured workflows, abnormal-input decision gates, N/A handling, rendering fallback, bulk-mode rules, and evidence requirements after failures. One point is deducted because static review cannot reproduce key paths and availability of tool placeholders, external references, and connectors is unverified.
The evidence clearly identifies audiences and scenarios for focused audits, bulk audits, migrations, and AI-crawler policy, while excluding on-page SEO and including Chinese trigger terms. Four points are deducted for limited evidence of host compatibility and mainland-China reachability; core fetching and performance workflows may depend on regionally constrained services.
The skill has readable progressive sections, Quick Start prompts, a contract, playbooks, templates, examples, Apache-2.0 licensing, version metadata, and installation context. Four points are deducted because maintenance ownership, changelog/update governance, and support information are incomplete, while SECURITY.md lists 17.x as current despite the skill declaring 18.0.0.
The evidence defines the objective, inputs, nine audit areas, scorecard, prioritized remediation plan, and handoff summary, making the intended output directly usable as a report structure. One point is deducted because no real execution output or third-party validation is provided; conclusions depend on data supplied or retrieved at runtime.
The files specify evidence fields, sample size, crawl date, source labels, thresholds, and a ledger-diff approach for validating fixes. Two points are deducted because the supplied material lacks committed key-path tests or third-party execution records sufficient to establish reproducibility statically.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →