What reviewers actually look at
When a campaign is submitted, a reviewer at the messaging platform and then at a carrier aggregator opens the brand's website. They check that it is real, that it describes the business named in the registration, and that the sign-up flow described in the campaign exists and says what the campaign claims. They follow the privacy policy and terms links from the form and read specific sentences. They compare the legal name and address with the registration. The whole visit takes a few minutes, and the 15 checks here are what happens in those minutes.
The groups are ordered the way a reviewer moves through the site: the home page first, then the form, then the two linked documents, then a comparison with the registration. Answer them in that order with the site open and you will see your site as the reviewer does.
The checks that cause rejections on their own
- A site that cannot be reviewed. Password walls, "coming soon" pages, parked domains and plain http:// are rejected without further reading.
- An opt-in flow the reviewer cannot see. Gated, in-app and paper flows need a hosted screenshot or document. This is the most common rejection reason by a wide margin.
- Pre-checked or bundled consent. The SMS checkbox must be separate and unchecked.
- An incomplete disclosure. Business name, message types, frequency, rates, STOP and HELP next to the box.
- A missing or non-compliant privacy policy. Public, on the same domain, with the no-sharing statement.
- No published terms. Program terms with frequency, rates, STOP, HELP and carrier liability.
- A brand that does not match the site. Legal name, address and EIN consistent across the registration, the website and official records.
Why "Not sure" counts as zero
A reviewer does not give credit for things they cannot confirm, so neither does the score. Marking a check Not sure keeps it out of the fix list but puts it in a "check and confirm" list so you remember to verify it. The score only reaches "Ready to submit" when every check is a Yes or the score is at least 90 with nothing marked No. In practice, a site with one or two Not sure answers and everything else Yes will pass; the status is deliberately strict so that you confirm before you submit, because every rejection costs a resubmission fee and days of delay.
Using the fix list
The fix list is plain text, sorted by weight, with the fix tip and a link to the ToolsOrbit generator that produces the missing piece: the checkbox builder for the form, the opt-in language generator for the disclosure, the privacy policy generator and the SMS terms generator for the documents, and the call-to-action generator for the message flow and samples. Paste it into a ticket or send it to whoever maintains the site. The Share button puts your answers in the link so a colleague can open the same checklist.
What this checker does not do
It does not fetch your site, so it cannot catch a typo in a URL or a policy that was edited after you answered. It does not cover the content rules for restricted categories (lending, debt collection, cannabis, gambling, adult content), which need specialist review regardless of how good the website is. And it does not replace reading your platform's rejection message if a campaign has already been declined: that message names the error code, and the campaign rejection guide explains each one and the fix.