Your generalist copywriter wrote a Fair Housing complaint into your neighborhood pages.
Familial-status proxies and steering phrases violate the 1968 Fair Housing Act and its 1988 amendment. · NAR SOP 10-2 codifies the safe harbor: third-party-attributed factual data with explicit source disclosure. · Programmatic SEO that uses demographic facets in URLs constitutes digital steering by HUD's definition.
Fair Housing has a lexical layer and an architectural layer. Both are enforceable.
Generalist copywriters reach for emotional, audience-targeted language by default. Each protected-class proxy is a violation. HUD's FHEO treats the SEO marketing stage as the critical entry point for digital steering. The repair is rewriting the lexical surface on the SOP 10-2 safe-harbor pattern and rebuilding the URL architecture so demographic facets aren't a filter dimension.
The prohibited-phrase pattern is broader than the explicit list. 'Perfect for families' violates the 1988 familial-status amendment. 'Safe neighborhood' and 'exclusive community' route buyers based on protected characteristics. 'Near churches' violates the 1968 religious protections. The rule isn't just the explicit phrases. Any qualitative claim that filters readers by protected class is a violation. The substitution is factual amenities, not emotional positioning.
NAR SOP 10-2 codifies the safe-harbor pattern. Demographic information can be provided if it's derived from a recognized, reliable, independent, impartial source with explicit attribution. U.S. Census figures, standardized walkability scores from a named index, transit accessibility metrics, factual school district boundaries with no subjective quality ratings on the schools (the ratings can be construed as proxy steering signals). Source disclosed in reasonable detail on the page. The neighborhood content is real; the synthesis is third-party.
Programmatic URL architecture is itself a violation surface. HUD's Fair Housing Planning Guide treats the marketing stage as the critical entry point. Using demographic variables (median age, religious affiliation, racial composition) as filtering facets, category tags, or URL parameters for neighborhood directories constitutes digital steering even when no individual page contains prohibited language. The architecture is the violation. The repair is rebuilding the URL and facet structure around geography and factual amenities instead of demographic cuts.
NAR SOP 10-1 layers on top of the federal floor. SOP 10-1 prohibits volunteering information regarding the racial, religious, or ethnic composition of a neighborhood. That's the per-REALTOR-conduct floor. SOP 10-2 is the safe harbor for content that needs to be rich and locally relevant without violating 10-1 or the FHA. Together they define the lexical and architectural surface the SEO program has to ship into.
From neighborhood-content audit to safe-harbor surface in four weeks. Then the architecture protects the next thousand pages.
- WEEK 0
Lexical and architectural audit
Every neighborhood, relocation, school, and city page reviewed against the FHA prohibited-phrase pattern and the digital-steering architectural pattern. URL structure reviewed for demographic facets. School-content reviewed for subjective quality ratings. Output names the violation surface per page and the architectural repair scope.
- WEEK 1
Safe-harbor template
Neighborhood-page template rebuilt on the SOP 10-2 pattern: third-party-attributed factual data with explicit source disclosure in the page body. Census data block. Standardized walkability index with named source. Factual school district boundary statement with no quality rating. The template is the safe harbor; individual pages inherit it.
- WEEK 2-3
Rewrite and re-architect
Existing neighborhood pages rewritten against the safe-harbor template. URL architecture rebuilt around geography and factual amenities, not demographic facets. Programmatic neighborhood pages regenerated through the template, with the source-attribution disclosure built in. Internal linking adjusted so the content surface and the URL surface align.
- ONGOING
Retainer cadence
Monthly cadence on new neighborhood and relocation content through the template. Quarterly review against HUD enforcement actions and state-level Fair Housing amendments (some states extend the protected-class list). Annual architectural audit on the URL and facet surface.
Named-client testimonials surface here as engagements ship.
Operators who closed the Fair Housing complaint and shipped clean.
What operators ask when the Fair Housing letter arrives.
-
Which neighborhood-content phrases are prohibited under the Fair Housing Act?
Familial-status proxies like 'perfect for families' violate the 1988 amendment. Steering-language proxies like 'safe neighborhood' or 'exclusive community' route buyers based on protected characteristics. Religious-proximity claims like 'near churches' violate the 1968 protections. The rule is broader than the explicit phrase list: any qualitative claim that filters readers by protected class is a violation. HUD's FHEO actively monitors online advertising for this language. -
Is there a safe harbor for talking about a neighborhood at all?
NAR SOP 10-2 codifies it. Demographic information can be provided if it's derived from a recognized, reliable, independent, impartial source with explicit attribution. In practice: U.S. Census figures, standardized walkability scores, transit accessibility metrics, factual school district boundaries. No subjective quality ratings on schools (those can be construed as proxy steering signals). Source disclosed in reasonable detail. The neighborhood content is real; the synthesis is third-party. -
Our programmatic neighborhood pages use demographic filters in the URL. Is that a problem?
Yes. HUD's Fair Housing Planning Guide treats the marketing stage as the critical entry point for digital steering. Using demographic variables (median age, religious affiliation, racial composition) as filtering facets, category tags, or URL parameters for neighborhood directories constitutes digital steering even when no individual page contains prohibited language. The architecture itself is the violation. The fix is rebuilding the URL and facet structure around geography and factual amenities instead of demographic cuts. -
We hired a generalist content shop and now we have a Fair Housing complaint. What got us here?
Generalist copywriters reach for emotional, audience-targeted language by default. 'Perfect for young professionals,' 'great for retirees,' 'family-friendly streets.' Each one is a protected-class proxy. The pages rank because the language is engaging, then HUD or a state agency reviews the surface and the complaint lands. The repair is rewriting every neighborhood page on the SOP 10-2 safe-harbor pattern and rebuilding the URL architecture so demographic facets aren't a filter dimension.
Rebuild your neighborhood and relocation content on the SOP 10-2 safe-harbor pattern before the next complaint. Book a diagnostic.
We read every neighborhood, relocation, school, and city page against the FHA prohibited-phrase pattern, the SOP 10-2 safe-harbor pattern, and the HUD digital-steering architectural test. Diagnostic comes back inside two weeks with the lexical violations, the URL-architecture repair scope, and the safe-harbor template.