OpenSEO ↗
OpenSEO · hosted usage-priced SEO/GEO product with explicit AI visibility and prompt research
← All toolsAnother direction / 01 Another direction / 02 Another direction / 03
The selection guideSource-backed research ↗
Content Optimization / Open-source Claude plugin and MCP-connected SEO/GEO skill collection.
Open SEO MCP Skills
Open-source SEO and GEO skills for Claude on a connected SEO MCP server
SEO and GEO agent workflowsAI visibility researchOpen-source Claude plugin
Why it stands out
MIT-licensed and inspectable skill layer.
Source review: · Public-source research, not a hands-on test
The repository is free and open source; hosted Ryze MCP access and external data services are separate commercial or operational dependencies.
↗ Best for
Technical SEOs and developers using Claude or Claude Code.
! Know before you buy
AI-referral reports can identify detectable AI-engine traffic and cited pages; complete prompt-level coverage is not established.
01 / Editorial assessment
Is Open SEO MCP Skills for you?
The AICiteKit take
Open SEO MCP Skills is a useful developer-led workflow layer for bringing SEO and GEO questions into Claude. Its public MIT repository, explicit skill list, and connection to Search Console, GA4, Google Ads, and DataForSEO make the scope inspectable. It is not a standalone visibility dashboard: hosted connector access, external data costs, permissions, and measurement design remain separate responsibilities. Shortlist it for an inspectable MCP experiment; choose a dedicated visibility platform when you need recurring prompt panels, model-by-region sampling, historical answers, exports, or governance.
A good fit if you are…
- Technical SEOs and developers using Claude or Claude Code.
- Agencies building repeatable client audit and briefing workflows.
- Teams that prefer first-party GSC and GA4 observations.
- Privacy-conscious teams able to review source code and permissions.
Consider another option if…
- Non-technical buyers wanting a turnkey dashboard.
- Teams requiring complete prompt monitoring across many models and regions.
- Regulated organizations needing independently verified security and retention evidence.
- Buyers expecting guaranteed rankings, citations, traffic, or revenue outcomes.
02 / Scope, not promises
Features & coverage
- Documented skills
SEO audit, keyword research, rank tracking, competitor gap, backlink check, AI visibility, content brief, and content optimization.
Archived research · Repository README checked 2026-10-27.Research excerpt · Quick facts- Data boundary
Repository describes Google Search Console, GA4, Google Ads, and DataForSEO inputs through the Ryze MCP connector.
Archived research · Repository and Ryze pages checked 2026-10-27.Research excerpt · First-party and external data sources- Independent evidence
GitHub topic and issue pages provide activity and discoverability context, not a representative satisfaction sample or GEO efficacy validation.
Archived research · Public activity pages checked 2026-10-27.Research excerpt · Evidence snapshot
Claude and MCP workflows
The repository documents a Claude plugin and MCP connection for repeatable SEO and GEO tasks. This supports agent access, not a guarantee that every Claude client exposes every feature.
First-party and external data
Search Console and GA4 can provide a site's observed data, while Google Ads and DataForSEO extend the workflow. Confirm scopes, retention, limits, and provider charges.
AI visibility through referral analytics
The AI-visibility skill is described around AI referral reports and cited pages. That is narrower than complete prompt sampling and cannot prove causal visibility or revenue lift.
Evidence boundary
Public repository activity supports existence and inspectability, while independent activity signals do not validate citation accuracy, rankings, traffic, or business outcomes.
A focused evaluation workflow
- Review the MIT repository and permissions.
- Install the plugin or copy the skills.
- Connect the Ryze MCP endpoint and bounded data sources.
- Run one representative audit, AI-visibility, or content-brief task.
- Record the time window, source accounts, output, and changes.
- Validate hosted, provider, retention, and governance costs before scaling.
03 / Commercial boundaries
Pricing & limits
Terms below reflect the 2026-10-27 source review, not a new live quote. Confirm currency, billing term, tax and required scope with the provider.
- License
MIT license shown in the public repository.
Archived research · Repository checked 2026-10-27.Research excerpt · Quick facts- Hosted commercial boundary
Ryze pricing page lists SEO Starter at $129/month and Traffic Printer at $599/month; these are hosted product terms, not a repository price.
Archived research · Ryze pricing checked 2026-10-27.Research excerpt · Pricing and limits
Pricing context & qualifications
The open-source skills are free under MIT. The hosted Ryze pricing page checked 2026-10-27 lists SEO Starter at $129/month and Traffic Printer at $599/month, but does not establish a standalone connector price, universal prompt quota, retention duration, or total external data cost. Confirm current hosted terms before scaling.
04 / The tradeoffs
Strengths & weaknesses
Reasons to shortlist
- MIT-licensed and inspectable skill layer.
- Explicit SEO/GEO skills for Claude and Claude Code.
- Connects workflows to first-party search and analytics data.
- Clear separation between free source code and hosted service dependencies.
Reasons to pause
- The repository is not a complete hosted dashboard.
- Public sources do not establish universal prompt quotas, retention, or API limits.
- Independent user evidence is sparse and activity signals are not reviews.
- AI-referral reporting is narrower than complete prompt-level citation monitoring.
AI-referral reports can identify detectable AI-engine traffic and cited pages; complete prompt-level coverage is not established.
05 / Choose by the job
Alternatives to consider
Editorial fit comparisons—not performance rankings or claims that one option always wins.
DataForSEO ↗
DataForSEO · underlying data APIs for a custom data and agent layer
SE Visible ↗
SE Visible · dedicated recurring AI-search visibility monitoring
06 / What we can substantiate
Reviews & evidence
Public feedback is sparse. GitHub activity provides a strong existence and community-interest signal, while the GEO topic listing and four visible repository issues provide discoverability and implementation context. These are not representative customer reviews and do not validate the AI-visibility module or business outcomes.
AICiteKit assessment: public-source research, not a hands-on product test. Official materials establish stated scope; reviews are dated and may concern the broader platform. Neither establishes guaranteed citations, traffic or revenue.
Sources & original verification dates
| Source | Evidence type | Checked |
|---|---|---|
| Open SEO MCP Skills repository ↗ | Official public repository | |
| Ryze pricing ↗ | Official pricing page | |
| Ryze SEO product page ↗ | Official product page | |
| Ryze Claude connector guide ↗ | Official integration guide | |
| GitHub GEO topic listing ↗ | Independent discovery and activity surface | |
| Repository issues ↗ | Public community activity surface |
Original review evidence & date context
Preserved from the published research. Dates, review counts and product-scope qualifications below have not been refreshed by this layout migration.
Evidence snapshot
| Source | Public signal | What it supports | Confidence |
|---|---|---|---|
| Official repository | MIT repository, documented skills, public activity | Product existence, license, and stated scope | High for repository facts; not efficacy evidence |
| Ryze pricing | SEO Starter $129/month and Traffic Printer $599/month | Hosted commercial boundary | High for checked vendor page |
| Ryze SEO page | GSC/GA4, content changes, AI-search positioning, approval workflow | Vendor-stated hosted behavior | Medium; vendor evidence |
| GitHub GEO topic | Current topic listing and activity signal | Independent discovery and activity context | Medium; not a review |
| Repository issues | Four public issues visible when checked | Public implementation questions | Low-to-medium |
No checked source independently validates AI citation accuracy, GEO outcomes, security, compliance, uptime, or revenue impact.
Research notes & unresolved discrepancies
- Official repository, Ryze pricing, SEO, and connector pages checked 2026-10-27.
- GitHub GEO topic page and repository issues used for independent/activity context, not quality endorsement.
- No checked source proves citation accuracy, rankings, traffic, conversions, revenue lift, security audit, or enterprise SLA.
Layout migration: October 4, 2026. The original MDX research is retained in the repository; this reorganization does not refresh its factual verification dates.