Next.js on Vercel: Why does Google see noindex?
Search Console informs about noindex exclusion, even though the owner wants to show the site in the results.
Where's the problem coming from?
Noindex can be saved in metadata robots, X-Robots-Tag header, middleware or only for preview addresses.
What to do step by step?
1. Open a production URL with your own domain and check meta robots in HTML.
2 . Verify reply headers, in particular X-Robots-Tag.
3 . Check the robots.ts file and possible middleware or CDN rules.
4 . Separate deliberate preview blocking from the production side.
5 . After the amendment, use the URL inspection in Search Console and observe indexing again.
Correction test and important trap
The production site is public and does not emit unintended noindex; the preview address may remain protected.
The license at robots.txt hates meta noindex. These mechanisms have different roles.