The latest articles on DEV Community by volnyn (@volnyn_8249e2bcefd516a59c). https://dev.to/volnyn_8249e2bcefd516a59c https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3909749%2F700686cd-6778-4870-8335-9e9ce0f9ba95.png https://dev.to/volnyn_8249e2bcefd516a59c en volnyn Tue, 11 Aug 2026 19:11:58 +0000 https://dev.to/volnyn_8249e2bcefd516a59c/we-had-appdebugtrue-in-production-google-indexed-2246-error-pages-3p4o https://dev.to/volnyn_8249e2bcefd516a59c/we-had-appdebugtrue-in-production-google-indexed-2246-error-pages-3p4o <p>Last week a Google Search Console alert told us 2,246 pages on our site were returning 5xx errors. That number was surprising on its own. What made it worse was what those error pages had been showing to anyone who loaded them.</p> <p><code>APP_DEBUG</code> was set to <code>true</code> in production.</p> <p>If you've worked with Laravel you already know what that means. For everyone else: instead of a generic "something went wrong" page, every crashing route was rendering Laravel's full debug screen. File paths. Stack traces. The actual source code around the failing line. SQL queries with table and column names. On some pages, environment variables.</p> <p>Publicly. For months. Indexed by Google.</p> <p>Here's how we found it, what the actual damage was, and the checklist we now run before anything goes live.</p> <h2> How it surfaced </h2> <p>We weren't looking for this. We were doing a routine SEO audit and pulled the Page Indexing report in Search Console.</p> <p>The breakdown looked like this:</p> ai seo laravel php