Skip to content
Arcjet Docs

Next.js bot protection reference

Arcjet bot detection allows you to manage traffic by automated clients and bots.

Configuration

Bot detection is configured by allowing or denying a subset of bots. The allow and deny lists are mutually-exclusive, such that using allow will result in a DENY decision for any detected bot that is not specified in the allow list and using deny will result in an ALLOW decision for any detected bot that is not specified in the deny list.

You can use only one of the following configuration definitions:

type BotOptionsAllow = {
  mode?: "LIVE" | "DRY_RUN";
  allow: ArcjetWellKnownBot[];
};
type BotOptionsDeny = {
  mode?: "LIVE" | "DRY_RUN";
  deny: ArcjetWellKnownBot[];
};

The arcjet client is configured with one or more detectBot rules which take one or many BotOptions.

Only allowing specific bots

Most applications want to block almost all bots. However, it is common to allow some bots to access your system, such as bots for search indexing or API access from the command line.

This behavior is configured with an allow list from our full list of bots.

/app/api/arcjet/route.ts
import arcjet, { detectBot } from "@arcjet/next";
import { NextResponse } from "next/server";


const aj = arcjet({
  key: process.env.ARCJET_KEY!,
  rules: [
    detectBot({
      mode: "LIVE",
      // configured with a list of bots to allow from
      // https://arcjet.com/bot-list - all other detected bots will be blocked
      allow: [
        // Google has multiple crawlers, each with a different user-agent. Check
        // the full list for more options
        "GOOGLE_CRAWLER", // allows Google's main crawler
        "GOOGLE_ADSBOT", // allows Google Adsbot
        "GOOGLE_CRAWLER_NEWS", // allows Google News crawler
        "CURL", // allows the default user-agent of the `curl` tool
        "DISCORD_CRAWLER", // allows Discordbot
      ],
    }),
  ],
});


export async function POST(req: Request) {
  const decision = await aj.protect(req);


  if (decision.isDenied() && decision.reason.isBot()) {
    return NextResponse.json(
      {
        error: "You are a bot!",
        // Useful for debugging, but don't return these to the client in
        // production
        denied: decision.reason.denied,
      },
      { status: 403 },
    );
  }


  return NextResponse.json({
    message: "Hello world",
  });
}

Only denying specific bots

Some applications may only want to block a small subset of bots, while allowing the majority continued access. This may be due to many reasons, such as misconfigured or high-traffic bots.

This behavior is configured with an deny list from our full list of bots.

/app/api/arcjet/route.ts
import arcjet, { detectBot } from "@arcjet/next";
import { NextResponse } from "next/server";


const aj = arcjet({
  key: process.env.ARCJET_KEY!,
  rules: [
    detectBot({
      mode: "LIVE",
      // configured with a list of bots to deny from
      // https://arcjet.com/bot-list - all other detected bots will be allowed
      deny: [
        "PERPLEXITY_CRAWLER", // denies PerplexityBot
        "CURL", // denies the default user-agent of the `curl` tool
        "ANTHROPIC_CRAWLER", // denies Claudebot
      ],
    }),
  ],
});


export async function POST(req: Request) {
  const decision = await aj.protect(req);


  if (decision.isDenied() && decision.reason.isBot()) {
    return NextResponse.json(
      {
        error: "You are a bot!",
        // Useful for debugging, but don't return these to the client in
        // production
        denied: decision.reason.denied,
      },
      { status: 403 },
    );
  }


  return NextResponse.json({
    message: "Hello world",
  });
}

Per route vs middleware

Bot protection rules can be configured in two ways:

  • Per API route: The rule is defined in the API route itself. This allows you to configure the rule alongside the code it is protecting which is useful if you want to use the decision to add context to your own code. However, it means rules are not located in a single place.
  • Middleware: The rule is defined in the middleware. This allows you to configure rules in a single place or apply them globally to all routes, but it means the rules are not located alongside the code they are protecting.

Per route

This configures bot protection on a single route.

/app/api/arcjet/route.ts
import arcjet, { detectBot } from "@arcjet/next";
import { NextResponse } from "next/server";


const aj = arcjet({
  key: process.env.ARCJET_KEY!,
  rules: [
    detectBot({
      mode: "LIVE",
      allow: [], // "allow none" will block all detected bots
    }),
  ],
});


export async function GET(req: Request) {
  const decision = await aj.protect(req);


  if (decision.isDenied() && decision.reason.isBot()) {
    return NextResponse.json(
      {
        error: "You are a bot!",
      },
      { status: 403 },
    );
  }


  return NextResponse.json({
    message: "Hello world",
  });
}

Middleware

This will run on every request to your Next.js app, except for static assets (configured in the matcher - see the Next.js docs for details).

Create a file called middleware.ts in your project root (at the same level as pages or app or inside src):

/middleware.ts
import arcjet, { createMiddleware, detectBot } from "@arcjet/next";
export const config = {
  // matcher tells Next.js which routes to run the middleware on.
  // This runs the middleware on all routes except for static assets.
  matcher: ["/((?!_next/static|_next/image|favicon.ico).*)"],
};
const aj = arcjet({
  key: process.env.ARCJET_KEY!, // Get your site key from https://app.arcjet.com
  rules: [
    detectBot({
      mode: "LIVE", // will block requests. Use "DRY_RUN" to log only
      // configured with a list of bots to allow from
      // https://arcjet.com/bot-list
      allow: [], // "allow none" will block all detected bots
    }),
  ],
});
// Pass any existing middleware with the optional existingMiddleware prop
export default createMiddleware(aj);

You can also customize the response depending on the decision. In this case we will return a 403 Forbidden response only if we detect a hosting provider IP address for the bot detection rule result:

/middleware.ts
import arcjet, { detectBot } from "@arcjet/next";
import { NextRequest, NextResponse } from "next/server";


export const config = {
  // matcher tells Next.js which routes to run the middleware on.
  // This runs the middleware on all routes except for static assets.
  matcher: ["/((?!_next/static|_next/image|favicon.ico).*)"],
};
const aj = arcjet({
  key: process.env.ARCJET_KEY!, // Get your site key from https://app.arcjet.com
  rules: [
    detectBot({
      mode: "LIVE", // will block requests. Use "DRY_RUN" to log only
      allow: [], // "allow none" will block all detected bots
    }),
  ],
});


export default async function middleware(request: NextRequest) {
  const decision = await aj.protect(request);


  if (
    // If the decision is deny because the request is from a bot and the bot IP
    // address is from a known hosting provider, then block the request
    decision.isDenied() &&
    decision.reason.isBot() &&
    decision.ip.isHosting()
  ) {
    return NextResponse.json({ error: "Unauthorized" }, { status: 403 });
  } else {
    return NextResponse.next();
  }
}

Avoiding double protection with middleware

If you use Arcjet in middleware and individual routes, you need to be careful that Arcjet is not running multiple times per request. This can be avoided by excluding the API route from the middleware matcher.

For example, if you already have a bot detection rule defined in the API route at /api/hello, you can exclude it from the middleware by specifying a matcher in /middleware.ts:

/middleware.ts
import arcjet, { createMiddleware, detectBot } from "@arcjet/next";
export const config = {
  // The matcher prevents the middleware executing on static assets and the
  // /api/hello API route because you already installed Arcjet directly
  matcher: ["/((?!_next/static|_next/image|favicon.ico|api/hello).*)"],
};
const aj = arcjet({
  key: process.env.ARCJET_KEY!,
  rules: [
    detectBot({
      mode: "LIVE",
      allow: [], // "allow none" will block all detected bots
    }),
  ],
});
// Pass any existing middleware with the optional existingMiddleware prop
export default createMiddleware(aj);

Decision

The quick start example will deny requests that match the bot detection rules, immediately returning a response to the client using Next.js middleware.

Arcjet also provides a single protect function that is used to execute your protection rules. This requires a request argument which is the request context as passed to the request handler.

This function returns a Promise that resolves to an ArcjetDecision object. This contains the following properties:

  • id (string) - The unique ID for the request. This can be used to look up the request in the Arcjet dashboard. It is prefixed with req_ for decisions involving the Arcjet cloud API. For decisions taken locally, the prefix is lreq_.
  • conclusion (ArcjetConclusion) - The final conclusion based on evaluating each of the configured rules. If you wish to accept Arcjet’s recommended action based on the configured rules then you can use this property.
  • reason (ArcjetReason) - An object containing more detailed information about the conclusion.
  • results (ArcjetRuleResult[]) - An array of ArcjetRuleResult objects containing the results of each rule that was executed.
  • ip (ArcjetIpDetails) - An object containing Arcjet’s analysis of the client IP address. See IP analysis in the SDK reference for more information.

See the SDK reference for more details about the rule results.

You check if a deny conclusion has been returned by a bot protection rule by using decision.isDenied() and decision.reason.isBot() respectively.

You can iterate through the results and check whether a bot protection rule was applied:

for (const result of decision.results) {
  console.log("Rule Result", result);
}

This example will log the full result as well as the bot protection rule:

Create a new API route at /app/api/route/hello.ts:

/app/api/route/hello.ts
import arcjet, { fixedWindow, detectBot } from "@arcjet/next";
import { NextResponse } from "next/server";


const aj = arcjet({
  key: process.env.ARCJET_KEY!,
  // Limiting by ip.src is the default if not specified
  //characteristics: ["ip.src"],
  rules: [
    fixedWindow({
      mode: "LIVE",
      window: "1h",
      max: 60,
    }),
    detectBot({
      mode: "LIVE",
      allow: [], // "allow none" will block all detected bots
    }),
  ],
});


export async function POST(req: Request) {
  const decision = await aj.protect(req);


  for (const result of decision.results) {
    console.log("Rule Result", result);


    if (result.reason.isRateLimit()) {
      console.log("Rate limit rule", result);
    }


    if (result.reason.isBot()) {
      console.log("Bot protection rule", result);
    }
  }


  if (decision.isDenied()) {
    return NextResponse.json({ error: "Forbidden" }, { status: 403 });
  }


  return NextResponse.json({
    message: "Hello world",
  });
}

Identified bots

The decision also contains all of the identified bots detected from the request. A request may be identified as zero, one, or more bots—all of which will be available on the decision.allowed and decision.denied properties.

Create a new API route at /app/api/route/hello.ts:

/app/api/route/hello.ts
import arcjet, { detectBot } from "@arcjet/next";
import { NextResponse } from "next/server";


const aj = arcjet({
  key: process.env.ARCJET_KEY!,
  rules: [
    detectBot({
      mode: "LIVE",
      allow: [], // "allow none" will block all detected bots
    }),
  ],
});


export async function POST(req: Request) {
  const decision = await aj.protect(req);


  if (decision.reason.isBot()) {
    console.log("detected + allowed bots", decision.reason.allowed);
    console.log("detected + denied bots", decision.reason.denied);
  }


  if (decision.isDenied()) {
    return NextResponse.json({ error: "You are a bot!" }, { status: 403 });
  }


  return NextResponse.json({
    message: "Hello world",
  });
}

Error handling

Arcjet is designed to fail open so that a service issue or misconfiguration does not block all requests. The SDK will also time out and fail open after 1000ms when NODE_ENV or ARCJET_ENV is development and 500ms otherwise. However, in most cases, the response time will be less than 20-30ms.

If there is an error condition, Arcjet will return an ERROR type and you can check the reason property for more information, like accessing decision.reason.message.

/app/api/hello/route.ts
import arcjet, { detectBot } from "@arcjet/next";
import { NextResponse } from "next/server";


const aj = arcjet({
  key: process.env.ARCJET_KEY!,
  rules: [
    detectBot({
      mode: "LIVE",
      allow: [], // "allow none" will block all detected bots
    }),
  ],
});


export async function GET(req: Request) {
  const decision = await aj.protect(req);


  // If the request is missing a User-Agent header, the decision will be
  // marked as an error! You should check for this and make a decision about
  // the request since requests without a User-Agent could indicate a crafted
  // request from an automated client.
  if (decision.isErrored()) {
    // Fail open by logging the error and continuing
    console.warn("Arcjet error", decision.reason.message);
    // You could also fail closed here if the request is missing a User-Agent
    //return NextResponse.json({ error: "Service unavailable" }, { status: 503 });
  }


  if (decision.isDenied()) {
    return NextResponse.json(
      {
        error: "You are a bot!",
      },
      {
        status: 403,
      },
    );
  }


  return NextResponse.json({
    message: "Hello world",
  });
}

Testing

Arcjet runs the same in any environment, including locally and in CI. You can use the mode set to DRY_RUN to log the results of rule execution without blocking any requests.

We have an example test framework you can use to automatically test your rules. Arcjet can also be triggered based using a sample of your traffic.

See the Testing section of the docs for details.

Examples

Protecting a page

You can protect a Next.js page from bots by calling the Arcjet SDK from within the page loader:

Protecting an app router page within the handler itself is not currently supported, but you can set up a matcher on the middleware instead:

/middleware.ts
import arcjet, { createMiddleware, detectBot } from "@arcjet/next";
export const config = {
  // The matcher runs just on the /hello pages route
  matcher: ["/hello"],
};
const aj = arcjet({
  key: process.env.ARCJET_KEY!,
  rules: [
    detectBot({
      mode: "LIVE",
      allow: [], // "allow none" will block all detected bots
    }),
  ],
});
// Pass any existing middleware with the optional existingMiddleware prop
export default createMiddleware(aj);

Wrap existing handler

All the examples on this page show how you can inspect the decision to control what to do next. However, if you just wish to send a generic 403 Forbidden response you can delegate this to Arcjet by wrapping your handler withArcjet.

For both the Node or Edge runtime:

/app/api/hello/route.ts
import arcjet, { detectBot, withArcjet } from "@arcjet/next";
import { NextResponse } from "next/server";


const aj = arcjet({
  key: process.env.ARCJET_KEY!,
  rules: [
    detectBot({
      mode: "LIVE",
      allow: [], // "allow none" will block all detected bots
    }),
  ],
});


export const GET = withArcjet(aj, async (req: Request) => {
  return NextResponse.json({
    message: "Hello world",
  });
});

Edge Functions

Arcjet works in Edge Functions and with the Edge Runtime.

/app/api/hello/route.ts
import arcjet, { detectBot } from "@arcjet/next";
import { NextRequest, NextResponse } from "next/server";


export const config = {
  runtime: "edge",
};


const aj = arcjet({
  key: process.env.ARCJET_KEY!,
  rules: [
    detectBot({
      mode: "LIVE",
      allow: [], // "allow none" will block all detected bots
    }),
  ],
});


export default async function handler(req: NextRequest, res: NextResponse) {
  const decision = await aj.protect(req);


  if (decision.isDenied()) {
    return NextResponse.json(
      {
        error: "You are a bot!",
      },
      {
        status: 403,
      },
    );
  }


  return NextResponse.json({
    message: "Hello world",
  });
}

Discussion