Two Separate Tests: Audience Targeting and Page Content
A personal loan page can fail for two different reasons. First, audience targeting: Google's privacy-related publisher policy says that in the United States and Canada, personalized advertising may not target credit-related products or services, banking products and services—including credit cards and loans, bank and checking accounts, and debt management products—by gender, age, parental status, marital status, or ZIP code. This is a targeting-setup problem, not a sentence problem. Second, page content: AFS compliance penalty guidance names “promising loans” among egregious violations, where one egregious violation equals one strike. This is a content-review problem. One limits ad recipients; the other counts against the publisher. Policies and enforcement change, so verify against the current Google publisher policy help center.
Loan-Page Claims That Map to Documented Violations
| Loan-page claim pattern | Policy category | Counting consequence |
|---|
| Explicit approval or funding promise (“promising loans”) | Egregious: concrete, impossible-to-fulfill promise | 1 egregious = 1 strike |
| Specific promise outside publisher control (“no credit check”) | Egregious: specific promise outside your control | 1 egregious = 1 strike |
| Vague benefit statement with no tangible offer or real list | Normal: unclear promise; referenced information absent | 5 violations = 1 strike |
| Personalized targeting of credit products by gender, age, parental status, marital status, or ZIP code (US/Canada) | Privacy: prohibited targeting basis for credit categories | Not covered by strike ratios; fix targeting, not copy |
The highest-risk draft wording is an approval promise—headline or button language that presents a lending outcome as certain. The penalty guidance places concrete, impossible-to-fulfill promises, including “promising loans,” in the egregious column. A “no credit check” claim marks a second egregious category: a specific promise outside the publisher's control, not a harmless marketing flourish. Vague affordability lines that reference an offer or list users never see are treated as normal examples. That distinction is a severity classifier, not a safe harbor. The excerpt gives categories, not a banned-phrase list; the penalty table is internal guidance without a public URL. Do not invent policy language.
Counting Violations and the Pre-Publish Check
Only two counting ratios are documented here: five normal violations equal one strike, and one egregious violation equals one strike. That changes review order. Several vague claims do not automatically equal one explicit approval promise. Catch egregious wording first—headline, hero copy, offer-table headers, call-to-action buttons—then remove filler that implies a benefit without supporting information. Log the changes and the evidence used. Other escalation thresholds, review timelines, and appeal mechanics were not in the retrieved material; do not infer them.
Credit-Audience Targeting on US Loan Pages
For US and Canada audiences, the privacy-related policy names credit-related and banking products and services as categories that cannot be personalized by gender, age, parental status, marital status, or ZIP code. Its examples include credit cards and loans, bank and checking accounts, and debt management products. Separately, personalized advertising may not use inferred or actual sensitive information, explicitly including negative financial-status signals such as a low credit rating or high debt burden. Inferred distress signals remain sensitive even if credit data was not deliberately collected. Safer framing is contextual or first-party-intent placement around loan content rather than demographic or ZIP-based personalization of a credit offer. The excerpts do not detail the full consent or configuration workflow, so confirm setup in the live policy center.
Placement Rules on Affiliate Loan Pages
Affiliate loan pages often stack an offer table, navigation, ad units, and a related-search box. Google publisher policy prohibits ad placement that overlaps or sits adjacent to navigation or action items in a way that could cause accidental interaction. It also prohibits ad or paid promotional content from occupying more screen space than the publisher's own content. For AFS product-integrated features and related-search units, the policy bars placement that encourages accidental clicks, misleading wording such as “click here” or “search now for the best offer,” and designs that make the unit the obvious focal point. Penalty examples include arrows directing clicks, no relevant content above the unit, and a page with no other visible content. Review mobile width, where an offer table and search unit crowd the same decision point. Keep editorial explanation visible and avoid navigation-adjacent units.
Identity and Site-Information Hygiene
Google's publisher policy requires accurate, complete, and non-misleading information for using its ad systems. Retrieved examples include site information such as ads.txt or app-ads.txt and data in ad requests; seriously incomplete, ambiguous, or inaccurate information is listed as a violation. On a loan content site, identity hygiene means not presenting the page as a lender, an approval authority, or the source of a guaranteed decision. That is a publisher-identity issue within the accurate-information category. It is not a substitute for lending-law disclosure review. The retrieved material does not establish CFPB, Truth in Lending Act, or state licensing obligations.
Limits of the Evidence and the Final Check
The retrieved material covers Google publisher policy and penalty guidance, not loan pricing, lender behavior, or US lending law. No rate, APR, lender, funding-time, or approval-outcome data was retrieved, so none is presented. Enforcement thresholds beyond the two counting ratios, restriction-adjudication steps, and appeal mechanics were not in the retrieved material. A restriction label has a documented commercial effect: fewer bidding ad sources, and Google Ads will not serve on content carrying the label. That is a reason to review before publishing, not a guarantee that a checklist prevents a restriction. Verify the current policy center, and route lending-law, disclosure, and licensing questions to a qualified professional.
Before publishing, scan the headline and offer table for approval promises; flag specific claims outside your control; cut vague lines that reference absent information; keep credit offers out of prohibited personalization bases; check ad and related-search adjacency at mobile width; confirm site and ads.txt accuracy. If a claim cannot be supported by real, visible content, cut it or rewrite it as a described category rather than a promise.
研究の知恵