Geotrackable.com
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 clean public patterns like /trackable/{code} and /trackable-group/{code} instead of teaching people to copy temporary dashboard state or query-string selection URLs.
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. |
| Public trackable group page | /trackable-group/{code} |
/{culture}/trackable-group/{publicCode} |
Copy this when a family set, club batch, classroom kit, or other grouped release needs one public page for the whole set before visitors drill into individual member trackables. |
| Journey dashboard | Not a single-item share URL |
/{culture}/trackables/map?scope=my |
This is the signed-in filtered view of the shared journey map for reviewing multiple routes. Geotrackable also keeps a /trackables/my card list for broader signed-in browsing. Selecting one item loads its map, stop details, and journey inside the workspace instead of changing the browser over to the public single-trackable page. |
A public trackable is a specific thing, so the share URL should stay specific too. Geotrackable keeps that single-item public route on /trackable/{code} instead of teaching dashboard query strings or internal data URLs as public sharing patterns.
That lets one finder hand another finder a clean public route even when the same signed-in user also works from the dashboard, the journey workspace, or remembered secret access later.
A full location note can later move, go private, or disappear while the route keeps its earlier saved point. The public journey page shows the route stop first and then adds any current visible location notes from that coordinate when the viewer is allowed to open them.
The /trackables/map?scope=my dashboard and the related signed-in list routes are workspaces for filtering, comparing, and reopening multiple routes. They are not meant to replace the clean public share URLs.
Selecting one item there updates the map, stop details, and journey inside the dashboard. Geotrackable still keeps compatibility redirects for older /trackables/journeys and selected query-string links, but the current signed-in workflow stays in place until you choose a public page or another route yourself.
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.
A saved route stop and a visible location note are not always the same thing, so clean page families make it easier to share, support, and explain the right page.
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 trackables get /trackable/{code}. Public trackable groups get /trackable-group/{code}. Localized pages are where people may land, and signed-in dashboards stay workspace-only.
