Analysis updated 2026-06-24
Add a full SEO and schema markup baseline to a Next.js or Astro site through an AI assistant
Audit a deployed site for missing Open Graph, robots.txt, sitemap, and hreflang setup
Set up Core Web Vitals, WCAG 2.2 AA, and security header checks in a coding agent workflow
Configure IndexNow for Bing and Yandex on a new site
| aycanozarpaci/seo-pro-max-skill | 09catho/axon | abdulrdeveloper/react--tic-tac-toe | |
|---|---|---|---|
| Stars | 13 | 13 | 13 |
| Language | JavaScript | JavaScript | JavaScript |
| Setup difficulty | easy | moderate | easy |
| Complexity | 2/5 | 4/5 | 1/5 |
| Audience | vibe coder | researcher | developer |
Figures from each repo's GitHub metadata at analysis time.
npm install path is not live yet, so installation is a manual curl or Invoke-WebRequest into your AI tool's rules folder.
seo-pro-max is a shared instruction file (called a skill) that you drop into an AI coding assistant such as Claude Code, Cursor, Windsurf, Cline, or GitHub Copilot Chat. Its job is to help the assistant set up the search-engine and accessibility plumbing of a website, the kind of small but opinionated decisions a generic AI would otherwise pick on its own and often get wrong. The README is firm that the skill is an executor, not a decision-maker. It runs a Phase 0 analysis of the project first, asks the user the questions an assistant should not answer alone (like title strategy, where the admin panel lives, how the database stores per-page overrides, whether to emit a keywords meta tag), and only then writes code. The author lists current standards the skill enforces so the assistant does not suggest dead patterns: Google's removal of FAQPage rich results on May 7, 2026, the deprecation of rel=prev/next, the boundaries of IndexNow support (Bing and Yandex only, not Google), soft-404 detection, and BCP 47 hreflang validation. A quick start section explains the planned install once an npm package is published: a single npx seo-pro-max install command that auto-detects which AI coding tool is in use and drops the right file in the right place. Until then, the README provides per-platform manual install instructions using curl on macOS and Linux or Invoke-WebRequest on Windows PowerShell, with the right path for each tool (~/.claude/skills/.cursor/rules/.windsurfrules.clinerules.github/copilot-instructions.md, and so on). A long What it covers section lists the areas the skill touches: meta tags, indexing controls, correct HTTP status codes, robots.txt, XML sitemaps, Open Graph and Twitter cards, a recommendation matrix for Schema.org JSON-LD types, favicons and PWA manifests, search-engine verification, the llms.txt file (noted as not used by Google for AI ranking), admin-panel placement, database schema choices, per-page overrides, internationalisation, OG image generation, WCAG 2.2 AA accessibility checks, Core Web Vitals gates, image optimisation, URL and slug rules, internal linking and orphan detection, security headers, and client-side meta updates for single-page apps. The FAQPage section repeats that the skill does not emit FAQPage JSON-LD for new builds and uses QAPage for real community Q&A pages instead. The install section then gives copy-paste commands for nine different AI coding tools.
A shared instruction file for AI coding assistants that handles SEO, accessibility, and schema markup setup. Asks the user the strategy questions first, then writes code.
Mainly JavaScript. The stack also includes Markdown, ClaudeCode, Cursor.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly vibe coder.
This repo across BitVibe Labs
Verify against the repo before relying on details.