Skip to main content
Glama
Akxan

google-seo-mcp

by Akxan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

On-page SEO audit of a URL

page_audit
Read-onlyIdempotent

Fetch any webpage and audit on-page SEO: redirects, metadata, robots, canonicals, headings, images, links, schema, and more. Flags issues to fix for better search visibility.

Instructions

The general on-page check; pair it with structured_data_audit for schema, geo_page_score for AI-answer readiness and eeat_audit for trust signals. Fetch a page like a crawler and report: final URL and redirect chain, status, title, meta description, robots (meta + X-Robots-Tag), canonical, lang/hreflang, Open Graph, RSS/Atom feeds, favicon (declared icons, apple-touch-icon, manifest, theme-color, and a live check that it is square, >=48x48 and crawlable by Googlebot/Googlebot-Image, which is what the mobile result icon needs), H1/H2/H3 outline, images missing alt, internal/external/nofollow link counts, word count, JSON-LD schema types, HTML size and fetch time, plus a list of flagged issues. Works for any site, no authorization needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
maxHeadingsNoHow many H1-H3 headings to include in the outline.
checkFaviconNoFetch the favicon and robots.txt to verify size, shape and crawlability (2 extra requests).
maxImagesMissingAltNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / checkFavicon
      Added value: +{
+  "default": true,
+  "description": "Fetch the favicon and robots.txt to verify size, shape and crawlability (2 extra requests).",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral detail: it fetches a page like a crawler, reports the redirect chain and flagged issues, and explicitly guarantees no authorization is needed. It does not contradict the annotations, though it does not mention rate limits or timeout behavior.

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

Conciseness4/5

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

The definition is front-loaded with the scoping phrase and sibling routing before the detailed output list. It is a single dense sentence with many enumerated items, but every item contributes concrete information. It earns its length, though it could be more skimmable with short clauses or bullets.

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

Completeness4/5

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

With no output schema, the description does the work of enumerating the return categories, covering redirects, status, metadata, headings, link counts, schema types, sizes, and flagged issues. It does not describe the response envelope or error behavior, and the maxImagesMissingAlt parameter remains ambiguous, but for a read-only, no-auth audit the tool is effectively fully specified.

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?

The schema documents maxHeadings and checkFavicon, and the description reinforces both with outline and favicon validation detail. However, schema coverage is only 50%, and maxImagesMissingAlt has no schema description; the description only mentions 'images missing alt' in the output list, leaving the parameter's limiting role implicit. The description adds some meaning but does not fully compensate for the coverage gap.

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?

States a specific action ('on-page SEO audit of a URL') and immediately frames it as 'the general on-page check', while enumerating the full report contents. This makes it clearly distinguishable from specialized siblings like structured_data_audit, geo_page_score, and eeat_audit without needing to inspect them.

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

Usage Guidelines5/5

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

Explicitly names sibling tools and the condition for pairing with each: schema, AI-answer readiness, and trust signals. It also states 'works for any site, no authorization needed', which removes the main usage prerequisite. An agent gets direct routing guidance rather than having to infer when this tool applies.

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

Deploy Server

Other Tools