AEO Lookup

What AEO Lookup does

AEO Lookup evaluates public web pages against several answer-engine optimization signals. Its checks cover whether AI crawlers can access a page, whether the page contains JSON-LD, whether an llms.txt file is available, and whether the page is ready to support answers generated from its content.

The service is aimed at workflows that need to inspect publicly reachable pages rather than private application data. Results can be consumed as JSON or requested through MCP, allowing an MCP-compatible agent to use the checks as part of a broader page-analysis workflow.

How it works

A caller submits a public-page check through the JSON API or connects an MCP client to the remote endpoint at https://aeolookup.com/mcp. AEO Lookup performs the advertised checks and returns structured output through the selected interface.

The service does not require an API key. That makes the connection configuration relatively small: the client needs the remote MCP address, or the JSON API endpoint used by the application making the request.

Setup and configuration

Use the remote MCP endpoint:

https://aeolookup.com/mcp

For applications that prefer direct HTTP requests, use the AEO Lookup JSON API. The service is described as public and keyless, so no authentication token is needed for the available checks.

Configuration depends on the consumer. An MCP client should be given the remote endpoint, while an application using the API should send requests to the API provided by AEO Lookup and handle its JSON responses.

Tools and capabilities

AEO Lookup focuses on four page-level checks:

• AI crawler access: inspect whether AI crawlers can reach a public page.
• JSON-LD: check for structured data expressed in JSON-LD.
• llms.txt: check for the presence or availability of an llms.txt resource.
• Answer readiness: evaluate signals related to a page’s suitability for AI-generated answers.

The same core purpose is available through two access paths: a JSON API for application integrations and a remote MCP interface for agent tool use.

Limitations and notes

Checks are scoped to public pages. The service is intended for examining externally reachable content and the specific signals listed above; it should not be treated as a general website crawler, private-page auditor, or broader SEO platform. Access is available without an API key, but callers still need to use either the published JSON API or the remote MCP endpoint.