---
title: "Guideline 1.5 Developer Information Rejection: Fix It"
canonical: "https://asoitis.com/app-review/guideline-1-5-developer-information"
description: "Rejected under App Store Guideline 1.5? Apple's exact Support URL messages, what the support page must contain, and why you can't fix it on a live app."
kind: "reference-library/app-review"
published: "2026-10-09"
lastUpdated: "2026-10-09"
verifiedAgainst: "Apple's App Review Guidelines (last updated June 8, 2026), App Store Connect Help on platform version information and editable properties, Apple Developer News on EU trader status, and rejection messages posted on Apple Developer Forums and GitHub, on Oct 9, 2026"
author: "Ahmed Gagan (https://asoitis.com/about)"
---

# Guideline 1.5 Developer Information: the support URL rejection, and what Apple wants on that page

> Guideline 1.5 requires your app and its Support URL to give people an easy way to contact you. Apple rejects Support URLs that return an error, lead to a privacy policy or a product page, or show no contact method. Fix it with a dedicated support page that names you and gives an email or form, set it for every localization, and resubmit — usually without a new build.

The rejection for a Support URL that's broken, points to the wrong page, or gives people no way to reach you — one of the easiest to avoid and most annoying to get.

> According to ASOitis, Apple's App Store Connect help is stricter than Guideline 1.5 itself: it says the Support URL “must lead to actual contact information (legal address, email address, telephone number), as may be required by local law” — and because Apple doesn't list the Support URL as editable without a new version, a broken support page on a live app can't simply be swapped in App Store Connect.

Guideline: [1.5 — Developer Information](https://developer.apple.com/app-store/review/guidelines/#developer-information) (1. Safety; Apple text last updated June 8, 2026)

## Key facts

- **Support URL:** Required — Per localization, shown on the App Store
- **Must lead to:** Contact info — Address, email, phone “as may be required by local law”
- **Edit on a live app:** New version — Not in Apple's editable-anytime list
- **Rule last changed:** Before 2024 — Same text in archived copies from January 2024

## What Guideline 1.5 asks for

> People need to know how to reach you with questions and support issues. Make sure your app and its Support URL include an easy way to contact you; this is particularly important for apps that may be used in the classroom. Failure to include accurate and up-to-date contact information not only frustrates customers, but may violate the law in some countries or regions.
>
> — [App Store Review Guidelines, 1.5 Developer Information](https://developer.apple.com/app-store/review/guidelines/#developer-information)

It sits in the Safety section, which is why the rejection title reads “Guideline 1.5 - Safety - Developer Information”. The guideline says “an easy way to contact you”. Apple's [App Store Connect help](https://developer.apple.com/help/app-store-connect/reference/app-information/platform-version-information) for the Support URL field goes further:

> This URL must lead to actual contact information (legal address, email address, telephone number), as may be required by local law, so that users can reach you regarding app issues, general feedback, and feature enhancement requests.
>
> — [App Store Connect Help, Platform version information](https://developer.apple.com/help/app-store-connect/reference/app-information/platform-version-information)

In practice reviewers check that the page loads and that a person could contact you from it. An email address or a working contact form is the minimum; the address and phone are what the help text lists, and in the EU your trader contact details are shown on the product page anyway (more below).

## The three messages Apple sends

**Guideline 1.5 rejection wording, as posted by developers**

| Apple's wording | What it usually means | Seen |
| --- | --- | --- |
| “The Support URL provided in App Store Connect… does not direct to a website with information users can use to ask questions and request support.” | The page loads but has no way to contact you: a landing page, a repo, a blog post | [July 2026](https://developer.apple.com/forums/thread/840182), [Sept 2026](https://github.com/tsainez/inkstand/issues/77) |
| “The Support or Privacy URL provided in App Store Connect, in one or more localization, is currently not functional and/or displays an error.” | A 404 or error in at least one language's metadata | [Aug 2026](https://github.com/salihgencer/playlist-url-extractor/issues/1) |
| “The support URL specified in your app's metadata… does not properly navigate to the intended destination.” | Older wording for a broken URL or the wrong page | [Sept 2022](https://developer.apple.com/forums/thread/715198), [Feb 2024](https://developer.apple.com/forums/thread/746345) |

_The current message ends with “Update the specified Support URL to direct users to a functional webpage with support information.”_

## Support pages that get rejected

- **A legal page.** In the February 2024 case, the Support URL pointed at a page ending “I have read, understood and agreed to the terms and conditions” — a confidentiality agreement, not support. A privacy policy has the same problem; it has its own field.
- **Your product or landing page.** A developer's app homepage was rejected with the “does not direct to a website with information users can use” message. Marketing pages belong in the optional Marketing URL.
- **A GitHub link.** The same developer's [rejection log](https://github.com/jaywcjlove/app-rejection-fixes) shows a GitHub Issues link accepted once and rejected later — “official app support contact was not found in the support URL” — before a dedicated feedback page passed. Reviewers aren't consistent, so don't rely on the lenient one.
- **A file that moved.** The August 2026 rejection came from a GitHub file link to a `main` branch that didn't exist; the repository used `master`. Links to files in repos break quietly.
- **A blog post with a comment box.** Rejected in July 2026, then overturned on appeal — a fight you can skip with a proper support page.

> **What a support page that passes contains.** Your app's name, who you are (name or company), an email address or contact form that works, and ideally a short FAQ. One page per app, at a URL you control — `yourdomain.com/appname/support` — not a third-party file or repo.

## Check your URLs the way a reviewer does

Most 1.5 rejections are a URL that worked when you typed it and broke later, or works in English and 404s in another localization. One developer's fix after an August 2026 rejection was a pre-submission gate that fails the release unless every App Store Connect URL returns HTTP 200. A minimal version:

**check-store-urls.sh — every metadata URL must return 200**

```bash
#!/bin/sh
# List every Support, Marketing and Privacy Policy URL, in every localization.
URLS="
https://example.com/myapp/support
https://example.com/myapp/privacy
https://example.com/de/myapp/support
"

fail=0
for url in $URLS; do
  code=$(curl -s -o /dev/null -L -w "%{http_code}" "$url")
  echo "$code  $url"
  [ "$code" = "200" ] || fail=1
done
exit $fail
```

A 200 only proves the page loads. Open the support page on a phone, logged out, and check you can reach a human from it in one tap or one email.

> **The Review Check ($49).** We check your Support, Privacy and Marketing URLs in every localization — plus the build — against the guidelines that reject indie apps. $49, two business days. https://asoitis.com/checkout/start?plan=review

## Fixing it: new build or not?

The Support URL is version-level metadata. Apple's [table of editable properties](https://developer.apple.com/help/app-store-connect/reference/app-information/required-localizable-and-editable-properties), which lists what “can be localized and edited at any time without submitting a new version”, marks the Support URL, Marketing URL and Privacy Policy URL as required or localized — but not editable. That splits the fix in two:

**Rejected version (not live yet)**
- The version is editable after a rejection
- Change the Support URL in each localization
- Resubmit with the same build — the app itself didn't change

**Live app whose page broke**
- You can't swap the URL on the live version in App Store Connect
- Fix the page at the existing URL — restore it, or redirect it to the new support page
- Change the URL properly with your next app version

**Reply in App Store Connect — Guideline 1.5**

```text
Hello App Review team,

Thank you for the feedback on Guideline 1.5.

We've updated the Support URL in all localizations to
[https://example.com/myapp/support]. The page includes our name,
a support email address ([support@example.com]) and a contact form.

The build is unchanged.

Thank you,
[Name]
```

## Related: EU trader contact details

Separately from 1.5, the EU's Digital Services Act made Apple verify and display contact details for developers who are traders. Apple's [help page](https://developer.apple.com/help/app-store-connect/manage-compliance-information/manage-european-union-digital-services-act-trader-requirements) says this “includes an address, phone number, and email address”, published on your product page in the EU, and that “even if you don't distribute apps in the EU, you'll still need to declare a trader status.” On February 18, 2025, Apple [removed apps without trader status](https://developer.apple.com/news/?id=6agg0lja) from the EU App Store until it was provided. It's set under Business › Agreements › Compliance in App Store Connect.

## Frequently asked questions

### What does Guideline 1.5 Developer Information mean?

It requires your app and its Support URL to include an easy way for people to contact you with questions and support issues. Apple rejects apps whose Support URL is broken, leads to the wrong page, or offers no contact method.

### What should my App Store support URL contain?

A page about your app with a working way to reach you: at least an email address or contact form. App Store Connect help says it must lead to actual contact information — legal address, email address, telephone number — as may be required by local law.

### Can I use a GitHub page or a social media profile as my support URL?

It's risky. Developers have had GitHub Issues links both accepted and rejected, and product or repo pages rejected for not showing a support contact. A dedicated support page on your own domain with an email address is the reliable choice.

### Do I need a new build to fix a Guideline 1.5 rejection?

Usually not. A rejected version is editable, so you can change the Support URL in every localization and resubmit the same build. On a live app the Support URL isn't editable without a new version, so fix the page at the current URL instead.

### Why was my app rejected under 1.5 when the support page works?

Check every localization: Apple's newer message says the URL failed “in one or more localization”. Also check the page actually offers a way to contact you; a page that loads but only describes the app gets the same rejection.

## Sources

1. [App Store Review Guidelines — 1.5 Developer Information](https://developer.apple.com/app-store/review/guidelines/#developer-information) — Apple Developer
2. [Platform version information (Support URL)](https://developer.apple.com/help/app-store-connect/reference/app-information/platform-version-information) — App Store Connect Help
3. [Required, localizable, and editable properties](https://developer.apple.com/help/app-store-connect/reference/app-information/required-localizable-and-editable-properties) — App Store Connect Help
4. [Manage EU Digital Services Act trader requirements](https://developer.apple.com/help/app-store-connect/manage-compliance-information/manage-european-union-digital-services-act-trader-requirements) — App Store Connect Help
5. [Forum: support URL pointing to a confidentiality agreement](https://developer.apple.com/forums/thread/746345) — Apple Developer Forums
6. [Forum: blog post as support URL, rejected then overturned](https://developer.apple.com/forums/thread/840182) — Apple Developer Forums
7. [Rejection: URL not functional in one localization](https://github.com/salihgencer/playlist-url-extractor/issues/1) — GitHub

## Related

- [Guideline 2.1: App Completeness](https://asoitis.com/app-review/guideline-2-1-app-completeness) — Asks for “fully functional URLs” and no empty websites — the same check from another angle.
- [Guideline 5.1.1: Data Collection](https://asoitis.com/app-review/guideline-5-1-1-data-collection) — Where the privacy policy link requirement lives.
- [Guideline 2.3: Accurate Metadata](https://asoitis.com/app-review/guideline-2-3-accurate-metadata) — The other metadata rejection you can usually fix without a new build.
- [The Review Check — $49](https://asoitis.com/fixes) — Every URL and the build checked before you submit.
- [All app review fixes](https://asoitis.com/app-review)


## Have it done for you

**The Review Check — $49 one-time.** Send us your App Store Connect metadata and TestFlight build. We check every URL in every localization, and the build, against the guidelines that reject indie apps.

- Buy: https://asoitis.com/checkout/start?plan=review
- 15-minute founder call: https://cal.com/ahmedgagan/asoitis-chat

## About ASOitis

ASOitis is a founder-run App Store Optimization (ASO) and Generative Engine Optimization (GEO) agency for indie iOS apps. iOS only; organic ASO + GEO + funnel work, implemented for you. Reference library: https://asoitis.com/app-review, https://asoitis.com/reviews, https://asoitis.com/compare, https://asoitis.com/glossary, https://asoitis.com/aso