Skip to content

Legacy integration manifest endpoint returns HTML

This check requests /.well-known/ai-plugin.json and reports an HTML response where a JSON manifest was expected. It examines that endpoint response; it does not establish that a current AI service automatically requests it.

Why this matters

A client configured to consume JSON from this exact endpoint cannot use an HTML application shell as that manifest. Whether this matters depends on a real integration. The response is not proof of lost search visibility or AI citations.

How to fix it

Identify whether any supported integration still requires the endpoint. If it does, serve the documented JSON response and verify it with that client. Otherwise retire the unused route with an appropriate response; do not invent a manifest or expose private APIs to satisfy an obsolete check.

Turn website findings into an action plan

Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.

Start Full Audit