Geolocation and edge logic in NextJS - Step-by-Step Execution

Concept Flow - Geolocation and edge logic

User Request

↓

Edge Middleware runs

↓

Check Geolocation from request

↓

Apply Edge Logic

↓

Modify Response or Redirect

↓

Send Response to User

The flow starts with a user request hitting the edge middleware, which checks geolocation data. Based on location, it applies edge logic or defaults, then sends the response.

Execution Sample

NextJS

import { NextResponse } from 'next/server';

export function middleware(request) {
  const country = request.geo?.country || 'US';
  if (country === 'FR') {
    return NextResponse.redirect(new URL('/fr', request.url));
  }
  return NextResponse.next();
}

This middleware checks the user's country from geolocation and redirects French users to a French page, others continue normally.

Execution Table

Step	Request Geo Country	Condition (country === 'FR')	Action	Result
1	FR	True	Redirect to /fr	User redirected to /fr
2	US	False	Continue	User proceeds normally
3	undefined	False	Continue	User proceeds normally with default US

💡 Execution stops after redirect or continuing to next middleware/handler.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
country	undefined	FR	US	US (default)

Key Moments - 2 Insights

Why does the middleware redirect only when country is 'FR'?

Because the condition checks if country === 'FR' (see execution_table step 1). Only then it triggers a redirect; otherwise, it continues.

What happens if geolocation data is missing?

The code uses 'US' as a default (execution_table step 3), so it continues without redirect.

Visual Quiz - 3 Questions

Look at the execution table, what is the action when the country is 'US'?

A Redirect to /fr

B Redirect to /us

C Continue normally

D Throw an error

💡 Hint

Check execution_table row 2 under 'Action' column.

At which step does the condition country === 'FR' evaluate to true?

A Step 1

B Step 2

C Step 3

D Never

💡 Hint

See execution_table 'Condition' column for each step.

If the default country was changed to 'DE', what would happen at step 3?

A Redirect to /de

B Continue normally

C Redirect to /fr

D Throw an error

💡 Hint

Default country affects variable_tracker and condition check in execution_table step 3.

Concept Snapshot

Next.js Edge Middleware can access user geolocation via request.geo.
Use this to apply edge logic like redirects or content changes.
Check if request.geo?.country matches a target country.
Redirect or modify response accordingly.
Fallback to default if geolocation is missing.
This runs at the edge, before page rendering.

Full Transcript

This example shows how Next.js Edge Middleware uses geolocation data from the request to decide what to do. When a user sends a request, the middleware runs first at the edge. It checks the country code from request.geo. If the country is 'FR', it redirects the user to the French page '/fr'. If the country is 'US' or geolocation is missing, it continues normally. The variable 'country' tracks the detected or default country. This logic helps serve location-specific content quickly and efficiently at the edge.