agentleFS
Sign inStart free
witi-projectswiti-projects/Skills/seo-auditing/SKILL.md

seo-auditing

Skill2 starsChanged 7 months agoMITView on GitHub

Audit technical SEO — meta tags, structured data, Open Graph, sitemaps, robots.txt, performance, and accessibility signals. Use when the user says "/seo-auditing", "seo auditing", or asks about seo auditing.

3 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 9 are common, 0 are distinctive, and 1 is very specific to this project.

  • 9

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Check and fix technical SEO issues in a web project.

    line 9
  2. Common:

    Every page must have:

    line 15
  3. Common:

    Test with https://developers.facebook.com/tools/debug/ and https://cards-dev.twitter.com/validator

    line 44
  4. Common:

    Add schema markup for rich search results:

    line 48
  5. Common:

    Test with: https://search.google.com/test/rich-results

    line 65
  6. Common:

    Not block CSS/JS files (search engines need them to render)

    line 87
  7. Common:

    Not block pages you want indexed

    line 88
  8. Common:

    Avoid layout shifts from dynamic content

    line 101
  9. Very specific:

    Use next/image or equivalent for automatic optimization

    line 102
  10. Common:

    Run Lighthouse in Chrome DevTools → check SEO score

    line 137

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SEO Auditing

Check and fix technical SEO issues in a web project.

Audit Checklist

1. Meta Tags

Every page must have:

<head>
  <title>Page Title — Site Name</title>
  <meta name="description" content="155 chars max, compelling summary" />
  <link rel="canonical" href="https://example.com/page" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
</head>

Check for:

  • Unique <title> per page (50-60 chars)
  • Unique <meta description> per page (120-155 chars)
  • Canonical URL set (avoids duplicate content)
  • No noindex on pages that should be indexed

2. Open Graph & Social

<meta property="og:title" content="Page Title" />
<meta property="og:description" content="Description for social sharing" />
<meta property="og:image" content="https://example.com/og-image.png" />
<meta property="og:url" content="https://example.com/page" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary_large_image" />

3. Structured Data (JSON-LD)

Add schema markup for rich search results:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Title",
  "author": { "@type": "Person", "name": "Author Name" },
  "datePublished": "2026-04-10",
  "image": "https://example.com/image.jpg"
}
</script>

Common types: Article, Product, FAQPage, Organization, BreadcrumbList

Test with: https://search.google.com/test/rich-results

4. Sitemap

/sitemap.xml should:

  • List all indexable pages
  • Include <lastmod> dates
  • Exclude pages with noindex
  • Be under 50MB / 50,000 URLs per file
  • Be referenced in robots.txt

5. Robots.txt

/robots.txt should:

User-agent: *
Allow: /
Disallow: /api/
Disallow: /admin/
Sitemap: https://example.com/sitemap.xml
  • Not block CSS/JS files (search engines need them to render)
  • Not block pages you want indexed

6. Performance (Core Web Vitals)

MetricGoodNeeds Work
LCP (Largest Contentful Paint)< 2.5s> 4.0s
INP (Interaction to Next Paint)< 200ms> 500ms
CLS (Cumulative Layout Shift)< 0.1> 0.25

Key fixes:

  • Compress and lazy-load images
  • Preload critical fonts and CSS
  • Avoid layout shifts from dynamic content
  • Use next/image or equivalent for automatic optimization

7. Crawlability

  • All important pages are reachable from internal links
  • No orphan pages (pages with zero internal links)
  • No redirect chains (A→B→C should be A→C)
  • 404 pages return proper HTTP 404 status
  • No broken internal links

8. Accessibility (SEO Signals)

  • All images have alt text
  • Heading hierarchy is correct (one h1, then h2, h3 etc.)
  • Links have descriptive text (not "click here")
  • Language attribute set: <html lang="en">

Quick Automated Check

# Check robots.txt
curl -s https://example.com/robots.txt

# Check sitemap
curl -s https://example.com/sitemap.xml | head -20

# Check meta tags
curl -s https://example.com | grep -E '<title>|<meta name="description"|<link rel="canonical"'

# Check HTTP status codes
curl -o /dev/null -s -w "%{http_code}" https://example.com/page

Tips

  • Run Lighthouse in Chrome DevTools → check SEO score
  • Google Search Console is the source of truth for indexing issues
  • Mobile-friendliness is a ranking factor — test on mobile viewports
  • Page speed directly affects rankings — optimize Core Web Vitals

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.

Check your setup, free