Documentation

Everything you need to go from sign-up to a deployed, fully-optimized local-SEO site.

Getting started

Create a free account, then open the dashboard and click + New build. The wizard walks you through nine short steps. When you reach the AI engine step you'll paste your OpenRouter key, and the final step generates the whole site right in your browser.

1. Sign up (email or Google).
2. Get an OpenRouter API key (see below).
3. Run the build wizard and download your ZIP.
4. Deploy the ZIP anywhere that serves static HTML.

Your OpenRouter key (BYOK)

Local Site Engine is bring-your-own-key. Generation happens entirely in your browser and talks directly to OpenRouter with your key — our servers never proxy the AI calls and never see or store the key. That's why you only pay OpenRouter's per-token cost (usually a few cents for a small site).

Get a key at openrouter.ai → Keys, then paste it into the “AI engine” step of the wizard. It stays in memory for that session only; it is never written to our database.

The build wizard

The nine steps:

• Site scope — city, state or national (decides how location pages are built).
• Business details — your NAP, hours, licenses and owner info.
• Domain — baked into canonicals, schema and the sitemap (optional).
• Niche & keywords — steer every headline and title.
• Services — one page each, with an AI-suggestion helper and a cannibalization guard.
• Coverage areas — one page each, with a doorway-footprint guard and mention-only tier.
• Design & media — pick a theme, brand colors, logo, photos and real reviews.
• AI engine — your key, the model, and optional blog posts.
• Review & build — confirm and generate.

What's in the ZIP

Every build produces a clean static site — no framework, no build step:

• Unique per-page copy with answer-first sections and FAQs
• LocalBusiness + Service + FAQ + Breadcrumb schema as one connected entity graph
• sitemap.xml, robots.txt, llms.txt, a 404 page
• Optimized WebP images and an Open Graph image
• site-config.json and a deployment README.md

Deploying your site

Unzip and upload the folder anywhere static. The included README has one-click steps for Netlify, Cloudflare Pages, Vercel and GitHub Pages, plus how to submit your sitemap in Google Search Console. The fastest path: drag the folder onto app.netlify.com/drop.

Projects & rebuilding

Each build saves its full wizard configuration to your account (never your key). From My Sites you can reopen a project, duplicate it, change the city or NAP, and regenerate — ideal for multi-location or rank-and-rent workflows. Completed ZIPs are stored in your account for re-download.

Plans & limits

The Free plan allows 1 build a month with up to 15 pages and a small footer watermark. Pro raises this to 20 builds and 120 pages with no watermark; Agency is unlimited with a white-label README and team seats. See pricing for details. Limits are enforced server-side before each build.

Troubleshooting

A page failed to generate. The build tolerates per-page failures and packages the rest; you can rebuild the project to retry.

“Build not allowed.” You've hit your plan's monthly build limit or page cap — reduce services/areas or upgrade.

Keep this tab open while a build runs — generation is happening locally in your browser.