On a headless property website, I traced missing posts to a route-generation query that fetched only the first page of GraphQL results. Valid content beyond that page never reached the generated route list.
I diagnosed the problem and specified the correction. The implementing developer added complete pagination; I verified the affected routes across the corrected deployment and production.
I also checked a separate failure: nonexistent property URLs displayed a 404 interface but returned HTTP 200. After the developer's correction, the tested missing URLs returned genuine 404 responses while valid properties continued to work.
The case study covers the diagnosis, collaboration and release checks behind both corrections.
Check it out
The 404 page returning 200 is such a sneaky one, it looks totally fine in the browser so nobody notices until Search Console starts flagging soft 404s. Did you also make new posts render on demand, so they don't have to wait for the next build?
Exactly—the rendered page hid the status mismatch, so I checked the HTTP response alongside what appeared in the browser.
On-demand publishing wasn’t part of the fix I validated. The posts were generated at build time, but generateStaticParams() only fetched the first GraphQL...
Back to our latest poll: y'all voted Black (60%). We shipped Pink anyway.
Our client's call, not ours - and once you see her brand, you'll get why. Feminine-led, bold, unapologetic - Pink was never really up for debate on her end. 💗👠
🔥 New addition to my portfolio 🔥
Previously I had an SVG mask of my logo in the center with my showreel behind it, but this had a couple of issues. So yesterday I pushed it further and I created a 3D variation, video playing inside it, glass refraction and it's even more beautiful when you click into it.
Take a look; www.grilledpixels.com