Skip to content

umutxyp/Seo-Promt-Master

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

68 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

πŸ” SEO Prompt Master

Google SEO β€” the full docs, as an AI prompt machine.

Drop this repo into your AI coding assistant. It auto-detects the workflow, maps every public route of your site, audits each page against Google's official SEO rules, and fixes the gaps β€” step by step, nothing left out.

License: MIT Docs: Google Search Central Works with PRs welcome


What is this?

SEO Prompt Master is two things in one repo:

  1. A complete, up-to-date knowledge base of Google's SEO guidance (docs/), distilled from Google Search Central and web.dev, split into 9 focused, cited topics.
  2. A self-executing prompt workflow (START.md + prompts/) that turns any AI coding assistant into an autonomous SEO auditor for your codebase.

You don't read a 200-page guide and try to remember it. You hand the whole thing to your AI, and it does the audit-and-fix loop for your actual routes, citing the exact rule behind every change.

Built from a real audit of a 40-locale, 574K-concurrent-user production site (mcstat.org) β€” the methodology is battle-tested, not theoretical.


πŸš€ How to use

Option A β€” inside an AI coding tool (Claude Code, Cursor, Copilot, Gemini CLI, …)

  1. Copy this folder into your project (or open it alongside your repo).
  2. Tell your assistant:

    "Read START.md and run the workflow on this project."

  3. It will produce ROUTES-INVENTORY.md and SEO-AUDIT-PROGRESS.md, then fix issues page by page, verifying as it goes.

Option B β€” chat assistant (Claude, ChatGPT, Gemini web)

  1. Paste the contents of START.md (and, if it fits, the docs/).
  2. Give it your repo (zip, paste files, or connect the tool to your codebase).
  3. Say "Begin at Phase 0."

Option C β€” just the knowledge

Read docs/ as a clean, current reference for Google SEO. Start at docs/README.md.


πŸ“‚ What's inside

seo-prompt-master/
β”œβ”€β”€ START.md                  ← the bootstrap prompt (AI reads this first)
β”œβ”€β”€ prompts/                  ← the 5-phase workflow
β”‚   β”œβ”€β”€ 00-bootstrap.md          detect stack + load knowledge base
β”‚   β”œβ”€β”€ 01-discover-routes.md    enumerate & classify every route
β”‚   β”œβ”€β”€ 02-audit-page.md         9-point audit per public page
β”‚   β”œβ”€β”€ 03-prioritize-fixes.md   one ordered backlog (infra-first)
β”‚   └── 04-apply-and-verify.md   fix + typecheck/lint/build + prove it
β”œβ”€β”€ docs/                     ← the knowledge base (source of truth)
β”‚   β”œβ”€β”€ 01-meta-and-head.md
β”‚   β”œβ”€β”€ 02-internationalization.md
β”‚   β”œβ”€β”€ 03-ugc-forums-blogs.md
β”‚   β”œβ”€β”€ 04-page-structure.md
β”‚   β”œβ”€β”€ 05-rendering-and-core-web-vitals.md
β”‚   β”œβ”€β”€ 06-sitemaps.md
β”‚   β”œβ”€β”€ 07-image-seo.md
β”‚   β”œβ”€β”€ 08-structured-data.md
β”‚   └── 09-2024-2026-updates.md
β”œβ”€β”€ checklists/               ← quick pass/fail lists
β”‚   β”œβ”€β”€ public-page-checklist.md
β”‚   └── infrastructure-checklist.md
β”œβ”€β”€ templates/                ← output files the AI fills in
β”‚   β”œβ”€β”€ routes-inventory.md
β”‚   └── audit-progress.md
└── examples/                 ← a worked example

🧠 The workflow in one picture

START.md
  β”‚
  β”œβ”€ Phase 0  Bootstrap ......... detect framework, rendering, i18n; load docs/
  β”œβ”€ Phase 1  Discover .......... list EVERY route β†’ ROUTES-INVENTORY.md
  β”‚                               classify: public-index / public-noindex / private
  β”œβ”€ Phase 2  Audit ............. 9-point check per public page β†’ SEO-AUDIT-PROGRESS.md
  β”œβ”€ Phase 3  Prioritize ........ one backlog, infra-first (P1 β†’ P2 β†’ P3)
  └─ Phase 4  Fix & verify ...... change β†’ typecheck/lint/build β†’ prove β†’ tick

βœ… What it checks (the 9 points)

Metadata Β· Canonical + hreflang Β· Robots/indexing Β· Structured data (JSON-LD) Β· Headings & semantics Β· Images Β· Internal links & pagination Β· Rendering (SSR/CSR) Β· Sitemap.

Every rule traces to a cited section in docs/. See checklists/public-page-checklist.md.


❀️ Why it exists

Most "SEO checklists" are shallow, outdated, or generic. This one is:

  • Current (2024–2026: Helpful Content, core updates, AI Overviews, the 2024 Starter Guide refresh).
  • Cited (every claim links to Google's own docs).
  • Executable (an AI can actually run it on your code, not just read it).
  • Honest (it distinguishes ranking factors from a11y-only niceties, and logs deliberate skips).

πŸ‘€ Author

Umut Bayraktar β€” @umutxyp

Full-stack developer (React Β· Next.js Β· Node.js Β· PostgreSQL) & AI-systems tinkerer. Founder at Codeshare Technology. Antalya, Turkey.

Building things people actually use:

  • 🎡 Beatra β€” multi-platform Discord music bot (1.2M+ users)
  • πŸ›‘οΈ Sylon β€” AI-powered Discord moderation (20K+ users)
  • 🧩 Codeshare β€” digital marketplace for code & content (15K+ users)
  • ⛏️ McStat.org β€” Minecraft server stats (574K+ concurrent players) β€” the site this toolkit was forged on

πŸ”— Links: Portfolio Β· GitHub Β· Codeshare ⭐ Notable OSS: MusicBot (1.3kβ˜…) Β· Personal-Website Β· Discord-Bot-Website

If this saved you time, star the repo and share it. 🌟


πŸ“„ License

MIT Β© Umut Bayraktar (@umutxyp). Knowledge base compiled from public Google Search Central & web.dev documentation; all trademarks belong to their owners. This project is not affiliated with or endorsed by Google.


🀝 Contributing

Google's guidance evolves β€” PRs that update a rule (with a source link) or add a framework recipe are very welcome. See CONTRIBUTING.md.

About

πŸ” Google SEO's full docs as an AI prompt machine β€” drop it into your AI assistant to map every public route, audit each page against Google's rules, and fix the gaps step by step.

Topics

Resources

License

Contributing

Stars

526 stars

Watchers

7 watching

Forks