Real Estate SEO: The Practitioner Guide for U.S. Agents, Teams, and Brokerages

Real estate SEO in the U.S. operates under a stack of constraints that do not exist in other verticals. Three overlapping regulatory frameworks (NAR Article 12, state real estate license law, federal Fair Housing) govern what a site can say. A structurally mandated duplicate-content environment (the MLS-IDX feed) governs what a site can show. A handful of directory aggregators (Zillow, Realtor.com, Redfin, plus the CoStar / LoopNet stack for commercial) govern most of the canonical authority. Generic SEO guidance ports to real estate poorly because it ignores all three constraints.

This guide covers the surface end to end: the regulatory layer, the data layer, the local-search layer, the schema layer, the post-Sitzer/Burnett intent layer, and the implementation work that holds the surface together. The reader is a real estate operator (brokerage owner, team lead, marketing director, ambitious independent agent) who needs the working machinery rather than the marketing pitch.

The Regulatory Layer

Three frameworks set the boundary conditions on what real estate SEO can look like.

NAR Article 12

The National Association of Realtors Code of Ethics Article 12 mandates truth in advertising. Its operational reach into SEO is a set of Standards of Practice that read directly onto site surfaces.

SOP 12-9 requires the firm (brokerage) name to be disclosed in all advertising, including websites and social media, alongside the state of licensure. This governs title tag formulation, H1 structure, footer boilerplate, and meta-description content for individual agent and team websites. An agent cannot optimize a site purely around their own name or a localized query (for example, “Miami Real Estate Team”) without prominently integrating the brokerage entity. The brokerage name disclosure carries through every page surface, not only the About page.

SOP 12-10 prohibits the deceptive use of meta tags, on-page terms, or other devices to divert internet traffic, as well as deceptive framing of brokerage websites. This is the explicit anti-cloaking, anti-doorway-page provision. Black-hat SEO patterns that would survive in other verticals trigger NAR ethics complaints in real estate.

SOP 12-12 prohibits registering or using URLs that present “less than a true picture,” limiting deceptive exact-match domains that imply official municipal or MLS affiliation. The standard governs domain strategy decisions: a domain like miami-mls.com operated by an independent agency is exposed to ethics action even if the WHOIS is correctly attributed.

SOP 12-8 requires REALTORS to use reasonable efforts to keep website information current and to promptly correct outdated information. The standard creates a compliance imperative for managing index bloat from expired listings, stale market reports, and superseded contact information.

SOP 12-1 restricts the use of “free” in meta titles and landing page copy. Agents cannot advertise services as free if they receive financial compensation from any source (including a seller-paid cooperating commission). This rules out a common conversion-page pattern in unregulated verticals.

State License Law

State real estate commissions layer additional constraints on top of the NAR baseline. Each state runs its own statutory framework: California DRE, Texas TREC, Florida FREC, New York DOS, and equivalent commissions in every other jurisdiction. The constraints vary in specifics but cluster around mandatory disclosures on every page (broker license number, brokerage name, jurisdiction-specific disclaimers), relative font-size requirements for the team name versus the brokerage name, and the legal definition of what constitutes a team versus a brokerage.

In the entity model, the consequence is that a real estate team is generally a nested entity within the brokerage rather than an independent corporate entity. Google Business Profile eligibility and RealEstateAgency schema deployment follow that nesting. Teams that schema-model themselves as independent organizations risk both ethics action and Knowledge Graph confusion.

Federal Fair Housing

Title VIII of the Civil Rights Act of 1968 (the Fair Housing Act) governs what real estate marketing can say about communities and prospective residents. The original 1968 act prohibited discrimination based on race, color, religion, and national origin. Subsequent amendments added sex in 1974 and disability and familial status in 1988. HUD’s Office of Fair Housing and Equal Opportunity actively monitors online advertising for discriminatory language.

The lexical consequences are sharper than most marketing teams realize. “Perfect for families” violates the 1988 familial status protections. “Safe neighborhood” or “exclusive community” function as proxy steering signals. “Near churches” violates the 1968 religious protections. Standard marketing copy in other verticals reads as discriminatory in real estate.

The safe harbor is codified in NAR SOP 10-2: demographic information can ship if it is derived from a recognized, reliable, independent, and impartial third-party source and the source is disclosed. The SEO pattern that survives a Fair Housing review on a neighborhood page is to embed Census Bureau data, standardized walkability scores, factual school district boundaries (without subjective quality ratings), and transit accessibility metrics with explicit attribution. Synthesized or qualitative demographic claims do not survive. See the Fair Housing words to avoid spoke for the operational vocabulary.

Architectural Fair Housing violations matter as much as lexical violations. Programmatic SEO builds that use demographic variables (median age, religious affiliation, racial composition) as filtering facets, category tags, or URL parameters constitute “digital steering” under HUD guidance and carry the same strict liability as a physical broker refusing to show a home. The marketing stage is the regulatory entry point, and the URL structure is part of the marketing stage.

The Data Layer

The core driver of real estate search traffic is listing inventory, which is governed by the MLS-IDX ecosystem. The full working machinery is covered at the IDX vs MLS article; the relevant facts here:

The U.S. runs roughly 529 local and regional MLSs, actively consolidating into mega-MLSs. NAR’s Internet Data Exchange (IDX) policy framework, established in the late 1990s and forcibly expanded by the 2008 DOJ antitrust settlement, allows brokers to syndicate MLS data to public-facing websites. The 2018 industry migration to the RESO Web API replaced the older RETS protocol with a standardized data dictionary, and that standardization is what makes scalable schema generation possible.

NAR’s 2019 Clear Cooperation Policy requires brokers to submit a listing to the MLS within one business day of marketing it to the public. This centralizes the freshness signal at the MLS submission timestamp.

The structurally mandated duplicate-content environment (every IDX-enabled site carries the same listing data) means individual agent sites cannot win the canonical cluster on listing content against directory authority. Schema completeness is the remaining lever, and the rendering pattern on the IDX feed determines whether schema accrues to the host domain at all.

The rendering pattern is the load-bearing decision. Iframe IDX renders listing content from the vendor’s domain and passes zero topical relevance to the host. Truly embedded IDX (RESO Web API ingestion rendered server-side or statically on the agent’s domain) passes everything. The view-source test resolves the distinction in under thirty seconds: look for an iframe element wrapping the listing detail content. If present, the implementation is iframe-rendered and the SEO ceiling is structural.

For commercial inventory, the data layer is different. CoStar, LoopNet (CoStar-owned), and Crexi dominate commercial listings. The residential MLS-IDX architecture does not extend to commercial, which means the canonical-authority workaround for commercial operators runs through knowsAbout populated for commercial practice areas (tenant rep, investment sales, asset classes) rather than through buyer-education content. See commercial real estate SEO for the commercial-side framing.

The Schema Layer

Schema.org provides specific types for real estate entities: RealEstateAgent, RealEstateAgency, and RealEstateListing. Deploying them correctly requires reflecting the regulatory and structural realities of the industry in the entity model.

RealEstateAgent and RealEstateAgency Nesting

RealEstateAgent is a subtype of LocalBusiness, Organization, Place, and Thing. Because state license laws and NAR SOP 12-9 require clear brokerage affiliation, the schema architecture must reflect the nested relationship to build Knowledge Graph confidence.

The critical slots:

• parentOrganization links the agent or team to the overarching brokerage.
• memberOf signals NAR membership and local board membership.
• department signals distinct teams within a brokerage (a team sits as a department of the brokerage rather than as an independent organization).
• knowsAbout signals practice-area specialization (luxury, first-time buyer, investment, relocation, commercial, specific asset classes).
• areaServed accepts AdministrativeArea, GeoShape, or Place and is the primary geographic-relevance signal for local pack visibility.

See the local SEO schema areaServed spoke for the deeper pattern on areaServed.

RealEstateListing and the Offer Pattern

RealEstateListing represents the listing page; the transactional data nests inside offers as an Offer or Demand. The businessFunction property within the offer specifies lease or sale. The datePosted property communicates the freshness signal that aligns with NAR’s Clear Cooperation Policy. spatialCoverage defines the property boundary. leaseLength carries rental terms. Property-specific facts (bedroom count, bathroom count, floor size, lot size, listed price, status) map directly from the RESO Web API Property Resource fields to the corresponding schema properties.

The minimum competent schema on a listing detail page surfaces RealEstateListing as the page type with offers, datePosted, spatialCoverage, numberOfRooms, floorSize, and the operational properties from RESO. Additional fields that the local MLS extends through custom properties land in the additionalProperty slot to prevent schema validation errors.

Organization and Person Schema for EEAT

Beyond the real-estate-specific types, the broader entity graph governs trust signals. The Organization schema for the brokerage or agency carries founder (linked to a Person node with sameAs connecting to LinkedIn and other verified profiles), contactPoint (email and phone), address (the licensed-broker address), and knowsAbout (the topical breadth of the practice). The Person schema for the agent carries jobTitle (the licensed designation), worksFor (linked to the brokerage Organization), and sameAs connecting to LinkedIn and licensed-real-estate-board profiles.

For Article schema on blog posts and long-form content, author links to the Person node, publisher links to the Organization, and articleSection carries the topic-cluster name. The author-attribution chain is part of the EEAT signal Google evaluates under the Helpful Content System and Reviews System updates.

The Local-Search Layer

Real estate search intent is heavily bifurcated into explicit local searches (“Miami real estate agent”) and implicit local searches (“real estate agent near me”). Google serves these queries primarily through the Local 3-pack (Local Finder), which relies on proximity, NAP (Name, Address, Phone) consistency, and citation quality as foundational ranking signals.

The real estate vertical introduces an entity conflict that other local-search verticals do not face. Historically, queries in a Google Business Profile business name were a major ranking factor. Agents responded with name stuffing (“John Doe - Miami Luxury Realtor”). This conflicts with NAR SOP 12-9, state license law, and Google’s own guidelines against name spam.

Google’s December 2021 Vicinity Update rebalanced the local algorithm: it significantly increased the weight of user proximity while decreasing the ranking power of queries in the business name. The risk-to-reward ratio of violating state advertising laws to stuff a GBP name has inverted. Proximity and category fidelity now carry the ranking weight that name stuffing used to carry.

The brokerage model creates a second filtering conflict. Google allows individual practitioners (agents) to have their own Google Business Profiles at the same physical address as the overarching RealEstateAgency (the brokerage). The local algorithm’s proximity and diversity filters often suppress competing agent profiles at the same address for the same query, forcing agents to compete against their own brokerage and colleagues for local pack visibility. See the GBP same-address filter spoke for the operational workaround.

The right local-search architecture for a brokerage with multiple agents:

• One Google Business Profile per physical location.
• One Practitioner profile per licensed agent (where the agent maintains their own profile) with consistent NAP referencing the brokerage address.
• Practice-area differentiation through categories (Real Estate Agent vs Real Estate Consultant vs Property Management) and through services.
• Service-area expansion through serviceArea rather than through additional false profiles at unrelated addresses.

NAP consistency carries across the entire citation graph: Google Business Profile, social media profiles, real-estate-specific directories (Zillow, Realtor.com, Homes.com), local business directories, and the site’s own contact page. Minor variations (St. vs Street, suite suffix formatting, phone-number spacing) accumulate into trust degradation when they appear at scale.

The Post-Sitzer/Burnett Intent Layer

The 2023 Burnett v. NAR antitrust verdict and the subsequent 2024 NAR settlement are altering the economic and search-intent landscape. The settlement eliminated the rule that required brokers to offer blanket buyer-side commission fees on the MLS and mandated that buyers sign representation agreements before touring homes.

Historically, buyer-side search intent skewed toward property-specific queries (“homes for sale in [city]”), which Zillow and Realtor.com dominate. With the new requirement for upfront buyer-broker agreements, a new search intent surface is emerging around buyer representation, agent negotiation, and fee structures. This opens a top-of-funnel SEO surface for agents and brokerages to capture traffic through educational content about the buying process, shifting some focus away from pure IDX listing competition toward Service and Person entity authority.

The content surface that maps to this shift:

• Buyer-broker agreement explainer pages.
• Fee-structure explainer pages (per-area cost ranges, the buyer’s-agent-fee discussion, alternative-compensation models).
• Negotiation-mechanics explainer pages (how the buyer-broker agreement affects offer terms, fee waivers, seller-concession patterns).
• Buyer-representation case studies (anonymized engagement narratives that demonstrate the value of representation independent of the seller-paid fee).

See the NAR settlement explained spoke for the deeper coverage on this surface.

The On-Page Layer

Once the regulatory, data, schema, and local layers are accounted for, the on-page work follows familiar SEO patterns. The differences are mostly in what the vertical’s vocabulary requires.

Title Tags and Meta Descriptions

Brokerage-name disclosure per SOP 12-9 carries into the title tag pattern. A standard pattern is [Page Topic] | [Agent or Team Name] at [Brokerage Name]. State licensure jurisdictions where the law requires license-number disclosure at the page level surface the license in the meta description or a fixed footer slot.

Meta descriptions stay specific to the page topic, between 140-160 characters, and do not promise outcomes that violate the SOP 12-1 “free” prohibition or imply NAR-specific protected claims (like REALTOR-only-membership claims that do not apply to non-REALTOR licensees).

H1 Structure

The H1 names the page topic in the buyer’s vocabulary. For a service page on listing agent representation, the H1 is “Listing agent” or “Sell your home” rather than the SEO-jargon “Listing agent services in [City].” For a neighborhood page, the H1 is the neighborhood name plus a factual qualifier (“homes for sale in [neighborhood]”) rather than a marketing qualifier that violates Fair Housing safe-harbor.

The H1 is one per page. Subsequent headings cascade through H2 and H3 in order. The cascade is structural for assistive technology and for Google’s content-extraction pipeline; skipping levels is a small but consistent quality signal degradation.

Internal Linking

The internal-link graph routes authority through the site according to commercial priority. The standard pattern is:

• Homepage carries the most inbound link weight from external sources and routes outbound link weight to the Tier 1 commercial pages (the head-term money pages and the primary service surfaces).
• Tier 1 commercial pages route outbound link weight to Tier 2 and Tier 3 commercial pages (sub-vertical service pages, geography-specific landing pages, comparison pages).
• Informational hubs (long-form pillar pages on the regulatory and data-layer surfaces) route outbound link weight to informational spokes (single-topic deep-dives), which route inbound link weight back to the hub and across to relevant commercial pages.

Anchor text is descriptive without over-weighting exact-match query terms. The anchor text on internal links is one of the strongest signals Google uses to understand topical relationships across the site graph.

URL Structure

URL structure mirrors the site graph. Commercial-page slugs match the query intent (/sellers-agent-seo/, /luxury-real-estate-seo/, /local-seo-real-estate-agents/). Informational-spoke slugs name the topic specifically (/blog/idx-iframe-vs-truly-embedded-seo/). The slugs are stable; rewrites or content updates do not change the URL. When a URL must change (rare), a 301 redirect carries the inbound link equity to the new URL.

For listing detail pages, the URL pattern that survives canonical normalization is typically /listings/[MLS-id]-[street-address-slug]/, with the canonical pointing at the agent’s own URL on a truly-embedded IDX. The IDX vendor’s default URL pattern is usually fine if the vendor is on the truly-embedded side; on the iframe side, the URL is moot because the canonical is the vendor’s.

Image Treatment

Image filenames are descriptive (oak-park-craftsman-3br-2ba.jpg rather than IMG_4892.jpg). Alt text describes the image factually for accessibility (“a single-story Craftsman house with a covered front porch”). Compressed image sizes (WebP or AVIF at ~70% quality) keep page weight inside the Core Web Vitals envelope.

For listing detail pages, the photo array maps through the RESO Web API media resource into the page’s image gallery. Each image carries alt text generated from the listing description (room type, view direction) where possible.

Page Speed and Core Web Vitals

Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) are direct ranking factors for the Page Experience signal. The thresholds Google considers “Good” are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.

The dominant LCP problems on real estate sites are large hero images and uncompressed listing photo galleries. The dominant CLS problems are IDX widgets that load asynchronously and reflow the page after the initial paint. The dominant INP problems are client-side rendering frameworks loading large bundles for interactive features (saved-search modals, mortgage calculators, lead-capture forms).

The right pattern is server-side or static rendering for the page chrome and the listing content, with progressive enhancement for the interactive components. Cloudflare, Vercel, and Netlify all handle this cleanly through their edge-deployment patterns.

Mobile-First

Most real estate searches happen on mobile devices. Google’s mobile-first indexing means the mobile rendering of the page is the version Google evaluates. Responsive design, touch-target sizing per the W3C 48x48 dp minimum, and mobile-specific gesture patterns (swipeable photo galleries, expandable schedule-a-tour modals) are baseline.

The IDX vendor’s mobile rendering is the most common failure point. Vendor-default IDX widgets often degrade on mobile (laggy maps, awkward filter modals, broken pagination). Evaluate the mobile experience explicitly as part of vendor selection.

The Content Hierarchy

The site’s content architecture follows the commercial-priority hierarchy.

Tier 1: Head-Term Money Pages

The homepage carries the head term verbatim (“Real Estate SEO” for an agency, “[City] Real Estate” for an agent). Tier 1 secondary pages carry the highest-value service queries (“Sell my home in [city]”, “Buyer agent in [city]”). These pages get the maximum on-page investment, the strongest internal-link inbound weight, and the most aggressive freshness cadence.

Tier 2: Service Pages

Service pages cover the specific capabilities the practice offers (listing agent, buyer agent, relocation specialist, investment-property agent, luxury specialist). Each service page targets a query family rather than a single query. The pages are deep (1500-3000 words), grounded in citable regulatory and data-layer facts, and route internal links to relevant Tier 3 pages and informational hubs.

Tier 3: Sub-Vertical and Geography Pages

Sub-vertical pages cover specific practice areas at depth (waterfront property, historic-district restoration, first-time-buyer programs, 1031 exchange investment). Geography pages cover specific service areas at neighborhood granularity. Both surface specialized vocabulary and regulatory detail that the broader Tier 2 pages cannot accommodate.

Informational Hubs and Spokes

Informational hubs are long-form pillar pages on the regulatory and data-layer surfaces (Fair Housing compliance, NAR Article 12 advertising rules, IDX integration mechanics, RESO Web API schema deployment). Each hub spans 3000-6000 words and routes to a cluster of informational spokes that cover specific sub-topics in depth.

This content-hierarchy pattern earns its keep on the regulatory and data-layer side because the queries cluster naturally (someone reading about Fair Housing safe-harbor patterns is also reading about NAR SOP 10-2 and HUD FHEO guidance). It earns less on the commercial side, where the queries are more spread out and the Tier 1/2/3 commercial structure carries the ranking weight.

Buyer Recognition Before Capability

The structural flow on every commercial page is consistent: name the buyer’s situation, deepen the buyer’s understanding of why their situation exists, then show the capability that resolves it. The H1 sets up the recognition. The body section makes the recognition specific. The services or CTA section offers the resolution.

A page that pivots to credentials or methodology before the buyer’s problem has been fully named loses the buyer. The buyer reads the credentials as defensive, the methodology as off-topic, and bounces. The same page that spends the first three sections on recognition and the last two on capability converts at multiples of the credentials-first page, because the buyer has already concluded by section three that the operator understands their situation.

This is true on Tier 1 commercial pages and on Tier 2 service pages. It is less true on Tier 3 deep-dive pages, where the buyer is already query-specific and is reading for the technical answer rather than for recognition.

The Off-Page Layer

Off-page SEO in real estate is dominated by local link acquisition (local business directories, chamber of commerce sites, community-news mentions, local sponsorships) and by industry-specific link acquisition (real-estate trade publications, NAR-affiliated content, MLS-board content). Generic guest-posting outreach on unrelated industry sites is weaker than the same outreach on real-estate-adjacent surfaces.

The RESPA Section 8 prohibition on giving or receiving anything of value for referral of settlement-service business creates a hard boundary on cross-vertical co-marketing. A real estate agent cannot exchange dofollow backlinks with a mortgage lender or title company in exchange for referral visibility without risking federal violation. Agent-to-agent referral fees are explicitly permissible under RESPA, so backlink exchanges between agents in non-competing markets are workable. The RESPA boundary lives on the lender-and-title surface; the agent-and-agent surface stays open.

For local citations (NAP listings on directories), consistency is more important than count. Aim for 20-30 high-quality, accurate citations on authoritative directories. Data aggregators (Data Axle, Neustar Localeze, Foursquare for Business) propagate citations to a wider directory graph from a single source of truth, which reduces the per-directory submission cost and keeps the NAP consistent.

For local link acquisition, the highest-yield tactics are local press coverage (provide quotes or market data to local journalists), community sponsorships that earn a link from the event or organization’s website, and partnerships with adjacent local businesses (home inspectors, stagers, contractors) where the partnership is genuine and the link is editorial.

Measurement

The metrics that actually map to retainer value:

• Commercial-query rankings. Track position on the head-term and Tier 2 service queries weekly. A move from position 8 to position 3 on a commercial query with meaningful search volume is the single largest revenue lever in the program.
• Local pack visibility. Track impressions and clicks on the Google Business Profile in the Performance tab of GBP. The local pack converts at multiples of organic search results for branded and proximity-driven queries.
• Commercial-query lead flow. Track form submissions and call tracking attributed to commercial-query landing pages. The traffic-to-lead conversion rate on commercial pages is the most reliable signal of whether the on-page recognition pattern is working.
• Listing-detail traffic and rich-result eligibility. Track impressions and clicks on listing detail pages in Search Console. Rich-result eligibility status in the Rich Results report flags schema completeness issues that suppress listing-page CTR.

Aggregate organic traffic and aggregate query count are less useful. The vertical’s content surface is large enough that a site can grow aggregate traffic without growing commercial-query revenue, particularly when the growth concentrates in low-intent informational queries (mortgage calculators, first-time-buyer guides) rather than commercial queries.

Cost and Timeline Expectations

Real estate SEO retainers in the U.S. range from roughly $1,500/month at the small-team / single-agent tier to $8,000+/month at the large-brokerage tier. The cost driver is content production cadence and the technical-implementation surface (whether the IDX is iframe vs truly embedded, whether the schema architecture needs reform, whether the canonical strategy needs rebuilding).

Timeline-to-rank on commercial queries depends on the starting domain authority. Sites with established backlink profiles and existing ranking signal see commercial-query position improvements in 3-6 months. Sites starting from zero (new domain, no backlinks) see meaningful commercial-query position improvements in 9-18 months, with informational-query positions appearing earlier as the content surface fills out.

The retainer pays for itself when the commercial-query position improvements translate to revenue at the deal-level economics of the practice. A brokerage closing 80-100 deals per year at $400K average price and 2.5% gross commission generates $800K-$1M in gross commission per year. A 10-15% organic-traffic-attributed lift on that revenue is $80K-$150K per year. The retainer math works at almost any reasonable tier.

Who Should Run This

The choice between in-house SEO and an external SEO practice depends on the brokerage’s current build. See in-house vs outsourced real estate SEO for the decision framework. The short version: in-house works when the brokerage has both a full-time SEO operator and a technical implementation surface to support them. External works when the brokerage’s strength is real estate operations and the SEO surface is a specialized add-on. Most brokerages are in the second category.

When evaluating an external practice, the criteria are: fluency on the regulatory and data layers (NAR Article 12 specifics, RESO Web API, Fair Housing safe-harbor patterns), schema and entity-model competence, transparent reporting on commercial-query rankings rather than aggregate traffic, and unhedged claims rather than guarantee-of-outcome marketing. See how to evaluate real estate SEO consultants for the longer-form vendor-evaluation pattern.

Frequently Asked Questions

How long does real estate SEO take to produce results?

Commercial-query position improvements take 3-6 months on sites with existing domain authority and 9-18 months on sites starting from zero. The Tier 1 head-term position is the slowest to move because the competitive density is highest. Tier 2 and Tier 3 service-page positions move faster because the competitive surface is thinner.

Is paid search a substitute for SEO?

No. Paid search delivers leads on the head-term and the highest-intent queries at $20-$60 per click in most markets, which is sustainable only at deal volumes that absorb the per-lead cost. Organic search delivers leads at a fraction of the per-lead cost once the position has been earned, and the position compounds over time rather than ending the day the budget runs out. The right model runs both in parallel, with paid covering the lead-flow during the organic ramp and contracting once the organic position holds.

Does the brokerage do SEO or does the agent do SEO?

Both, in different surface areas. The brokerage owns the brand-level surface (Tier 1 head-term pages, brokerage-level service pages, brokerage-level Google Business Profile, brokerage-level schema). The agent owns the practice-level surface (agent bio page, agent-specific blog content, agent Practitioner profile on GBP, agent-specific schema as a RealEstateAgent nested under the brokerage’s RealEstateAgency). Confusing the surfaces (running an agent site that claims to be a brokerage, or running a brokerage site that puts agent names in the H1) is one of the most common SEO failures in the vertical.

What changes after the NAR settlement?

The buyer-broker agreement requirement creates a top-of-funnel surface around buyer-representation queries that did not exist before. The seller-paid buyer-agent commission display has been removed from the MLS, which means agent sites need to surface fee-structure content explicitly rather than implicitly. Existing commercial-page content largely remains valid; new content around buyer representation, fee transparency, and negotiation mechanics is now load-bearing. See the NAR settlement explained spoke for the deeper coverage.

Do I need IDX to rank?

Not for commercial queries. Agent sites without IDX inventory can rank for commercial queries (service descriptions, practice-area pages, geography-specific content, buyer-representation queries) as cleanly as sites with IDX. IDX is the decision to compete on listing-inventory queries and to ship a richer search-UX on the site; it is not a prerequisite for commercial-query ranking. See the IDX vs MLS article for the deeper IDX surface.

What about voice search and AI overviews?

Voice-search queries and AI Overview answers both reward the same content patterns that traditional organic-search queries reward: schema completeness, vocabulary specificity, factual-answer clarity in the first paragraph, and structured Q&A formatting. The Overview surface in particular favors content that names the working machinery explicitly rather than hedging. The vocabulary pattern (NAR SOPs by number, RESO Web API named explicitly, state commissions referenced by acronym) reads as authoritative to the AI summarization layer and earns more inclusion in AI Overviews than generic marketing prose.