Volnyn

A Google Search Console alert last week told us 2,246 pages on our site were returning 5xx errors. The number was bad enough. What those error pages had been showing publicly was worse.

APP_DEBUG was set to true in production.

For anyone unfamiliar with Laravel: instead of a generic error page, every crashing route was rendering the full debug screen. File paths. Stack traces. Source code around the failing line. SQL queries with table and column names.

Publicly. For months. Crawled and indexed by Google.

Three things I took from it:

1. We run four Laravel apps under one domain. Three had APP_DEBUG=false. The fourth was set up quickly during a migration and never audited. Environment config drifts, especially when no one owns all of it.

2. Fixing it wasn't enough. Google had those URLs indexed and no reason to recrawl. You have to explicitly trigger "Validate Fix" in Search Console. Without that, errors sit in the report for months and you have no idea whether your fix worked.

3. Search Console turned out to be a genuinely useful production monitoring tool. It caught something our own logs hadn't surfaced, because the errors were on routes nobody was watching.

Full writeup with the checklist we run now: [Dev.to post ka link yahan paste karein]

Curious whether others here have found Search Console useful for catching production issues, or whether that's just us.