The route nothing imports: how eleven broken endpoints hid behind one Search Console error

The mechanism worth taking away is the gap between what generates a route and what exercises it. `app/[locale]/opengraph-image.tsx` is a file convention: you do not import it, you do not link to it, and no page renders it, according to the author's account ^[2]. Its only output is a meta tag pointing at a route Next builds on your behalf ^[2]. So the normal feedback loop has nothing to grab. Clicking through the site shows nothing, because no page requests the image ^[3]. The build compiles, because the failure happens per request at render time ^[4]. Deploy checks that fetch pages and grep for text skip it, because it is not a page ^[5]. And the user-visible symptom lands on someone else's server: a blank preview card on a social site ^[6].

The failure itself is small enough to be invisible in review. `next/og` renders through Satori, which requires a div with more than one child to declare `display: flex` or `display: none` ^[7]. The offending line reads as one sentence to a person and as two JSX children to the compiler: the expression container and the adjacent text node ^[8]. Every other div in the file either declared display or genuinely had one child, so the broken one looked like its neighbours ^[9].

Then the diagnosis gets pushed two layers away from the code. `ImageResponse` streams, so by the time Satori throws, headers are sent and the body has started; Next cannot render a 500 page and closes the connection ^[10]. nginx, still waiting on the upstream, logs a premature close and returns 502 ^[11]. That is infrastructure vocabulary. It sends you to memory, to the process, to the proxy config, when the cause is a JSX child count ^[12].

The fix the author chose was not the one the error message asks for. Wrapping the content in a single template literal makes it one text node, so the multi-child rule never applies ^[13]. Adding `display: flex` also works, but it turns the text into a flex item and changes how it wraps against the `maxWidth: 1000` ^[14]. One of those fixes the crash and leaves layout alone.

The blast radius was not uniform, and that is the part the author says turned a curiosity into a bug. Pages that set `openGraph.images` explicitly override the file convention and were fine; pages that did not, including the privacy policy and terms pages in all eleven locales, inherited the broken route and published a 502 as their og:image ^[15]. That is 22 pages serving a dead image reference on a site of roughly 1,700 pages ^[22][1], which is why the sampling logic matters more than the ratio: Search Console reports what it happened to crawl, so one 5xx on a locale-parameterised route means at least one ^[16]. A for-loop over the locale list took the count from 1 to 11 ^[17].

The durable lesson is the checking discipline, and it is unglamorous: curl the route after you touch it, because nothing in the normal loop covers a file nothing imports ^[18]. After the change, all eleven locales returned 200 with a 244,560-byte PNG at 1200x630 ^[19].