Geolocation Testing

Your website may look different depending on where your visitors are. Language versions, compliance banners, regional pricing, and cookie notices can all change based on location. Use geolocation testing to validate what visitors in a specific region see before you publish.

Where to find it

The Region dropdown is in the Basic Setup section when creating or editing a scan. Select a region and Sitepager runs the scan from that location.

Sitepager supports 30+ regions. The default is United States. The regions available in your workspace are configured for your account. If you need a region that is not showing, contact support@sitepager.io and we will add it.

How it works

When you select a region, Sitepager routes the scan through that location. Your site receives the request as if a real visitor from that country loaded the page.

Your site’s geolocation logic runs naturally. If your site serves different content based on IP location, that content appears in the scan results. Cookie banners, language redirects, regional pricing, compliance notices. Whatever your site shows to visitors in that region is what the scan captures.

Setting it up

1. Click New Scan from the Dashboard
2. Enter your Website URL
3. Select a Region from the dropdown in Basic Setup
4. Configure the rest of your scan settings as needed
5. Click Run Scan

Screenshots, broken links, SEO checks, and all other results reflect what a visitor from that region would see.

Your first run creates the baseline for that scan. Every subsequent run compares against it.

One region per scan

Each scan runs from a single region. To validate your site from multiple regions, create a separate scan for each one.

For example, if your site serves content in English (US), French (France), and Chinese (Hong Kong), create three scans:

• Main Site - Desktop - US
• Main Site - Desktop - FR
• Main Site - Desktop - HK

Each scan has its own baseline and run history. Changes to your US scan do not affect your France baseline.

What to validate

Language versions If your site redirects visitors to a language-specific version based on their location (for example, /fr for French visitors), the geolocation scan captures that redirect and screenshots the localized version.

Compliance banners GDPR cookie notices for European visitors, CCPA banners for US visitors. These often appear or disappear based on region. Run scans from the relevant regions to confirm they appear correctly.

Regional pricing and offers If your site shows different pricing, currencies, or promotions based on location, validate each version with a regional scan.

Currency and date formatting Numbers, dates, and currencies may format differently by region. A geolocation scan shows exactly how they render for visitors in that location.

Multilingual sites

For sites with language-specific URL paths (like /fr, /de, /es), you have two options.

Option 1: Use the language path as your Website URL. Set the Website URL to yoursite.com/fr and select France as the region. This scans the French version of your site from a French IP.

Option 2: Use your root URL and let geolocation handle the redirect. Set the Website URL to yoursite.com and select France as the region. If your site redirects French visitors to /fr, Sitepager follows the redirect and captures the French version.

Option 1 gives you more control. Option 2 validates that your redirect logic works correctly.

For either option, use exclude patterns to scope the scan to only the relevant language path. Include & Exclude Pages

Verifying region routing

To confirm a scan is routing from the correct region:

1. Click New Scan
2. Enter https://visitor-info-app.vercel.app/ as the Website URL
3. Select the region you want to verify
4. Click Run Scan
5. Open the screenshot. It shows the IP address, country, and city the scan ran from.

This is a one-time verification step, not part of your regular workflow.

How it fits into the release process

Run geolocation scans alongside your standard pre-publish checks before any update that touches region-specific content.

Typical flow:

1. Make your changes
2. Re-run your baseline scan to confirm the site looks right
3. Re-run your geolocation scans to confirm each regional version looks right
4. Publish

Tips

Start with your highest-traffic regions. Check your analytics to see where your visitors come from and prioritize those regions first.

Use consistent scan settings across regions. Keep the same device, max pages, and scope settings so you can compare results meaningfully.

Name your scans with the region. Use names like “Full Site - Desktop - FR” or “Key Pages - Mobile - HK” so you can find and re-run them quickly.

Re-run regional scans before updates that touch global styles or shared components. A CSS change or template update can affect every language version. Re-running all regional scans before publishing catches issues across all versions.