# The New-Home Builder's Website Is Invisible to AI Shoppers — Here's the Fix (and the Compliance Traps)

Production builders ship great photos and thin schema. Price and move-in-ready availability are invisible to AI. Here's the structured-data fix, plus the Fair Housing, RESPA, and Reg Z traps.

Author: J.A. Watte
Published: May 30, 2026
Source: https://jwatte.com/blog/blog-mega-analyzer-production-homebuilder-readiness/

---

A first-time buyer almost never starts at a builder's homepage anymore. They start in a chat window. "What new construction is under $400k near me, move-in ready?" The assistant answers from whatever it can *read* — structured data, FAQ markup, a clean entity graph — not from the hero video or the drone shot of the cul-de-sac.

I added a **production-homebuilder readiness** check to the [Mega Analyzer](/tools/mega-analyzer/) after auditing a stack of national and regional new-home builders the same deterministic way an AI engine would: pull the page, parse the schema, ignore the marketing. The pattern was consistent and a little surprising. Production builders are usually *better* at the basics than people assume — a clean `Organization` graph on every page, real `HomeAndConstructionBusiness` nodes on communities, HSTS, and (refreshingly) excellent image alt text on the big photo galleries. What they miss is narrow, specific, and expensive: **the two facts a buyer actually needs are the two facts the machines can't see.**

## The core miss: price and availability are invisible

Walk a typical builder's floor-plan page through a parser and you'll usually find a `FloorPlan` node with dimensions:

```json
{
  "@type": "FloorPlan",
  "floorSize": { "@type": "QuantitativeValue", "value": "1,305", "unitCode": "FTK" },
  "numberOfBedrooms": 3,
  "numberOfBathroomsTotal": 2
}
```

That's it. No price. No availability. The `FloorPlan` isn't wrapped in anything an engine can *sell*. So when an AI shopping surface or an AI Overview tries to answer "what's available move-in ready under $400k," your homes are dimensionally described and commercially mute. Two defects compound it: the `floorSize` value carries a thousands comma (`"1,305"` instead of `1305`, which schema.org's `QuantitativeValue.value` treats as a number), and the community-level `priceRange` is often a bare numeric range with no currency symbol — `"3189-3639"` — which an engine can't distinguish from a square-foot range.

The fix is to make the home a *thing that can be priced*:

```json
{
  "@type": "SingleFamilyResidence",
  "name": "The Chestnut",
  "numberOfBedrooms": 3,
  "numberOfBathroomsTotal": 2,
  "floorSize": { "@type": "QuantitativeValue", "value": 1305, "unitCode": "FTK" },
  "offers": {
    "@type": "Offer",
    "price": "364035",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "priceValidUntil": "2026-12-31",
    "seller": { "@id": "https://example.com/#org" }
  }
}
```

Use `InStock` for a move-in-ready spec home and `LimitedAvailability` / `PreOrder` for to-be-built. This is the single highest-leverage change, and across the builders I benchmarked, **none of them ship it well.** It's an open lane.

## FAQPage at scale — the AEO land grab

Most builders already *have* the Q&A content — "how does the buying process work," "what does move-in ready mean," "how do new-home loans work," "what's covered under the warranty." It sits on the page as plain prose. The good builders even ship a real `FAQPage` on their market-hub pages. The gap is that the template stops there: the process page, the financing page, the warranty page — the exact pages where the high-intent "is this builder legit / how does this work" questions get answered — carry no `FAQPage` markup at all.

Wrapping that existing copy is nearly free and it's what AI Overviews preferentially lift:

```json
{
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What does move-in ready mean?",
    "acceptedAnswer": { "@type": "Answer", "text": "A move-in-ready home is fully built..." }
  }]
}
```

## The other open lanes

- **Per-community `Place` + `areaServed` + `geo`.** Community pages often have an address but no `geo` coordinates and no `areaServed`. A community is a physical location; without lat/long and an enumerated service area, "new homes in [city]" can't place it on the map.
- **`Person` on the people who actually close.** Division leaders and especially the on-site new-home consultants are entity-dark. No builder I checked ships `Person` broadly. It's the most authentic local-trust signal a builder has, and it's sitting unused.
- **Defensible `AggregateRating` / `Review`.** A builder's public review corpus is a major trust asset that AI can't cite as "rated X by N buyers" unless it's structured — and nobody in the set ships it. *But* this is the one place to slow down (see compliance, below).
- **Spanish.** Entry-level and first-time-buyer demand skews heavily Hispanic, and Spanish-language new-home and financing content is an under-served, winnable surface. Most national builders are English-only.

## The part most schema guides skip: this is regulated advertising

Here's where homebuilders are different from a SaaS company or a blog. Almost everything above touches an advertising-compliance regime, and **machine-readable claims carry the same legal liability as the visible copy.** If you bolt on schema without threading the compliance, you can automate a violation across hundreds of programmatic pages.

- **Fair Housing Act (42 U.S.C. 3604(c)).** It is unlawful to make or publish any housing ad that indicates a preference or limitation based on a protected class. This applies to *imagery and alt text*, not just words — "perfect for a young family," "adults-only community," or an alt attribute describing an idealized occupant are all exposure. Describe the home and its features, never the intended occupant. Display the Equal Housing Opportunity logo and statement sitewide; AI answers about whether a builder is legitimate look for it, and so do buyers and lenders.
- **RESPA Section 8 (12 U.S.C. 2607) + Regulation X.** The moment a builder steers buyers to an affiliated or "preferred" lender or title company — increasingly common, often a joint venture — an affiliated-business-arrangement (ABA) disclosure is required: the nature of the relationship, an estimate of charges, and an explicit "you are not required to use this provider as a condition of purchase." If your financing pages promote an in-house lender with no ABA disclosure in sight, that's a flag.
- **TILA / Regulation Z (12 CFR 1026.24).** Once an ad states a specific rate or payment — "as low as 5.99%," "$1,899/mo," "$0 down," "down-payment assistance available" — Reg Z's trigger-term rules attach required disclosures (APR, terms, "subject to credit approval," lender NMLS #). Don't leave a bare rate or payment in an extractable schema field unless the disclosure travels with it.
- **New-home warranty + FTC substantiation.** State the actual warranty coverage (the "1-2-10" workmanship/systems/structural pattern, or the third-party administrator) and keep "move-in ready" claims accurate. And any review count or "satisfaction" claim — visible or in `AggregateRating` — has to be substantiable under the FTC's endorsement and testimonial rules. A production builder's reputation is usually *mixed*; cherry-picking one five-star community to imply a company-wide rating is both a trust risk and an enforcement risk.

That's why the readiness check pairs every schema recommendation with its disclosure obligation, and why the honest advice is the same one I'd give in any regulated vertical: **route the financing, Fair Housing, and warranty surfaces through legal before anything ships.** The win is real — being the builder whose homes are actually shoppable by an AI assistant is a genuine edge while competitors are mute — but you capture it by being precise, not fast.

## Run it on your own site

Point the [Mega Analyzer](/tools/mega-analyzer/) at a builder's community or floor-plan page and the homebuilder-readiness card will surface the missing `Offer`/price/availability, the FAQPage gaps, the per-community `Place`/`areaServed` holes, the Person and review-schema lanes, and the Fair Housing / RESPA / Reg Z / warranty checks — with a copy-ready fix prompt. Then validate every emitted block on the [Schema Validator](/tools/schema-validator/) before it goes live.

If you're a small or regional builder doing this yourself rather than through an agency, the whole playbook — building a machine-readable web presence on a near-zero budget — is the subject of my book *The $97 Launch*. The schema and the discipline are the same whether you sell four homes a month or four thousand.

## Fact-check notes and sources

- Fair Housing Act advertising prohibition: [42 U.S.C. § 3604(c)](https://www.law.cornell.edu/uscode/text/42/3604) and HUD's advertising guidance ([24 CFR Part 109 history / HUD Fair Housing](https://www.hud.gov/program_offices/fair_housing_equal_opp)).
- RESPA Section 8 and affiliated-business arrangements: [12 U.S.C. § 2607](https://www.law.cornell.edu/uscode/text/12/2607) and CFPB Regulation X ([12 CFR Part 1024](https://www.consumerfinance.gov/rules-policy/regulations/1024/)).
- Truth in Lending advertising / trigger terms: Regulation Z [12 CFR § 1026.24](https://www.consumerfinance.gov/rules-policy/regulations/1026/24/).
- FTC endorsement and testimonial substantiation: [Guides Concerning the Use of Endorsements and Testimonials in Advertising, 16 CFR Part 255](https://www.ftc.gov/legal-library/browse/rules/guides-concerning-use-endorsements-testimonials-advertising).
- Schema.org types referenced: [SingleFamilyResidence](https://schema.org/SingleFamilyResidence), [FloorPlan](https://schema.org/FloorPlan), [Offer](https://schema.org/Offer), [HomeAndConstructionBusiness](https://schema.org/HomeAndConstructionBusiness), [FAQPage](https://schema.org/FAQPage), [Place](https://schema.org/Place).
- WCAG 1.1.1 (non-text content / alt text): [W3C Understanding SC 1.1.1](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html).

## Related reading

- [Legal-site readiness: what attorney websites get wrong for AI search](/blog/blog-mega-analyzer-legal-site-readiness/)
- [The image alt-text audit — WCAG 1.1.1 at scale](/blog/blog-tool-image-alt-audit/)
- [Generative engine optimization: getting cited by AI, not just ranked](/blog/blog-generative-engine-optimization/)
- [SGE / AI Overview readiness — the answer-shaped content that wins](/blog/blog-tool-sge-readiness-audit/)
- [Cite and blockquote markup for source-quality signals](/blog/blog-cite-and-blockquote-source-quality/)

---

*This post is informational, not legal or compliance advice. Mentions of statutes, regulations, and third-party standards are nominative fair use. No affiliation is implied. Builders should have counsel review Fair Housing, RESPA, TILA/Reg Z, and warranty language before publication.*


---

Canonical HTML: https://jwatte.com/blog/blog-mega-analyzer-production-homebuilder-readiness/
RSS: https://jwatte.com/feed.xml
JSON Feed: https://jwatte.com/feed.json
Hero image: https://jwatte.com/images/blog-mega-analyzer-production-homebuilder-readiness.webp