Why Google Search Console Still Shows Old Errors After You Fix Them
Why Google Search Console can keep showing old indexing errors after fixes, and how to use live URL testing, validation, and request indexing correctly.
I'm a DevOps Engineer, Software Developer, and Cybersecurity Professional with over two decades of experience across retail, finance, ad-tech, and AI. I've led cloud migrations, designed CI/CD pipelines, and architected infrastructure-as-code for enterprise environments.
Right now I'm focused on applying AI and machine learning to real problems — not demos, but tools that reach users and hold up in production.
Full background →A mix of shipped tools, work-in-progress experiments, and technical systems.
Machine learning platform that helps students and early-career professionals make informed decisions based on their education, interests, and aptitude.
View project →Privacy-first CV distribution system. Requesters verify identity via OTP email — access is rate-limited, auditable, and requires zero third-party auth services.
View project →SaaS decision-support app that runs one hard prompt through multiple AI models, critiques the answers, and returns a structured verdict.
View project →Technical writing on DevOps, AI, cybersecurity, and building software that matters.
Why Google Search Console can keep showing old indexing errors after fixes, and how to use live URL testing, validation, and request indexing correctly.
A practical Hugo stale URL audit workflow using rg searches, front matter checks, aliases, internal links, generated output, and sitemap validation.
A practical guide to cleaning stale Hugo URLs with Netlify redirects, using real netlify.toml and static _redirects examples.
Building production AI tools and writing about the process.
Last updated: April 2026
Full now page →