SUPPORT · SELF-SERVICE TODAY
Know what to try. Know what is not staffed.
URLand does not publish a support address, response-time promise, or live intake form. These steps cover the current public mapper, guest battle, and browser-local progression.
Common paths
A SITE WILL NOT MAP
Check the public boundary
Use a complete public HTTP or HTTPS URL. The site must return HTML, permit the requested path, stay on its host boundary, and finish within the published limits.
A CITY IS PARTIAL
Read the frontier reason
Page, depth, time, robots, response, and network boundaries can stop a crawl early. Partial does not mean the unseen pages are absent.
PROGRESS DISAPPEARED
Check this browser and site data
Guest progression is browser-local. Private browsing, storage denial, clearing site data, or switching browsers can remove or isolate it. URLand cannot restore it from an account.
A BATTLE IS REJECTED
Keep both cities distinct and public
Both cities must resolve safely, represent different sites, use supported agents, and produce verified equal-start snapshots. Client-supplied power is ignored and rejected.
Useful product references
- Crawler policy — exact network, robots, content, and crawl limits.
- Game rules — equal starts, deterministic replay, rewards, and no pay-to-win.
- Privacy — public crawl data, browser-local state, deletion, and export limits.
- Status — tested components versus services that are not live.
Product boundary reviewed 11 August 2026.