Package Exports

geo-optimization-cli
geo-optimization-cli/lib/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (geo-optimization-cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

geo-optimization-cli

AI-powered Generative Engine Optimization (GEO) tool — generate llms.txt, robots.txt AI crawler rules, and Schema.org markup to make your website discoverable and citable by ChatGPT, Claude, Perplexity, and Gemini.

Installation

# Global install (recommended)
npm install -g geo-optimization-cli

# Verify install
geo --version

# Or run without installing
npx geo-optimization-cli --help

Quick Start

Pick the scenario that matches your situation:

Scenario A — You have a GEO audit report

Got a GEO-AUDIT-REPORT.md from Claude or another tool? Jump straight in:

# Step 1: See your score and what needs fixing
geo score ./GEO-AUDIT-REPORT.md

# Step 2: Generate all optimization files automatically
geo generate ./GEO-AUDIT-REPORT.md -o ./geo-artifacts

# Step 3: Preview the generated files
ls ./geo-artifacts

# Step 4: Deploy to your website root
geo deploy ./geo-artifacts

Scenario B — Starting from scratch (no audit report)

Tell the tool your business type and it generates everything:

# Generate files for a SaaS product
geo generate -t saas -o ./geo-artifacts

# Other business types:
geo generate -t ecommerce -o ./geo-artifacts   # Online store
geo generate -t publisher  -o ./geo-artifacts   # Blog / media site
geo generate -t local      -o ./geo-artifacts   # Local business
geo generate -t general    -o ./geo-artifacts   # Everything else

# Preview without writing files (dry run)
geo generate -t saas --dry-run

Scenario C — Initialize a project config first

# Create a .geo-optimization.json config in current folder
geo init

# Then generate (reads config automatically)
geo generate -o ./geo-artifacts

# Check what's already live on your site
geo verify

What Gets Generated

After running geo generate, you'll find:

geo-artifacts/
├── llms.txt                    # AI data policy (upload to yoursite.com/llms.txt)
├── robots-txt-update.txt       # Paste these lines into your robots.txt
├── implementation-plan.md      # Prioritized action checklist
├── schema/
│   ├── organization.json       # Paste into <head> as JSON-LD script
│   ├── faq-page.json
│   ├── breadcrumb-list.json
│   └── software-application.json  # (saas only)
│   └── product.json               # (ecommerce only)
│   └── local-business.json        # (local only)
│   └── article.json               # (publisher only)
├── deploy.sh                   # One-click deploy helper
└── verify.sh                   # Verification script

How to use the generated files

File	What to do
`llms.txt`	Upload to `https://yoursite.com/llms.txt`
`robots-txt-update.txt`	Copy the rules into your existing `robots.txt`
`schema/*.json`	Add each as `<script type="application/ld+json">...</script>` in `<head>`
`implementation-plan.md`	Follow the checklist from top to bottom

All Commands

Command	What it does
`geo score <file>`	Parse an audit report and show your GEO score + issues
`geo generate [file]`	Generate `llms.txt`, `robots.txt` rules, Schema JSON
`geo generate -t <type>`	Generate without an audit report (specify business type)
`geo deploy [dir]`	Copy generated files to your website root
`geo verify`	Check live GEO status of your site
`geo init`	Create `.geo-optimization.json` project config
`geo analyze <url>`	Fetch and analyze a URL

Flags

Flag	Description
`-t, --type <type>`	Business type: `saas` \| `ecommerce` \| `publisher` \| `local` \| `general`
`-f, --file <path>`	Input audit report path
`-o, --output <dir>`	Output directory (default: `./geo-artifacts`)
`--dry-run`	Preview what would be generated, no files written
`-v, --version`	Show version
`-h, --help`	Show help

Business Types

Type	Use when your site is...
`saas`	A software product or SaaS platform
`ecommerce`	An online store or product catalog
`publisher`	A blog, news site, or media platform
`local`	A restaurant, shop, or local service
`general`	Anything else

Not sure? Use general — it generates a safe baseline set of files.

API Usage

import { GeoOptimizer, AuditParser, SchemaGenerator } from 'geo-optimization-cli';

// Generate artifacts programmatically
const optimizer = new GeoOptimizer({ businessType: 'saas' });
const artifacts = await optimizer.generateArtifacts({ type: 'saas' });
await optimizer.saveArtifacts(artifacts, './output');

// Parse an audit report
const parser = new AuditParser();
const parsed = parser.parse(markdownContent);
console.log(parsed.overallScore, parsed.businessType);

// Generate a specific schema type
const schema = new SchemaGenerator();
const org = schema.organization({ name: 'Acme Corp', url: 'https://acme.com' });

Requirements

Node.js >= 18
Zero external dependencies