Rendex
Get API key
Recipe

Compare a Page Rendered from Different Countries in n8n

Localized pricing, geo-gated content, and regional CDNs mean users in different countries see different pages. Capture the same URL from each country in parallel with Rendex geo screenshots and merge them for a side-by-side check — all in one n8n workflow.

Last updated 2026-07-21

Get Free API KeyDownload n8n templateSetup Guide

The Problem

You ship different pricing, offers, or content by region, but you can't easily see what a user in Germany or Japan actually gets. VPN-hopping by hand is slow and unreliable, and a normal screenshot only ever shows your own location.

The Solution

Set Geo Country on each Rendex capture to an ISO code — US, DE, JP, GB — and the page renders from that country's egress. Run the captures in parallel branches, then a Merge node combines them into one item so you can review or store the regional variants together. Add a branch per country you care about.

How the Workflow Runs

Trigger

A manual run or schedule starts the comparison

Rendex geo ×N

Capture the same URL from each country in parallel

Merge & compare

Combine the captures into one item for side-by-side review

Input → Rendered Output

Two screenshots of the same pricing page side by side, one labeled US and one labeled DE, showing different currencies and offers.

Rendered by Rendex

What You Need

  • A Rendex API key on the Pro or Enterprise plan (geo targeting is Pro+)
  • n8n with the Rendex community node installed
  • The URL you want to compare across regions
  • The ISO country codes to test (e.g. US, DE, JP)

What This Recipe Uses

Render from any country

Set Geo Country to an ISO code and the page renders from that country's egress — see exactly what regional users see.

Parallel + merge

Run a capture branch per country in parallel, then combine them with a Merge node for a single side-by-side result.

Verify localization

Confirm localized pricing, currency, geo-gated offers, and regional CDN variants without VPN-hopping by hand.

Build It

rendex-geo-node.json
{
  "parameters": {
    "resource": "screenshot",
    "operation": "capture",
    "source": "url",
    "url": "https://example.com/pricing",
    "format": "png",
    "binaryPropertyName": "de",
    "additionalOptions": { "geo": "DE", "fullPage": true }
  },
  "name": "Rendex — Capture (DE)",
  "type": "n8n-nodes-rendex.rendex",
  "typeVersion": 1
}

100 free API calls/month — no credit card required. Get your API key and start building.

This workflow is for teams whose page changes by geography and who need proof of what each region sees. Growth teams verify localized pricing and currency; content teams confirm geo-gated availability; performance teams check that the right regional CDN or edge variant is being served. Each Rendex node sets a single ISO country code, and because the captures run in parallel branches feeding a Merge node, adding another country is just another branch. Geo targeting is a Pro/Enterprise feature and is visual-only — a geo render returns the image, not extracted text, so it can't be combined with a text diff. Point the branches at the same URL, label each by country, and store or diff the results however your review process needs.

Frequently Asked Questions

Related Resources

Documentation

Free Tools