OpenSEO Studio
SEO writing for developers who hate bloat.

OpenSEO Studio is a client-side SEO writing tool that stays out of your way.

No backend. No accounts. No tracking. You bring the OpenRouter key, it generates clean Markdown, and nothing leaves your browser except the API call you authorize.

Why this exists

Most SEO writing tools are built like SaaS funnels. OpenSEO Studio is not.

Bloated dashboards, feature walls, and upsell traps get in the way of writing. Accounts everywhere mean another password and another profile to delete. Black-box AI decisions leave you guessing what happens to your prompts and your data.

OpenSEO Studio is deliberately small. No onboarding maze, no hidden switches, no sales metrics. Open the page, drop in your key, write, and move on.

  • Fat SEO tools with features you do not need
  • Accounts and subscriptions for basic output
  • Black-box AI decisions you cannot audit
  • Locked content formats that fight your stack
  • Tracking scripts and surprise charges

How it works

Everything runs in your browser. Nothing else.

  1. Open the app
  2. Paste your OpenRouter API key
  3. Choose a model
  4. Generate content
  5. Copy clean Markdown

API calls go directly from the browser to OpenRouter. No proxy. No server storage.

Core features

Focused on shipping content, not dashboards.

Security & BYOK

You keep the keys and the control.

BYOK means you supply the OpenRouter API key. It stays in your browser. Optionally store it in localStorage for convenience or keep it ephemeral for every session.

Every call goes straight from your browser to OpenRouter. No proxying, no hidden servers, no data collection. You decide the model, you control the spend, and you can audit the behavior by reading the source.

  • Key never leaves the browser
  • Optional localStorage, no database
  • No server-side logs or metrics
  • Costs stay in your control
  • Inspectable source code

Open-source commitment

Built in public under the MIT license.

OpenSEO Studio lives on GitHub. Fork it, self-host it, or contribute. The codebase is small and readable on purpose so you can verify every request path and adapt it to your workflow.

  • MIT licensed
  • Public repository
  • Forkable and self-hostable
  • Contributions welcome

If this matches how you like tools to work, you already know what to do.