Client project
Next.js and WordPress launch checks
I reviewed a headless Next.js and WordPress website, identified page and deployment problems, and retested the changed behavior on the live site.
The project
-
What the client needed
Published pages should show the intended content and canonical URL. Missing pages should return the correct error, and the production website should match the approved release.
-
The problem
- Pages and error responses needed checks across the Next.js and WordPress setup.
- HTML, browser-rendered content, and framework responses needed separate checks for incorrect URLs or metadata.
- Preview and production environments behaved differently.
-
My role
- Led the technical SEO and launch checks.
- Investigated whether problems came from the application, CMS, or deployment.
- Supplied reproducible findings and retested the changed website.
-
What I changed
- Scoped page and response corrections against the affected page types.
- Aligned canonicals and CMS links with the intended public URLs.
- Compared preview, immutable deployment, and production before approving the changes.
-
How I checked it
- Repeated HTTP and browser checks on the affected page types.
- Checked missing-page responses, canonicals, internal links, and CMS URLs.
- Retested production after the implementation changes were available.
About these results
- This summary describes technical checks and corrections. It does not report indexing, traffic, ranking, or revenue growth.
- Client names and private materials are withheld. The original test records are not reproduced here.