Index of every page on this site: llms.txt
All skills
agricidaniel avatar

/seo-technical

@468ed5b
by Agrici Danielagricidaniel/claude-seo31k stars
3,860
Run it yourself

Audit technical SEO across crawlability, indexability, security, URLs, mobile, Core Web Vitals, rendering, structured data, and IndexNow. Use when the user asks for a technical SEO audit or about crawling, indexing, rendering, or site speed. Exclude content strategy and backlinks.

Use this Skill: https://skilld.dev/gh/agricidaniel/claude-seo/seo-technical

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesstack-cve-exposure.md

≈1.3k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Server Stack & CVE Exposure (read-only)

A technical audit should flag when a site runs a server-side stack with a known critical CVE, so the owner can patch it or take it offline. This is a read-only detection check. It never attempts exploitation; detection here means reading normal HTTP responses, not sending attack payloads.

Scope boundary

  • Ask the user whether they own the site or have written authorization to test it before requesting any path beyond the page they asked you to audit.
  • Until ownership is confirmed (for example a competitor audit), use only the passive signals in the normal response for the audited URL. Do not request /wp-login.php, /xmlrpc.php, or any other probe path.
  • Send ordinary requests a normal visitor would. Do not fuzz, brute-force, or send payloads crafted to trigger a vulnerability.
  • Report exposure and the patch path. Fixing is the owner's or host's job.

PHP critical RCE advisory (dated 2026-10-21)

Treat as a point-in-time snapshot and re-check the sources below before acting.

  • CVEs: CVE-2026-109618 (GHSA-w8hw-w9fx-j79w, "RCE via OOM corruption") and CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp, "RCE via stale global state").
  • Severity: both Critical, CVSS v4.0 base score 9.2.
  • Impact: unauthenticated remote code execution as the web worker account; CVE-2026-109619 also covers heap use-after-free and memory disclosure.
  • Who is at risk: every PHP installation serving web requests (PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, LiteSpeed). The PHP project rates the risk highest for mod_php.
  • Fixed in: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
  • PHP 8.1 and older: no upstream release. The PHP security team published minimal source backports for 7.4, 8.0 and 8.1 for people building from source; otherwise the fix comes from a distribution or LTS vendor, or an upgrade.
  • Backports hide the version: Linux distributions and LTS vendors received the patches in advance, so a patched build can still report an older version string in X-Powered-By.
  • Interim mitigations (php.net says these do not make an installation safe): memory_limit=-1 set where applications cannot override it; post_max_size of 8M (no uploads) or 32M (uploads), with upload_max_filesize below it; session.upload_progress.enabled=0; on PHP 8.5, fatal_error_backtraces=0. Restart every worker after changing them.
  • If patching is not possible quickly: the UK NCSC advises to "consider taking the system offline until it can be fully mitigated."
  • Sources:

Detection signals (what to read, not exploit)

Run the bundled fetch against the audited URL and read the response:

"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run fetch_page.py https://example.com --json

Classify the stack from signals already present in a normal response:

Signal Where Reading
X-Powered-By: PHP/<ver> response header PHP in use; compare <ver> to fixed list
Server: value (Apache/LiteSpeed/nginx) response header Host software, not proof of PHP by itself
Set-Cookie: PHPSESSID= response header PHP session in use
Link: <...wp-json/>; rel="https://api.w.org/" response header/HTML WordPress (PHP)
<meta name="generator" content="WordPress ..."> HTML <head> WordPress (PHP)
/wp-login.php, /xmlrpc.php returning a real login/XML page (200) path (owner-confirmed sites only) Live WordPress; a 403/404 alone is not confirmation
_next/static, __NEXT_DATA__, Vercel/Netlify headers HTML/headers Static or Node stack, not PHP

A managed or static host (Vercel, Netlify, Cloudflare Pages, a Next.js app) that shows no PHP signal is not exposed by this advisory. A 403 or 404 on a WordPress path is the host refusing a path that does not exist, not evidence of WordPress.

Reporting

  • Runs PHP, version string below the fixed list: High, "likely exposed, confirm with the host". The version string alone is not proof because of distribution backports. Ask the operator to confirm the build (php -v plus the package changelog, or the host's support).
  • Owner confirms an unpatched build: Critical. Patch to a fixed release or a vendor backport, apply the interim mitigations meanwhile, and consider taking the system offline until it is fixed.
  • Runs PHP, version unknown: Info. Tell the operator how to read the exact version and confirm it is a fixed release or a patched vendor build.
  • Managed/shared hosting: the server-level PHP is the host's responsibility. Advise the operator to confirm with the host that it runs a fixed or patched build, and provide a short message they can send to support.
  • No PHP signal: Pass. State that it is an external read only, which shows exposure, not a proof that no PHP exists anywhere in the operator's estate.

Related

  • Section 3 (Security) in SKILL.md.
  • SECURITY.md and the CLAUDE_SEO_LOCAL_TARGETS allowlist for pre-deployment hosts.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning4d5 checks · Risk SAFE
  • Gen Agent Trust Hub5d

    The skill is a professional technical SEO auditing tool. It uses local Python scripts to audit websites for crawlability, speed, and security. It includes built-in safeguards to treat fetched web content as untrusted data and provides instructions for auditing local or private development environments via user-controlled configuration.

  • Socket4d

    No alerts

  • Snyk5d

    Risk: MEDIUM · 1 issue

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 468ed5b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated last week
user-invocable
true
argument-hint
[url]
metadata
{
  "author": "AgriciDaniel",
  "version": "2.6.2",
  "category": "seo"
}
  • SEO
  • technical-seo
  • crawlability
  • indexability
  • core-web-vitals
  • security-headers
  • structured-data
  • robots-txt
  • mobile-optimization

README badge

README badge for agricidaniel/claude-seo/seo-technical

Audits a website across nine technical SEO categories: crawlability, indexability, security, URL structure, mobile optimization, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol support. Flags issues like robots.txt misconfigurations, missing security headers, non-mobile-friendly layouts, and slow LCP/INP metrics, with optional integration to Google PageSpeed Insights and CrUX APIs for real field data.

Generated from the current SKILL.md.

Does this skill check AI crawler rules in robots.txt?
Yes. The skill audits crawlability including robots.txt validity and flags AI-specific crawlers (GPTBot, ClaudeBot, PerplexityBot, Bytespider, Google-Extended, etc.). It provides guidance on selective AI crawler blocking and distinguishes between crawlers that affect model training vs search indexing.
What are Core Web Vitals and does this skill measure them?
Core Web Vitals are LCP (Largest Contentful Paint, target <2.5s), INP (Interaction to Next Paint, target <200ms), and CLS (Cumulative Layout Shift, target <0.1). The skill audits these using PageSpeed Insights API or CrUX data when available, or flags when data is unavailable (common for low-traffic sites).
Does this cover JavaScript rendering and SPA frameworks?
Yes. The skill detects whether content requires JavaScript to render, identifies client-side vs server-side rendering, flags SPA frameworks (React, Vue, Angular) that may cause indexing issues, and audits whether critical SEO elements (canonical, meta robots, structured data) are in raw HTML vs injected by JavaScript.
Does this skill require API credentials?
No. The skill performs basic audits out of the box. Integration with Google APIs (PageSpeed Insights, CrUX, Search Console) and DataForSEO is optional when credentials are configured.
Does this check for HTTPS and security headers?
Yes. The skill audits HTTPS enforcement, SSL certificate validity, and security headers including CSP, HSTS, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. HSTS preload list inclusion is also checked.

Generated from the current SKILL.md. These answers refresh after source changes.