Card Pages Are Allowed; the Promises Around Them Are Not
Card content is not banned inventory. Pages under Google's publisher restrictions can still carry AdSense code, but they are likely to get less ad volume than unrestricted content; ordinary card comparisons compete on normal terms.
The rules name cards explicitly in the personalization section, alongside loans, bank and checking accounts, and debt management products. In the US and Canada, personalized ads for those credit-related products may not be aimed at users by gender, age, parental status, marital status or postal code. Inferred or actual sensitive financial data — a low credit rating, a high debt burden — is likewise off-limits for selecting ads or building audience lists.
If you serve personalized ads, three duties follow: hold every right needed to use audience data such as cookie lists; carry an in-ad statement that the ad is interest-based, like the Ad Options icon; and follow applicable self-regulatory codes such as the Digital Advertising Alliance principles or the IAB Europe framework.
Vague Claims Versus Promises You Cannot Keep
The compliance tables split violations into ordinary and egregious, and card marketing produces both.
An ordinary violation is a promise left unclear or unverifiable; five ordinary violations equal one strike.
An egregious violation is a concrete promise that cannot be fulfilled: free or cash offers, promising loans, unreasonably cheap offers, misrepresenting your identity, or specific promises outside your control. The policy's own illustration is "Open a PNC high-yield savings account with no credit check!" One egregious violation equals one strike.
Map that onto cards. "Approval is likely for most applicants" is soft and unverifiable — ordinary tier. "Guaranteed approval," "no credit check," "everyone qualifies," or a promised welcome bonus you cannot control are issuer-dependent outcomes: the egregious shape. Underwriting belongs to the issuer, not to the site publishing the link.
The guidance also defines egregiousness by significant scale of impact, a notable failure to follow best practices, particular deceptiveness toward users or Google, or direct advertiser harm. Scale, not just wording, is a factor: one misleading line on a high-traffic comparison table reaches further than the same line on a dormant blog. Google may stop serving ads to a site and disable an AdSense account for violations.
Application Data, Impersonation, and the Phishing Line
Card pages often sit beside forms asking for income, employment and identity details, which pulls in the deceptive-behavior rules. The policy bars baiting users with false or ambiguous content, trying to obtain personal information or tricking users into disclosing it — phishing is the named example — and promoting products through deceptive information, including get-rich-quick schemes.
Misrepresentation is the companion risk. Publishers may not misstate or conceal who they are, who created the content, or what it is for, and may not falsely imply endorsement by another organization; the policy's example is impersonating Google products or misusing logos. A page built to look like an issuer's application carries that exposure, plus trademark concerns.
Privacy Duties Card Traffic Makes Hard to Avoid
Monetized pages must keep a privacy policy that clearly discloses any data collection, sharing and use arising from Google products, including cookies, beacons, IP addresses or other identifiers, and must note that third parties may place and read cookies or use beacons because of ads there. If you collect or infer precise location from GPS, Wi-Fi or cell data, disclose possible uses including personalization, analytics and attribution and partner sharing; obtain explicit opt-in first; send it to Google encrypted; and describe the practice.
Two more boundaries apply. Sites under COPPA must tell Google through Search Console, an AdMob SDK flag or child-directed marking, and must not run interest-based advertising or remarketing against users known to be under 13. EU consent rules apply too, so European-facing card content needs consent handling even when the business is US-based.
Affiliate Hops and Landing Page Consistency
Traffic-source rules govern the affiliate path most card offers travel. The source must be relevant and accurately describe the destination, may not promise offers that are missing or hard to find on the landing page, and the landing page must look broadly the same to paid and organic arrivals. You answer for every source, including affiliates: an outdated bonus claim in a partner's creative is your problem.
Placement rules apply too: no ad code in pop-ups, emails or software, ads must not overlap navigation in ways that invite accidental clicks, must not imitate menus or download links, and search ad units belong only on clearly labeled search results pages.
A Pre-Publish Pass You Can Finish in an Afternoon
- Rewrite approval language. Drop "guaranteed," "no credit check" and "everyone approved"; the issuer decides.
- Re-check every affiliate destination. Match your offer text to the issuer page today; if you cannot verify it, delete the claim.
- Verify placement. No ad beside navigation, none covering copy, none where a menu belongs.
- Confirm disclosures. The privacy policy names cookies, beacons and identifiers; consent exists for EU readers and location data.
- Separate editorial from advertising visually, and label ad units so no reader mistakes them for your comparison.
What These Rules Do Not Decide
These policies constrain monetization; they say nothing about APRs, fees, credit-scoring models, or whether a specific card suits a particular reader. Those questions need the issuer's terms and, where consequences are binding, qualified professional advice. The examples cited are illustrative rather than exhaustive, enforcement is assessed case by case, and policy text changes, so verify the current version. Regional scope varies too: publishers in certain sanctioned jurisdictions cannot use Google publisher products. For a US card publisher the takeaway stays narrow: keep the content, drop guaranteed outcomes, and verify tomorrow every claim a reader can see today.