Rankplus API Verified

{
  "service_type": "platform",
  "base_url": "https://rankplus.io",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "model": "free",
      "currency": "USD",
      "note": "No account and no API key required; read-only access."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Search Rank+ blog articles",
    "Retrieve a single article rendered as Markdown",
    "Run basic SEO checks on a page with a score",
    "Extract a page's JSON-LD structured data",
    "Preview search-result appearance for a page",
    "Read Open Graph and Twitter meta tags",
    "Measure mobile and desktop page speed",
    "Validate hreflang tags",
    "Produce H1–H6 heading outline",
    "Score readability of text or a page",
    "Score headlines with suggestions",
    "Look up domain registrar, registration dates, and age",
    "MCP-compatible interface for AI assistants (ChatGPT, Gemini, Grok, Claude, Copilot)"
  ],
  "raw_analysis": "Rankplus is a free SEO tooling platform whose interface here is exposed as an MCP-compatible service rather than a documented public REST API. It provides read-only SEO diagnostics and knowledge-base retrieval for AI assistants: article search/read from the Rank+ blog, on-page SEO scoring, JSON-LD extraction, search-result previews, Open Graph/Twitter tag inspection, mobile/desktop speed measurement, hreflang validation, heading outlines, readability/headline scoring, and domain registrar/whois-style lookups.\n\nMaturity: Early/lite. The vendor profile shows no explicit features list, no documented REST endpoints, no integrations, and no pricing beyond 'free'. No account or API key is required, which strongly suggests a low-friction, public, read-only service intended for AI agent consumption. Rate limits are not disclosed; if consumed via a public MCP endpoint, expect undisclosed throttling.\n\nWho it's for: AI assistant users and developers who want SEO diagnostics embedded in chat/agent workflows without authentication. Limited appeal for enterprises needing SLAs, bulk access, or write operations.\n\nTechnical notes: Because the description says 'MCP' rather than 'REST API', the base URL (https://rankplus.io) is likely a website, not an API host. A real integration would go through the MCP server endpoint (e.g., an /mcp path or a separate host), which is not specified. No swagger/OpenAPI docs, no auth scheme, no structured error contract published. Treat endpoints as unknown and require discovery before building.\n\nRisk and limitations: Free tier, no guarantees, no authentication or rate-limit documentation, and vendor maturity appears low. Best used for non-critical, advisory SEO checks. Capabilities are broad enough to be useful for on-page auditing and lightweight content research."
}

3/3 tests passed

```json
{
  "overall": 77,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 8.5,
    "response_parseability": 8.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 9.5,
    "latency": 6.5,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "model": "free",
    "currency": "USD",
    "monthly_cost": 0,
    "notes": "The MCP/read-only tools need no account and no API key. Pricing for the full Rank+ WordPress SaaS was not provided."
  },
  "issues": [
    "The homepage loaded in 930ms, which falls in the <2s band. The robots.txt and llms.txt endpoints were faster (452ms and 312ms).",
    "The homepage's default language is Hebrew (lang=he, dir=rtl). Some agents may find that a friction point when recommending it to English-speaking users, although English is supported.",
    "The tool set is read-only, so agents can't trigger the core SaaS functions (automated SEO, content generation, site management) through the free interface.",
    "No information was given on rate limits, uptime guarantees, or a status page, so reliability is hard to verify.",
    "Only 3 checks were run, and none exercised the MCP endpoint directly. Tool behavior and error handling are unverified.",
    "The MCP tools overlap with free SEO utilities from many other providers, so the differentiator is unclear from the data."
  ],
  "recommendations": [
    "Publish documentation for the MCP endpoint, including tool schemas, example calls, error responses, and rate limits.",
    "Add a public status page and state uptime expectations.",
    "Explain in llms.txt how the free read-only tools relate to the paid SaaS, and how users can upgrade or connect a WordPress site.",
    "Serve an English default (or content negotiation) for the homepage to help agents recommend it to non-Hebrew users.",
    "Reduce homepage response time to under 500ms with caching or a CDN.",
    "Consider an authenticated API tier so agents can take write actions (e.g., apply SEO fixes) on behalf of users."
  ]
}
```