Install guides
Choose an install
Which install fits your site, and what each one asks of you.
Every install does the same thing: crawler requests go to Intercrawl, and everything else reaches your site exactly as before. They differ in where that decision is made. On the Sites page, Intercrawl detects how your site is hosted and opens the install that fits.
| Your site | Install | Code to add |
|---|---|---|
| On Vercel | Add to Vercel | None |
| Domain on Cloudflare (proxied) | Add to Cloudflare | None |
| Next.js, anywhere | Next.js middleware | One file |
| Vercel, another framework | Vercel middleware | One file |
| Netlify | Netlify edge function | One file |
| Cloudflare Pages | Pages middleware | One file |
| Domain on Cloudflare, any host | Cloudflare Worker | One Worker |
| Any host, server code you control | Prerender-compatible API | Your own middleware |
| Any host, no code access | DNS mode | None, one DNS record |
If you use an AI coding tool, Install with AI gives it a prompt that adds the right file for you.
Before you start
- Verify your site.
- Create an API token on the Account page, under API tokens. It starts with
ic_live_and is shown once. The install files read it from the environment variableINTERCRAWL_TOKEN; never write it into a file or commit it.
The install files are single files with no dependencies of their own. Use them as they are.
Not answered here? Write to hello@intercrawl.com.Next: Install on Next.js