agentleFS
oegeyilmaz9oegeyilmaz9/seo-aeo-geo-ultimate/skills/seo-page/SKILL.md

seo-page

Skill6 starsChanged 3 months agoApache-2.0View on GitHub

Use when one URL needs a bounded mixed SEO review across reader task, content, metadata, links, technical delivery, accessibility, and structured data; produce an evidence map and route each fix to its real owner instead of a page score.

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-sxo, seo-maps and 8 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.
  • timruebenachSkill

    seo-sxo

    Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".

    Also in 20 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

  • indranilbanerjeeSkill

    seo-drift

    Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"

    Also in 22 projects that use this

  • mangollcSkill

    seo-backlinks

    Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.

    Also in 16 projects that use this

  • +6 more from timruebenach

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 5

    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:

    Read markdown-delivery-contract.md for every task.

    line 10
  2. Very specific:

    Read references/page-review-protocol.md before a formal review.

    line 19
  3. Distinctive:

    Read search-result-presentation.md when the page is expected to rank, improve CTR, or ship a complete search-result appearance.

    line 20
  4. Distinctive:

    Do not infer indexation, rankings, citations, or traffic from a page capture.

    line 37
  5. Distinctive:

    Do not change a page, deploy markup, submit URLs, or claim approval.

    line 38
  6. Distinctive:

    No overall page score. Preserve conflicting evidence instead of averaging it.

    line 39
  7. Distinctive:

    Treat content intent, technical eligibility, measurement, and platform-specific AI visibility as separate questions.

    line 40

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

One-page SEO Review

Markdown delivery contract

Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats.

Lane outputs: page-review.md; query-answer-map.md (combine small related steps with stable section links). Review the canonical HTML page and its substantive Markdown representation as one page owner. Preserve title/meta/H1 and user experience work, query intent, direct answers, entity facts, locale and source consistency.

Purpose

Assess a single page in its actual context and turn confirmed observations into specialist-owned next steps. This is a coordination/audit skill, not a generic rewrite, site crawl, implementation tool, or universal score.

Read references/page-review-protocol.md before a formal review. Read search-result-presentation.md when the page is expected to rank, improve CTR, or ship a complete search-result appearance.

Input gate

Collect the canonical/requested URL, page role, reader task, locale/device, raw and rendered capture where possible, key headers, current metadata/structured data, internal destinations, and authorized performance/indexing evidence. If the page or context cannot be accessed, explain the limitation and list safe evidence to collect.

Workflow

  1. Declare the page contract. What audience, task, site role, locale, intended query family, and canonical/indexability state does this URL serve?
  2. Inspect the rendered experience and delivery. Separate visible content/links/media from raw response, directives, canonicalization, rendering, and structured data. Keep observations tied to a capture and time.
  3. Map observations by lane. Route content usefulness and drafts to seo-content; delivery/crawling/rendering to seo-technical; structured data to seo-schema; media to seo-images; locale cluster issues to seo-hreflang; and sitemap/inventory questions to seo-sitemap.
  4. Complete search-result presentation when it is in scope. Check the unique title, descriptive meta description, visible main heading, canonical/indexability, site name context, and hostname favicon. A missing, duplicated, generic, or under-informative field is not dismissed because it is a basic item. Route copy to seo-content and favicon/crawl delivery to seo-technical.
  5. Distinguish defects from choices. A mismatch with an explicit page contract may be a confirmed defect; an apparent opportunity without evidence is a hypothesis. Avoid arbitrary meta-length, heading-count, word-count, keyword-density, or internal-link quotas. Judge meta descriptions by page-specific semantic completeness, not a hard character target.
  6. Create a handoff. Give each recommendation an evidence pointer, scope, owner, impact/risk statement, acceptance criterion, verification, and rollback if the change could harm users or discovery. Use seo-action-plan for an approved cross-team implementation plan.

Guardrails

  • Do not infer indexation, rankings, citations, or traffic from a page capture.
  • Do not change a page, deploy markup, submit URLs, or claim approval.
  • No overall page score. Preserve conflicting evidence instead of averaging it.
  • Treat content intent, technical eligibility, measurement, and platform-specific AI visibility as separate questions.

Formal evidence handoff

When this work needs a cross-team, approval-ready plan, package evidence-bound findings as an immutable seo-findings.json bundle using the checked-out suite contract. Let <suite-root> mean ${CLAUDE_PLUGIN_ROOT} in Claude Code. In Codex, read .seo-suite-runtime.json beside this SKILL.md when present and use its suite_root value; otherwise use the absolute repository checkout. Keep every referenced capture/source below raw/, retain declined claims and limitations, and run python "<suite-root>/scripts/validate_seo_findings.py" validate-findings <bundle>/seo-findings.json --bundle <bundle>. Send only a passing bundle to seo-action-plan; otherwise label the handoff provisional.

Output

Return the page contract, query-family ownership, search-result presentation matrix, actual proposed title/meta copy when evidence supports it, favicon/site-identity state, capture limitations, lane-by-lane evidence table, confirmed defects, provisional opportunities, routing/ownership, and a minimal next action list. For implementation, cite the required approved action-plan item.

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.