Next.js + Headless WordPress Production SEO QA

Published articles were returning “not found,” while some nonexistent property pages were reporting successful responses.

Nour Estates runs a Next.js website connected to WordPress, with deployments on Vercel. I investigated these problems and worked with the site’s developer to check the corrections through to production.

One issue affected published blog posts. The build process fetched only the first batch of posts from WordPress, leaving other valid articles unavailable. I traced the failure to incomplete pagination, documented the affected routes and verified them after the developer updated the implementation.

Property pages had a different problem: an invalid URL could display a convincing error screen while still returning HTTP 200. I checked the actual server responses and retested both missing and valid property URLs after the routing changes.

The work also covered canonical URLs, incorrect links pointing back to the headless CMS, empty listings and discrepancies in property information. I compared preview deployments, specific release builds and the live website to check that the approved corrections reached production.

My role covered investigation, reproducible issue reports, correction requirements and independent release QA. The site’s developer implemented the application changes.

The final checks confirmed that the tested articles loaded, missing property URLs returned the expected 404 response, and the reviewed listing and content corrections were present on the live site.