Vercel SEO
Most Vercel SEO problems aren’t in your code but in the platform settings around it: a staging domain that Google indexes, or a firewall rule that denies AI search bots. Check the live production URL, not a preview, because previews carry a noindex header that production doesn’t.
What Vercel adds between your code and a crawler
Vercel adds X-Robots-Tag: noindex to preview deployments, and to production deployments opened through their unique deployment URL. That is the right default, and it also means any SEO test you run against a preview link will report noindex that your real site doesn’t have.
The exception catches people out: a preview served from a custom domain assigned to a Git branch, such as staging.example.com, gets no header. Search engines can index it unless you protect it or add the header yourself. curl -I against the URL shows whether x-robots-tag: noindex is there.
The firewall is the other layer. Vercel’s AI bots managed ruleset covers bots that crawl for training, for search and for user-initiated fetches; it is off by default and can be set to log or deny. Set to deny, it turns away the bots that would cite you, not only the ones that train. The bot protection ruleset challenges non-browser traffic but excludes verified bots such as Googlebot. Both are off until someone turns them on, and easy to forget once they are.
Common causes, and the fix for each
noindex on the domain you wanted found
Fecto check index.noindex · Page may be indexed and quoted
If your production domain is attached as a branch domain, or a header rule in vercel.json or middleware adds noindex for the wrong host, the live page carries it. The check reads the response headers as well as the meta tag, which is where Vercel-level noindex lives.
The AI bots ruleset set to deny
Fecto check access.possible-bot-block · Possible bot block at the CDN
Besides its own fetch, the scan repeats the request with the user agents of the bots assistants send when someone asks about a page (ChatGPT-User, Claude-User, Perplexity-User and others). If those come back blocked, the AI bots ruleset on deny is the first thing to look at. It is reported for information only, because Fecto’s requests come from Fecto’s IP and a firewall that checks bots by IP may treat the real ones differently. The fix is a dashboard setting only you can change: log instead of deny, or a custom rule that blocks training bots by user agent and lets search bots through.
A challenge page instead of your content
Fecto check access.challenge-page · No challenge page instead of content
Fecto’s scan identifies itself as FectoScan and is not a verified bot, so if bot protection or Attack Mode is on, the scan may get a challenge instead of the page. Verified crawlers such as Googlebot are let through, so read this finding as “check the firewall”, not “you are invisible”. Unverified fetchers, which include many smaller AI tools, do get the challenge.
A home page that redirects by script or to another domain
Fecto check read.redirect-hygiene · Clean redirects
The check flags a home page that moves visitors on with a meta refresh, with script only, or to a different domain. On Vercel the fix is a redirect in vercel.json or in the domain settings, answered by the server, so crawlers that don’t run scripts follow it too.
Let your agent do it
Your agent fixes what lives in the repo, such as vercel.json headers, middleware and redirects, as pull requests, and it tests them on the preview with Vercel’s noindex in mind. Dashboard settings like the firewall rulesets it reports as a blocked step, naming the exact setting for you to change, because it can’t and shouldn’t touch your Vercel account.
No coding agent yet? Install the Claude app, sign in, then come back and choose Claude app.
Set it up by hand
curl -fsSL https://fecto.ai/install | shThen tell it
Use Fecto to check and fix my site.Don’t remove the preview noindex
It keeps half-finished work out of search. Test SEO on production, or on a preview with the header in mind, rather than switching the protection off.
What it costs
You pay only when the result shows up on your site: +20% more visits or enquiries is $30, +50% is $60, double is $100, and anything below +20% costs $0. Never more than $100 a site a month.
Questions
Does hosting on Vercel help SEO by itself?
Vercel serves what your framework builds. A server-rendered Next.js app arrives with its text; a client-only app arrives empty on Vercel as it would anywhere else. What the platform adds is the layer this page is about: headers, domains and firewall rules.
How do I check a staging domain isn’t indexed?
Run curl -I against it and look for x-robots-tag: noindex. If the header is missing and the domain is assigned to a branch, protect the deployment or add the header in your config. Then search Google for site: and the staging domain to see whether anything already got in.
Should I block GPTBot on Vercel?
That is your choice, and Fecto never counts it against you. If you want to, block GPTBot and other training-only bots by user agent in a custom rule, rather than setting the whole AI bots ruleset to deny, which also catches the search and user-fetch bots that would cite you.
Related guides
Checked against Vercel docs: environments (preview indexing) and Vercel docs: bot management on 18 November 2026.