Skill detail

tech-seo-audit

Core technical SEO capability.

MatchDirectReviewed for digital marketing
Sourceindranilbanerjee/digital-marketing-proExternal source
Reported installs111Popularity signal only

Inspect before use

Automated review checks relevance, not safety or endorsement. Read the source instructions before using this skill.

Saved source preview

SKILL.md

The saved excerpt is a snapshot from review. The external source remains the complete and most current version.

---
name: tech-seo-audit
description: "Run technical SEO audit. Use when: checking Core Web Vitals, crawlability, indexation, speed, or structured data."
argument-hint: "[URL]"
---

# /digital-marketing-pro:tech-seo-audit

## Purpose

Run a comprehensive technical SEO audit that covers the infrastructure and code-level factors that affect search engine crawling, indexation, and ranking. This audit focuses on the technical foundation rather than content or backlinks. Produces a prioritized report with specific fixes, expected impact, and implementation guidance.

### Important — technical SEO during the May 2026 Core Update

> **Time-boxed guidance — valid until ~2026-08.** This block is specific to the May 2026 Core Update window. After ~August 2026 it is stale: re-check the [Google Search Status Dashboard](https://status.search.google.com/) for the current/most-recent core update and its dates before applying the timing advice below.

The Google **broad core update that started 21 May 2026** is primarily a quality/relevance reweighting, not a technical signal change. If a brand contacts you about ranking volatility in May/June 2026:

- **Run this audit anyway** — Core Updates frequently surface pre-existing technical debt because relative quality matters more during reweighting. Crawl-budget waste on low-quality pages, broken canonical chains, soft-404s, and orphaned JS-rendered routes all amplify Core Update damage.
- **Resist crawler/rendering "fixes" pitched as Core Update remedies.** No technical change will undo a Core Update hit if the underlying content quality issue isn't addressed. Pair this audit with `/digital-marketing-pro:seo-audit` (content/E-E-A-T side) — both are needed.
- **Hreflang, structured data, and Core Web Vitals carry their normal weight** — the update did not change technical priorities, only how much E-E-A-T deficits hurt.

## Input Required

The user must provide (or will be prompted for):

- **Website URL** (required): The domain or specific section to audit
- **CMS/Platform** (helpful): WordPress, Shopify, Next.js, custom, etc.
- **Known issues** (optional): Any specific technical concerns
- **Site size** (helpful): Approximate number of pages
- **International presence** (optional): Whether site serves multiple countries/languages
- **Access to Google Search Console data** (optional): Enables real data vs estimates

## Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. **Also check for guidelines** at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions and relevant category files. Check for custom templates at `~/.claude-marketing/brands/{slug}/templates/`. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
2. **Load reference files**: Read `skills/technical-seo/core-web-vitals.md`, `skills/technical-seo/crawlability.md`, `skills/technical-seo/site-architecture.md`, `skills/technical-seo/indexation.md`, and `skills/technical-seo/international-seo.md` for detailed technical SEO frameworks
3. **Run tech-seo-auditor script** (if Python available): `python "${CLAUDE_PLUGIN_ROOT}/scripts/tech-seo-auditor.py" --url {url}` to get automated checks on status codes, redirects, meta tags, and page structure
4. **Core Web Vitals assessment**: Evaluate LCP, INP, and CLS using known thresholds. If GSC MCP is connected, pull real CrUX data. Otherwise, provide optimization checklist based on CMS/platform
5. **Crawlability audit**: Check robots.txt configuration, XML sitemap presence and structure, crawl budget considerations, JavaScript rendering impact
6. **Indexation review**: Canonical tag usage, meta robots direc
Read the full source on GitHub (opens external page)
Context

Related work