Skip to content
Policies & Jurisdictions

Adapt

Planned

See the site the way each region gets it.

Preview the banner, the defaults and the enforcement behaviour for each configured region before publishing, and test them afterwards — the same site can legitimately behave differently in three places, and you should be able to look at all three.

Regional Experiences

  • Per-region preview
  • Per-region verification
  • Difference view
  • Fallback behaviour

How it helps

What you get with Regional Experiences

1

Preview before publish

Catch the region whose configuration was never finished before a visitor does.

2

Test after publish

Privacy Health can run per region, so the verification covers what is actually served.

3

Differences are visible

A side-by-side view of what differs, rather than three separate screens to remember.

Know what runs before you ask visitors to trust it.

Start with a scan of what your website loads today. The list is usually longer than the team expects, and that is the useful part.

No code to install for a scan Public pages only DotCensus runs on DotCensus