Bug examples
These are ordinary CMS problems that can ship without a code diff: changed slugs, missing fields, weak SEO metadata, and incomplete image content.
Examples
| Failure | What cms-lab reports | Typical fix |
|---|---|---|
| Published CMS entry resolves to a page that returns 404. | CMS-ROUTE-404 with the sanitized path and CMS source. | Fix the slug, route mapping, or dynamic route data fetch. |
A template expects author.name, but the field is blank. | CMS-FIELD-MISSING for the configured field path. | Fill the content or make the template handle the missing value. |
| SEO title or description is empty in provider-native fields. | SEO-META-MISSING on the affected document. | Add metadata in the CMS or map the project-specific SEO fields. |
| Hero image has no useful alt text. | A11Y-IMG-ALT with the nested image field path. | Write specific alt text or mark decorative images in the app. |
| One template repeats the same issue across many CMS documents. | A repeated-finding group such as page /:uid plus the full row-level diagnostics. | Fix the shared route/template code or bulk-edit the affected CMS records. |
Demo screenshot
The CLI output is intentionally plain so it works in local terminals and CI logs.
npx @cms-lab/cli scan --ci --report cms-lab project next pages documents 39 errors CMS-ROUTE-404 - Route /blog/missing returned 404 warnings CMS-FIELD-MISSING - Document article-12 is missing data.author.name SEO-META-MISSING - Document page-7 is missing meta_description scan failed - 1 error