Seo technical audit
Skill architshahdigital/claude-marketing-skills/skills/seo-technical-audit
🧠Original Claude Agent Skills for AI-native digital marketing — GEO/AEO, paid ads, SEO, and content systems. Built by Archit Shah. All rights reserved.
npx -y skills add architshahdigital/claude-marketing-skills --skill seo-technical-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Run a technical SEO audit of a website and return a prioritized fix list — crawlability, indexation, site architecture, Core Web Vitals / page speed, mobile, and structured data. Use when the user wants a site audited, rankings are stalling for non-content reasons, a migration or redesign needs checking, or Core Web Vitals are failing. Produces a scored audit with issues ranked by impact × effort. Triggers on: "technical SEO", "site audit", "Core Web Vitals", "page speed", "crawl issues", "indexing problem", "why isn't my site ranking", "SEO health check".
SKILL.md
3.9 KB, as published. Nobody here has run it
SEO Technical Audit
Great content can't rank on a broken foundation. This skill checks the machine-readable health of a site — can search engines crawl it, index it, and does it load fast enough to keep users — and returns a fix list ordered by what actually moves the needle.
Fallback: Running in Cloud/Web Environments (e.g., Claude.ai, CoWork)
If you are running in a cloud-based or web-based environment (such as Claude.ai web or CoWork) where local file system or repository access is unavailable:
- Ask the user to provide their site URL, sitemap link, or paste Google Search Console (GSC) screenshots, crawl logs, or PageSpeed Insights data.
- Conduct the technical audit, indexation check, and Core Web Vitals analysis manually in-context.
- Output the structured Scorecard and the Prioritized Fix List using the templates below.
Workflow
-
Intake & Data Gathering:
- Request URLs, GSC error lists, or PageSpeed metrics.
- Define the main objective (e.g., debugging indexation drops, fixing Core Web Vitals, migrating domains).
-
Crawl & Indexation Check:
- Audit
robots.txtrules, XML sitemap validation, canonical setups, andnoindexdirectives.
- Audit
-
Site Architecture & Internal Links:
- Evaluate crawl depth (clicks from home page), internal link anchors, and redirect setups (301 vs. chains/loops).
-
Page Speed & Core Web Vitals Audit:
- Evaluate:
- LCP (Largest Contentful Paint): Loading speed of main images/fonts.
- INP (Interaction to Next Paint): Input latency and heavy JS execution.
- CLS (Cumulative Layout Shift): Visual stability of layout.
- Evaluate:
-
Schema & Semantic Markup:
- Verify structured data (LocalBusiness, Article, Product, FAQ) for eligibility in Google Rich Snippets.
Templates & Output Format
Ensure the audit results are clear, structured, and prioritized:
1. Technical SEO Health Scorecard
| Audit Area | Status | Gaps & Issues Detected |
|---|---|---|
| Crawlability & Indexation | [PASS / WARN / FAIL] | E.g., Missing robots sitemap link, canonical loop. |
| Site Architecture | [PASS / WARN / FAIL] | E.g., Orphan pages, deep redirect chains. |
| Core Web Vitals & Speed | [PASS / WARN / FAIL] | E.g., Poor LCP due to uncompressed images. |
| Mobile & Rendering | [PASS / WARN / FAIL] | E.g., Non-responsive tables, small tap targets. |
| Structured Data (Schema) | [PASS / WARN / FAIL] | E.g., Missing required fields in Product schema. |
2. Prioritized Technical Fix List
Rank issues using the impact-effort matrix (High Impact + Low Effort = Priority 1):
| Priority | Issue / Fix Required | Affected Pages | Impact | Effort | Recommendation / Solution |
|---|---|---|---|---|---|
| 1 | E.g., Eliminate 3 redirect loops on homepage. | homepage | HIGH | LOW | Update link destinations to final URLs. |
| 2 | E.g., Add dimensions to hero images (CLS fix). | blog template | MEDIUM | LOW | Set explicit width and height attributes. |
| 3 | E.g., Lazy-load B-roll videos below-the-fold. | landing-page | HIGH | MEDIUM | Implement standard lazy loading/defer scripting. |
[!IMPORTANT] Priority Focus: Highlight the Top 3 High-Impact Fixes in a clear callout box at the top of your response to give the user immediate focus.