App Store Connect asks for a Support URL on every app, and it will not let you submit without one. Unlike most metadata fields, this one ends up on your public product page — users tap it when something breaks — and a reviewer opens it before your app goes live.
It is the field most likely to be filled in with whatever URL was closest to hand, and that is exactly why it causes avoidable rejections.
What the field expects
A support URL is an http or https address pointing at a page where a user of your app can get help. Three constraints matter:
- It must be a URL, not an email. A
mailto:link is not accepted in the field. Put the email address on the page instead. - It must open without a login. The reviewer will not create an account to read your support page, and neither will a frustrated user.
- It must be about your app. A generic company homepage with no mention of the app leaves the reviewer — and the user — with nowhere to go.
The mistakes that get flagged
Ranked roughly by how often they show up in rejection threads:
- A social media profile. X, Facebook or Instagram profiles are the most common substitute and the most commonly rejected: several require a login to view content, and they are blocked outright in some regions.
- A dead or placeholder page. The same class of problem as a broken privacy policy link, and one of the standing reasons apps get rejected.
- A link to the App Store listing itself. Circular, and reviewers notice.
- A page in the wrong language for the storefronts you are shipping to.
What to put on the page
A support page does not need to be elaborate. For most apps, one page covering the following is enough:
- The app name, and one line on what it does.
- How to get help — an email address that you actually read.
- Answers to the three or four questions you already get asked most.
- A link to your privacy policy, since you need one of those too.
- If your app has user accounts, how to delete one — increasingly its own requirement rather than a nice-to-have.
- A last-updated date, so it does not read as abandoned.
Where to host it
This is one static HTML page that has to stay reachable for as long as the app is on the store. No database, no build step, nothing dynamic.
If you have a site, add a /support page and use that. If you do not, you can host it free as a static site — upload a single index.html and paste the HTTPS URL into App Store Connect. Since the privacy policy has the same shape of requirement, it is usually least effort to write both pages at once, zip them together, and get one URL for each.
The support URL lives under App Information in App Store Connect, which means it applies to the app rather than to a specific version. You can correct it without shipping a new build — useful, because the most likely failure is not the day you submit but the day the page quietly goes away.
Frequently Asked Questions
What is a support URL for an app?
It is a web page where users of your app can get help. App Store Connect requires one for every app, and the link appears on your App Store product page under the developer information.
Can the support URL be an email address?
No. The field expects an http or https URL, not a mailto link. You can put a contact email on the page it points to, and that is the usual pattern for small apps.
Can I use my Twitter or Facebook profile as the support URL?
It is a common cause of rejection. A social profile is not a support page, may require a login to view, and can be inaccessible in some regions. Point at a page you control instead.
Can the support URL and the marketing URL be the same?
They can point at the same site, but the support URL should land on something that actually helps a user with a problem. The marketing URL is optional; the support URL is not.
Does the support page need to be a full website?
No. A single page with what the app does, how to get help, a working contact route and a last-updated date satisfies the requirement.
