A support site for people experiencing domestic abuse needs descriptive search results, but those titles could also be visible in browser tabs and history. Is there a way to make titles less revealing for visitors without losing search visibility?
A quick exit button and guidance on private browsing are already planned. I'm wondering whether changing the title with JavaScript is viable, and whether showing search engines something different would be considered cloaking.
Changing document.title after load isn't a reliable way to give search engines one title and visitors another. Search engines can render JavaScript, and the title shown in search results may differ from either version. Test the rendered page and search results rather than assuming the original HTML title will be used.
Serving a descriptive version specifically to search bots and a different version to everyone else raises a cloaking concern. I'd avoid user-agent detection as the solution and check the search engine's current guidance before considering any differential serving.
A neutral domain and neutral URL paths may be worth considering alongside titles. A discreet tab title won't help much if the address itself identifies the subject in history or autocomplete.
One possible design is a discoverable site plus a separate, discreet address visitors can choose to use. That needs careful planning around duplicate content, indexing and navigation, and it still won't erase the route someone took to get there.
Please don't present title masking as a way to hide the visit. Search queries, browser history, synced accounts and other device records may still reveal it. Private browsing can reduce some local traces, but it doesn't make browsing invisible to everyone or guarantee safety on a monitored device.
Give visitors a clear, discreet explanation of the limits and involve people with safety expertise in the design. A quick exit is useful as an option, not a promise that evidence of the visit is gone.
Be cautious with history.replaceState and location.replace. They can change the current history entry or navigation behavior, but they don't reliably wipe earlier visits or searches. Breaking the back button could make the site harder to use without providing the protection people expect.
Test any changes across the browsers and devices the audience uses, including what appears in tabs, history and autocomplete. Treat that as a usability and safety check, not proof that no trace remains.
Answers are reviewed before publication.
y408~gearlock_3:
There could also be a brief flash of the original title before the script runs, so the timing matters for safety as well as indexing.