Meta ad rejected because of the landing page: what the page has to get right
Published on 23 August 2026 · 8 min read
The pattern is familiar: a Facebook or Instagram campaign gets blocked, the stated reason stays vague, and the advertiser spends two days reworking the image before realizing none of it was the issue. Meta's ad review doesn't stop at the content of the ad itself: it includes the destination the click leads to, and sometimes the pages reachable from it. A page that throws an error, promises something different from the ad, or collects data without a privacy policy can be enough to get an entire campaign rejected.
Why the destination page is part of the review
From the platform's point of view, an ad is a complete experience: the impression in the feed, the click, then what the person finds on arrival. Meta says so explicitly in its advertising policies — the rules apply to the ad and to its destination. So a reviewer, human or automated, opens the URL and judges the page as it renders, cold, knowing nothing about your product or your intentions. That's a very different stance from a marketing team looking at its own page, and it lines up with the principles in our guide to building a landing page for Meta Ads: a page designed for cold traffic is also a page that's easier to review.
These rules aren't box-ticking. A study by Zeng, Kohno and Roesner published in 2021 at the CHI conference — based on a survey of 60 participants followed by the annotation of 500 real ads by around a thousand people — builds a taxonomy of positive and negative reactions to online advertising and finds that a significant share of web advertising is judged by users as clickbait, untrustworthy, or in poor taste (Zeng, Kohno & Roesner, 2021, CHI '21). The platform's reasoning follows: content perceived as deceptive degrades the experience, and with it the value of the ad inventory — and the destination page is part of what users judge. Since policies change regularly, the official documentation in force is the only up-to-date reference to check before a launch.
The page has to be reachable and functional
This is the first filter, and by far the most common cause of "unexplained" rejections. The page simply has to open, fully, for anyone.
- No load errors. A 404, a server error, an expired HTTPS certificate, a domain still propagating: if the reviewer hits an error, rejection is immediate. Launching a campaign on deployment day is a classic way to trip this.
- No unexpected redirects. A URL that redirects to another domain, to a generic homepage, or to a destination that varies by country muddies the review.
- No content locked behind a login. A page that demands an account, a password, or group membership before showing anything can't be reviewed.
- No automatic downloads. A file that downloads on page load, with no user action, is a strong negative signal: a white paper should download after a deliberate click.
- A load time within reason. A very slow page, whose main content only appears after several seconds, can be treated as non-functional.
The content has to match what the ad promises
The second family of rejections comes from the gap between the ad and its destination. If the creative highlights a free training and the page sells a multi-thousand-euro coaching program, or if the hook states a price the page never shows, review flags an inconsistency — even when every element is perfectly legal on its own. This overlaps with the message match between ad and landing page work already done for conversion reasons, and a rejection of this type is usually the symptom of a broader relevance problem, investigated with the same tools as a Meta ad relevance diagnostic.
Deceptive practices on the page itself
- Fake countdown timers. A clock that resets on every visit is manufactured urgency — a topic covered in our article on urgency and scarcity. A real deadline is no problem at all.
- Fake reviews and invented testimonials. Quotes with no real person behind them, fabricated ratings, client or press logos shown without any actual relationship.
- Blocked exits. A popup with no visible close button, an exit message that reopens in a loop, a disabled back button: these fall under dark patterns and are explicitly targeted.
- Misleading interface elements. A button disguised as a video player, a fake system notification, a field that triggers something other than what it suggests.
- Unverifiable claims. Income promises, health cures, guaranteed results: they often trigger stricter scrutiny of the entire account.
Mobile, legal information, and higher-scrutiny categories
Most Meta traffic is mobile, and review happens under those conditions: a page whose text overflows, whose primary button sits out of thumb reach, or that a popup covers with no way to close it on a small screen can be judged non-functional. On the legal side, the page has to let visitors identify the business behind the offer — that's the point of the legal notices and terms a landing page must carry — and expose an accessible privacy policy as soon as a form collects data, which includes a single email field. Finally, some verticals carry extra requirements or targeting restrictions: health, financial products and credit, employment, housing. Our article on the landing page in a regulated industry covers those trade-offs.
From symptom to fix: diagnosing a rejection
| Symptom | Likely cause on the page | Fix |
|---|---|---|
| Rejected within seconds | URL unreachable: 404, server error, invalid HTTPS | Open the exact URL in a private window, fix it, request a review |
| Rejected while the creative passes elsewhere | Gap between the ad's promise and the page | Rewrite headline, offer and price to echo the ad |
| Rejected on a page that works for you | Content only visible after login, cookie or geolocation | Test from a direct link, no session, on another network |
| Repeated rejections across several creatives | Persistent deceptive element: fake countdown, fake reviews, blocking popup | Remove the element outright, don't just soften it |
| Rejected on a legal offer | No legal notices or privacy policy despite a form | Add the legal pages and link them from the footer |
| Rejection mentions a special category | Health, finance, employment, housing or credit | Reread the category requirements in the official documentation |
- Reread the ad AND the page like a reviewer, cold and without context: what does the first screen promise, and does the page deliver it?
- Open the page on a phone, from a direct link — no bookmark, no active session, no cookies, ideally in a private window.
- Check the exact URL used in the ad, parameters included: that's what gets reviewed, not the clean URL you usually test.
- Fix the cause, not the symptom. Swapping the creative to work around a page-related rejection only postpones the problem.
- Request a new review once the fix is live, after confirming the deployment reached production and not just a preview build.
- Document what you changed — useful leverage if another rejection or an account restriction follows.
Prevention: the pre-launch checklist
- The final URL returns 200 over HTTPS, with no surprise redirect, tested in a private window.
- The first screen repeats the ad's exact promise and offer, including the price if the ad states one.
- No essential content is hidden behind a signup or an account, and no download fires without a click.
- Every popup closes in one gesture, including on a phone screen.
- Countdowns, stock counts and reviews on the page reflect something verifiable.
- Legal notices, contact details and privacy policy are reachable from the page.
- Tracking is in place via the Meta pixel and Conversions API, so you can measure what happens once the campaign is approved.
- If the offer touches health, finance, employment, housing or credit, the category rules have been reread.
A large share of rejections comes less from shady intent than from a page built for an already-convinced visitor and tested only on its author's laptop. Starting from a structure designed for cold traffic removes most rejection triggers before they appear. LanderKit's coach & consultant template ships with that skeleton: proof sections that don't need fake testimonials, legal blocks already wired in, a tested mobile layout, and Next.js code you edit directly. The 10 LanderKit templates are €89 each, or €229 for the full pack. What's left is checking the advertising documentation in force on launch day — the one thing no template can freeze in place for you.
FAQ
Frequently asked questions
Does Meta only review the destination page, or the pages linked from it too?
Review starts with the destination URL, but it can extend to pages reachable from it: the checkout flow, the legal pages, a sales page one click away. A compliant landing page that points to a problematic page is therefore still exposed to a rejection.
Can I edit the landing page without recreating the rejected ad?
Usually yes: you fix the page, then request a new review of the existing ad. Just make sure the change is actually deployed to production and visible from a direct link before requesting the review, otherwise the second rejection will arrive as fast as the first.
Can a cookie consent popup get an ad rejected?
A standard consent banner isn't a problem in itself. What is a problem is a popup that covers the whole screen with no clear way to dismiss it, blocks access to the promised content, or reopens indefinitely — especially on mobile, where space is tight.
Do I need a privacy policy even without a form on the page?
It's required as soon as personal data is collected, which includes a single email field but also the advertising trackers installed on the page. Since most Meta Ads landing pages combine at least a pixel and a form, it's safer to plan for one by default.
Read next
Related articles
- Google Ads destination page disapproved: common causes and how to fix themAn ad can be blocked for what it says, but also for where it sends people. When the disapproval reason points at the destination, the fix isn't in the ad — it's in the page. The hard part is knowing what the review actually looks at.
- Content-Security-Policy on a landing page: allowing GTM, Meta Pixel and Stripe without blocking everythingA landing page loads five to ten third-party scripts on average — GTM, Meta Pixel, a Google Ads conversion tag, a reviews widget, Stripe — and the browser runs every one of them with exactly the same trust it gives the site's own code. A Content-Security-Policy header changes that rule: it explicitly lists what is allowed to execute and blocks everything else by default. How to write one without breaking anything, and why the most common configuration protects against nothing at all.
- Meta Ad Relevance Diagnostics: what Quality, Engagement, and Conversion Rate Ranking say about your landing pageTwo Meta advertisers can run the exact same creative, on the same audience, with the same budget — and pay a very different cost per result because one of them has a below-average "conversion rate ranking." That diagnostic almost never talks about the ad. It talks about what happens after the click, on the landing page.