Does my app's landing page need to live on a different site from my privacy policy?

No. A Forvibe landing page and a project's generated legal pages, privacy policy included, are served from the same project domain, so the policy can live at a path under the same URL as the landing page rather than needing a separate site.

Is a Marketing URL required in App Store Connect?

No, it is optional. Apple describes it only as the website where users get more information about the app. A Privacy Policy URL, by contrast, is required for every app with no exception, and a Support URL is required and has to lead to actual contact information, not just a generic homepage.

Can I submit an app with a free Forvibe subdomain as its landing page, or do I need a custom domain?

A free subdomain is enough. Creating a project in Forvibe's console includes choosing one, so a project set up that way has a working yourapp.forvibe.app URL once a page is published and set live. What Apple's and Google's own pages describe is what a URL has to do, resolve, show a real privacy policy, and, for the Support URL, show real contact information, not what kind of domain it sits on. A custom domain is a paid upgrade for branding, not something tied to either store's submission requirements.

What happens to a landing page's URL if a custom domain gets added later?

The free subdomain keeps working alongside a verified custom domain; a project's dashboard shows both at once. Whatever URL is already entered in App Store Connect or Google Play Console keeps resolving exactly as before. Switching that entry to the custom domain afterward is a separate, manual edit in each store's console.

Does publishing a landing page automatically make it the page visitors see?

No. Publishing snapshots the page as a new version and marks it published, but a project can hold several landing pages at once and only one of them is active. A published page still has to be set as the active page before it replaces whatever is currently live at the project's URL.

For indie app developers

How to make a landing page for a mobile app

To make a landing page for a mobile app, you need one hosted page that says what the app does, links out to it on the App Store or Google Play, and carries a reachable privacy policy URL, since that is the one piece every store submission asks for no matter what the page looks like.

Build your landing page See pricing

No credit cardFree tier with 200 AI creditsCancel anytime

starter templates

live preview breakpoints

legal pages generated automatically

The short answer

Forvibe builds that page from a short description and a template: pick a starting layout, let AI write the initial headline, feature copy, and structure from what you describe, refine it with a chat-driven editor, then publish it to a free project subdomain or, on a paid plan, a custom domain you already own. A landing page built this way, or by hand, clears the same bar either way: a live privacy policy link, a download destination that actually resolves for the visitor's device, and metadata fields in App Store Connect and Google Play Console that describe the same app the page does.

The symptoms of a landing page that does not hold up at submission

A privacy policy link gets typed into App Store Connect or Google Play Console once and never checked again, so by the time a reviewer or a user clicks it, it 404s or still points at a placeholder from before the app existed.

A landing page's download button links straight to one store, so a visitor on the other platform lands on a page that cannot install anything for their device.

The Marketing URL or Support URL entered in App Store Connect points at a page that no longer matches what the app does: a renamed feature, a screenshot of an old screen, a support address nobody reads.

What a store submission actually needs from a landing page

Apple and Google gate submission on working links, not on how a page looks: a live Privacy Policy URL is required for every app, a Support URL with real contact information is required, and a Marketing URL is optional.

Privacy Policy URL required: Apple's own reference page lists a Privacy Policy URL as required for every app.
Support URL, real contact: Apple's Support URL is required and must lead to actual contact information: a legal address, email, or phone number.
Marketing URL is optional: The Marketing URL is optional, described by Apple only as where users go for more information about the app.
Google Play's own rule: Google requires the same privacy policy link to sit on a live, public, non-geofenced URL that isn't a PDF.
One domain, kept in sync: A Forvibe page, its legal pages, and any smart link redirects all publish from the same project domain.

Read the full explanation

Apple and Google both gate submission on working links, not on how a page looks. On the App Store, a Privacy Policy URL is required for all apps: that is exactly what Apple's own reference page says. Apple documents the rest of an app's public links as two separate fields: a required Support URL, which it says must 'lead to actual contact information (legal address, email address, telephone number)', and an optional Marketing URL, described only as 'the website where users get more information about the app.' Google Play asks for the same kind of privacy policy link, on the store listing page and inside the app itself, and is specific about the URL's condition: it has to be 'available on an active, publicly accessible and non-geofenced URL (no PDFs) and is non-editable.' Neither store's requirement is about design. A hand-built page and a generated one clear the same bar: a URL that resolves, says what it needs to say, and keeps matching the app once something changes. A Forvibe landing page publishes to a project's subdomain, or a verified custom domain on a paid plan, and that same domain also serves a project's generated legal pages, privacy policy included, and any smart link redirects configured for it. Once the page is live, the URL handed to a visitor is the same one entered as the Marketing URL, and the privacy policy's own path under it is the one entered as the Privacy Policy URL.

The sequence for building and publishing a landing page

Describe the app once
Give the page a name and, optionally, a short description of the app when creating it. That description is what steers the template's starting copy.
Pick a starting template
A page with no content yet opens straight into the template picker. Each template is a single HTML page, previewed at desktop, tablet, and mobile width inside the editor, so the choice at this step is about layout and tone, not separate markup per device.
Refine it with the chat editor
Describe what to change in plain language, attach a screenshot if it helps make the point, and the assistant rewrites the page's HTML directly. Nothing is public yet: every change stays a draft until it is published.
Publish, then set it live
Publishing snapshots the page as a new numbered version, but it does not make that page live by itself. A project serves one active page at a time, so a published page still has to be set as the live page to replace it.
Match the store metadata to the live page
Copy the page's URL into the Marketing URL field (optional), and into the Support URL field (required) only if it shows real contact information. Copy the project's privacy policy path into the Privacy Policy URL field on both stores.
Point the download button at a smart link
To send iPhone and Android visitors to their own store from the same button, use a project's smart link as the destination instead of one store's URL. It redirects by the visitor's platform automatically, with a fallback URL for anything else.

How the two approaches compare

Hand-rolled page

Generated in Forvibe

Starting a page

Design a layout, write copy, and build markup from a blank editor or a downloaded template

Pick a built-in template and describe the app; AI writes the initial headline, feature copy, and structure

Making changes

Edit HTML and CSS directly, or reopen whatever design tool built the original template

Describe the change in the chat editor and the assistant rewrites the page's HTML

Hosting, SSL, and a domain

Set up hosting, DNS, and a certificate before the page has a working URL

Publishes to a free project subdomain with hosting and SSL already handled; a verified custom domain is available on a paid plan

Write and host a separate privacy policy page, and wire the download button to each store by hand

The project's generated legal pages and any smart link redirects are served from the same domain as the landing page

Version history

Whatever the deploy pipeline or the last person to touch the files happened to keep

Every publish is saved as a numbered version with a change summary, so an earlier version can still be reviewed

Questions, answered

How Forvibe does this

Landing Page Builder

AI-powered landing pages for your mobile app

See Landing Page Builder

Ready to get started?

Create a free Forvibe account and put this into practice.

Build your landing page See how it works

Keep reading

Definition

App Store Connect

Definition

Google Play Console

Last updated: September 8, 2026