workspace-domains feature flag is enabled for your workspace.
Link and verify a domain
- Open Domains in the sidebar.
- Click Link domain and enter the hostname (for example
example.com). - Complete verification on the link-domain page. Hyperlocalise supports:
- DNS TXT — add a TXT record at
_hyperlocalise.{domain} - HTML file — upload a token file to the site root
- Meta tag — add a
<meta>tag to the homepage
- DNS TXT — add a TXT record at
- Click Verify when the record or file is live.
Research surfaces
Open a linked domain to switch the sidebar to domain-scoped navigation. Each surface is its own route under/org/{slug}/domains/{domainId}/….
The locale selector lives in the page header, not as a separate tab. Pick a market to filter metrics and research data. The selected market persists in the URL as
?locale={marketId} and stays when you move between surfaces.
If a market has no saved data yet, the UI shows an explicit empty state instead of mixing in another locale’s metrics.
Supported markets
Live domains currently expose four fixed research markets:
Every verified domain can use all four markets. Research rows are stored per market in Postgres (
marketId, DataForSEO locationCode, and languageCode).
Custom per-domain locale lists and link-dialog locale editing are planned but not persisted yet. Linking sends only the hostname today.
Keyword research workflow
On Keyword research:- Choose a market in the locale selector.
- Enter a seed keyword and expand ideas. Hyperlocalise calls DataForSEO Labs through the internal
go-svcservice (default 50 ideas, up to 200). - Open a SERP snapshot for any idea to inspect live organic results.
- Save keywords you want to track or revisit. Saved keywords persist per domain and market.
Rank tracking
On Rank tracking:- Select keywords to track for the current market (up to 20 keywords per refresh request).
- Run a refresh to fetch live positions for your verified hostname.
- Historical snapshots are stored for each tracked keyword.
Operator setup
Domains research is optional infrastructure. Segment validation ingo-svc works without it.
Web app
The Next.js app proxies research togo-svc over GO_SVC_URL. It does not read DATAFORSEO_API_KEY directly. The browser never sees the research service token.
go-svc
Set these on thego_svc Vercel service (see apps/go-svc/README.md):
Without
DATAFORSEO_API_KEY, research mutations return provider_not_configured or dataforseo_not_configured.
Research routes require both a signed-in WorkOS session cookie and the server-only X-Go-Svc-Research-Token header. Only the web app should call them.
API (organization scope)
Authenticated org routes live under/api/orgs/{organizationSlug}/linked-domains. All routes require the workspace-domains flag.
Linked domains
Research
Nested under/linked-domains/{id}/research:
Common error codes:
linked_domain_not_found, market_not_found, provider_not_configured, provider_unavailable, provider_rate_limited.