Vercel — Forward AI traffic

If your site is on Vercel, this takes 30 seconds.

Add the rule

1. Open your Vercel project → Firewall → Custom Rules → Add Rule.
2. Configure:

3. Save (rules deploy in seconds).

Important

The redirect destination is a single static URL with no path component.
Path reconstruction happens on our side via the Referer header — don't
try to template $path or similar; Vercel WAF treats it as literal text
and will DNS-resolve it as part of the hostname.

Verify

Back on the MCP page, click Check forwarding
on the indigo card. We send a request to your homepage with a GPTBot/1.2
UA, follow zero redirects, and confirm the 3xx target hostname is
oasy.<your-domain>.

Test yourself

curl -I -A "GPTBot/1.2" https://your-domain.com/
# → HTTP/2 307
# → location: https://oasy.your-domain.com

Common gotchas

• Apex vs www — Vercel's automatic apex→www canonicalisation happens
  before your custom rule fires. If www.your-domain.com is your canonical
  host, the rule applies there. Our verifier follows the canonical hop, so
  this works either way.
• Bypass on staging — if you want the rule off for preview.your-domain.com,
  add a hostname condition: AND Hostname does not equal preview.your-domain.com.
• Rate limiting — Vercel WAF runs before your edge functions, so the
  redirect doesn't count against compute time or rate limits.