Skip to main content
Glama
AutomateLab-tech

automatelab-ai-seo

Official

Audit canonical link integrity

audit_canonical
Read-onlyIdempotent

Audit canonical link integrity including presence, self-reference, cross-domain mismatches, trailing-slash hygiene, and og:url consistency for debugging duplicate content.

Instructions

Audit a page's canonical link integrity: presence, self-reference, cross-domain mismatches, trailing-slash hygiene, and og:url consistency.

Read-only. One HTTP GET to fetch the HEAD section.

Deterministic, rule-based; no LLM.

When to use: a focused canonical-only audit (e.g. debugging a duplicate-content issue). For a full HEAD audit including OpenGraph, hreflang, noindex, title, use check_technical. For everything-on-a-page, use audit_page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic URL whose canonical link tag and og:url consistency you want to audit. Must be a fully-qualified http(s) URL. The tool fetches the URL (following redirects) and inspects only the <head> section; the body is not parsed.
respect_robotsNoIf true (default), respect robots.txt before fetching. Set false only for auditing your own site where you've intentionally blocked crawlers.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
og_urlYes
findingsYes
canonicalYes
fetched_atYes
cross_domainYesWhether the canonical points to a different domain.
self_referencingYesWhether the canonical points to the audited URL.
Behavior5/5

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

Adds behavioral context beyond annotations: read-only, one HTTP GET, only HEAD section, deterministic and rule-based. No contradiction with annotations.

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?

Concise, front-loaded with purpose. Three short paragraphs, no fluff. Every sentence adds value.

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 output schema exists, description need not explain return values. It covers scope, behavior, and usage conditions sufficiently. Complete for the tool's complexity.

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

Parameters4/5

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

Schema coverage is 100%, so baseline 3. Description adds extra context for the url parameter (must be fully-qualified, follows redirects, only inspects <head>), which adds value.

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?

Description clearly states the tool audits canonical link integrity including presence, self-reference, cross-domain mismatches, trailing-slash hygiene, and og:url consistency. It distinguishes itself from sibling tools like audit_page and check_technical.

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 states when to use (focused canonical-only audit) and when not to (use check_technical for full HEAD audit, audit_page for everything-on-a-page). Provides concrete alternative tool names.

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/AutomateLab-tech/ai-seo-mcp'

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