Web audit and SEO · Claude Code skill

Website audit from a document

website-audit-from-doc

Works an SEO audit, QA punch list or client fix list against the live site, one item at a time, verifying every claim before acting on it.

  • Web audit and SEO
  • MIT licensed
  • Free
  • No setup needed

What Website audit from a document does

You have an improvement document and a site URL. This prioritises the list, then walks through it one item at a time, checking each claim against the live site first. Audit documents go stale fast, so reporting that something was already fixed is a useful result rather than a failure.

What you give it

An improvement document, spreadsheet of issues or fix list, plus the URL of the live site.

What you get back

  • A prioritised order for the whole list, stated before any work starts
  • Per item: the live pages affected, the part of the doc it maps to, and the specific problem actually found
  • The fix, explained only once you ask for it

Use cases

  • An agency SEO audit landed in your inbox

    Find out which items are real, which were fixed weeks ago, and which blame the wrong cause, before any time goes into them.

  • A client's list of requested changes

    Technical items you can do alone are sorted to the front; anything needing a decision or new content goes last.

  • Pre-launch QA

    Work a punch list against the staging or live site with each item verified rather than assumed.

How to use Website audit from a document

  1. Install the web audit toolkit

    /plugin install web-audit-toolkit@claude-skills

  2. Hand over the doc and the URL

    Ask to "work through this audit" or "action this list".

  3. Approve the order

    The prioritised list is stated before any item is started, so the order itself can be corrected cheaply.

  4. Go item by item

    Each item is investigated against the live site, the real problem is explained, and the fix only follows when you ask.

Benefits

  • Diagnoses, does not change

    Nothing on the site or in the document is edited unless you explicitly say so. You stay in control of every change.

  • Checks the live site, not the cache

    It uses a browser with a cache-busting query string, because a plain fetch gets served a copy from last week and ends up confirming problems that no longer exist.

  • One item at a time

    Audits go wrong when a batch of plausible-looking fixes is approved in one go and two of them rested on a stale claim.

  • Says when the doc is wrong

    Instead of quietly working around a bad claim, it tells you the document is out of date.

Install website-audit-from-doc

This skill ships in the web-audit-toolkit plugin. Add the marketplace once, then install the plugin in Claude Code.

/plugin marketplace add rodneylungayan/claude-skills
/plugin install web-audit-toolkit@claude-skills

After that the skill loads on its own whenever your request matches it. You can also invoke it by name with /website-audit-from-doc.

Questions about website-audit-from-doc

Will it change my site?
No. It diagnoses and explains. Nothing is edited, added or updated unless you explicitly tell it to.
What if the audit document is wrong?
It says so plainly. Every claim is checked against the live site first, and "this was already fixed" is reported as a result, not hidden.

Need this built, not just automated?

I build WordPress and Next.js sites for a living, and these skills are the toolkit behind that work. If you would rather hand the job over, get in touch.