seo-agent-suite

Improve GitHub and open-source repository SEO/discoverability across GitHub metadata, README/docs, package registries, GitHub Pages or docs sites, Google Search Console, and release verification. Use when the user asks why a repo/package cannot be found on Google, npm, crates.io, PyPI, etc.; asks to do SEO for a GitHub repo; needs README/package metadata optimization; wants Search Console submission; needs branded package scope planning for public repos; or wants evidence-backed repo/package/site discoverability audits.

Plan and review SEO content, keyword maps, content briefs, GEO/AEO readiness, AI-search citation potential, FAQ/schema opportunities, and comparison/disambiguation pages. Use when Codex needs content strategy, long-tail page ideas, AI answer optimization, E-E-A-T/entity clarity, or launch/discoverability copy that should align with Shipwise positioning.

Choose and document SEO data sources and MCP/provider boundaries for audits. Use when Codex needs to decide between local scripts, Firecrawl, Google Search Console, PageSpeed Insights, CrUX, DataForSEO, SE Ranking, Ahrefs, browser checks, or paid/live integrations; or when SEO findings require explicit source, cost, account, API-key, and confidence boundaries.

Run evidence-backed technical SEO audits for websites, docs sites, landing pages, and GitHub Pages properties. Use when Codex needs to inspect crawlability, title/meta/canonical tags, robots.txt, sitemap.xml, Open Graph/Twitter metadata, JSON-LD/schema, status codes, redirect/canonical issues, internal links, JavaScript rendering risk, Core Web Vitals boundaries, or technical SEO issues for a site.