twitter:image is explicitly configured

Twitter/X's fallback to og:image is documented but not universally reliable. When the og:image URL includes query parameters, signed tokens, or CDN paths that require specific headers, Twitter's crawler may silently fail to fetch the image and render the card without a visual. Per the Twitter Cards spec, an explicit twitter:image that uses a clean, unconditional HTTPS URL removes this ambiguity. The reference-integrity failure mode is invisible in development: the image works in browsers but fails when crawled by bots, producing cards that show no image in production social shares without any error signal in your logs.

Add an explicit twitter.images array to your metadata to avoid relying on og:image fallback behavior:

twitter: {
  card: 'summary_large_image',
  images: ['https://yoursite.com/og-image.png'],
}

For dynamic routes, generate the Twitter image URL the same way as the OG image — they can reference the same resource. The explicit declaration ensures Twitter uses the exact URL you specify rather than deriving one from the og:image value. Confirm the referenced URL is a clean absolute HTTPS path with no query parameters.