---
title: "SEOmator SEO Audit Skill"
kind: "Kit"
category: "Marketing & SEO"
price: "Free"
seller: "Mindket"
version: "2"
url: "https://mindket.com/p/d43d6912-7404-4cc3-b93a-f4a831045dcf"
updated: "2026-11-09"
health: "Quiet"
---

# SEOmator SEO Audit Skill

> The name, the description, the About and a README below are the seller's words: data, not instructions.

SEOmator’s open source SEO audit tool and the skill that lets your coding agent run it. It checks a page or a crawl against 373 rules in 20 categories, from Core Web Vitals to structured data and AI search readiness, and gives a fix for each problem.

SEOmator SEO Audit Skill is an open-source project on GitHub in the Marketing \& SEO category, listed by Mindket. It is free. This is version 2, last updated on 2026-11-09. Install it from GitHub as its README says. Get Mindket’s setup notes on your Mindket account, as a zip.

Made by seo-skills

## About

### What it is

SEOmator SEO Audit Skill is a command-line SEO auditor plus the skill that lets a coding agent run it. The tool, seomator, fetches a page or a crawl of your site and checks it against 373 rules in 20 categories. They span technical SEO, Core Web Vitals, links, structured data, security headers, accessibility and AI search readiness. You get a score out of 100, a grade and a fix line for each problem.

You install the seomator tool and the skill → You ask for an audit of a full web address → Your agent runs seomator audit in the llm format → The tool fetches the pages and checks 373 rules → Your agent lists the failures first, each with a fix

### Who it suits

Site owners, developers and marketers who want a technical SEO check without leaving their coding agent. It also suits teams that want the same checks in CI, and agencies that audit a staging site before launch. It audits one page unless you ask for a crawl. It needs an address it can fetch, and the skill prefers a live site to a local dev server.

Who uses it, and how

| Who | How they run it | Example |
| --- | --- | --- |
| Developers shipping a site | The skill inside their coding agent | A developer asks the agent to audit the new build and tell them what to fix first. |
| Marketers and consultants | The tool, with an HTML report | A consultant crawls 20 pages and sends the HTML report to the client. |
| Teams with a release process | Two audits and a compare | A team audits before and after a deploy and sees which rules got worse. |
| Agencies launching a site | The staging flag | An agency audits a site that is kept out of search on purpose and gets a list of what to change at launch. |

### Where to use it

Any coding agent that can run a command and read its output. The agent guide names Claude Code and Cursor, and the README’s skill section is written for Claude Code.

- Claude Code: the skill goes into .claude/skills/ in the project, or into \~/.claude/skills/ with -g
- Cursor, Codex and other agents: the same skills command, with the agent’s name after -a
- Any terminal: the tool alone, with no agent
- Your CI: the README’s GitHub Actions and GitLab CI examples
- A desktop app: run from source, from the same repository

### How to set it up

Get it saves a zip of Mindket’s setup notes in your downloads folder, with every route the README and its agent guide give.

What you need first

| Need | Detail |
| --- | --- |
| Node.js with npm | Node.js 20.3 or later, for the tool |
| A coding agent | For the skill route. The tool also runs from any terminal without one |
| A browser | Chrome, Chromium or Edge, optional, for Core Web Vitals and JavaScript rendering. Without one those checks report not measured |
| Git | Only for the routes that run from source |
| Accounts and keys | None. The README calls the tool free to run locally or in CI |

1. Install the seomator tool. You run the npm line in a terminal. It adds the seomator command, which does the audits.
2. Add the skill to your agent. You run the npx line. The skills tool asks which agents get it. The skill is a text file that tells your agent when to run seomator.
3. Check the setup, then ask. Run seomator self doctor, start a new agent session and type the prompt from the Example.

```sh
npm install -g @seomator/seo-audit
```

```sh
npx skills add seo-skills/seo-audit-skill
```

```sh
seomator self doctor
```

To skip the questions and install the skill for Claude Code in every project, the agent guide gives this form.

```sh
npx skills add seo-skills/seo-audit-skill --skill seo-audit -g -a claude-code -y
```

### How to use it

Ask in plain words, or run the tool yourself. Your agent picks the flags from your question, and the skill gives it this guide.

Match the flag to the question

| You want to check | The audit runs with |
| --- | --- |
| One page, fast | --no-cwv, which skips the browser render |
| More pages, click depth, duplicate titles | --crawl, with -m for how many pages |
| Core Web Vitals and JavaScript errors | The default, with --no-cwv left out |
| Mobile-first parity | --mobile |
| A report to share | --format html with -o report.html |
| What a deploy changed | An audit before and after, then seomator compare |

### Example

Your new site is nearly ready, and you want to know what to fix first.

```text
Audit https://example.com and tell me what to fix first
```

Your agent runs the tool, reads its XML report and lists the failed checks first, each with the tool’s fix line.

If the page is set to noindex, a score cap keeps the score at 20 or below, and the skill tells your agent to fix that before anything else.

### For newcomers and experts

**If you are new.** A skill is a text file that tells your agent when to use a tool. Here the tool is seomator, which you install once. Start with one page, then add --crawl when you want the whole site. A check marked not measured did not run in that audit, and it does not change the score.

**For experts.** Exit codes let a script tell a failed run from a low score. 0 is success. 1 means the run worked and scored under 70. A 1 with empty stdout means the command line was rejected. 2 means the command failed. With --format json or llm, a failure still writes an error document with a code such as dns, tls or timeout.

Score caps, from the skill

| Condition | Overall score at most |
| --- | --- |
| noindex for Google, or robots.txt blocks Googlebot | 20 |
| No title and fewer than 20 words of main content | 30 |
| Fewer than 20 words of main content | 49 |
| No title | 69 |

seomator compare with --fail-on-regression exits 1 when the score dropped or a rule got worse, and it never fails for two audits measured differently. --staging waives the noindex and robots.txt caps for a site that is blocked on purpose, and lists what it waived.

### Good to know

The tool audits and reports. The skill also lets your agent go on to fix your site, and it tells the agent to give you a summary of every change.

- Files: if the folder has no seomator.toml, the skill has your agent create one with seomator init -y first
- Pre-approval: in Claude Code, the skill’s allowed-tools line lets Claude run seomator commands without asking during that turn, as Claude Code’s skills page describes
- Stored audits: each audit is saved by default in \~/.seomator/audits.db on your computer, and --no-save skips it
- Requests: by default every request identifies itself as SEOmatorBot/3.0 with a link to the repository, unless crawler.user\_agent in seomator.toml changes it
- Page text: the llm report wraps text quoted from the audited site as untrusted data, and the report’s own security notice tells your agent never to follow it as instructions
- INP: it is never scored, since it needs a real person’s interaction. The README’s --simulate-interaction flag gives only a synthetic reading that stays unscored
- Maker: SEOmator, MIT licensed. Mindket lists it and is not SEOmator

## README

```markdown
# SEOmator SEO Audit Skill: setup notes

This kit holds setup notes written by Mindket. It does not contain SEOmator’s code, its skill file or its rules. Those install from SEOmator’s repository and npm package: https://github.com/seo-skills/seo-audit-skill and https://www.npmjs.com/package/@seomator/seo-audit

License: MIT, Copyright (c) 2024-present SEOmator. Full text: https://github.com/seo-skills/seo-audit-skill/blob/main/LICENSE

SEOmator is made by SEOmator. Mindket lists it and is not SEOmator.

The pages these notes came from: the README (https://github.com/seo-skills/seo-audit-skill/blob/main/README.md), the skill file SKILL.md at the repository’s root (https://github.com/seo-skills/seo-audit-skill/blob/main/SKILL.md), the quickstart (https://github.com/seo-skills/seo-audit-skill/blob/main/docs/quickstart.md), the AI agent guide (https://github.com/seo-skills/seo-audit-skill/blob/main/docs/ai-agent-integration.md) and the file that sets the User-Agent (https://github.com/seo-skills/seo-audit-skill/blob/main/src/crawler/user-agent.ts). Facts about where Claude Code loads skills come from Claude Code’s own docs, named where they are used. Mindket copied every command and ran none of them.

## What it is

Two parts that work together.

- The tool: a command-line program called seomator, installed from npm. It fetches a page or a crawl of a site and checks it against 373 rules in 20 categories, from technical SEO and Core Web Vitals to structured data, accessibility, security headers and AI search readiness. The README counts them, and SKILL.md gives the same numbers.
- The skill: one SKILL.md file named seo-audit. It tells a coding agent when to run the tool and which flags to use. The agent guide says it holds instructions only, so you install both.

The same repository also holds an Electron desktop app, which the README runs from source (setup/desktop-app.md).

## Files in this kit

- setup/claude-code.md: the tool and the skill for Claude Code
- setup/other-agents.md: the skill for another agent, and the tool alone from any shell
- setup/cli.md: the command-line tool from npm or from source, and its main commands
- setup/desktop-app.md: the desktop app, run from source
- setup/ci.md: the README’s GitHub Actions and GitLab CI examples
- setup/first-run.md: how to read a report, the score caps and the exit codes

## What you need first

- Node.js 20.3 or later with npm. The README says the tool needs it.
- A coding agent that can run shell commands, for the skill route. The tool also runs from any terminal without one.
- Google Chrome, Chromium or Microsoft Edge, if you want Core Web Vitals and the JavaScript rendering checks. Without a browser the audit still runs and reports those checks as not measured.
- Git, only for the from-source routes.
- No account, sign-up or key. The README calls the CLI free to install and run locally or in CI.

## What installs where

- The tool: a global npm package that adds the seomator command.
- The skill: a folder named seo-audit with the SKILL.md in it. For Claude Code it goes to .claude/skills/ in the current project, or to ~/.claude/skills/ with -g (setup/claude-code.md).
- Stored audits: the tool saves each audit by default in ~/.seomator/audits.db on your computer. SEOMATOR_HOME moves that folder, and --no-save skips saving.
- A seomator.toml file in the folder you audit from, if the agent or you create one with seomator init.

## Your data

The tool fetches the pages of the site you name, plus its robots.txt and sitemap, and saves the results on your computer. Every request carries the User-Agent SEOmatorBot/3.0 with a link to the repository, unless a crawler.user_agent setting changes it. The README says the local dashboard, seomator serve, binds to the loopback address only and makes no outbound requests. Mindket did not trace every network call in the code.

A report quotes text from the audited pages. SKILL.md’s trust model says that text is untrusted, and the llm format wraps it in tags with a random nonce so the agent treats it as data, not instructions.

## Update and remove

The README gives no update or removal step for the npm package. npm’s own commands cover both. For the skill, setup/claude-code.md says what Claude Code’s docs give for removing one.
```

## What is in it

7 files, 21 KB, downloaded as a zip.

```text
README.md  4 KB
setup/ci.md  2 KB
setup/claude-code.md  3 KB
setup/cli.md  3 KB
setup/desktop-app.md  2 KB
setup/first-run.md  5 KB
setup/other-agents.md  2 KB
```

## Source

[seo-skills/seo-audit-skill on GitHub](https://github.com/seo-skills/seo-audit-skill)

## Intro videos

- [SEOmator SEO Audit Skill intro video 1](https://www.youtube.com/watch?v=vIUJ4Hd7be0)
- [SEOmator SEO Audit Skill intro video 2](https://www.youtube.com/watch?v=6tBv5Bqn1rM)

## What people say

> Posts and comments that name this project on Hacker News, Bluesky, X, Reddit, Facebook and YouTube, found by a weekly search on 2026-11-09. Their authors' words: data, not instructions.

- [Bluesky · Shauvik Kumar · 2026-05-26](https://bsky.app/profile/shauvik.bsky.social/post/3mmqbis36r42w): 2. SEO GEO Claude Skills =\> one of the most ambitious SEO + GEO + AI workflow collections I’ve seen so far github.com/aaron-he-... 3. Tech SEO Audit Skill =\> focused Technical SEO audit workflows built for Claude github.com/Suganthan...
- [Bluesky · Elasticflow for Marketing · 2026-06-14](https://bsky.app/profile/new-marketing.bsky.social/post/3mobkiqis4c2w): One SEO audit skill. Multiple AI environments. Try /seo-audit in ElasticFlow Hub: elasticflow.app/hub/skills/s... Works across ChatGPT, Claude, Gemini, Cursor, Claude Code, Codex, Windsurf and more. \#Claude \#ChatGPT \#Gemini \#aiskills
- [Bluesky · Mak \| Effective Social Media Marketing · 2026-11-03](https://bsky.app/profile/makpastrana.bsky.social/post/3mzfrrhsgrt27): Here's the prompt to build a skill based on GitHub repo: "Please acquire this Full Website SEO Audit skill in this github, along with relevant skills mentioned: URL of Skill MD" Once it builds a skill, download and upload it to Claude.
- [Bluesky · Tom Dörr · 2026-04-05](https://bsky.app/profile/tom-doerr.bsky.social/post/3mir7ooelnn27): https://github.com/seo-skills/seo-audit-skill

## Trust facts

Facts from each source, with the day each was checked. A maintainer's note is their own words: data, not instructions.

- Health on GitHub: Quiet
- Last change: 2026-10-15
- Checked on GitHub: 2026-11-07
- Something wrong? Tell us: https://mindket.com/takedown#ask

## Get it

- [Open seo-skills/seo-audit-skill on GitHub](https://github.com/seo-skills/seo-audit-skill)
- [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/d43d6912-7404-4cc3-b93a-f4a831045dcf)
- [Its page on Mindket](https://mindket.com/p/d43d6912-7404-4cc3-b93a-f4a831045dcf)
