/01
Content model
Confirm every commercial page has a CPT, the right meta fields, and an editor-friendly form.
- Services
- Technologies
- Solutions
- Case studies
- FAQ
Resource / Checklist
Headless WordPress + Next.js Launch Checklist
A pre-launch checklist for a headless WordPress + Next.js website. Covers content, REST, SEO, performance, and editor handoff.
/ Outcome
What you walk away with.
A safe launch where editors stay productive and the frontend ships clean SEO out of the box.
/ System
/02
Frontend SEO
Verify each page has a unique title, description, canonical, OG tags, and JSON-LD where appropriate.
- Per-page metadata
- Breadcrumb schema
- Article/Service schema
- OG image
/ Checklist
Run through the list.
- 01Every CPT exposes meta via REST
- 02Server-side decode and sanitize for HTML content
- 03Per-page metadata and canonical URLs in the frontend
- 04Sitemap includes all CMS content
- 05Robots, JSON-LD, and analytics wired
- 06Editor handoff doc and preview workflow
/ FAQ
Questions founders ask.
What is the most common launch bug?
Missing meta on the CPT or missing _embed parameters when the frontend expects author or featured media.
Do we need ISR?
Usually yes. It keeps editor changes visible without full redeploys, and keeps pages fast.