Release Notes TL;DR
BrokerOS Web is built as a managed platform, so not every meaningful update is about launching a brand-new marketing page.
Some of the most useful work happens in the shared layer: how sites describe themselves to search systems, how synced repos stay easier to maintain, and how published content gets surfaced once a library of articles starts growing. That was the focus of this release.
This update centered on three practical areas:
This release included a useful shared-schema improvement in the BrokerOS layer.
The LocalBusiness schema logic was updated so site-level enablement can apply more broadly instead of being limited to a smaller set of page types like the homepage and certain contact pages.
That is a practical improvement for managed freight broker websites. When shared schema rules are easier to apply consistently, sites become easier to maintain as content grows and as teams add more pages that still need clear company and location signals.
This kind of work is not flashy, but it supports a better long-term technical foundation for search engines and other systems that rely on structured page meaning.
The underlying BrokerOS workflow also picked up maintenance improvements that make shared-site operations easier to manage.
That work included:
These changes are especially relevant when teams are working with synced shared components or troubleshooting remote-feed behavior. Instead of forcing every site maintainer to remember extra cleanup steps, the shared workflow now does more of that work directly and includes tests to help keep those expectations stable.
This release also improved how the news hub highlights featured content.
When a custom featured product link is not supplied, the shared template now falls back to the newest article automatically. That means the supporting link under the featured story can point visitors to the latest published content instead of relying on a generic default destination.
For prospects, that creates a cleaner path into the freshest BrokerOS product updates and educational content. For current customers, it helps the hub feel more current without requiring manual rewiring every time a new article goes live.
Instead of appending that reference inline at the end of the summary, the template now renders it as its own block below the main description. That keeps the featured summary easier to scan and gives the follow-up link a clearer visual role.
These are small presentation details, but they matter on a freight broker website platform. Product updates, educational resources, and proof points all work better when the reading path is clear and the next action is easy to spot.
This in-repo BrokerOS Web work included:
Freight broker websites should not get harder to manage as they grow.
They need a shared technical foundation that stays easier to maintain, easier for search systems to interpret, and easier for visitors to navigate once more content goes live.
This release reflects that model in practice: strengthen the schema layer, reduce maintenance friction, and make the content hub more useful without needing one-off manual cleanup every time the platform evolves.
If you want to see how these kinds of shared improvements fit into the broader platform, explore BrokerOS Web . If you want to talk through what an evolving freight-specific website foundation could look like for your brokerage, contact us .
Keep reading
Most CRMs are built for software sales pipelines. Freight brokerages have carriers, shipper prospects, onboarding flows, and TMS data that do not fit that model — and adapting a generic tool to freight usually creates more problems than it solves.
Shippers are increasingly using ChatGPT and Google Gemini to find freight brokers. Most brokerage websites are invisible to those tools — not because they do not deserve to show up, but because they are not built for it.
Join the BrokerOS Web Growth Webinar Series to learn how freight brokers can improve website strategy, SEO, AEO, online authority, and sales visibility.
This website uses cookies to improve functionality and user experience. By continuing to use this site, you acknowledge our use of cookies. See our privacy policy .