agentleFS
ZachArticulateVZachArticulateV/designer-pro-and-seo/skills/seo-page/SKILL.md

seo-page

Skill10 starsChanged 28 days agoMITView on GitHub

Single-URL SEO review — runs the technical audit and the content audit on one page (on-page elements, meta, E-E-A-T signals, readability, keyword placement, schema, images, lab performance risks, internal links) in one pass with two deterministic scores (real Core Web Vitals field data when seo-google is connected). Lightweight alternative to seo-audit when only one page matters. Trigger when the user says "analyze this page", "check page SEO", "single URL", "check this page", "review this URL", or provides one specific URL.

31 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 2 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

  • timruebenachSkill

    seo-flow

    FLOW framework integration — evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.

    Also in 9 projects that use this

  • mangollcSkill

    seo-local

    Local SEO optimization: Google Business Profile post generation, 30-day posting calendars, NAP consistency checks, local citation audits, review response templates, local keywords.

    Also in 19 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If seo-google (PageSpeed/CrUX) is available, pull real LCP/CLS/INP.

    line 56

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

Family: seo Status: Stable

Purpose

The single-page analyzer: the same on-page, meta, schema, image, and internal-link checks as a full audit, scoped to one URL, plus observable performance issues — real Core Web Vitals field data only when seo-google is connected. Cheaper to run and easier to act on for spot checks, pre-publish reviews, and "is this page good?" questions. The free path (fetch + parse + score) is the whole product; paid APIs only add live ranking and field-performance context.

Triggers

  • "analyze this page" / "check this page" / "review this URL"
  • "single URL SEO" / "check page SEO"
  • "page-level analysis"

Inputs

  • A single URL (or local HTML file)
  • Optional: target keyword(s) for relevance scoring

Steps

  1. Fetch the page (WebFetch, or curl-style retrieval of the raw HTML). For a local build, read the file directly.
  2. On-page, meta & technical — run the technical audit on the saved HTML (pass --url for URL-structure checks):
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/tech_audit.py" --file page.html --url <URL> --no-network --human
    Title, meta description, one <h1>, canonical, meta robots / X-Robots-Tag, Open Graph, viewport, lab CWV risks, JS-rendering and mixed content — each with a fix (catalog: references/seo-technical/check-catalog.md).
  3. Content quality — run the content audit with the target keyword:
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/content_audit.py" --file page.html --url <URL> --keyword "<target>" --type <article|product|local|home|category> --human
    E-E-A-T signals (YMYL-aware), heading order, readability, depth for the page type, keyword placement / stuffing, in-content internal links and anchors, scaled-content tells, passage citability (rubric: references/seo-content/content-rubric.md). Then judge intent match by hand; hand deep E-E-A-T work to seo-content.
  4. Schema — detect JSON-LD; validate type appropriateness and required properties; flag rich-result eligibility. (Delegate deeper work to seo-schema.)
  5. Images — alt text presence/quality, dimensions declared (CLS), modern formats (WebP/AVIF), and lazy-loading below the fold.
  6. Performance — note render-blocking resources and obvious payload issues. If seo-google (PageSpeed/CrUX) is available, pull real LCP/CLS/INP; otherwise report observable issues and say field data needs seo-google.
  7. Internal links — the content audit counts in-content internal links and flags generic anchors; judge whether they point at the right hub and next step.
  8. Optional enrichment — if the DataForSEO extension is configured, add live ranking/keyword context; otherwise state, in one line, what it would add.
  9. Render a compact report — findings grouped Critical / High / Medium / Low, each with a specific fix.

Outputs

  • Page-level findings grouped by priority, each with a concrete fix
  • Two deterministic scores — technical (lab) and content — plus the combined view
  • A short "what paid data would add" note when running the free path

Dependencies

  • scripts/seo/tech_audit.py (required) — technical / on-page / lab-CWV checks
  • scripts/seo/content_audit.py (required) — content quality, E-E-A-T signals, links
  • references/seo-content/content-rubric.md (required) — content thresholds + scoring
  • Optional: seo-schema (deep schema), seo-content (deep E-E-A-T), seo-google (real CWV/field data), DataForSEO extension (ranking context)

Notes

A focused single-page subset of seo-audit; both exist because their cost profiles differ (one URL vs. a full crawl). They share the same checks — keep the simple entry point (see references/ENGINE-CONTRACTS.md §5 on the free path).

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.