Install geoaeo

Requirements

• Node.js 20 or later
• npm, pnpm, yarn, or bun
• A site to audit — a live URL or a local directory

Install

Install as a dev dependency in any site:

npm install geoaeo

Or install globally if you run it across many repos:

npm install -g geoaeo

One-off without install

Use npx when you only need a single audit:

npx geoaeo audit https://example.com
npx geoaeo audit ./ --json

Verify both bins

The package provides two bins. Check that both resolve:

npx geoaeo --help
npx geoaeo-mcp --help

geoaeo is the CLI. geoaeo-mcp is the MCP server over stdio. You do not run the MCP bin by hand when an agent manages it.

Scaffold config

Create geoaeo.config.ts from the example. The config holds site facts used by every generator.

npx geoaeo init ./
cat geoaeo.config.ts

init detects Next.js, Astro, SvelteKit, Nuxt, or Remix and writes routes that emit each artifact. Other directories receive static files. Existing files stay unchanged unless you pass --force.

npx geoaeo init ./ --force

Config shape

A minimal config looks like this:

import { defineConfig } from 'geoaeo';

export default defineConfig({
  siteName: 'Example',
  siteUrl: 'https://example.com',
  description: 'An example site.',
  pages: ['pricing', 'faq'],
});

See geoaeo.config.example.ts in the repo for the full shape with tools, plans, and FAQ entries.

Next steps

• CLI reference — audit, gen, humanize, and mcp in detail
• MCP server — wire geoaeo-mcp into your agent
• Claude Code guide — first harness setup