Geotrackable.com
Trackables are the individual items that carry public codes, secret access, route history, optional images, and optional verified outside links.
That split is why Geotrackable keeps public-code pages, secret-code access, activation, map logging, images, and support reporting as related but separate workflows.
The public code is the safe share code for the public page. The secret code or private QR is the private control path that unlocks remembered browser access and protected workflow steps.
Secret codes and private QR values are intentionally shown only on the creation reveal page, so creators should save, print, or label them before leaving that screen.
A trackable can stay under one person or be activated to a team. Group-created items can begin with shared default title, description, status-message, and link values until item-level edits take over.
If you leave a group unactivated for later finders or recipients, Geotrackable can still treat you as a group follower so ownership and watch delivery choices merge cleanly when one of those items later overlaps with you.
A journey can include simple location reports and fuller location notes. Both move the route forward, but the route history stays tied to the saved stop while current visible location notes are rediscovered from the same coordinate.
Public pages can show a route map, journey stops, public-safe images, and a verified external link without exposing the private controls used to move the item.
A public trackable page can show the public code, title, story, route map, logged stops, owner or team label when that information is meant to be public, uploaded images that are visible to the page, and one verified external link when the owner has added one.
If the item belongs to a public trackable group, the page can also link back to that batch page. Location-only stops can still appear in the travel log, and visible location notes can appear from the same coordinate when the viewer has access to them.
Secret codes, private QR values, remembered-access tokens, one-time creation reveal details, and private workflow controls are not copied onto the public page.
That is why the public code is the safe code to print or share widely, while the secret code should stay with the person physically handling the item or managing the private workflow.
A group watch still covers the visible member trackables in that batch, but Geotrackable now merges the delivery choices when the same person later becomes an owner too.
That means a creator can leave a batch unactivated for later finds or handoffs, keep following the whole release, and still avoid duplicate email or text when one item eventually overlaps with their own ownership scope.
A simple location report is the lightweight route point. It is useful for a quick geocaching handoff, a drop, or a find when the person in the field just needs to move the journey forward.
A full location note is the richer version. It can carry longer text, fuller note access rules, and its own media or links when the workflow calls for more than a quick stop.
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.
Both save into the journey, and Geotrackable now opens a receipt page after each save so the person logging can verify the exact point before moving on.
Use the single-item flow when one physical item needs its own title, visibility choice, image set, external link, category, and activation plan.
Create a Single TrackableUse the group flow when multiple items should start from one shared setup and then diverge later through overrides or activation.
Create a Group of TrackablesUse My Trackables for the broader card list, My Trackable Journeys for the shared journey map with your personal filters already selected, the clean /trackable/{code} page for one public item, and /trackable-group/{code} when the grouped release itself is the public story.
My Trackable JourneysUse the field guide when you want the full path from creation to cache placement to finding and logging the next move.
How to Geocache GeotrackablesTrackables usually become more useful when their stops are logged as real locations instead of guesses, and when any uploaded images actually help people recognize the item or understand the story.
Images are screened before they are saved, processed into Geotrackable-managed image files, and tied to the visibility of the parent trackable or team page. Image reports should go through the public report buttons or the support page when something looks unsafe or out of date.
Trackable links are verified before saving. Geotrackable checks that the link is a valid outside address, tries to read the page title, and rejects localhost-style or private-network destinations instead of storing them.
If a link later looks broken, misleading, or unsafe, use the support page or the report path tied to that page so support can review the destination and decide whether it should be removed.
Use the public code for public browsing, use the secret code or private QR only for the person with real access to the item, decide whether the right follow is the single item or its whole group, and use support reporting when a page, image, or link no longer matches what should be public.
That keeps the route story readable, keeps the private controls private, and makes it easier for Geotrackable to stay accurate even when the trackable changes hands many times.
