Why Geolocation and edge logic in NextJS? - Purpose & Use Cases

The Big Idea

Discover how moving location checks to the network edge can make your website feel lightning fast and smart for every visitor!

The Scenario

Imagine building a website that shows different content based on where your visitors are in the world. You try to check their location on the server and then send the right page. But every time someone visits, the server has to do extra work, slowing down the site.

The Problem

Doing location checks on the main server makes pages load slower because the server must wait for location data before sending the page. It also means more work for the server, which can cause delays and errors when many users visit at once.

The Solution

Using geolocation with edge logic means the location check happens closer to the user, at the network edge. This speeds up responses and lets your site quickly show the right content without overloading the main server.

Before vs After

✗ Before

const location = await getLocationFromIP(req.ip);
const content = location.country === 'US' ? 'Welcome US user' : 'Welcome visitor';

✓ After

import { headers } from 'next/headers';
export const runtime = 'edge';
export default function Page() {
  const country = headers().get('x-vercel-ip-country') || 'unknown';
  return <p>{country === 'US' ? 'Welcome US user' : 'Welcome visitor'}</p>;
}

What It Enables

This lets your website deliver personalized content instantly and reliably to users worldwide, improving speed and user experience.

Real Life Example

A news website shows local headlines and weather based on the visitor's country without delay, making users feel the site is made just for them.

Key Takeaways

Manual geolocation on servers slows down websites and adds errors.

Edge logic moves location checks closer to users for faster responses.

Combining geolocation with edge logic creates personalized, speedy web experiences worldwide.

Practice

1. What is the main purpose of using geolocation in a Next.js app with edge logic?

easy

A. To manage user authentication

B. To improve server-side rendering speed

C. To store user data securely

D. To customize content based on the user's location

Solution

1. Step 1: Understand geolocation usage

   Geolocation helps identify where a user is accessing the app from.

2. Step 2: Connect geolocation with edge logic

   Edge logic runs code near the user to customize responses quickly, often based on location.

3. Final Answer:

   To customize content based on the user's location -> Option D

4. Quick Check:

   Geolocation = Customize content [OK]

Hint: Geolocation customizes content by user location [OK]

Common Mistakes:

• Confusing geolocation with authentication
• Thinking geolocation improves rendering speed directly
• Assuming geolocation stores user data

2. Which of the following is the correct way to access the user's country code in Next.js middleware using edge logic?

easy

A. const country = request.geo.country

B. const country = request.location.countryCode

C. const country = request.headers['x-country']

D. const country = request.geoCode.country

Solution

1. Step 1: Recall Next.js middleware geo API

   Next.js provides a geo object on the request with location info.

2. Step 2: Identify correct property for country code

   The correct property is request.geo.country to get the country code.

3. Final Answer:

   const country = request.geo.country -> Option A

4. Quick Check:

   request.geo.country = country code [OK]

Hint: Use request.geo.country to get country code [OK]

Common Mistakes:

• Using incorrect property names like geoCode or location
• Trying to get country from headers without custom setup
• Confusing geo with location objects

3. Given this Next.js middleware code snippet, what will be the redirect URL if the user is from 'US'?

export function middleware(request) {
  const country = request.geo?.country || 'unknown';
  if (country === 'US') {
    return Response.redirect(new URL('/us-home', request.url));
  }
  return Response.next();
}

medium

A. /unknown

B. /home

C. /us-home

D. /

Solution

1. Step 1: Check country value from request

   The code sets country to request.geo?.country or 'unknown'. For a US user, it is 'US'.

2. Step 2: Analyze redirect condition

   If country is 'US', the middleware redirects to '/us-home'. Otherwise, it continues normally.

3. Final Answer:

   /us-home -> Option C

4. Quick Check:

   Country 'US' triggers redirect to /us-home [OK]

Hint: Country 'US' redirects to /us-home [OK]

Common Mistakes:

• Ignoring the redirect condition
• Assuming default path is used for US
• Confusing Response.next() with redirect

4. Identify the error in this Next.js middleware code that tries to redirect users from Canada to '/ca-home':

export function middleware(request) {
  const country = request.geo.country;
  if (country = 'CA') {
    return Response.redirect(new URL('/ca-home', request.url));
  }
  return Response.next();
}

medium

A. Missing optional chaining on request.geo

B. Using assignment '=' instead of comparison '===' in the if condition

C. Response.redirect should be Response.redirectTo

D. URL constructor is used incorrectly

Solution

1. Step 1: Check the if condition syntax

   The condition uses country = 'CA', which assigns 'CA' instead of comparing.

2. Step 2: Identify correct comparison operator

   It should use === to compare values, not =.

3. Final Answer:

   Using assignment '=' instead of comparison '===' in the if condition -> Option B

4. Quick Check:

   Use '===' for comparison, not '=' [OK]

Hint: Use '===' for comparison, not '=' [OK]

Common Mistakes:

• Confusing assignment and comparison operators
• Thinking Response.redirectTo exists
• Overlooking optional chaining necessity

5. You want to serve different homepage content for users from Europe and Asia using Next.js edge middleware. Which approach correctly implements this logic?

export function middleware(request) {
  const country = request.geo?.country || '';
  const europeCountries = ['FR', 'DE', 'IT'];
  const asiaCountries = ['JP', 'CN', 'IN'];

  if (europeCountries.includes(country)) {
    return Response.redirect(new URL('/eu-home', request.url));
  } else if (asiaCountries.includes(country)) {
    return Response.redirect(new URL('/asia-home', request.url));
  }
  return Response.next();
}

hard

A. This code correctly redirects European and Asian users to their homepages

B. The includes method cannot be used on arrays in middleware

C. The country variable should be fetched from request.headers instead

D. Response.redirect requires a status code as second argument

Solution

1. Step 1: Verify country detection and arrays

   The code safely gets country with optional chaining and defines arrays for Europe and Asia countries.

2. Step 2: Check redirect logic

   It uses includes to check membership and redirects accordingly, else continues normally.

3. Final Answer:

   This code correctly redirects European and Asian users to their homepages -> Option A

4. Quick Check:

   Array.includes works and redirects correctly [OK]

Hint: Use array.includes to check country and redirect [OK]

Common Mistakes:

• Thinking includes is not allowed in middleware
• Trying to get country from headers without setup
• Assuming Response.redirect needs status code