Skip to content
Tuesday, November 17, 2026

Font directory, previews & typography guides

Latest
Typography

Why Your Listing Pages Look Off-Brand (And How IDX Feeds Cause It)

By UrbanFonts Team8 min read
Listing

You paid for a logo, picked a serif for headlines and a clean sans for body copy, and settled on a navy that looks expensive without trying too hard. The homepage looks great. Then a buyer clicks “Search Homes” and lands on a page set in Arial, with bright blue buttons, cramped price text and a photo carousel that crops every kitchen at the countertop.

That jump is so common most agents stop noticing it. Buyers don’t. The listing page is where they spend the most time on your site, so it’s the worst possible place for your brand to disappear.

The cause is almost always the IDX feed and the way it gets embedded. Once you see how the plumbing works, you can tell which parts of the mismatch are fixable with a stylesheet, which ones are rules you have to live with, and which ones call for a different setup altogether.

What an IDX Feed Actually Puts on Your Site

IDX stands for Internet Data Exchange. It’s the arrangement that lets a brokerage show other brokers’ listings from the local MLS on its own website, so a buyer can search the whole market without leaving your domain. The rules come from the MLS and, for REALTOR-affiliated MLSs, from the National Association of REALTORS’ IDX policy.

The listing data itself is the easy part: address, price, beds, baths, square footage, photos, remarks. What decides how it looks is the layer in between. Most agents and small brokerages don’t pull raw data and design pages around it. They buy an IDX product from a vendor, paste in an embed code or install a plugin, and the vendor’s templates draw the search bar, the results grid and the property detail page.

That template was designed to work for thousands of customers at once. It has to sit next to a luxury brand and a farm-and-ranch office alike, so it defaults to the most neutral choices available. Neutral, in practice, means it looks like nobody’s brand in particular.

Why the Vendor’s Widget Ignores Your Brand Kit

The biggest culprit is the iframe. An iframe is a window cut into your page that loads a completely separate page from the vendor’s server. Your site’s stylesheet stops at the edge of that window. Whatever fonts, colors and spacing you defined don’t reach inside it, because technically it’s a different document.

That explains the most common symptoms:

  • Fonts fall back. Your web fonts are loaded for your pages, not the vendor’s. Inside the frame, text renders in whatever the vendor specified, usually a system stack.
  • Colors clash. Buttons, links and map pins use the vendor’s default accent color unless the dashboard lets you swap it, and often only one or two colors are exposed.
  • Spacing doesn’t line up. Your content column might be 1,140 pixels wide with generous margins. The widget has its own grid, its own padding and its own idea of where a card ends.
  • Mobile breaks twice. Your theme and the widget each have breakpoints, and they rarely agree. On a phone you can end up with a scroll bar inside a scroll bar.

Plugin-based IDX tools that render listings directly in your pages behave better, since your theme’s CSS can reach the markup. Even then you’re styling someone else’s class names, and a vendor update can rename them overnight. When the vendor widget simply can’t be styled to match, some brokerages commission a custom IDX integration from a development firm such as Glorium Technologies so listing pages run on the site’s own templates.

The Parts You Can’t Restyle (and Shouldn’t Try)

Before you start overriding everything, separate brand problems from compliance elements. Some of what looks like clutter on a listing page is there because the MLS requires it.

Under NAR’s IDX policy, an IDX display has to identify the name of your brokerage firm in a readily visible color and typeface. Listing attribution, meaning the name of the firm that holds the listing, has to appear on listings shown through IDX too. Later updates to the policy describe that attribution as needing a typeface no smaller than the median size used for the listing data around it, so shrinking it to six-point gray type in the footer isn’t an option. The policy carves out tiny displays such as thumbnails and messages of 200 characters or less, which is why a results grid can look cleaner than a full detail page.

MLSs also typically require a data disclaimer, a last-updated timestamp and sometimes the MLS’s own logo or IDX icon. Local rules vary, so check yours before you remove anything.

Here’s the design takeaway: treat these elements as fixed content and style around them. A disclaimer set in your body font at a readable size, with proper line height, looks deliberate. The same text crammed into a gray box in the vendor’s default font looks like an apology.

Iframe vs. API-Based IDX: What Changes for Design

Not every IDX setup gives you the same amount of control. Here’s how the three common approaches compare from a design point of view.

Iframe widget Plugin or hosted template Custom build on the MLS API
Uses your web fonts No Usually, with CSS overrides Yes
Uses your color tokens Only what the dashboard exposes Mostly Yes
Layout matches your site Rarely Partly Yes
Listing pages on your domain Content lives on the vendor’s page Often Yes
Setup effort Minutes Hours to days Weeks to months

The data side has changed too. The Real Estate Standards Organization has moved the industry from RETS, the older XML-based transfer standard, to the RESO Web API, which delivers listing data as JSON over a modern RESTful interface. RESO announced RETS’s retirement in 2018, although plenty of MLSs and vendors still run it alongside the newer standard. For you, that shift matters because a developer working against the Web API can pull clean fields and pour them into your own templates, instead of wrapping a vendor’s finished page.

There’s a search angle as well. With an iframe, the listing content sits on the vendor’s URL, not yours. Google can sometimes associate framed content with the page that embeds it, but you don’t control how that happens, and you’re competing with every other site using the same feed.

What You Can Control Without Switching Vendors

Most agents won’t rebuild their IDX next month, and they don’t need to. Much of the off-brand feeling comes from a handful of details you can usually fix inside your vendor’s settings or with custom CSS.

Run this quick audit on one listing detail page, on desktop and on your phone:

  • Price typography. Is the price the most prominent number on the page, set in your headline font or a deliberate weight of your body font?
  • Beds, baths and square footage. Do they use one consistent style and order across the results grid and the detail page?
  • Accent color. Does every button and link use your brand color, or are there stray vendor blues left on the “Schedule a Tour” button and the map pins?
  • Font fallback. If your web font can’t load inside the widget, does the fallback at least match its proportions? A geometric sans falls back better to Helvetica than to Times.
  • Photo ratio. Are gallery images cropped to one consistent ratio, so rooms don’t lose their ceilings?
  • Compliance text. Is the brokerage attribution and MLS disclaimer readable, styled and placed consistently, not floating in a gray box?
  • Spacing. Does the widget sit inside your content width, or does it run wider or narrower than the page around it?

On font fallback specifically: if you can’t get your brand font into the widget, pick your site’s body font with that limitation in mind. Fonts with ordinary proportions and a close system equivalent survive the swap. Quirky display faces don’t, and the gap between page and widget becomes obvious.

On color, write your palette down as a short list of named tokens: primary, accent, text, muted text, background, border. Many IDX dashboards let you set two or three colors. If you know exactly which hex values map to which roles, you can fill those fields in a minute instead of eyeballing blues.

When the Template Runs Out

You’ll know you’ve hit the ceiling when the remaining problems are structural. The detail page puts the map above the photos and there’s no setting to move it. You want neighborhood pages that blend editorial content with live listings, and the widget only comes in one shape. Or your designer hands over a property page mockup and the vendor’s answer is “that’s not configurable.”

At that point the choice is between living with the gap and moving to an IDX setup where your own developers or an outside team build the listing pages from the MLS data. It costs more and takes longer than pasting an embed code, and you’ll take on responsibility for keeping the display compliant as the rules change. In return, your listing pages finally use the same type scale, components and spacing as the rest of the site.

For a single agent, a well-tuned plugin is usually enough. For a brokerage that sells on its brand, the listing page is where that brand gets tested most often.

Where to Start

Open one of your listing pages next to your homepage and look at them side by side. If the type, color and spacing feel like two different companies, start with the audit above: fix the price styling, the accent color and the photo ratio first, because buyers notice those immediately. Leave the brokerage attribution and MLS disclaimer in place and style them properly instead of hiding them. If you work through the list and the page still can’t match your design, that’s your signal that the problem is the embed method, not your brand kit.

Share: X Facebook Pinterest

UrbanFonts Team

Font guides, text styles and typography how-tos from the UrbanFonts editorial team.

More posts by this author →

Related posts