seo-geo-mcp-server

Full On-Page SEO Audit

seo_audit

Read-onlyIdempotent

Audit any page's SEO across seven weighted areas—meta, headings, content, structured data, images, links, crawlability—and get a 0-100 score, A-F grade, and prioritized fixes.

Instructions

Fetch a page once and audit it across seven weighted sections — meta tags & social preview, heading structure, content quality, structured data, image SEO, links and crawlability — returning a 0–100 score, an A–F grade and a prioritised fix list.

This is the tool to start with for any "how is this page doing for SEO?" question; drill into the single-purpose tools afterwards for detail.

Args:

url (string): the page to audit.
include_geo (boolean): also score AI answer-engine readiness (default false).
check_broken_links (boolean): sample-verify that links resolve (default false).
response_format ('markdown' | 'json'): output format (default 'markdown').

Returns: { score, grade, indexable, sections[{id, label, score, grade, weight, issues[]}], top_recommendations[], geo, findings[] }.

Example: "Audit the SEO of https://example.com/pricing" -> seo_audit(url="https://example.com/pricing"). Note: a noindex page or a site-wide robots.txt block caps the score, because nothing else matters until that is fixed. Errors: returns an error if the URL is unreachable, non-HTML, or returns an HTTP error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Page URL to analyse, e.g. 'https://example.com/blog/post'. The scheme defaults to https://.
`include_geo`	No	Also score GEO (AI answer-engine) readiness. Adds ~2 requests.
`response_format`	No	Output format: 'markdown' for a human-readable summary (default) or 'json' for the full structured payload.	markdown
`check_broken_links`	No	Sample up to 25 links and verify they resolve. Slower, but catches dead links.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`geo`	Yes
`url`	Yes
`grade`	Yes
`score`	Yes
`status`	Yes
`fetch_ms`	Yes
`findings`	Yes
`sections`	Yes
`final_url`	Yes
`indexable`	Yes
`redirect_hops`	Yes
`top_recommendations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.2.0Sep 16, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / properties / findings / $ref

Removed value: -"#/properties/geo/anyOf/0/properties/findings"

addedOutput schema / properties / findings / items

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "severity": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "severity",
+    "message"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / findings / type
```
Added value: +"array"
```

First observedv1.0.0Aug 3, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only/idempotent behavior, and the description adds meaningful behavioral context beyond that: it fetches the page once, caps the score on noindex or robots-blocked pages, and reports errors for unreachable, non-HTML, or HTTP-error responses. It also tells the agent what payload shape to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized for a comprehensive tool: purpose, usage rule, args, return shape, example, and critical edge-case note each earn their place. It is front-loaded with the most important scoping information and remains scannable despite covering a lot of ground.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter aggregator with many siblings, the description covers selection context, output format, error behavior, and a crucial caveat (noindex/robots-block caps the score). The return structure is spelled out in prose, and the error note addresses the main call-time risks, so an agent has what it needs to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters, defaults, and side effects. The description's Args section largely restates that information, but the natural-language example ('Audit the SEO of https://example.com/pricing' -> seo_audit(url=...)) adds a concrete invocation pattern beyond the structured schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Fetch a page once and audit it across seven weighted sections', enumerating exactly what is audited and the outputs (0–100 score, A–F grade, prioritised fix list). It also distinguishes itself from the many single-purpose siblings by positioning itself as the starting audit tool, so an agent can tell it apart from tools like meta_tags_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'This is the tool to start with for any "how is this page doing for SEO?" question; drill into the single-purpose tools afterwards for detail.' This gives a clear selection rule and points to follow-up tools, though it does not enumerate exactly which sibling to choose for each specific follow-up need.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server