url_audit

How the check works

1. Every configured route type is fetched from Prismic, once per configured language.
2. Each document is turned into a URL using the route pattern and its resolvers.
3. The build log of your most recent Vercel deployment is read for the pages it actually rendered.
4. Anything in the first list and missing from the second is recorded against the project.

Because it reads the latest deployment, a check run against a failed or partial build will report a lot of missing URLs. Check the builds tab first if a run looks suspiciously bad.

Running a check

Click Check URLs. It confirms first, because a full run pages through every document in the repository and pulls a complete build log. Results replace whatever was there before.

Clear all removes the tracked URLs for the project without running anything, which is the quickest way to start from a clean slate after a fix.

If a schedule is configured, an Auto-check every N days badge appears next to the buttons. See the setup guide for scheduling and Slack alerts.

Working through the results

Each row is one URL, with the date it was first recorded, and two actions:

• ignore - marks a URL as known and expected. The row stays, struck through and green, so it does not read as an outstanding problem. Click again to un-ignore.
• note - attaches a free text note, for example a ticket reference or why the page is intentionally unbuilt.

Ignores and notes are per project and survive future checks on the same URL, so triage done once stays done.

Common causes

• A whole type missing - usually no route for that type, or a resolver that fails for every document so the URLs are skipped before comparison.
• One language missing - the language code is not in the languages list, or the pattern has no :lang segment.
• Scattered single pages - often genuinely unbuilt: a prerender error, or a page not reachable from any crawled link. The builds tab lists prerender errors with the path and the page that linked to it.
• Everything missing - the last deployment failed early, or the Vercel project ID points at a different project than you think.

Requirements

Prismic repository name, Vercel project ID and token, and at least one route. Without them the Check URLs button opens the settings panel instead of running.