⚡ Quick start — pick one

| You want… | Do this | Time | |---|---|---| | A score and a findings list for a live site | npx github:umutxyp/Seo-Promt-Master --url https://your-site.com --md seo-report.md | 1 min | | An agent to audit and fix your codebase | bash /path/to/Seo-Promt-Master/install.sh inside your project, then tell your agent "run the SEO audit" | 1 min to set up | | A ready-made prompt for one task (robots.txt, hreflang, JSON-LD, traffic drop…) | Open the prompt library, copy, fill in {{variables}}, paste | 30 s | | To read the rules | docs/README.md — a current, cited reference to SEO and GEO | — |

No account, no API key, and zero dependencies. Node 18+ is the only requirement for the tool.

What is this?

Four things in one repository:

1. A knowledge base (docs/01–docs/18), distilled from Google Search Central, web.dev, and the official documentation of Bing, Yandex, Apple, Brave, DuckDuckGo and the AI crawler operators. Every claim is cited. Docs 01–11 cover the page. Docs 12–18 cover crawling and crawl budget, indexing and canonicals, content quality and the spam policies, measurement, migrations, off-page authority, and the engines beyond Google.
2. A skill that installs into whichever agent you use, so "audit my SEO" starts the whole workflow without you pasting anything.
3. A prompt library — 47 copy-paste prompts in 8 categories, from "rewrite my robots.txt" to "diagnose a traffic drop". Each one is built to ask for evidence and to refuse outdated advice. It's also available as a CSV.
4. Two tools that run (tools/). Reading a repository tells you what a project intends; only a request tells you what the server returns.

The tools are not decoration. Tested against production sites before release, seo-audit.mjs found live P1 blockers that source review had missed: a Disallow: /_next/ breaking rendering, and a template returning 200 for every URL under it.

🚀 Install as a skill

git clone https://github.com/umutxyp/Seo-Promt-Master.git
cd /path/to/your-project
bash /path/to/Seo-Promt-Master/install.sh

That copies the knowledge base, prompt library and tools into .seo-prompt-master/, then writes the entry-point file each agent actually reads:

| Agent | File it discovers | |---|---| | Claude Code | .claude/skills/seo-audit/SKILL.md | | OpenAI Codex CLI, Amp, Jules, Windsurf | AGENTS.md | | Cursor | .cursor/rules/seo-prompt-master.mdc | | Gemini CLI | GEMINI.md | | GitHub Copilot | .github/copilot-instructions.md |

Then just ask: "run the SEO audit". The agent finds the workflow itself.

If your project already has an AGENTS.md or GEMINI.md, the installer appends to it and never replaces it. Re-running the installer is safe.

Prefer not to install? Put the repo next to your project — most agents auto-discover AGENTS.md and start on their own. Or paste START.md into any chat assistant and say "begin at Phase 0".

🛠️ The tools

# The thorough pass — sample the sitemap, audit each page, compute SEO + GEO scores
npx github:umutxyp/Seo-Promt-Master --url https://example.com --max 40 --md report.md
(or, from a clone:)  node tools/seo-audit.mjs --url https://example.com --max 40 --md report.md
The ten-second deploy tripwire
SEO_SMOKE_404_PATHS="/ /blog /products" bash tools/seo-smoke.sh https://example.com

Both have zero dependencies. The auditor needs Node 18+; the smoke test needs curl and awk. Both exit non-zero on failure, so either can gate a deploy or a CI job (--fail-on P1|P2|never), and both work against http://localhost:3000.

What seo-audit.mjs catches that reading code cannot:

• Soft 404s, template by template — a route that answers 200 for URLs that don't exist. In frameworks with Suspense boundaries this has no visible symptom at all: a loading.tsx above one segment silently turns that whole template's 404 into a 200 shell.
• One-way hreflang — a set that isn't reciprocal is discarded in full, so every language in the cluster loses the signal. You can only see it by comparing pages against each other.
• Signals that contradict each other — a canonical pointing at a redirect, a 404 or a noindex page; sitemap URLs that redirect or that robots.txt blocks; a noindex sent in the X-Robots-Tag header that no one sees in the HTML.
• A crawler access matrix — robots.txt resolved per RFC 9309 for Googlebot, Bingbot (which also feeds DuckDuckGo, Yahoo and Copilot), Applebot (Siri, Spotlight, Safari), YandexBot, DuckDuckBot, Baiduspider, Naver and Seznam, plus 16 AI crawlers split into training, AI search and user-triggered. Blocking Bing by accident is a P1; blocking an AI trainer is a policy decision.
• Streamed metadata — frameworks that flush early and emit