No, the Marketing URL in App Store Connect is not required; it is an optional field you can leave blank. The field that is required is the Support URL, which every app must have. So if you are blocked at submission wondering about the Marketing URL, you can skip it and submit. The practical questions that actually matter are whether users see and click it, what to do if you have no website, and whether Apple checks it, and the short version is: it appears on your product page as a link some users may click, you should leave it blank rather than invent one if you have no site, and while Apple does not require it, a Marketing URL you do provide should work, because a broken link can cause a metadata rejection.
Short answer
The Marketing URL is optional; leave it blank if you do not have a relevant page. Per Apple's App Store Connect help, the Marketing URL is an optional app information field, while the Support URL is required. If you provide a Marketing URL, it shows on your App Store product page as a link users can click, so it should load and be relevant to your app. Apple does not require it, but per the App Review Guidelines, metadata including your URLs must be accurate, so a broken or irrelevant Marketing URL can draw a rejection. With no website, leave it empty and make sure your required Support URL works.
Is the Marketing URL required?
No, the Marketing URL is not required, and you can submit your app with the field empty. It is an optional piece of app information meant to point to a promotional or marketing page for your app, and Apple treats it as a nice-to-have rather than a submission requirement. If your only question is whether a blank Marketing URL will block your submission, it will not.
The field that is required, and the one people sometimes confuse with this, is the Support URL. Every app must provide a Support URL where users can get help, and leaving that blank will block you. The Privacy Policy URL is also required for essentially all apps. So among the URL fields, remember that Support and Privacy Policy are mandatory while Marketing is optional. Knowing which is which saves you from either scrambling to invent a marketing page you do not need or, worse, skipping the Support URL that you do.
Where the field is and what to put
The Marketing URL lives in your app's information in App Store Connect, alongside the Support URL and Privacy Policy URL, on the page where you manage your app's metadata. It takes a full web address, so a valid entry is a complete URL to a page about your app, such as your app's landing page or product page on your own site. There is no special format beyond being a working link that is relevant to the app.
What to put there depends entirely on whether you have a suitable page. If you have a website or landing page for the app, use that URL. If you have a general company site rather than an app-specific page, a relevant page on it is fine. What you should not put is an unrelated URL, a placeholder, or a link to somewhere that has nothing to do with the app, because the point of the field is to send interested users to real information about your app, and an irrelevant link works against that and against review.
Do users click the Marketing URL?
Yes, users can click the Marketing URL, because when you provide one it appears on your App Store product page as a link, so it is public-facing rather than internal. On the product page, alongside the developer information, a provided Marketing URL is shown as a way for interested users to visit your app's page, and anyone browsing your listing can follow it. In practice, only a small share of visitors click through, but the link is real and reachable.
Because it is user-facing, treat the Marketing URL as part of your public presentation, not a hidden form field. If you provide one, it should lead somewhere that reflects well on your app and gives a visitor useful information, since it is a link your potential users may follow from the store. And because it is optional, there is no benefit to providing a weak or broken link just to fill the field; an empty Marketing URL simply means no such link appears, which is better than a link that disappoints or fails.
What should you put if you have no website?
If you have no website, leave the Marketing URL blank, because it is optional and a blank field is the correct answer when you have nothing relevant to link. Do not invent a URL, use a placeholder, or link somewhere unrelated to fill it, since an irrelevant or non-working link is worse than no link and can cause problems at review. An empty Marketing URL is completely acceptable and will not affect your submission.
The field you cannot leave blank, even without a website, is the Support URL, which is required. If you have no site at all, you still need somewhere users can get support, so create a simple page for it, which can be as minimal as a basic landing page or a page with a support contact, and some developers use a free page or a link to a support form. So the practical split for a developer with no website is to leave the optional Marketing URL empty and put a minimal but working page behind the required Support URL, rather than trying to fabricate a marketing presence you do not have.
Does Apple verify it?
Apple does not require the Marketing URL, but if you provide one, it should work, because App Review can check the URLs on your listing and holds your metadata to an accuracy standard. Reviewers may follow the links you supply, and a broken or clearly irrelevant URL can lead to a metadata rejection, since your app information is expected to be accurate. This applies more strictly to the required URLs, a broken Support URL or Privacy Policy URL is a common rejection cause, but a Marketing URL you choose to include is part of the metadata that should hold up.
The practical takeaway is that verification is a reason to either provide a good URL or none at all. If your Marketing URL loads and is relevant, it is fine; if it is broken, points somewhere unrelated, or was a placeholder you forgot to update, it can cause a delay you did not need, because the field was optional in the first place. So before submitting, either confirm your Marketing URL works and fits your app, or remove it. Never leave a dead or wrong link in a field you were not obligated to fill.
Marketing URL versus the required URLs
Sorting the URL fields clarifies what you actually must provide. The table below compares them.
| Field | Required? | Purpose |
|---|---|---|
| Marketing URL | No, optional | A promotional or marketing page for the app |
| Support URL | Yes, required | Where users get help and support |
| Privacy Policy URL | Required for essentially all apps | Your privacy disclosure |
Read the table before you scramble: only the Support and Privacy Policy URLs can block your submission, while the Marketing URL is optional and safely left blank.
Field checklist
Working through the URL fields correctly avoids both scrambling and rejections. The checklist below covers them.
| Step | Action | Done? |
|---|---|---|
| Decide on a marketing page | Use a relevant app page if you have one | [ ] |
| Leave blank if none | Do not invent or use a placeholder URL | [ ] |
| Use a working link if provided | Loads and is relevant to the app | [ ] |
| Set the Support URL | Required; must be a working page | [ ] |
| Set the Privacy Policy URL | Required for essentially all apps | [ ] |
| Verify all links before submit | No broken or wrong URLs | [ ] |
The step that prevents a rejection is verifying every link before you submit, especially the required Support and Privacy Policy URLs, and removing any Marketing URL that does not work.
Secure the app behind the listing
Filling in your store fields correctly gets you through submission, but the fields are only the listing; the app users download is what carries the real risk. Getting the Marketing URL right does nothing for whether your build ships a leaked key or an insecure data flow, which is a separate and more consequential check.
A scanner like PTKD.com analyzes your build and reports issues such as leaked keys and secrets, insecure data storage, and over-broad permissions by severity, mapped to OWASP MASVS, so you catch real security issues while you are finishing the submission details. To be clear about the boundary: PTKD does not fill in your App Store Connect metadata, set your URLs, or submit your app. It checks the build behind the listing so the app you ship is as sound as the metadata is complete.
What to take away
- The Marketing URL in App Store Connect is optional, so you can leave it blank and submit; the Support URL is the one that is required.
- If you provide a Marketing URL, it appears on your product page as a link users can click, so it should load and be relevant to your app.
- With no website, leave the Marketing URL empty rather than inventing one, and put a minimal working page behind the required Support URL.
- Apple does not require the Marketing URL, but a broken or irrelevant one you provide can cause a metadata rejection, so verify it or remove it.
- Verify every listing URL before submitting, and check the app behind the listing with a tool like PTKD.com.
