Google’s “Preferred Sources” feature just moved from being a Top Stories / AI Mode personalization option to something that can also show up in AI Overviews. That matters because the answer layer is now the first screen for a lot of planning queries — including the ones homeowners ask before they ever call a remodeler, designer, builder, or showroom.

Datum’s take: the best response isn’t “AI schema.” It’s publishing one page per high-intent decision that’s so clear and constraint-heavy that it becomes the page your customers save — and the page AI can safely cite without flattening the caveats.

What Google actually changed

  • Preferred Sources can appear in AI Mode and AI Overviews for users who have selected your domain as a preferred source.
  • Only domain-level and subdomain-level sources are eligible (subdirectories like `/blog` aren’t eligible).
  • Google’s AI features documentation still says there are no special requirements or special markup needed to appear in AI Overviews or AI Mode.

The operator play: build “Default Citation” pages

If your site is a building business (not a publisher), the best “Preferred Sources” strategy is not chasing news. It’s building decision pages that encode real-world constraints: what you do, what you don’t do, what must be true for the advice to apply, and what happens next.

  • Start with the 5–10 questions that generate the most bad-fit leads (pricing range, timeline, service area, permitting, who buys materials, what’s excluded).
  • Answer in one paragraph, then list constraints (minimums, lead times, exclusions) in a tight bullet block that is easy to quote correctly.
  • Add one proof module: a real case slice with numbers and context (before/after, what changed, what didn’t, why).
  • End with a single next action (apply / schedule / request a bid review) and tell the user what happens after they click.

How to actually use Preferred Sources (without being cringe)

If you have a newsletter, a client portal, or even just an “Owners” email list, you can share a simple note: “If you use Google’s AI answers, add our site as a Preferred Source so you see our process + constraints.” Google’s own Preferred Sources doc includes a deeplink format that pre-fills your domain in the Source Preferences tool.

  • Example deeplink format: `https://google.com/preferences/source?q=example.com` (swap in your domain).
  • Put it next to a real asset (your decision page) so the request feels useful, not promotional.

Technical hygiene: keep your truth-set pages easy to interpret

  • Use stable canonicals and clean URLs so the same page gets cited consistently.
  • Keep structured data accurate (Article/BlogPosting + BreadcrumbList) and make sure it matches the visible title/description/date/image.
  • Make key constraints visible in HTML (not hidden behind JS-only UI), because AI features can use multiple retrieval passes to assemble an answer.

Datum’s take

Preferred Sources is a reminder that the game is moving toward trust + repeatable decision support, not one-off SERP hacks. In the building industry, your advantage is operational truth: constraints, sequencing, and proof that generic AI summaries can’t safely invent. Build pages that preserve those details — then give customers a simple way to save you as their default source.

Sources Read