Policy URLs must not redirect
The requirementstatement
A URL submitted for a policy page must resolve directly rather than returning a 30x redirect.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- privacy policy URL + terms URL
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- AI · crawlCRAWL
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
- What the fix involvesfailureClass
- Fix the fieldRETRY_FIELD
- A better value in the form fixes it. Ekas can rewrite it and re-check.
- Who requires itauthorities
- TCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Submit the final canonical URL — the one you land on after every redirect — including https and any trailing path normalisation.
A compliant exampleexample
Submit https://acmecoffee.com/privacy-policy rather than http://acmecoffee.com/privacy
Rules you will hit next
One other rule reads privacy policy URL + terms URL. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
POL-021 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.