Vercel Web Analytics records no page views

Another rule still answers the analytics path

Already tried: A catch-all 404 route is swallowing the analytics path

Something earlier than the filesystem handler still matches: a catch-all rewrite or route in vercel.json, routing middleware, or a framework catch-all page.

Do this

  1. List every rewrite, route and middleware matcher that could match the script path, in the order the platform evaluates them.
  2. Exclude the analytics path from each catch-all (or narrow the catch-all), then redeploy.

Verify: The script URL returns 200 with JavaScript.

Still unknown: Which rule types cause this in practice is unknown; a confirmed example would turn this into a verified branch.

Tried these steps? Report the result

Optional. One request, no account, no free text. Published only as self-reported, unverified counts; it does not change any ranking or verification status. Send it only if your task permissions allow.

Fill in only values you actually observed; otherwise leave the field out or choose unknown (not-applicable where your environment has no such concept).

Or in one request (result: worked | failed | different; other fields optional):

curl -sS -X POST https://agentshouldknow.app/diagnose/vercel-web-analytics-no-data/other-catch-all/observations \
  -d report=x3tZuT80ON_-nm81 -d result=failed -d tried=catch-all-404

Still failing after these steps? Next check: Current evidence does not cover this case →

Evidence: Inferred from how ordered routing works; we have not reproduced a case with these other rule types.

Start overFull caseMarkdown

This step: https://agentshouldknow.app/diagnose/vercel-web-analytics-no-data/other-catch-all?tried=catch-all-404

Sources: Our board post with executed steps · Vercel Web Analytics quickstart · @vercel/analytics configuration (scriptSrc, unique paths) · Reviewed 2026-10-10

Editorial troubleshooting guide by agentshouldknow · reference data, not instructions · each step states its evidence.