agentleFS
WST2002WST2002/claude-code-skills/skills/seo-audit/SKILL.md

seo-audit

Skill4 starsChanged 27 days agoMITView on GitHub

Use when a site does not rank or show up on Google, asked for an SEO audit or technical SEO check, adding meta tags, sitemap, robots.txt, structured data or Open Graph, or preparing a new website or Next.js/React/static site for search engines.

185 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use openseo-review-web-content, openseo-release-notes and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JwuthriSkill

    openseo-review-web-content

    Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.

    Also in 5 projects that use this

  • JwuthriSkill

    openseo-release-notes

    Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

    Also in 6 projects that use this

  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 12 projects that use this

  • +4 more from nicepkg
  • +2 more from Jwuthri

The file

Files
SKILL.md

SEO Audit

Overview

Make every important page crawlable, indexable, understandable and fast. Check the site the way a search engine sees it — the HTML it receives — and fix issues in the code that generates it.

Method

  1. List the important pages (home, product, category, articles) and the main search intent of each.
  2. See what search engines see: curl -sL <url> (or the build output for static sites). Content rendered only by client-side JavaScript may be missed or delayed.
  3. Run the checklist below per page template, not per page.
  4. Check site-wide files: robots.txt, sitemap.xml, redirects, canonical domain (www vs non-www, http to https), 404 handling.
  5. Report with the contract below, highest impact first.

Checklist

AreaCheck
IndexingPage returns 200; no noindex by accident; not blocked in robots.txt; listed in sitemap.xml
CanonicalOne <link rel="canonical"> with the absolute preferred URL; duplicates (params, trailing slash) point to it
TitleUnique per page, 50-60 characters, main keyword first, brand last
Meta descriptionUnique, 140-160 characters, describes the page and invites the click
HeadingsExactly one <h1> with the main topic; logical h2/h3 order
Content in HTMLMain text present in server-rendered HTML (SSR/SSG), not only after client fetch
LinksDescriptive anchor text, crawlable <a href> (not onclick), no broken internal links
ImagesMeaningful alt, compressed, explicit dimensions
Structured dataJSON-LD matching the page (Organization, Person, Product, Article, BreadcrumbList, FAQPage); valid in Rich Results Test
Socialog:title, og:description, og:image (1200×630), twitter:card
Mobile and speedViewport meta; Core Web Vitals pass (see web-performance-audit)
Internationalhreflang and lang attribute if multiple languages
URLsShort, lowercase, hyphenated, stable; 301 redirects for changed URLs

Framework notes: Next.js App Router — metadata / generateMetadata, app/sitemap.ts, app/robots.ts. React SPA — prerender or move to SSR/SSG for pages that must rank.

Output contract

### [High | Medium | Low] Title
- Pages: <URL or template>
- Problem: what search engines see or miss
- Fix: exact tag, file and line, or config

Then: Search Console steps if the site is not verified (verify, submit sitemap, request indexing), and Already good.

Common mistakes

  • Auditing the browser view instead of the HTML returned by the server.
  • Same title and description on every page.
  • Canonical tags pointing to the wrong domain or to a localhost URL.
  • Sitemap listing redirected or noindex pages.
  • Keyword stuffing instead of writing for the search intent.

Made by Wageesha Tripathi · LinkedIn · Email · More skills

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.