Integrations built and maintained by other people, in their own repositories. They are listed here so you can find them. They are not part of OpenCode SEO: the maintainer has not audited their code, does not ship or update them, and cannot support them. Read an integration's code and install script before you run it, the same as for any third-party tool, and send questions and bug reports to its own repository.
OpenCode SEO does not bundle third-party paid services as first-party extensions. A separate repository listed here is the way to offer one.
| Integration | Maintainer | What it does | Cost |
|---|---|---|---|
| claude-seo-proxlane | @scarsam (maintains Proxlane) | Fetches pages through a self-hosted Proxlane gateway that fails over between scraping providers and reports why a page failed (gone, blocked, rate limited). | Gateway is self-hosted; the scraping providers behind it are paid. |
Open an issue with a link to the repository. An integration is listed when it:
- Lives in its own public repository with an open-source licence.
- Says plainly who maintains it and whether the maintainer sells the service it connects to.
- Says what it costs to use, including any paid API behind it.
- Carries no tracking or affiliate links (no UTM parameters, no referral codes) in skill files, scripts or docs.
- Installs only into the user's own directories, has an uninstall script, and does not change OpenCode SEO's files or dependencies.
- Keeps credentials out of the repository and out of command output.
- Treats fetched page content as untrusted data in its skill instructions.
A listing is removed if the repository is archived, stops meeting these points, or is reported for behaviour its README does not disclose.
"Official SEO MCP Servers" in docs/MCP-INTEGRATION.md is a different list:
it holds servers published by the data provider itself.