agentleFS
Sign inStart free
NikoxkxNikoxkx/Agent-Skills/skills/web-development/seo-optimizer/SKILL.md

seo-optimizer

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

Implements technical SEO for web pages: meta tags, structured data, sitemap, robots.txt, and Core Web Vitals. Use when improving search ranking or auditing a site's SEO.

19 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Dynamic pages: Always use generateMetadata and fetch data server-side.

    line 74
  2. Distinctive:

    JavaScript-heavy sites: Ensure critical content is in HTML (SSR or SSG).

    line 77
  3. Distinctive:

    Run Google Rich Results Test on structured data.

    line 82
  4. Distinctive:

    Run Lighthouse (SEO + Performance categories) — target 90+.

    line 84
  5. Very specific:

    Use web-vitals library or CrUX dashboard to measure real-user LCP/CLS/INP.

    line 85

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

Overview

Implements comprehensive technical SEO: essential meta tags (title, description, canonical), Open Graph + Twitter Cards, JSON-LD structured data for rich results (Article, Product, BreadcrumbList, FAQ, etc.), sitemap.xml generation, robots.txt rules, and a prioritized Core Web Vitals (LCP, CLS, INP) optimization checklist with concrete code changes.

When to Use This Skill

  • Launching a new site or page that needs to rank in search.
  • Auditing or improving an existing site's SEO.
  • The user mentions "SEO", "meta tags", "sitemap", "structured data", "rich results", or "Core Web Vitals".

Prerequisites

  • Access to the <head> or Next.js metadata API / generateMetadata.
  • Ability to generate or edit sitemap.xml and robots.txt.
  • Google Search Console or similar for verification (recommended).
  • Performance measurement tools (Lighthouse, web-vitals).

Steps

  1. Base meta tags (every page):
    • <title>, <meta name="description">, canonical, viewport, charset.
    • Robots meta (index, follow).
  2. Social cards:
    • Open Graph (og:title, og:description, og:image, og:type, og:url).
    • Twitter Card (twitter:card, twitter:title, etc.).
    • Image size recommendations (1200x630).
  3. Structured data (JSON-LD):
    • Choose the right schema type for the page content.
    • Provide complete, valid examples for Article, Product, Breadcrumb, FAQPage, HowTo, etc.
    • Use <script type="application/ld+json">.
  4. Next.js Metadata API (App Router):
    • Static and dynamic metadata export.
    • generateMetadata function for dynamic pages.
    • OpenGraph and Twitter objects.
  5. Sitemap & robots:
    • Generate app/sitemap.ts that returns XML.
    • app/robots.ts.
    • Include all important URLs, lastmod, priority, changefreq.
  6. Core Web Vitals optimization:
    • LCP: image optimization (next/image), preload critical resources, font display swap.
    • CLS: reserve space for images/ads, avoid inserting content above the fold.
    • INP (Interaction to Next Paint): defer non-critical JS, use loading="lazy", efficient event handlers.
    • Provide a checklist with exact code diffs.
  7. Output:
    • Complete <head> example or Next.js metadata object.
    • JSON-LD snippets for common page types.
    • sitemap.ts and robots.ts examples.
    • CWV fix list tailored to the page.

Examples

Full Next.js generateMetadata example for a blog post with Article + Breadcrumb structured data, sitemap code, and a CWV improvement patch are included.

Edge Cases & Error Handling

  • Dynamic pages: Always use generateMetadata and fetch data server-side.
  • Duplicate content: Strong canonical strategy.
  • Images for social: Provide multiple sizes or use a service like Vercel OG.
  • JavaScript-heavy sites: Ensure critical content is in HTML (SSR or SSG).

Verification

  1. View source — all meta tags present and correct.
  2. Run Google Rich Results Test on structured data.
  3. Submit sitemap in Google Search Console.
  4. Run Lighthouse (SEO + Performance categories) — target 90+.
  5. Use web-vitals library or CrUX dashboard to measure real-user LCP/CLS/INP.
  6. Success: Pages are indexable, rich results appear in search, Core Web Vitals pass.

References

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