Fix a failing middleware check - Dedica

When the middleware check fails, Dedica tells you what to fix. The check fetches https://<your domain>/.well-known/dedica.json and looks for a recent heartbeat. During onboarding the dashboard runs it every 15 seconds.

Result	What it means	How to fix it
Connected	Your middleware is connected.	Nothing to do.
No heartbeat	Your site serves the Dedica file, but the middleware hasn’t sent a heartbeat in the last 15 minutes.	Check the middleware is configured with your current token.
Redirects elsewhere	`/.well-known/dedica.json` redirects to another site.	The middleware must answer on your domain itself.
Blocked	Your site answered with an error status: a firewall or bot protection is probably blocking the check before the middleware runs.	Allow the user agent `DedicaBot/0.1 (+https://getdedica.com/bot)`, or the path `/.well-known/dedica.json`.
Unreachable	Dedica couldn’t reach the well-known file.	Check your site is up on HTTPS.
Wrong site id	The middleware is set up for a different site.	Configure it with the site id shown in Dedica.
Not in front	The middleware is running, but requests to your domain don’t go through it.	Route your site’s traffic through it. On Cloudflare, add the routes `example.com/` and `www.example.com/` to the worker and make sure the DNS records are proxied (orange cloud).
Not installed	Dedica hasn’t heard from your middleware yet.	Deploy it with your site id and token. The dashboard keeps checking.
Stopped	The middleware used to send heartbeats but has stopped, and your site doesn’t serve the Dedica file.	Check it is still deployed and in front of your site.

”Verified live” doesn’t complete

Once serving is on, Dedica fetches /llms.txt and one of your agent pages (its .md URL) from your domain with the user agent DedicaBot/0.1 (+https://getdedica.com/bot), and compares them with what it serves. If a path doesn’t match, the check says why:

Result	What it means	How to fix it
Your site answered with an error	A firewall or bot protection blocked the check, or your site returned an error.	Allow the user agent `DedicaBot/0.1 (+https://getdedica.com/bot)`.
Agents get an older version	The middleware serves Dedica’s content, but a recent change hasn’t reached it yet.	Wait a minute or two; it refreshes on its own.
Agents get your site’s own response	The answer came from your site, not from Dedica.	Check the middleware is connected and in front of your site. It picks up serving within a minute of you turning it on.

The middleware gives Dedica’s check the agent version at .md URLs, even when your site has its own .md files there. At normal page URLs it gets your normal page, like other monitors.

On the Cloudflare Worker, open https://<your domain>/__dedica/status to see whether the worker is configured, and run npx wrangler tail to watch its [dedica] logs.