Back to blog

support url not working app review

Support URL Not Working in App Review: How to Fix It Fast for iOS Submissions

If Apple says your support URL is not working during app review, this guide shows the exact causes, fixes, and examples Apple expects, plus how to set up a stable support page and privacy policy for your iOS app website.

February 20, 20264 min read955 words

When Apple reports “support URL not working” during app review, they usually mean the link you provided in App Store Connect fails to load reliably, is blocked, requires a login, or doesn’t contain support contact information. The fix is almost always straightforward: publish a public, fast, mobile-friendly support page on a stable HTTPS URL, verify it loads from a clean device/network, and ensure it clearly offers a way to contact you. This article walks through the most common review failures and gives copy-and-paste examples you can use today.

What Apple means by “support URL not working”

In App Store Connect, the Support URL is expected to be a publicly accessible web page that helps users get assistance with your app. During review, Apple staff will open the link in a standard browser environment. If it times out, redirects unexpectedly, shows an error, blocks certain regions, or requires authentication, they may mark it as not working.

A “working” support URL is not just a page that loads sometimes on your home Wi‑Fi. It should load consistently over HTTPS, on mobile, without popups, without app-only deep links, and without requiring an account to view basic support info.

Quick checklist: the minimum a support page should include

A valid HTTPS URL (not an http link)

A page that loads without a login, invite, or paywall

A visible support contact method: email link (mailto), contact form, or both

Your app name and basic help context (so it’s clearly for that app)

Most common reasons the support URL fails in App Review (and how to fix each)

1) The URL redirects to an app-only deep link or opens inside another app. Fix: Use a normal web URL that stays in the browser and displays support information immediately. Avoid links that trigger universal links to open your own app, Discord, Slack, Notion apps, etc.

2) The page requires a login (Google Drive, Notion workspace, Airtable, Zendesk portal with auth, private GitHub repo). Fix: Make the support page public. If you use a hosted knowledge base, confirm anonymous access to the specific page.

3) The domain or certificate is misconfigured. Fix: Ensure the site uses HTTPS with a valid certificate chain. Avoid expired certificates, mixed content errors, or redirects that land on HTTP.

4) The page is blocked by geography, IP reputation filters, or firewall rules. Fix: Remove country blocks. If you use Cloudflare or similar, ensure Apple’s review traffic isn’t challenged with CAPTCHA/managed challenges. Disable “Under Attack” mode and avoid requiring JavaScript challenges just to view the page. Test from a different network or a VPN to simulate reviewer access patterns (without doing anything that violates policies).

URL formatting issues in App Store Connect that cause “not working”

Use a complete URL including https://

Avoid spaces, missing characters, or copying the wrong environment URL (staging vs production)

Avoid temporary preview links (for example, share links that expire)

Avoid URLs that immediately download a file instead of showing a support page (PDF-only is risky)

How to test your support URL the way reviewers do

Open the link on a device that is not signed into your accounts (or use a private browsing window) and confirm it loads fully.

Test on cellular data and on a different Wi‑Fi network to rule out DNS or firewall issues.

Test on an older iPhone screen size to ensure the support email/contact method is visible without weird layout issues.

Check that the page loads quickly. If your hosting is slow, Apple may time out before it renders.

What a good support page looks like (copy-ready examples)

Example support page structure (simple, effective):

AppName Support

Contact: support@yourdomain.com

Common questions: How do I restore purchases? How do I export data? How do I delete my account? (If applicable)

Frequently asked questions

Can I use a Twitter/X profile, Discord invite, or App Store page as my Support URL?

It’s risky. Social profiles or community chat invites can be blocked, require login, or change over time. A dedicated web page on your own domain is the most reliable option for app review and long-term users.

Is an email address alone enough for the support URL?

Apple asks for a Support URL, so you should provide a webpage. The page can be simple, but it should clearly display your support email and/or a contact form.

My support page works for me but Apple says it doesn’t. What should I do?

Assume the reviewer is hitting a different network, region, or browser state. Check for CAPTCHA challenges, region blocks, login requirements, expiring share links, or DNS/certificate issues. Test in private browsing and from a different network, and confirm the URL is HTTPS and stable.

Do I need a privacy policy link too?

Often yes. If your app collects any data, uses analytics, has accounts, or otherwise triggers Apple’s privacy requirements, you should publish a privacy policy page and link it in App Store Connect. Even when not strictly required, it reduces review friction.

How does MyAppDeck help with support URLs and legal pages?

If you want a quick, stable web presence for App Store submissions, MyAppDeck can be used to publish an app website with dedicated pages like Support and Privacy Policy, giving you clean URLs you can paste into App Store Connect.

Promote your app

Turn this strategy into real app growth

Launch a polished website for your app with a conversion-ready landing page, support URL, and hosted privacy and terms pages. Get App Store-ready and start promoting faster.

Related articles