This guide explains which Geotrackable URLs are meant to be copied, which ones are just localized landing pages, and which ones should stay private or signed-in only.
That is why Geotrackable keeps the clean /trackable/{code} route for one selected item instead of teaching a second single-item path or a query-string selection URL.
The share URL column is what you should copy when you want another person to open a public page. The landing column is where the browser may actually render the experience once language and page rules are applied.
| Page family | Share URL | Browser landing | When to use it |
|---|---|---|---|
| Public profile page | /profile/{userName} |
/{culture}/profile/{userName} |
Use this when the profile itself is meant to be public. It is the short route you would copy into messages, printed materials, or posts. |
| Public team page | /team/{teamSlug} |
/{culture}/team/{teamSlug} |
Use this for the public-facing team page. Invite links and edit pages are different workflows and should not be copied as public addresses. |
| Public trackable page | /trackable/{code} |
/{culture}/trackable/{publicCode} |
Copy the short /trackable/{code} route. Geotrackable resolves that code into the localized single-trackable page for both public sharing and signed-in review. |
| Journey dashboard | Not a single-item share URL |
/{culture}/trackables |
This is the signed-in dashboard for reviewing multiple journeys. Once one item is selected, Geotrackable keeps the browser on the single-trackable /trackable/{code} page. |
A selected trackable is a specific thing, so the URL should stay specific too. Geotrackable now keeps that single-item route on /trackable/{code} instead of splitting the experience across a second GUID-based journey path.
The broader /trackables dashboard is the signed-in workspace list, but once one trackable is selected the canonical path stays on the single-trackable route.
Trackables keep a short share route because that route can safely accept a public code, a short secret code, or a long private scan token without teaching three different entry patterns.
If the code is public, Geotrackable lands the browser on the localized single-trackable page. If the code is private, Geotrackable can move into the protected handling flow instead. That is why /trackable/{code} stays the share URL while /{culture}/trackable/{publicCode} is the rendered page family.
People copy whatever URL is sitting in front of them. If the product teaches one clean public pattern, people are much less likely to paste an edit screen, a private workflow, or a credential-based route into a message by mistake.
That keeps Geotrackable easier to explain, easier to support, and safer for the people who only need the public story instead of the private control path.
Public pages get short share URLs. Localized trackable pages are where people may land. Private handling routes stay private. Once one trackable is selected, the clean route is /trackable/{code}.
