agentleFS
divyanshu-iitiandivyanshu-iitian/agent-website-design-skills/technical-seo-discovery/SKILL.md

technical-seo-discovery

Skill2 starsChanged 4 months agoMITView on GitHub

Diagnose, implement, and verify technical SEO and public-content discovery for web products, including crawlability, indexability, redirects, canonicals, metadata, structured data, sitemaps, rendering, internal links, quality thresholds, and search-console evidence.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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:

    Add internal links from crawlable hubs.

    line 18
  2. Distinctive:

    Add structured data only when the visible page supports it.

    line 19
  3. Distinctive:

    Verify with raw headers, rendered HTML, robots and sitemap fetches, schema validation, and search-console inspection.

    line 20
  4. Distinctive:

    Do not index expired jobs, empty profiles, private posts, search results, or unlimited filter combinations.

    line 25
  5. Distinctive:

    Read references/indexing-checklist.md for a release or search-console incident.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Discovery

Make valuable public pages discoverable without generating index bloat, duplicate routes, or thin programmatic content.

Workflow

  1. Inventory public page types, canonical hosts, authentication boundaries, rendering modes, and content quality signals.
  2. Trace one URL through DNS, redirects, status, response headers, HTML robots, canonical, rendered content, internal links, and sitemap membership.
  3. Separate crawl, index, canonicalization, rendering, quality, and ranking problems. Do not treat sitemap submission as indexing proof.
  4. Define an indexability policy per page type. Private, empty, duplicate, filtered, and low-quality pages should not enter discovery surfaces.
  5. Make public pages return stable 200 responses with server-rendered primary content, self-canonicals, useful titles and descriptions, and no accidental noindex header.
  6. Build sitemap indexes or bounded sitemaps from canonical, indexable records only. Use stable URLs and meaningful modification timestamps.
  7. Add internal links from crawlable hubs. Keep redirect chains to one hop and use one canonical host consistently.
  8. Add structured data only when the visible page supports it. Never fabricate ratings, jobs, organizations, or profile claims.
  9. Verify with raw headers, rendered HTML, robots and sitemap fetches, schema validation, and search-console inspection. Record recrawl latency as an external dependency.

Programmatic SEO Rules

  • Publish pages because they answer a distinct query, not because a database row exists.
  • Do not index expired jobs, empty profiles, private posts, search results, or unlimited filter combinations.
  • Paginated or faceted directories need bounded crawl paths and canonical policy.
  • A large sitemap with zero indexed pages is a quality or technical signal to investigate, not a reason to create more URLs.
  • Rankings require content usefulness, links, reputation, and time after technical eligibility is fixed.

Delivery Contract

Provide or implement:

  1. URL inventory - page types, canonical policy, and indexability rules.
  2. Diagnosis - status, redirects, headers, robots, rendering, links, and sitemap evidence.
  3. Fixes - routing, metadata, structured data, sitemaps, and quality gates.
  4. Verification - commands or inspected responses for representative URLs.
  5. Monitoring - coverage, crawl errors, indexed quality pages, impressions, and regressions.
  6. Expectations - what is technically fixed versus what still depends on recrawl and ranking signals.

Reference

Read references/indexing-checklist.md for a release or search-console incident.

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.