Code checks
Before release, typecheck, lint, test, links, structure, route audit, security, line endings should pass.
- npm run typecheck
- npm run links:check
- npm run route:audit
pre-merge check
Content QA
The checklist a new page passes before entering archive, sitemap, search, or ad flow.
Content QA catches not only typos, but broken routes, wrong index, duplicates, unsafe promises, and mobile dead ends.
Content checks
Check meaning: no duplicate, role, CTA, safety, internal links, metadata, mobile order.
- No duplicate page.
- Safety note present.
- Mobile first screen useful.
Operational checks
If page is internal, it must be noindex. If public, it needs search/sitemap decision.
- noindex for internal ops.
- sitemap for public evergreen.
- redirects for aliases.
checklist
- No TS errors.
- No unknown hrefs.
- No forbidden claims.
- No empty page without explanation.
- Report file added.
red flags
- Page exists but is linked nowhere.
- New internal section is indexed.
- Route registry not updated after change.
rewrite like this
QA result
AvoidSeems fine, can upload.
Prefertypecheck/lint/test/links/route/security passed; build compiled but container timed out during page-data stage.
Result wording
AvoidThis card definitely means the person will return.
PreferThis card points to the theme of return, but it does not replace conversation or a person's free choice.
Purchase call
AvoidBuy a deep scroll or the sign will remain closed.
PreferA deep scroll fits when you want context, positions, and a gentle next-step plan.
definition of done
All checks pass or known timeout is honestly described.
Archive cleaned of node_modules/.next/secrets.
User receives clear change list.
related doors
Publishing rulesWhen a page is ready to publish and when it should stay in draft.SEO metadataTitle, description, slug, internal links, and search intent without clickbait.Forbidden claimsForbidden promises: medical, legal, financial, immigration, and guaranteed future claims.Launch QAChecks before launch, redeploy, and ads.