u/Vishal8080S

Hi everyone,

We recently migrated our website from .NET to Next.js.

After the migration, we noticed a strange issue. If we open around 20 pages at the same time, some pages randomly show a 404 error. If we refresh the same page once or twice, it loads normally.

I also checked our GA data and found that users coming from Google, Bing, Yandex, DuckDuckGo, ChatGPT, Gemini, Claude, and Perplexity have sometimes landed on these 404 pages.

But when I open the same URLs manually, they work normally.

Has anyone faced this type of issue with Next.js? What could cause an intermittent 404 like this?

Hi everyone,

We recently migrated our website from .NET to Next.js.

After the migration, we noticed a strange issue. If we open around 20 pages at the same time, some pages randomly show a 404 error. If we refresh the same page once or twice, it loads normally.

I also checked our GA data and found that users coming from Google, Bing, Yandex, DuckDuckGo, ChatGPT, Gemini, Claude, and Perplexity have sometimes landed on these 404 pages.

But when I open the same URLs manually, they work normally.

Has anyone faced this type of issue with Next.js? What could cause an intermittent 404 like this?

Hi SEO community,

We recently migrated our website from .NET to Next.js and noticed an intermittent 404 issue.

Some valid pages randomly return a 404 when users access them. If we refresh the page, it usually loads correctly.

I checked GA and found traffic from Google, Bing, Yandex, DuckDuckGo and AI platforms such as ChatGPT, Gemini, Claude and Perplexity reaching these 404 pages.

The same URLs work when I test them manually.

I'm concerned that if search engine crawlers also receive these temporary 404 responses, it could create an SEO problem.

Has anyone experienced this after a .NET → Next.js migration? What should we check to find the root cause?

Hi everyone,

We recently migrated our website from .NET to Next.js, and we're facing a strange problem. some valid pages randomly show 404 when many pages are opened at the same time. If I refresh the 404 page once or twice, it works.

I checked GA data and found that users from Google, Bing, duck duck go and other search engines, as well as AI platforms, have also landed on 404 pages.but the URLs themselves are correct and work when I open them manually. Developer hasn't been able to find the reason yet.

What could cause this, and what should we check first?

Would appreciate any ideas from people who have worked with large Next.js websites.

Hi everyone,

I noticed that Google is crawling many /\_next/image URLs.we already have the original image URLs, but Next.js also creates its own image URLs. Because of this, bot is crawling both URLs.

I am worried that this may use our crawl budget.

What is the best way to handle these URLs?, Should i use robots.txt, X-Robots-Tag?

I don't want to anything that could affect the indexing of our main pages.

Has anyone faced the same issue on a large Next.js website? What solution worked for you?

Thanks in advance!

Hi everyone,

I noticed in GSC that Google is crawling a large number of /_next/image URLs.

The same images also have their normal image URLs, so it looks like Google is crawling two different URLs for the same images.

My main concern is the amount of crawling. I’m wondering if these Next.js image URLs are using unnecessary crawl resources.

I spoke with our developer about adding noindex & block by robots.txt, but they are concerned that it could affect the indexing of pages that use these images.

Has anyone dealt with this on a large Next.js site?

What would you recommend here X-Robots-Tag, disallow by robots txt, changes to the Next.js image setup or something else?

I’m mainly looking for a way to reduce unnecessary crawling without affecting the indexing of the main pages.