Skip to content
Starter $4 · soon
Menu
Docs: Workflow

GEO and SEO with Claude Code: the two workflows

Agent2Ship has two paths. For a new site you go from idea to brief, stack, build, design, deploy and a weekly growth loop. For a site you already have, you start with a Claude Code SEO audit, then work through opportunities, fact-checks and design. Both paths cover SEO (being found in Google) and GEO (being cited in AI answers).

New site: idea to growth

  1. /a2s-idea (optional). Validates an idea with live autocomplete demand, competition, AI-answer gaps and hosting cost. Gives go / maybe / skip with an honest confidence level.
  2. /a2s-brief. Writes SITE-BRIEF.md: name, domain, competitor, keywords and a keyword map with one search intent per page.
  3. /a2s-stack. Writes STACK.md with a 🟢 / 🟡 / 🔴 hosting verdict before anything is built.
  4. /a2s-build. Phase A installs design tools, you restart Claude Code, Phase B builds the site in the project root and runs the design department.
  5. /a2s-deploy. Cloudflare deploy, domain, redirects, Search Console and sitemap, checked with real requests.
  6. /a2s-adsense-ready. AdSense readiness on the live site (only if you want ads).
  7. /a2s-audit + /a2s-geo-check. Technical SEO and AI-search check of the live site.
  8. /a2s-grow, weekly. Health check, measurement of past changes and a small plan.

Existing site: audit first

  1. /a2s-setup <url>. Detects your stack, fills SITE-CONTEXT.md from your code, drafts GEO prompts and checks Search Console access.
  2. /a2s-audit. The crawler audit with prioritized fixes.
  3. /a2s-opportunities. Search Console data turned into page-level tasks.
  4. /a2s-fact-check. Every claim checked against your code and official sources.
  5. /a2s-design review. If the site looks basic, a design review against competitors.
  6. /a2s-grow, weekly.

The audit agents work with Astro, Next.js and React sites.

What does the Claude Code SEO audit check?

/a2s-audit runs a zero-dependency Node crawler, then the technical SEO agent explains and fixes what it finds. The crawler checks:

  • Indexability, meta tags and canonicals
  • Redirects (it follows them) and http/www duplicate hosts
  • Orphan pages and client-side-rendered pages that show crawlers an empty shell
  • Schema misuse, such as page-specific schema repeated on every page
  • AI bots blocked by robots.txt or by the CDN

How does GEO work with Claude Code?

GEO (generative engine optimization) means getting your site mentioned and cited in AI answers. /a2s-geo-check takes 10–20 real questions your visitors ask (saved in geo-prompts.txt), checks the AI answers for them (with API keys if you set them, or in manual mode without), and shows whether your site is cited and who is cited instead. It then explains why those pages win and suggests on-page changes and off-site actions. AI answers vary between runs, so compare trends every 2–4 weeks rather than trusting one result.

Claude Code SEO optimization after launch

Once Search Console has data, /a2s-opportunities finds striking-distance queries (positions 4–20), low-CTR pages, gaps and cannibalization. You change a few pages at a time, /a2s-measure saves a baseline with a recheck date 4–6 weeks out, and then compares a fresh Search Console export to tell you whether the change worked.

Why the files matter

Each step writes its decisions into .claude/agent2ship/ (brief, stack, design plan) and reports into seo-reports/, with a changelog of every change. That is why you can start a fresh session for each big step without losing context.

Every command in detail: the commands reference. Habits that save time: tips.