Menu

Next.js opengraph-image in Crawled – currently not indexed: should you fix it?
📰

Next.js opengraph-image in Crawled – currently not indexed: should you fix it?

DEV Community: nextjs·Mohamed Gado·1 day ago
#jgvZcuYx
#devtonextjs#devto#dev#opengraph#noindex
Reading 0:00
15s threshold

Search Console's Page indexing report put 14 URLs from this site under "Crawled – currently not indexed". Only 4 of them were pages. The other 10 were files: six per-page opengraph-image routes, feed.xml , favicon.ico , and the root card twice, once with its cache-busting query. None of those should ever be in the index, so the status is harmless for them. I still added X-Robots-Tag: noindex to every one, but the more useful thing I learned is what that header does not do.

Why does Google crawl opengraph-image at all?

In the App Router, an opengraph-image.tsx file next to a page becomes a route that returns a PNG, and Next.js writes its URL into the page's head:

<meta property = "og:image" content = "https://www.mohamedgado.com/projects/quizz-app/opengraph-image" >

Enter fullscreen mode

Exit fullscreen mode

Googlebot follows URLs it finds, and this is a plain absolute URL on your own domain. It fetches the image, sees that it isn't a page, and doesn't index it as one.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.