agentleFS
TraX22TraX22/HydraOps-Skills/seo/SKILL.md

seo

Skill1 starsChanged 38 days agoApache-2.0View on GitHub

On-page SEO audit and optimization for a live URL or a draft - search intent, title and meta description, headings, keyword research without paid tools, internal links, structured data, Core Web Vitals notes and content quality - ending in a prioritized fix list. Use when the user asks to audit, optimize or "improve the SEO" of a page, post or landing page, or wants keywords or titles for search.

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

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 145 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask once, if unknown and it matters: target country/language, primary audience, and the one action the page should drive.

    line 21
  2. Distinctive:

    Ask the questions a quality rater would:

    line 62
  3. Distinctive:

    Add structured data for content not visible on the page.

    line 122

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

Output is always a prioritized fix list with concrete rewrites, not a lecture on SEO. You cannot see the site's Search Console, analytics or rendering engine; say so and focus on what the page itself and the live search results show.

Inputs

  • A URL: open it with fetch_url. Also try <origin>/robots.txt and <origin>/sitemap.xml if indexing is in question (only report them if they actually loaded).
  • A draft: work from the text; ask for the target URL/slug if links or canonicals matter.
  • Ask once, if unknown and it matters: target country/language, primary audience, and the one action the page should drive. Otherwise state assumptions.

Workflow

1. Determine the target query and intent

  • Identify 1 primary query and 3-8 secondary/related queries the page should rank for.
  • Classify intent: informational (learn), commercial (compare), transactional (buy/sign up), navigational (find a brand).
  • Check the live results: web_search the primary query (in the target language and, if possible, region). Note what ranks: format (guide, list, tool, product page, video), depth, freshness, and who ranks (brands, forums, publishers). The page must match the dominant format, or the intent is wrong and no tweak will fix it.

Keyword research without paid tools: see references/keyword-research.md.

2. Audit the page

Work through references/audit-checklist.md. The essentials:

ElementWhat good looks like
Title tagUnique, primary query near the front, clear benefit, roughly 50-60 characters so it is not truncated; brand at the end if space
Meta description1-2 sentences, roughly 140-160 characters, matches intent, gives a reason to click; not a ranking factor but affects clicks
H1One, says what the page is, close to the title (not necessarily identical)
Headings H2/H3Logical outline; answer the sub-questions searchers have; no keyword stuffing
OpeningAnswers the query or states the value in the first 2-3 sentences
BodyCovers the topic better than what ranks: specifics, examples, data, first-hand experience
URL slugShort, readable, lowercase, hyphens; do not change existing URLs without a 301 redirect
ImagesDescriptive file names and alt text; compressed; width/height set
Internal linksLinks in from related pages and out to relevant pages with descriptive anchor text
External linksTo credible sources where claims need support
Structured dataJSON-LD matching visible content (Article, Product, FAQ where eligible, HowTo, Organization, BreadcrumbList, LocalBusiness...)
IndexingNot noindex by mistake; canonical points to itself (or to the right master); in the sitemap
Mobile & speedSee Core Web Vitals notes below

3. Content quality

Ask the questions a quality rater would:

  • Does it show first-hand experience or expertise (who wrote it, why trust them)?
  • Is there something here that the top results lack (data, examples, a tool, a clearer answer, a more recent update)?
  • Is it written for people first? Remove filler intros, repeated keyword variants and generic paragraphs.
  • Is the date shown and honest? Updating a date without updating content is a bad signal.
  • Would a reader leave satisfied, or go back to search?

4. Core Web Vitals notes

You usually cannot measure from here. Give notes, not scores:

  • Thresholds for "good" (as of September 2026, verify with web_search if it matters): LCP <= 2.5 s, INP <= 200 ms, CLS <= 0.1, at the 75th percentile of real users.
  • Point the user to PageSpeed Insights or Search Console for field data.
  • From the HTML you can still flag likely issues: huge hero images without dimensions, render-blocking scripts in <head>, many third-party tags, web fonts without font-display, lazy-loading the LCP image, layout shifts from late-injected banners.

5. Prioritize and write the fix list

Rank each fix by impact x effort:

  • P1 - blocks ranking or clicks: wrong intent, noindex/canonical errors, missing or duplicate title/H1, thin content vs competitors, broken key links.
  • P2 - meaningful gains: title/meta rewrite, missing sections searchers need, internal links, structured data, image alt text, obvious speed issues.
  • P3 - polish: slug tweaks (only on new pages), minor heading wording, extra FAQ.

Output format

**Target:** <primary query> (<intent>, <country/language>)
**What ranks now:** <1-2 lines on the dominant format and competitors>

### Fixes
| # | Priority | Issue | Fix | Effort |
|---|---|---|---|---|
| 1 | P1 | ... | ... | S/M/L |

### Rewrites
- Title: "<new title>" (<n> chars)
- Meta description: "<new description>" (<n> chars)
- H1: "<new H1>"
- Suggested outline: H2 ... / H2 ...

### Structured data (if relevant)
<JSON-LD snippet matching visible content>

### Not checked
<what needs Search Console, PageSpeed or a crawl>

Do not

  • Promise rankings or traffic numbers.
  • Recommend keyword stuffing, hidden text, doorway pages, buying links, or mass AI-generated pages; these violate search engine spam policies.
  • Add structured data for content not visible on the page.
  • Recommend changing ranking URLs without redirects.
  • Invent search volumes. Without a data tool, describe demand qualitatively and say how you judged it.

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.