Crawld and Next.js
Fixes arrive as a pull request, built before you see it.
Status: Not built yet . this connector is not built. The page describes how delivery works on Next.js given the constraints of the platform, and what verification would honestly be available. Today you can run the free scorecard against a Next.js site without granting any access at all.
How fixes would arrive
A branch with the change, a pull request, and the result of a real build attached to it.
A Next.js site is a repository, so the change can be compiled before it is proposed. That is what makes the build-verified label honest here and not on a hosted CMS.
The strongest rung. Because we hold the repository, the change can be built before you ever see it, and the pull request carries the result of that build. Nothing merges without your click.
What the rubric can see here
- Metadata exported from
generateMetadataand staticmetadataobjects - Canonical tags, Open Graph and structured data emitted from layouts
- App Router and Pages Router both, including per-route metadata
- Whether a route ships content in its HTML or paints it client-side
Limits worth knowing before you plan around this
- Content coming from a headless CMS is fixed at the CMS, not in the repo, that is a Mode D problem living inside a Mode A site
- A fix that depends on runtime data cannot be verified by a build alone
Where this sits on the ladder
| Mode | What we get | How changes arrive | Verification | Status |
|---|---|---|---|---|
| A · Repo write | A connected repository we can push a branch to | Opens a pull request. You review the diff and merge it. | Build-verified | Not built yet |
| B · Read-only repo | Read access, plus somewhere to push | Pushes to a fork or a branch you own. | Build-verified | Not built yet |
| C · Cloud mirror | A one-time snapshot or export | Works on a clone in our cloud, returns a patch or a PR. | Build-verified (mirror) | Not built yet |
| D · CMS drafts | OAuth into a hosted CMS | Writes unpublished drafts. You publish them. | Preview-verified | Not built yet |
| E · URL only | Nothing: a public URL | A scorecard and a patch you apply yourself. | Advisory only | Available now |
Build-verified means a build actually ran. It applies to modes A, B and C and to nothing else. A hosted CMS has no build to run, so mode D is preview-verified and mode E is advisory. Those labels are never blurred, because the honesty of the verification is the product.
What you can do today
Scan the site. The free scorecard needs no access to Next.js at all. It reads the published HTML the way a search or answer engine does, runs the full 129-check rubric against it, and reports what it could not measure rather than counting it as a pass.
Everything it finds is actionable by hand regardless of whether a connector ever exists, because the finding names the page and the change rather than a button to press.