The direct answer for US rental-apartment pages
In the United States and Canada, Google’s privacy-related publisher standards restrict housing and real estate services, including for-rent listings, says Google’s AdSense publisher policy. Google ad code or platform products may not select or target personalized ads for that category using gender, age, parental status, marital status, or postal code. Those five signals are the core answer; the rest is how to avoid rebuilding them and what to fix around them.
Five barred signals in ordinary rental work
A listing page may describe a two-bedroom near campus. That editorial description is different from using a personal attribute to choose which ad a visitor sees. For rental campaigns, the prohibited basis includes postal code, so ZIP-level “apartments near you” targeting is not an approved personalized-ad basis. It also includes parental status and marital status, which rules out audience framing such as “family renters” or “couples” for personalized selection. Gender and age are barred too, so “young professionals” or “female renters” cannot drive it.
The harder problem is inferred data. Personalized ads and audience-data use may not be based on health or medical information, negative financial-status information, race or ethnicity, religious belief, criminal or alleged criminal behavior, political affiliation, union membership, or sexual behavior or orientation. A rental page that sorts visitors by inferred credit distress, or builds a “life-stage” segment that reconstructs age or parental status, is working from the same kind of restricted basis even when no demographic field is named.
Two activity-source bars also matter. Personalized ads may not be based on activity from users known to be under 13, sites or apps directed to children under 13, or adult, gambling, and government-institution sites or apps. This is separate from the five housing signals, and it applies across categories.
Housing versus employment in the same clause
The same clause lists housing and employment, but their exceptions differ.
| Restricted category | Barred personalized-ad signals (US/Canada) | Exception in retrieved text | Rental work implication (analysis) |
|---|
| Housing (for-sale or for-rent listings) and real estate services | Gender, age, parental status, marital status, postal code | None documented | Rental pages and ads cannot be personalized on these five signals |
| Employment services, such as recruitment and job-listing sites | Gender, age, parental status, marital status, postal code | Limited US government job ads where a bona fide occupational qualification (BFOQ) applies | Rental-property hiring ads face the employment bar; the exception does not cover private rental employers |
The shared signal list matters because a rental business posting property-management or leasing roles is not using a housing exception. The retrieved text documents only a BFOQ carve-out for certain predetermined US government advertisers promoting job information; it documents no housing exception. Do not read the employment exception across to rental listing ads.
Disclosures that remain after targeting is fixed
Even a clean audience setup needs ad-level and data-level disclosures. Publishers must hold all rights needed to use audience data such as cookie lists. Personalized or interest-based ads need an in-ad disclosure, such as the Ad Options icon, and participants must follow applicable self-regulatory frameworks such as the Digital Advertising Alliance principles or IAB Europe’s framework. Those duties sit alongside, not instead of, a site privacy policy.
If a rental page collects precise location from GPS, Wi-Fi, or cell-tower data, four steps apply: disclose possible uses through an interstitial or timely notice; obtain explicit opt-in before collection; send data to Google encrypted or through an encrypted channel; and describe collection, processing, and sharing in applicable privacy policies. An implied or silent location flow does not match the retrieved requirement.
Listing claims, ad layout, and search boxes
Misrepresenting the publisher, the content’s purpose, or the listing itself is prohibited, as is falsely implying an affiliation or endorsement. Deceptive or ambiguous content used to induce clicks is barred. Rental copy should therefore avoid unsupported absolutes and fake urgency; applying the retrieved “impossible promise” example to no-credit-check marketing is an analogue, not a documented rental example.
Ad interference rules bar Google ads from overlapping or sitting next to navigation in ways that invite accidental clicks, seriously interfering with content use, or creating “no way out” screens. For a photo grid beside navigation, that means testing whether the ad competes with the next-photo control and whether content is pushed off screen.
If the page runs AdSense for Search, queries must come from genuine user intent: a query the user typed and submitted without editing or filtering, an approved product-integrated feature, or an approved alternative query on a search-enabled site. Search boxes may not be pre-filled, and publishers may not build links containing pre-filled terms. Limits include at most two AFS search ad boxes per page, AFS code only on search results pages, no toolbar or extension integration, and no code modification. More search ads than organic results is a disallowed pattern; the described normal example has some organic results but more ads, while the egregious example has none or irrelevant organic results.
Pre-launch checks, ads.txt, and evidence limits
Before shipping, verify seven items: classify the page as housing or real estate; audit every audience basis, including inferred segments; confirm in-ad interest-based disclosure; document location consent; review listing claims; test ad adjacency and exits; check ads.txt and permitted ad experiences. Google policy also requires the publisher to be listed as an authorized seller in ads.txt, prohibits screens that fail the Coalition for Better Ads standards, and bars publisher products in specified sanctioned territories.
The retrieved policy text is a partial translation stored in an internal compliance base, not a complete live policy, and Google may revise it. This is compliance background, not legal advice, and it does not address US fair-housing law, state rental law, or market conditions. Penalty mechanics retrieved are scoped to AFS product-integrated features and related-search units, not housing targeting. Re-check the live Google policy pages before launch.