Trakis SEO checks
66 technical SEO and AI-readiness checks: what each looks at, why it matters, how to fix it
使うべきか
品質と安全性
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"seo-checks": {
"url": "https://trakis.io/mcp"
}
}
}リモートエンドポイント
https://trakis.io/mcpstreamable-httpできること
ツール一覧
ツール（3）
🟢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.
入力スキーマ
{
"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.
入力スキーマ
{
"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.
入力スキーマ
{
"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
}コミュニティ
エビデンス