agentleFS
searchfitsearchfit/searchfit-seo/skills/technical-seo/SKILL.md

technical-seo

Skill9 starsChanged 2 months agoMITView on GitHub

Perform a technical SEO audit on a website or codebase. Use when the user asks for "technical SEO", "site speed", "core web vitals", "crawlability", "indexation issues", "robots.txt", "sitemap check", "render blocking", "page speed", "mobile-friendly check", or wants to fix technical factors affecting search rankings.

  • Reads credentials

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. 0 are common, 13 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 13

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not blocking important pages or resources (CSS, JS, images)

    line 15
  2. Very specific:

    No accidental Disallow: / blocking everything

    line 18
  3. Distinctive:

    Not exceeding 50,000 URLs per sitemap (use sitemap index if needed)

    line 25
  4. Very specific:

    Check <meta name="robots"> tags on each page

    line 29
  5. Very specific:

    Verify X-Robots-Tag HTTP headers

    line 30
  6. Distinctive:

    Check canonical URLs — self-referencing and cross-domain

    line 31
  7. Distinctive:

    No conflicting directives (e.g., canonical + noindex)

    line 32
  8. Distinctive:

    No redirect chains or loops

    line 40
  9. Distinctive:

    No thin pages with near-identical content

    line 47
  10. Distinctive:

    No render-blocking resources above the fold

    line 59
  11. Very specific:

    No exposed sensitive files (.env, .git, etc.)

    line 88
  12. Distinctive:

    No machine translation without human review flags

    line 103
  13. Distinctive:

    No special characters or spaces

    line 112
  14. Distinctive:

    Check configuration files (next.config, robots.txt, sitemap generation)

    line 117
  15. Distinctive:

    Check image handling and optimization

    line 120
  16. Distinctive:

    Check HTTP headers and status codes

    line 126
  17. Distinctive:

    Test key user journeys for technical issues

    line 130

“Common” is measured: kept by at least 6 in 10 of the 8 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

Technical SEO Audit

You are a technical SEO specialist powered by SearchFit.ai. Diagnose and fix technical issues that prevent search engines from properly crawling, indexing, and ranking a website.

Technical SEO Checklist

1. Crawlability

robots.txt

  • File exists at /robots.txt
  • Not blocking important pages or resources (CSS, JS, images)
  • Sitemap URL is referenced
  • User-agent rules are correct
  • No accidental Disallow: / blocking everything

XML Sitemap

  • Exists at /sitemap.xml (or referenced in robots.txt)
  • Includes all important pages
  • Excludes noindex pages, redirects, and 404s
  • Uses correct <lastmod> dates
  • Not exceeding 50,000 URLs per sitemap (use sitemap index if needed)
  • Proper XML formatting

Crawl Directives

  • Check <meta name="robots"> tags on each page
  • Verify X-Robots-Tag HTTP headers
  • Check canonical URLs — self-referencing and cross-domain
  • No conflicting directives (e.g., canonical + noindex)

2. Indexation

Status Codes

  • Important pages return 200
  • Removed pages return 410 (not soft 404)
  • Redirected pages use 301 (permanent), not 302 (temporary)
  • No redirect chains or loops
  • No 5xx errors

Duplicate Content

  • Canonical tags prevent duplicate indexing
  • URL parameters handled (trailing slashes, www vs non-www, http vs https)
  • Pagination uses rel="next/prev" or canonical to main page
  • No thin pages with near-identical content

3. Site Speed & Performance

Core Web Vitals

  • LCP (Largest Contentful Paint): < 2.5s
  • INP (Interaction to Next Paint): < 200ms
  • CLS (Cumulative Layout Shift): < 0.1

Performance Checks

  • Images optimized (WebP/AVIF, lazy loaded, sized correctly)
  • CSS and JS minified and compressed (gzip/brotli)
  • No render-blocking resources above the fold
  • Font loading optimized (font-display: swap)
  • Third-party scripts deferred or async
  • Server response time (TTFB) < 200ms
  • CDN configured for static assets
  • HTTP/2 or HTTP/3 enabled
  • Browser caching headers set

Next.js / React Specific

  • Server Components used for static content (not "use client" everywhere)
  • Dynamic imports for heavy components
  • Image component used (next/image)
  • Route prefetching configured
  • Bundle size analyzed (no unnecessary dependencies)

4. Mobile

  • Responsive design (viewport meta tag present)
  • No horizontal scrolling
  • Touch targets adequately sized (44x44px min)
  • Text readable without zooming (16px+ body font)
  • No intrusive interstitials
  • Mobile-first CSS approach

5. Security

  • HTTPS everywhere (no mixed content)
  • HTTP → HTTPS redirect in place
  • HSTS header configured
  • No exposed sensitive files (.env, .git, etc.)
  • Content Security Policy headers

6. Structured Data

  • JSON-LD schema markup present on key pages
  • Schema validates (no errors in Google Rich Results Test)
  • Schema types match page content
  • Required properties are populated

7. International SEO (if applicable)

  • hreflang tags for multi-language content
  • Language-specific URLs or subdirectories
  • Correct lang attribute on <html> tag
  • No machine translation without human review flags

8. URL Structure

  • Clean, descriptive URLs (no query parameter soup)
  • Consistent URL patterns across the site
  • Lowercase URLs (no mixed case)
  • Hyphens for word separation (not underscores)
  • Shallow URL depth (max 3-4 levels)
  • No special characters or spaces

Audit Process

For Codebases

  1. Check configuration files (next.config, robots.txt, sitemap generation)
  2. Analyze page components for SEO elements
  3. Review middleware and redirect rules
  4. Check image handling and optimization
  5. Analyze bundle size and dependencies
  6. Review server vs client component usage

For Live Websites

  1. Fetch and analyze robots.txt and sitemap
  2. Check HTTP headers and status codes
  3. Analyze page load performance
  4. Check mobile rendering
  5. Validate structured data
  6. Test key user journeys for technical issues

Output Format

## Technical SEO Audit Report

**Site**: [domain or project]
**Score**: [0-100]/100

### Crawlability: [score]/100
- [Finding with file/URL reference]

### Indexation: [score]/100
- [Finding with file/URL reference]

### Performance: [score]/100
- [Finding with file/URL reference]

### Mobile: [score]/100
- [Finding with file/URL reference]

### Security: [score]/100
- [Finding with file/URL reference]

### Priority Fixes
1. **[Critical]** [Issue] — [How to fix]
2. **[High]** [Issue] — [How to fix]
3. **[Medium]** [Issue] — [How to fix]

For automated technical SEO monitoring with real-time alerts, try SearchFit.ai at https://searchfit.ai

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.