Trakis SEO checks

66 technical SEO and AI-readiness checks: what each looks at, why it matters, how to fix it

Should I use this

Quality & Safety

A
Description quality
93%
Schema completeness
97%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~461Tokens (tool definitions)
~791 BTypical response size
Minimal attention impact (0.36% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "seo-checks": {
      "url": "https://trakis.io/mcp"
    }
  }
}

Remote endpoints

https://trakis.io/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_checks(query)

Find Trakis checks by a word or a problem, when you do not know the check's code. Searches titles, what each check looks at, why it matters and where the problem usually comes from. Returns up to 10 checks, best matches first.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "A word or short phrase, e.g. \"canonical\", \"robots.txt\", \"duplicate title\", \"structured data\"."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}
🟢explain_check(id)

The full explanation of one Trakis check: what it looks at, why it matters, where the problem usually comes from, how to fix it (with a worked example when there is one), how to verify it without Trakis, and how an audit counts it.

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "The check's code, e.g. \"CRAWL-008\" or \"onpage-005\". Case does not matter."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}
🟢list_checks(category, severity)

Every check a Trakis audit runs, optionally only one category or one severity, with its code, title and a link to its explanation.

Input Schema

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "enum": [
        "crawlability",
        "indexation",
        "onpage",
        "content",
        "structured-data",
        "links",
        "performance",
        "ai-readiness"
      ],
      "description": "Only the checks of this category."
    },
    "severity": {
      "type": "string",
      "enum": [
        "critical",
        "warning",
        "notice"
      ],
      "description": "Only the checks of this severity."
    }
  },
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools