🔍 SEO Prompt Master

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

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.

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:

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 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 <head> early and emit <title> later. Browsers hoist it; bots that stop reading at </head> see an untitled page.
• Bot protection — it recognises a Cloudflare, Akamai or Imperva challenge and reports it once, instead of scoring an unreadable site as broken.
• Plus: render-critical JS and CSS blocked by robots.txt, sitemap limits and lastmod credibility (including .xml.gz), host consolidation, duplicate titles, JSON-LD validity and policy (Product with no offer, review or rating; aggregateRating with no ratings behind it), raw-HTML content volume, image dimensions, viewport, lang, and AI-answer snippet controls (nosnippet, noarchive/nocache).

The output is an SEO Score and a GEO Score out of 100, each with a per-category breakdown that shows where the points went, the crawler access table, and every finding cited to docs/.

What it deliberately cannot see — so it stays your job: content quality (docs/14), off-page authority (docs/17), and real field Core Web Vitals, which come from CrUX rather than from fetching a page (docs/05). A high score means the technical foundation is sound, not that the site will rank.

See tools/README.md for every flag.

seo-prompt-master/
├── install.sh                ← writes the skill into your project, for every agent
├── package.json              ← `npx github:umutxyp/Seo-Promt-Master` runs the auditor
├── GUIDE.md · GUIDE.tr.md    ← usage guides (English · Türkçe)
├── VERSION · CHANGELOG.md    ← semver; a major means old scores aren't comparable
│
├── .claude/skills/seo-audit/SKILL.md    ← Claude Code
├── AGENTS.md                            ← Codex, Amp, Jules, Windsurf (and most others)
├── .cursor/rules/seo-prompt-master.mdc  ← Cursor
├── GEMINI.md                            ← Gemini CLI
├── .github/copilot-instructions.md      ← GitHub Copilot
├── CLAUDE.md · START.md                 ← the workflow itself
│
├── tools/                    ← the parts that run
│   ├── seo-audit.mjs            live SEO + GEO audit, scored, exits 1 on any P1
│   ├── seo-smoke.sh             deploy tripwire
│   └── build-prompts-csv.mjs    regenerates prompt-library/prompts.csv
│
├── prompt-library/           ← 47 copy-paste prompts in 8 categories (+ prompts.csv)
├── prompts/                  ← the 5-phase workflow (+ 1 optional)
├── docs/                     ← the knowledge base (source of truth), 01–18
├── verticals/                ← 24 industry overlays (optional, additive)
├── checklists/ · templates/ · examples/
└── tests/                    ← fixture sites the tools are tested against (npm test)

START.md
  │
  ├─ Phase 0  Bootstrap ......... detect framework, i18n, rendering; load docs/;
  │                               RUN tools/seo-audit.mjs for the baseline
  ├─ Phase 1  Discover .......... every route → ROUTES-INVENTORY.md
  │                               classify: public-index / public-noindex / private
  ├─ Phase 2  Audit ............. 9-point check per page → SEO-AUDIT-PROGRESS.md
  ├─ Phase 3  Prioritize ........ one backlog, infra-first (P1 → P2 → P3)
  ├─ Phase 4  Fix & verify ...... change → typecheck/lint/build → re-fetch → tick
  └─ Phase 5  Live signals ...... optional: CrUX and live scrape via MCP

Progress lives in ROUTES-INVENTORY.md and SEO-AUDIT-PROGRESS.md, so a long run survives a context reset and resumes where it stopped.

Metadata · Canonical + hreflang · Robots and indexing (meta and header) · Structured data · Headings and semantics · Images · Internal links and pagination · Rendering · Sitemap · Crawler access for every major search engine and AI crawler — every rule traces to a cited section in docs/.

The output is a number with its working shown: a deterministic SEO Score and GEO Score out of 100 (docs/11), each with a per-category breakdown. A P1 crawl or index blocker caps a page's score no matter what else it gets right, because a page that cannot be indexed gains nothing from polish. No score is reported as final without full coverage plus a self-recheck of a random sample. And it is always stated as a technical-readiness score: backlinks, content quality and competition are out of scope.

Most SEO checklists are shallow, generic, or quietly out of date. This one is:

• Current (reviewed October 2026). It is explicit about what changed: INP replaced FID in March 2024; FAQ rich results are limited to government and health sites; HowTo rich results are gone; rel=next/prev has been unused by Google since 2019; Google doesn't support IndexNow but Bing and Yandex do; Bing still obeys Crawl-delay; llms.txt is not a ranking or citation lever. Advice that repeats the old version is out of date, and the knowledge base says so.
• Not Google-only. Google is the reference engine, but Bing's index sits behind DuckDuckGo, Yahoo and Copilot, and Applebot sits behind Siri and Safari's suggestions. docs/18 covers where the engines differ, and the auditor checks all of them.
• Cited. Every claim links to official documentation. If something isn't in docs/, the agent is told to say "not covered by the knowledge base" rather than recall it from training data.
• Executable and tested. An agent can run it against your code and your server. The tools are themselves tested against a healthy and a deliberately broken fixture site on every push.
• Honest about its limits. It separates ranking factors from hygiene, logs deliberate skips, and names what it can't measure.

Umut Bayraktar — @umutxyp

Full-stack developer, AI-systems researcher and content creator, with 6+ years of building platforms end to end. Founder and CEO of Codeshare Technology, a London-based software studio (founded 2025; its products date back to 2020) built on one idea: software that stays free for the people who need it.

The methodology here comes from running these products, not from theory — and the tools were tested against their production sites before every release:

Across the portfolio: 41.5K+ Discord servers, 3M+ Discord users and 466K+ Minecraft players reached (figures from codeshare.me, October 2026).

Open source: MusicBot · Seo-Promt-Master · Discord-Bot-Website · Personal-Website · v14-discord-bot · Shroudly

🔗 Portfolio · GitHub · LinkedIn · YouTube · Codeshare Technology

If this saved you time, star the repo. 🌟

MIT © Umut Bayraktar (@umutxyp). The knowledge base is compiled from public documentation by Google Search Central, web.dev, Microsoft Bing, Yandex, Apple, Brave, DuckDuckGo and the AI crawler operators. All trademarks belong to their owners. This project is not affiliated with or endorsed by any of them.

Search guidance moves. PRs that update a rule with a source link, add a framework recipe or a prompt, or add a check to tools/ (with a fixture test) are very welcome — see CONTRIBUTING.md.