Topic
Technical SEO, Redirects & Migrations
Domain moves, URL structure changes, and database migrations always look clean, until Google starts indexing 404s and soft-404s. Here you'll find a redirect-chain audit spanning four mechanisms, the search-replace trap that misses Gutenberg blocks, and a Next.js sitemap that never becomes a sitemapindex. For anyone responsible for keeping old URLs alive through big changes.
8 articles
Start here
Auditing a 3-Hop 301 Redirect Chain That Was Hiding Across Four Mechanisms
Wildcard 301 Redirect Across Hosts Turns Every Old URL Into a `404`? The Path Does Not Exist on the New Host
July 13, 2026
Next.js `generateSitemaps` Returns an Empty `<urlset>` Instead of a `<sitemapindex>`? The Convention Can't Emit One
July 10, 2026
Your Next.js `not-found` Page Returns HTTP 200? The Soft-404 That Won't Let Google Deindex
July 10, 2026
WAF Blocks Your `curl` Scraper With 403s and JS Challenges? Move Extraction Into the Logged-In Browser With a JSON-LD Bookmarklet
July 2, 2026
`update_option` Migration Succeeded but the Frontend Still Shows the Old Value? One Setting Stored Under Two Option Keys
June 29, 2026
Site URL Migration With Better Search Replace Misses Gutenberg Blocks, You Need the Escaped `\/` Form
June 28, 2026
Renaming Slugs + Changing URL Structure in One Deploy: Why Your Redirect 404s Instead of 301s
June 24, 2026