agentleFS
NadavShanun-designNadavShanun-design/opengtm/skills/seo-fundamentals/SKILL.md

seo-fundamentals

Skill4 starsChanged 30 days agoMITView on GitHub

Use when improving a site's visibility in classic search engines (Google, Bing) - technical SEO (crawlability, indexing, speed, mobile), on-page (titles, meta, headings, internal links, search-intent match), content (topical authority, E-E-A-T, freshness), and off-page (earned links, brand mentions). The traditional-search companion to generative-engine-optimization; do both together.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use intelligent-routing, nextjs-react-expert and 4 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.
  • SKB3002Skill

    intelligent-routing

    Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

    Also in 5 projects that use this

  • SKB3002Skill

    nextjs-react-expert

    React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

    Also in 3 projects that use this

  • xfstudioSkill

    rust-pro

    Master Rust 1.75+ with modern async patterns, advanced type system

    Also in 5 projects that use this

  • jornalistainclusivoSkill

    design-spec

    How to author a DESIGN.md file — the machine-readable design-token + human-rationale format that must exist before any UI is built. YAML front-matter token schema (colors, typography, spacing, rounded, components), type system, token references, and canonical section order.

    Also in 3 projects that use this

  • zzfancitizenSkill

    verify-changes

    Verify code changes do not break the project by running tests, linter checks, and import validation. Use after making any code changes, editing Python files, modifying imports, updating dependencies, or refactoring.

    Also in 3 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    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:

    No internal linking, so authority never flows to money pages.

    line 83

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

Overview

SEO earns a ranking in organic search results - still a large, intent-rich demand channel even as AI answers grow. It rests on four pillars: can engines crawl and index you (technical), do your pages match what people search (on-page + content), and do others vouch for you (off-page). Much of this work also helps AI answer engines - do SEO and GEO together (see generative-engine-optimization).

Pillar 1 - Technical (can they crawl & index you)

  • Clean robots.txt (don't block what you want indexed), an accurate sitemap.xml, and canonical URLs to avoid duplicate-content splits.
  • Core Web Vitals and page speed; mobile-first (the mobile page is what's indexed); HTTPS everywhere.
  • Server-render or statically generate important content - don't hide it behind JS.
  • Fix crawl errors, broken links, redirect chains, and orphan pages.

Pillar 2 - On-page (does the page match the query)

  • Title tag (unique, front-loads the primary term) and a compelling meta description (drives click-through even if not a direct ranking factor).
  • Exactly one <h1>; logical H2/H3 structure.
  • Match search intent - informational, navigational, commercial, or transactional. A "how to X" query wants a guide, not a product page.
  • Internal links with descriptive anchors to spread authority and help crawling.
  • Descriptive image alt text; structured data (JSON-LD) for rich results.

Pillar 3 - Content (topical authority)

  • Topic clusters: a pillar page plus supporting articles interlinked around one theme - signals depth and authority better than scattered one-offs.
  • E-E-A-T (Experience, Expertise, Authoritativeness, Trust): named expert authors, primary sources, real experience. Critical for YMYL (health/finance/legal).
  • Freshness where the query expects it - update and show real dates (never fake-bump).
  • Genuinely useful, people-first content. Thin or AI-slop pages get filtered.

Pillar 4 - Off-page (who vouches for you)

  • Earn backlinks from relevant, authoritative sites (original data, useful tools, genuinely linkable content) - don't buy link schemes (manual penalties).
  • Unlinked brand mentions and consistent NAP/profile data build entity trust.
  • Digital PR and guest contribution where it's genuinely relevant.

Measurement

  • Google Search Console: impressions, clicks, average position, CTR, index coverage, Core Web Vitals.
  • Track rankings for target clusters and, increasingly, AI Overview presence.
  • Leading = indexation + impressions; lagging = organic traffic → pipeline.

SEO vs GEO (do both)

Big overlap (crawlable, authoritative, well-structured content wins both), but the win condition differs: SEO wants a rank; GEO wants a citation inside an AI answer (non-deterministic, measured as a rate). The access and authority work is shared; see generative-engine-optimization for the answer-engine-specific layer.

Do / Don't

  • Do match content to the searcher's intent and build topic clusters.
  • Do earn links with genuinely linkable assets.
  • Don't block indexing by accident or hide content behind JS.
  • Don't buy links, stuff keywords, or publish thin pages - all get filtered or penalized.

Common mistakes

  • Chasing keywords while ignoring crawl/index health (nothing ranks if nothing's indexed).
  • Content that targets a term but not the intent behind it.
  • No internal linking, so authority never flows to money pages.
  • Buying links or keyword-stuffing (short-term bump, long-term penalty).

Go live with Chronos (optional)

  • geo_analyze_website - audit a site for technical/on-page/content gaps.
  • geo_get_seo_geo_ideas - prioritized SEO + GEO improvement ideas for a connected repo.
  • geo_implement_seo_idea - ship one as a reviewable pull request (never merges to your default branch - you approve).
  • geo_mark_seo_idea - track which ideas are done/dismissed.

Connect in ~30s → CONNECT-CHRONOS.md. Free, no card.

See also: generative-engine-optimization, content-marketing-engine.

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.