Skills technical-seo-checker

📦

technical-seo-checker

Name: technical-seo-checker
Author: aaron-he-zhu

v17.0.0 Content revision r1 Safe ⚙️ External commands📁 Filesystem access🌐 Network access

Audit Technical SEO and Prioritize Fixes

Technical defects can block crawling, indexing, and page performance. This skill checks key signals and produces an evidence-based repair plan.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "technical-seo-checker" from https://skillstore.io/skills/aaron-he-zhu-technical-seo-checker.md and its manifest at https://skillstore.io/api/skills/aaron-he-zhu-technical-seo-checker/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/aaron-he-zhu-technical-seo-checker.md Signed manifest GET /api/skills/aaron-he-zhu-technical-seo-checker/manifest Signed lockfile GET /api/skills/aaron-he-zhu-technical-seo-checker/lockfile

Test it

Using "technical-seo-checker". Audit crawlability and indexability for an ecommerce domain.

Expected outcome:

Crawlability: 6/10. Faceted paths consume crawl capacity, and several product URLs are absent from the sitemap.
Indexability: 5/10. Sampled products show conflicting canonical and noindex signals.
Priority: verify affected templates, remove conflicting directives, update the sitemap, and retest representative URLs.

Using "technical-seo-checker". Prepare a technical SEO migration checklist.

Expected outcome:

Before launch: capture URL, status, canonical, metadata, sitemap, and performance baselines.
At launch: validate one-hop redirects, robots rules, canonicals, analytics, and critical templates.
After launch: compare results after one, seven, and thirty days, then escalate regressions.

Using "technical-seo-checker". Review AI crawler handling for a public documentation site.

Expected outcome:

Policy decision required: choose open, closed, or split access. Preserve search crawlers, document training restrictions, and verify edge rules after publishing.

Security Audit

Safe

v4 • 7/12/2026 Open versioned report

Most static findings are Markdown fences, relative documentation links, placeholders, or SEO checklist text. Five findings are confirmed: four executable command recipes and one outbound-network use at SKILL.md lines 98-104; no prompt injection or malicious intent was found.

Files scanned

980

Lines analyzed

Review items

False positives ignored

Capability review items (5)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

SKILL.md:98

Ruby/shell backtick execution

**Zero-dependency local helpers** (no tool needed, run yourself): `python3 "${CLAUDE_PLUGIN_ROOT}/sc

Line 98 explicitly tells the agent to run local Python helpers with a user-supplied URL and includes a shell pipeline. This is legitimate SEO tooling, but command execution and unvalidated input create real execution risk.

Medium

SKILL.md:100

Ruby/shell backtick execution

**JS-rendering fallback (keyless)**: when `crawl.py`/`onpage.py` return an empty or thin body on a c

Line 100 directs the agent to execute a Firecrawl helper against a supplied URL and permits an own-site bypass. The command is relevant, but it performs active network retrieval through executable code.

Medium

SKILL.md:102

Ruby/shell backtick execution

**Keyless recipe sharpeners**: subdomain inventory from certificate-transparency logs — `curl "https

Line 102 provides an executable curl recipe that interpolates a supplied domain and sends a request to crt.sh. Shell interpolation and outbound execution are genuine risks even though the audit purpose is legitimate.

Medium

SKILL.md:104

Ruby/shell backtick execution

**Index-push after fixes (write channel, gated)**: once crawl/indexing fixes ship, `python3 "${CLAUD

Line 104 directs execution of an index-push helper that can submit URLs to external search services when --live is used. The dry-run gate reduces risk, but the command has an intentional external side effect.

Low

SKILL.md:102

Hardcoded URL

**Keyless recipe sharpeners**: subdomain inventory from certificate-transparency logs — `curl "https

Line 102 intentionally sends audit queries to crt.sh and identifies the W3C validator as another external endpoint. These are relevant public services, but they disclose the queried domain or URL to third parties.

Risk Factors

⚙️ External commands (32)

📁 Filesystem access (9)

references/bulk-audit-playbook.md:3 references/pre-migration-playbook.md:3 references/technical-audit-example.md:3 SKILL.md:28 SKILL.md:92 SKILL.md:96 SKILL.md:98 SKILL.md:108 SKILL.md:166

🌐 Network access (6)

references/llm-crawler-handling.md:58 references/robots-txt-reference.md:47 SKILL.md:10 SKILL.md:14 SKILL.md:75 SKILL.md:102

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/aaron-he-zhu-technical-seo-checker/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/aaron-he-zhu-technical-seo-checker/security.svg)](https://skillstore.io/skills/aaron-he-zhu-technical-seo-checker?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/aaron-he-zhu-technical-seo-checker?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/aaron-he-zhu-technical-seo-checker/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/aaron-he-zhu-technical-seo-checker.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

aaron-he-zhu. (2026). technical-seo-checker security audit report (audit version 4) [Author version 17.0.0]. Skillstore. https://skillstore.io/skills/aaron-he-zhu-technical-seo-checker/audits/4

BibTeX citation

@techreport{aaron-he-zhu-aaron-he-zhu-technical-seo-checker-2026,
  author = {aaron-he-zhu},
  title = {technical-seo-checker security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/aaron-he-zhu-technical-seo-checker/audits/4},
  note = {Author version 17.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "technical-seo-checker security audit report (audit version 4)"
version: "17.0.0"
type: report
authors:
  - name: "aaron-he-zhu"
date-released: "2026-07-12"
url: "https://skillstore.io/skills/aaron-he-zhu-technical-seo-checker/audits/4"
identifiers:
  - type: other
    value: "skillstore:aaron-he-zhu-technical-seo-checker:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Diagnose an indexing decline

Review crawl barriers, canonical conflicts, status codes, and sitemap coverage after organic traffic drops.

Prepare a site migration

Build a baseline, redirect map, staging checklist, cutover plan, and post-launch comparison.

Audit an ecommerce catalog

Sample URL patterns, identify template-level defects, and prioritize fixes by affected page count.

Try These Prompts

Check one page

Check Core Web Vitals and indexability for [URL]. Label each metric source and list the three highest-priority fixes.

Audit a domain

Perform a technical SEO audit for [domain]. Score each area, cite evidence, and separate measured results from estimates.

Review a large catalog

Bulk audit URLs from [sitemap]. Group patterns, sample representative pages, estimate affected counts, and produce a portfolio priority queue.

Plan a migration

Create a pre-migration audit from [old domain and stack] to [new domain and stack], including redirects, staging checks, launch gates, and monitoring.

Best Practices

Provide target URLs, business-critical templates, and recent tool exports when available.
Confirm whether results may be fetched, rendered, stored, or submitted to external services.
Retest representative URLs after fixes and compare against the original evidence.

Avoid

Do not present estimated metrics as measured results.
Do not apply broad robots.txt or canonical changes without testing affected patterns.
Do not submit URLs or contact external services without explicit approval.