Direct answer
A project can hold both an App Store URL and a Google Play URL, which gives generation context about an existing, live listing rather than starting from a blank slate. This matters most for apps that are relaunching, rebranding, or refreshing their listing — the existing URL tells the workflow this is an update to something real, not a cold-start pitch for something that doesn't exist yet.
Cold start vs. relaunch are different generation problems
A brand-new app's listing copy has to introduce the app from zero — establish what it is, who it's for, and why it matters, with no prior context to build on. A relaunch is a different problem: there's already an existing listing, existing users, and often existing store history, so the copy needs to read as a continuation or an improvement rather than a reintroduction. Filling in the existing store URLs is how a project signals which situation it's actually in.
What the URL fields don't automatically do
Adding an App Store or Google Play URL provides context that this is an existing listing — it is not a substitute for putting the actual current listing content into the description and highlights fields. If the current listing has claims, positioning, or feature framing worth preserving, that still needs to be captured explicitly in the project's other inputs rather than assumed from the URL alone.
Use both URLs even for a single-platform-first launch
If an app already has a live listing on one platform and is expanding to the other, filling in the existing URL for the live platform still helps — it gives the project a real reference point for tone and positioning continuity even while the new platform's listing is being generated fresh.
Common mistakes
- Leaving both URL fields blank for an app that already has a live listing, losing the relaunch/update context.
- Assuming the URL field itself pulls in the existing listing's copy — it doesn't replace writing the current positioning into the description.
- Filling in the URL but not updating the description to reflect what's actually changing in this update.
Checklist
- Add the existing App Store or Google Play URL whenever a listing already exists, even if only on one platform.
- Explicitly describe what the current listing already claims, not just what the update is meant to add.
- Be clear in the description about what's actually changing — new positioning, new feature, or just a refresh — since the URL alone doesn't communicate that.
Operating rule
The URL fields tell the workflow this is an update, not a launch — but the actual continuity or change in positioning still has to be written into the project's other fields by hand.