agentleFS
Sign inStart free
UXMagicaiUXMagicai/seosorted-skills/skills/page-seo-audit/SKILL.md

page-seo-audit

Skill0 starsChanged 40 days agoMITView on GitHub

Audit one page of any website with SEOsorted — title, meta description, canonical, headings, word count, images, links, structured data, Open Graph, hreflang, HTTPS, broken links and Core Web Vitals (LCP, CLS, INP) — with a fix for each issue. Free, no credits. Use when the user asks to audit a page or URL, check on-page SEO, why a page doesn't rank, check schema or meta tags, page speed or Core Web Vitals, or broken links on a page.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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:

    If the page should rank for a keyword, check_google_results operation: "results" with that keyword (1 keyword lookup credit) to compare …

    line 15
  2. Very specific:

    If it is a SEOsorted article, fix it with update-and-republish.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Page SEO audit

audit_any_page checks any public URL live. No credits are used; calls are rate-limited per workspace. Only the HTML is fetched — JavaScript is not executed.

Steps

  1. audit_any_page operation: "audit" with url — title, meta description, canonical, meta robots, lang, viewport, H1s and heading outline, word count, images missing alt or dimensions, link counts, JSON-LD and microdata with parse errors, Open Graph and Twitter tags, hreflang, HTTPS and mixed content, and the site-audit issues for the page, each with a fix.
  2. operation: "speed" with url — PageSpeed mobile score and LCP, CLS, INP (field data when Google has it, otherwise a lab run).
  3. operation: "links" with url — status of up to 50 links on the page; broken ones flagged.
  4. If the page should rank for a keyword, check_google_results operation: "results" with that keyword (1 keyword lookup credit) to compare with what ranks.

Output

  • One line: is the page indexable and what is its biggest problem.
  • Fix first: blocking issues (noindex, wrong canonical, missing title, broken H1 structure, failing Core Web Vitals).
  • Then: meta length, missing alt text, schema errors, broken links.
  • For a JS-rendered page with little HTML text, say the audit sees what crawlers without JavaScript see — that is also what many AI crawlers see.

Next

If it is a SEOsorted article, fix it with update-and-republish. Site-wide problems → seo-audit.

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.

Check your setup, free