# WEB-119 — The whole site must be screened for prohibited content, not just the landing page

> Prohibited-content screening must cover the entire website, not only the page the campaign points at.

- **Rule ID:** WEB-119
- **Layer:** Website (`WEBSITE`)
- **Checks:** `brand website (all pages)`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the crawled website or policy page
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** TCR, Twilio, AWS, T-Mobile
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/website/web-119/

## Why this rule exists

Vetting crawls the brand's whole site, so a compliant campaign landing page does not protect a business whose shop sells vape hardware two clicks away. This is a common and expensive surprise: the campaign content is clean and the registration still fails on the brand.

## How to fix it

Audit the whole site against the prohibited-content list before registering. Where the business genuinely sells a restricted category alongside a compliant one, expect the brand to be judged on the restricted category.

## Notes

Requires multi-page crawling. Today the product fetches a single page, so this rule is a known coverage gap rather than an implemented check.