Skip to main content
Glama
seonix-ai

Seonix SEO MCP

Official
by seonix-ai

audit_site

Audit any website for SEO, GEO/AEO, and speed problems. Receive CMS-neutral recommendations to fix issues without modifying the site.

Instructions

READ-ONLY, platform-agnostic site auditor. Works on ANY website (WordPress, Shopify, custom, static — anything). Audits SEO, GEO/AEO and speed: it SHOWS problems and gives CMS-neutral 'how it should be' recommendations — it does NOT modify the site; you decide whether/how to fix. Discovers pages via sitemap.xml (polite ~1 req/sec, default 25 / max 100 pages), fetches each page's HTML, and runs: title/meta-description length, image alt text, H1 count, emoji/overlong/before-H1/broken-hierarchy headings, mixed content, JSON-LD Article author/dates + structured-data validity, AI-restrictive meta robots, /llms.txt, robots.txt AI-bot blocking, canonical, viewport, Open Graph — PLUS always-on speed heuristics (render-blocking head resources, images missing width/height, un-lazy offscreen images, large inline blocks, page weight, DOM size). When PAGESPEED_API_KEY is set, it also runs Google PageSpeed Insights (Core Web Vitals + Lighthouse opportunities) on a small sample of pages. Returns a per-pillar summary {seo, aeo, speed} (score + health_label + issue count) and a flat issues[] where each item = {code, category, severity, url, evidence, why, target_state, recommendation}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYesThe site to audit, e.g. https://example.com
max_pagesNoMax pages to crawl from the sitemap (default 25, cap 100).
speed_sampleNoHow many pages to measure with PageSpeed Insights (homepage + representative pages). Default 3. Ignored unless PAGESPEED_API_KEY is set; HTML speed heuristics always run on every fetched page.
Behavior5/5

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

Despite no annotations, the description thoroughly discloses behavior: read-only, polite crawling (1 req/sec), default/max pages, reliance on sitemap.xml, detailed checks, speed heuristics always run, PageSpeed Insights conditional on API key. No hidden traits are omitted.

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 description is long but well-structured with lists and clear sections. Every sentence adds value, though some redundancy could be trimmed. It is front-loaded with key identity and behavior, making it scannable.

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?

Given no output schema, the description fully explains the return format (per-pillar summary with score/health/issue count, and issues array with fields). It also covers edge cases like conditional PageSpeed and default limits. The tool's complexity is well-addressed.

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

Parameters5/5

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

Schema coverage is 100%, and the description adds meaningful context beyond schema descriptions. It explains max_pages has a cap of 100, speed_sample is ignored without API key, and HTML speed heuristics always run. This enriches parameter understanding.

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 clearly states it is a 'READ-ONLY, platform-agnostic site auditor' and explicates what it audits (SEO, GEO/AEO, speed) and its non-modifying nature. The verb 'audits' and resource 'site' are specific, and the scope is well-defined. Although sibling 'speed_audit' exists, the description indirectly differentiates by covering a broader scope.

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

Usage Guidelines3/5

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

The description says 'Works on ANY website,' implying broad applicability, but provides no explicit when-to-use or when-not-to-use guidance. It does not mention the sibling tool 'speed_audit' or contrast it. Usage is implied but not explicitly directed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/seonix-ai/seonix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server