Where loans sit in the policy map
Google publisher policy treats credit-related products and services as a category of its own, and its stated examples include credit cards and loans beside bank and checking accounts and debt management products. A loan page is therefore not generic finance content; it inherits rules written for credit.
Two rule families apply. Content restrictions govern what a page may contain to carry ads at all. Behavioral restrictions govern how ads and audiences are handled, including who an ad may be personalized to. Promise problems are mostly content-side; audience problems are behavioral. Label each issue before editing, because the fixes live in different places.
The US and Canada personalization limits
In the US and Canada, personalized ads for the credit and banking category may not be targeted by gender, age, parental status, marital status, or ZIP code. These limits are written for personalization; contextual delivery, where the ad matches the page rather than a person, is the point of comparison.
A sharper rule sits nearby. Negative financial-status information — signals of a low credit rating or a high debt burden — is sensitive data that may not select or target personalized ads, or be collected into cookie-list audiences.
Together they invalidate a common build. An audience assembled from "bad credit" or "debt-stressed" signals is not a targeting shortcut; it is inferred financial distress used as a personalization input. Writing about credit is fine. Building a list of people you believe have damaged credit is the act the policy addresses.
Two tiers of promise enforcement
Google's enforcement guidance separates egregious examples — one violation, one strike — from normal examples, where five violations equal one strike. The tier turns on precision and control, not tone.
Vague, non-explicit slogans fall in the normal tier, as does promising specific information you never supply. "Promising loans," by contrast, appears in the egregious column, alongside specific promises outside your control, illustrated by a "no credit check" account offer. That example is a policy illustration, not a verified product claim about any bank.
Apply the distinction to a draft. "Rates depend on your credit profile and lender criteria" describes a defensible process. "Approved regardless of credit" or "funded by tomorrow" asserts an outcome you do not control — the pattern carrying the heaviest weighting. No structure guarantees safety; the guidance supplies examples and strike weight, not a safe harbor.
| Policy example (as quoted in retrieved Google enforcement guidance) | Violation tier | Stated strike weighting |
|---|
| Vague or non-explicit promise, e.g. "Graduate education should be affordable! Let's go!" | Normal example | 5 violations = 1 strike |
| Specific information promised but not supplied, e.g. "See a list of top doctors near you!" with no list provided | Normal example | 5 violations = 1 strike |
| "Promising loans" | Egregious example | 1 violation = 1 strike |
| Specific promises outside your control, e.g. "Open a PNC high-yield savings account with no credit check!" | Egregious example | 1 violation = 1 strike |
The gap is arithmetic rather than nuance: five vague slogans consume the same enforcement budget as one loan guarantee. Deleting one loud claim usually matters more than rewording ten soft ones.
Misrepresentation, affiliation, and thin pages
Beyond promises, content policy bars misrepresentation — distorting or concealing information about the publisher, the content's purpose, or the content itself — and false signals of affiliation with or endorsement by another person, organization, product, or service. Loan pages typically borrow credibility: a badge implying a lender reviewed the page, a "recommended" line with no relationship behind it. The deceptive-practices clause adds a parallel bar, illustrated by "get rich quick" schemes.
Two resource-value rules compound this for templated verticals: ads or paid promotion may not occupy more screen space than publisher content, and copied content without added commentary, organization, or value is not acceptable. A page that is mostly ad slots around syndicated lender blurbs fails both. Original analysis of what a term means for a borrower is what the rules call value.
Affiliate traffic counts as your traffic
AFS traffic-source policy requires the source to be relevant to and accurately describe the destination page. It forbids promising products, services, or promotions that are missing from, or hard to find on, the landing page, and it makes you accountable for every traffic source, including networks and affiliates.
So a campaign promising "instant approval" that funnels to an informational page breaches the rule even when your own copy is clean. Audit affiliate claims as if you wrote them, because the policy treats them that way.
Disclosure and data handling
Three checks before publication. Your privacy policy must disclose the collection, sharing, and use that occurs through Google products, naming cookies, web beacons, and IP addresses. Personalized ads need an in-ad interest-based notice, such as the AdChoices icon, and adherence to self-regulatory codes like the Digital Advertising Alliance's online behavioral advertising principles. And you may not pass to Google anything it could use as or recognize as personally identifiable information without advance notice and explicit consent.
Fix list and where the guidance stops
Run the sequence in order: promise language, then audience and exclusion settings, then affiliate traffic claims, then disclosures. Rewrite outcome claims as process statements; retire audiences built on inferred credit distress; align landing pages with whatever your traffic promises.
Then mark the limits. The verified material here is Google publisher policy — an ad-monetization rule set, not lending law. Lending compliance, state rules, and disclosure mechanics belong with the CFPB, state regulators, and lender documents, none of which were retrieved here. The demographic limits above are scoped to the US and Canada and should not be extended elsewhere. Policy text is being consolidated and revised, so cite the current version at publication. And no page tested here predicts an enforcement outcome.
研究の知恵