Use the page a returning user wants first, not the page a new visitor needs. For stores and blogs that's usually the home page; for SaaS, forums and dashboards it's the logged-in area (for example /app or /dashboard) that redirects to login when needed. Always use the final https:// address, avoid redirects and tracking tags, and add one deliberate parameter like ?source=android_app if you want to measure app traffic.
Match the start URL to what users do
| Kind of site | Good start URL | Why |
|---|---|---|
| Online store | / or /shop | Browsing is the first thing people do |
| SaaS / web app | /app, /dashboard | Skips the marketing landing page |
| Forum / community | /latest | Fresh posts beat an about page |
| Course platform | /my/ or the course list | Learners want their courses |
| Booking page | The booking widget itself | One tap to book |
| News / blog | / | Latest stories first |
Get rid of redirects
If example.com redirects to www.example.com which redirects to /en/, every launch pays for three round trips on a mobile network. Paste the address you finally land on. Also check the http→https redirect isn't part of the chain.
Parameters: one on purpose, none by accident
Copying a link from an ad or email often drags along utm_*, fbclid or gclid tags. Baked into the app, they'd attribute every app session to that old campaign. Strip them, then add a single clear marker if you want to segment app users in analytics. The app UTM link builder does both.
Subdomains change the app's scope
Most converters treat the start URL's domain as “inside the app”. If your shop is on shop.example.com but login happens on accounts.example.com, make sure both are inside, or login will bounce to an external browser and the session won't come back. Map your links with the link scope tester.
Fragments and single-page apps
For single-page apps that route with #/, the fragment is part of the start URL and is fine to include. For apps using history routing, make sure the server returns the app for deep paths — reloading /dashboard mustn't 404.
FAQ
Can I change the start URL after publishing?
Yes, by building a new version with a higher version code and publishing it as an update. The package name stays the same.
Can I use an IP address or localhost?
Only for testing on your own network. Published apps need a public https domain — see intranet URLs for private tools.
Should the start URL include a language path?
Only if all your users speak that language. Otherwise let the site detect language from the phone's settings.