Classify the page before you change a setting
Google's policy for the US and Canada names credit-related products and services among the categories that may not be personalized on certain audience attributes, and supplies its own examples: credit cards and loans, bank and checking accounts, and debt-management products. That example list settles most classification questions. A card review, an annual-fee roundup, a balance-transfer comparison, and a debt-payoff guide all fall inside it, as does a checking-account comparison page on the same site. Moving from acquisition content to repayment content is not an exit from the category.
The five barred attributes, and the sixth people forget
In the US and Canada, ads for these categories may not be personalized on an audience's gender, age, parental status, marital status, or ZIP code. Read that as an audit script: any segment in your ad stack named after one of those five, feeding a credit-category line item, is the configuration to retire.
ZIP code is the one that survives audits because it looks like ordinary geography. At postal-code granularity it works as a proxy for income, housing tenure, and credit profile, which is why the clause lists it beside demographic attributes rather than under location targeting.
The sixth is easy to miss because it sits in a different clause. Personalized ads may not be selected using inferred or actual sensitive information, and that list explicitly includes negative financial-status signals, such as indications of a low credit rating or a high debt burden. The segment a card marketer most wants — applicants with thin or damaged credit — is the segment this rule removes. A lookalike audience modelled on credit-stressed behaviour is the same input under a different name.
Restricted ad volume is not the same as a strike
Pages subject to Google Publisher Restrictions may still carry AdSense code, but such content is expected to receive less ad volume than unrestricted content. That is a revenue effect, not an enforcement action. Strike-level behaviours sit elsewhere: promises outside the publisher's control, misleading labels above ad units, ads that mimic menus or download links, and paid content occupying more screen space than publisher content. Cleaning up audience lists addresses the first problem; only copy and layout discipline addresses the second.
Barred signals versus a page-content basis
The table condenses the retrieved text. Verify each row in your own ad stack; the cells are not legal conclusions.
| Signal or basis | Status | What the retrieved material says | Practical implication |
|---|
| Gender | Barred for US/Canada credit ads | Listed attribute; the category includes credit cards and loans | Remove gender from credit-category audience definitions |
| Age | Barred | Same listed-attribute clause | Retire age-band targeting on card comparison pages first |
| Parental status | Barred | Same clause | Life-stage builds that imply creditworthiness are covered |
| Marital status | Barred | Same clause | Newly-married or joint-applicant segments aimed at card offers fall inside |
| ZIP code | Barred | Postal code sits alongside demographic attributes | ZIP-level geo-targeting of a card offer is often overlooked |
| Negative financial status | Barred as sensitive input | Low credit rating or high debt burden are prohibited inputs | Hardship-built credit-repair lists cannot be reused for card ads |
| Cookie lists or third-party data | Conditional | Requires data rights, an in-ad interest-based notice, and self-regulatory alignment | Confirm rights and the Ad Options-style notice before launch |
| Page-content-only basis | Not addressed as barred | Bars the listed attributes and sensitive data; no blanket permission is granted | Practical fallback, but verify current policy text |
What a compliant setup looks like
Start from the page. A balance-transfer comparison can carry card ads because the page is about cards: the basis is the article's subject matter, not a guess about the reader. Where cookie lists or third-party audience data stay in use, three conditions apply together: you must hold all necessary rights to that data, the advertiser must include an in-ad notice that the ad is interest-based (an Ad Options-style icon), and all parties must follow recognised self-regulatory codes such as the Digital Advertising Alliance's Online Behavioural Advertising Principles or the IAB Europe framework. Record each list's basis, source, and review date. Off-platform audience tools and advertiser-side financial-services rules are outside this article.
The copy and placement traps that produce strikes
Promise language is the first check. The punishment guidance lists a specific promise outside the publisher's control — a "no credit check" account-opening claim — among egregious examples, where one violation equals one strike. Describe published card terms; never promise an issuer's approval.
Labels come next: "Ads" or "Sponsored links" is acceptable above a Google ad unit; "Site favorites" or "Today's deals" is not.
Then layout. Ads must not be mistaken for menus, navigation elements, or download links, and ads or paid promotional content must not occupy more screen space than your own content. Check all three on a rendered mobile view.
Pre-launch checklist and what this article does not cover
Before relaunch, confirm that the page is classified as credit-related; every audience list has been checked against the five attributes; hardship and credit-stressed segments are excluded; data rights and the interest-based notice are in place; labels above ad units read accurately on the rendered page; the ad-to-content ratio holds on mobile; and traffic-source copy matches what the landing page actually offers.
Scope limits matter here. This is publisher-side Google policy, not Google Ads advertiser requirements, which the retrieved material did not cover. The source was a Chinese-language compliance summary, so wording above is an English rendering and the live English policy page governs. The retrieved summary places the credit clause inside a section headed publisher policies, so confirm clause placement on the live page before citing it internally. No US statute or regulator guidance was retrieved, so nothing here is legal advice; consult qualified counsel for legal questions. The credit clause is specific to the US and Canada, and Google may revise it at any time.