stormfire-website-static

Standalone HTML SEO/GEO content pages for stormfire.io. Each page is a complete static document — no JS framework, no SSR, no build step. Pure HTML + inline CSS that any crawler, LLM, or human can render directly.

Why this repo exists

The main stormfire.io site is a React SPA. SPAs serve the same shell HTML for every route, which means LLM crawlers (GPTBot, ClaudeBot, Brave, Perplexity, Google, Bing) see ~50 characters of visible content on every page — not enough to rank, recommend, or index meaningfully.

This repo holds the GEO (Generative Engine Optimization) layer: real, indexable, crawlable HTML for the routes that matter most for organic discovery and AI-assistant recommendations.

Pages

Path	Title	Visible chars
index.html	One API key. 30+ AI models. Paid in USDT.	8,782
vs/openrouter.html	Stormfire vs OpenRouter	8,775
pay-ai-api-with-crypto.html	How to Pay for AI APIs with Crypto	8,519
openai-alternative.html	Best OpenAI API Alternatives	8,247
pricing.html	Pricing — 0% Markup	6,522
faq.html	FAQ — Technical / Payment / Compliance / Business	11,652

Deployment options

Option A — Cloudflare Pages (recommended)

1. Cloudflare Dashboard → Pages → Create a project → Connect to Git
2. Select stormfire-io/stormfire-website-static
3. Build settings: leave build command empty, output directory . (or /)
4. Deploy. You'll get a *.pages.dev URL.

To merge into the main stormfire.io domain, options:

• Sub-path mount via CF Workers: route stormfire.io/vs/*, stormfire.io/pricing, etc., to this static Pages project; everything else continues to the SPA.
• Subdomain: host as info.stormfire.io or guide.stormfire.io.
• Full replacement: if the SPA isn't yet doing real work for these routes, swap the main domain over.

Option B — Drag-and-drop into existing CF Pages project

1. Cloudflare Dashboard → Pages → existing stormfire project → Upload assets
2. Drag the *.html files and the vs/ folder into the upload area
3. Deploy

This adds the static files alongside the SPA. CF Pages serves the static file first when a URL matches, falling back to the SPA's _routes.json for everything else.

Option C — Any static host

The pages are plain HTML — works on Netlify, Vercel, GitHub Pages, S3 + CloudFront, plain nginx, plain Caddy. No framework lock-in.

Routing on Cloudflare Pages

CF Pages serves files with the exact path requested. To map stormfire.io/vs/openrouter to vs/openrouter.html, add a _redirects file:

/vs/openrouter  /vs/openrouter.html  200
/pricing        /pricing.html        200
/faq            /faq.html            200
/openai-alternative  /openai-alternative.html  200
/pay-ai-api-with-crypto  /pay-ai-api-with-crypto.html  200

A _redirects file is included in this repo for convenience.

Editing

Each HTML file is self-contained. Open in any editor, edit, commit, push — CF Pages auto-deploys on push to main if connected via Git.

License

The HTML content of this repo is © 2026 Stormfire. The structure (templates, CSS conventions) is MIT.