Overview
Eyemoved now keeps property detail links compact while preserving return-to-results continuity.
Guide
Returning to search results from a property
How Eyemoved keeps property URLs short while preserving search context across details and contact flows.
The process
The path forward
Each milestone stands on its own—follow in order, or skip ahead when you already know the basics.
bookmark_add
How return navigation works
When you open a property from search results, Eyemoved uses a short context token in the URL. This avoids very long links while still remembering where you came from.
Primary context: short token (`r`)
Portable fallback context: compact snapshot (`rs`)
Legacy compatibility: older `returnUrl` links still resolve
tune
New tab and shared link behavior
If a short token cannot be resolved in a different tab/session, Eyemoved falls back to the compact snapshot and sends you to the nearest equivalent search route instead of losing context entirely.
Fallback targets are restricted to search-intent pages:
`/search-results`
`/for-sale`
`/to-rent`
notifications_active
Contact flow continuity
Return context is preserved through:
1. Property details -> Contact form
2. Verification step (when needed)
3. Contact success page
4. Back to property details and then back to search
This means you can enquire and still return to your search journey with fewer resets.
bookmark_add
What did not change
Canonical detail route remains `/properties/:id`.
Saved/account-origin breadcrumb behavior is unchanged.
Search filters still control result relevance; map view state remains presentation-level context.
Your journey continues with a single step.
Any questions? Our team is ready to help you find the right answer.
Was this helpful?