agentleFS
stoffl6781stoffl6781/claude-skill/skills/seo/SKILL.md

seo

Skill1 starsChanged 7 months agoMITView on GitHub

Klassisches SEO für Laravel-Projekte: robots.txt, sitemap.xml, Meta-Tags, Open Graph, Structured Data (JSON-LD), hreflang, Focus-Keywords, Redirects. Nutze bei: "SEO", "Suchmaschinenoptimierung", "robots.txt", "sitemap", "Open Graph", "OG Tags", "Meta Tags", "Structured Data", "JSON-LD", "Schema.org", "hreflang", "Focus Keyword", "SEO Audit", "SEO Check", "SERP", "Google Search Console", "ranking verbessern", "Canonical URL", "Rich Snippets", "Meta Description", "SEO generieren". Für KI-Auffindbarkeit (ai.txt, llms.txt) → GEO Skill.

156 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, seo-maps 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.
  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 5 projects that use this

  • timruebenachSkill

    seo-maps

    Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".

    Also in 17 projects that use this

  • megastepSkill

    seo-images

    Image optimization analysis for SEO and performance. Checks alt text, file sizes, formats, responsive images, lazy loading, and CLS prevention. Use when user says "image optimization", "alt text", "image SEO", "image size", or "image audit".

    Also in 24 projects that use this

  • timruebenachSkill

    seo-image-gen

    AI image generation for SEO assets: OG/social preview images, blog hero images, schema images, product photography, infographics. Powered by Gemini via nanobanana-mcp. Requires banana extension installed. Use when user says \"generate image\", \"OG image\", \"social preview\", \"hero image\", \"blog image\", \"product photo\", \"infographic\", \"seo image\", \"create visual\", \"image-gen\", \"favicon\", \"schema image\", \"pinterest pin\", \"generate visual\", \"banner\", or \"thumbnail\".

    Also in 15 projects that use this

  • megastepSkill

    seo-sitemap

    Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".

    Also in 26 projects that use this

  • renepfSkill

    orch-pipeline

    Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.

    Also in 4 projects that use this

  • +3 more from timruebenach
  • +1 more from megastep

The file

Files
SKILL.md

SEO – Search Engine Optimization

Für Google, Bing, DuckDuckGo, Yandex, Ecosia. Für KI-Auffindbarkeit → GEO Skill. Wenn User "SEO" sagt, prüfe ob GEO auch relevant ist.

Workflow

SchrittPrüfen
1. Analyserobots.txt, sitemap, Meta-Tags, OG, JSON-LD, SEO-Felder auf Models
2. Discoveryrobots.txt dynamisch via Route, sitemap.xml dynamisch + gecacht
3. Meta-Tagstitle, description, canonical, hreflang, geo-targeting, OG, Twitter Cards
4. Structured DataJSON-LD pro Seitentyp (Organization, Article, Product, FAQ, Breadcrumb)
5. ContentSEO-Felder auf Models, Focus-Keyword-Analyse, KI-Generierung
6. Redirects301 für alte URLs, nie 302 für permanente Weiterleitungen
7. ValidierungRich Results Test, Schema.org Validator, OG Debugger

Core Web Vitals sind Ranking-Faktor. Für Performance-Optimierung → laravel-perf Skill.

robots.txt (Dynamisch)

Route: GET /robots.txt → gecacht 1h
- User-agent: * / Allow: / / Disallow: /admin/, /api/, /livewire/
- Sitemap: {APP_URL}/sitemap.xml
- APP_ENV=local → Disallow: /
- NIEMALS statische Datei in /public/
- Für KI-Crawler → GEO Skill

Sitemap (Dynamisch)

Route: GET /sitemap.xml (Index) + /sitemap-{locale}.xml (pro Sprache)
Cache: 1h, invalidieren bei Content-Änderung
- Nur publizierte Inhalte, <lastmod> aus updated_at
- hreflang-Annotations in Sitemap (xhtml:link)
- Max 50.000 URLs pro Sitemap

Priorities: Homepage 1.0, Archive 0.8-0.9, Details 0.6-0.8, Statisch 0.3-0.5

Meta-Tags (im <head>)

<title>{meta_title} - {site_name}</title>          <!-- max 60 Zeichen -->
<meta name="description" content="{...}">           <!-- max 155 Zeichen -->
<link rel="canonical" href="{canonical_url}">
<link rel="alternate" hreflang="de" href="{de_url}">
<link rel="alternate" hreflang="en" href="{en_url}">
<link rel="alternate" hreflang="x-default" href="{default_url}">
<meta name="geo.region" content="AT">
<meta name="google-site-verification" content="{aus Settings}">

Open Graph + Twitter

<meta property="og:type" content="{website|article|product}">
<meta property="og:title" content="{title}">
<meta property="og:description" content="{description}">
<meta property="og:image" content="{1200x630, lokal, max 300KB}">
<meta property="og:image:alt" content="{alt}">
<meta property="og:locale" content="{de_AT|en_US}">
<meta name="twitter:card" content="summary_large_image">

og:type pro Seite: Homepage→website, Blog→article, Produkt→product

Structured Data (JSON-LD)

Nur die wichtigsten – projekt-spezifische (LocalBusiness, TouristAttraction, Event etc.) je nach Bedarf ergänzen:

  • Homepage: Organization (name, url, logo, sameAs)
  • Blog: Article (headline, datePublished, author, image)
  • Alle Seiten: BreadcrumbList
  • FAQ-Sektionen: FAQPage
  • Produkte: Product (name, offers, price)

Validieren: Google Rich Results Test + Schema.org Validator

SEO-Felder pro Model

meta_title (translatable, max 60 Zeichen)
meta_description (translatable, max 155 Zeichen)
focus_keyword (1-3 Wörter)

Focus-Keyword Score (0-100): Keyword in Titel (15), Description (15), URL (10), Intro (10), Content (10), Länge ≥600 (10), H2-H4 (10), Titel ≤60 (10), Description ≤155 (10)

KI-Generierung: "SEO generieren" Button → Queue-Job → füllt fehlende Felder. Batch über SEO-Dashboard.

Redirects

// 301 für permanente Weiterleitungen (alte URLs, Slug-Änderungen)
Route::redirect('/alter-pfad', '/neuer-pfad', 301);
// Redirect-Tabelle im Admin für dynamische Verwaltung

Audit-Checkliste

DISCOVERY: robots.txt dynamisch, sitemap mit hreflang, nur publizierte Inhalte
META: title+description auf jeder Seite, canonical, hreflang DE+EN+x-default
OG: og:type/title/description/image auf jeder Seite, Default-Bild vorhanden
JSON-LD: Organization+BreadcrumbList minimum, validiert
CONTENT: SEO-Felder auf allen Models, Alt-Texte, Heading-Hierarchie korrekt
REDIRECTS: Alte URLs → 301, keine Ketten, keine Schleifen
PERFORMANCE: Discovery Files gecacht, keine N+1 in Sitemap, <500ms Response

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.