Featured Clients: Anonymized automotive dealership groups across multiple OEM brands and website platforms.
Stream Companies checked the outside code running on more than 600 client websites. We found three separate problems that were hurting conversion tracking and site health.
Each problem hit a different group of clients, and each one took a different partner and a different fix. No client reported any of them. No report flagged them. We found all three because we went looking.
The Challenge
Most websites break quietly. Code fails, old vendor code lingers, tracking stops working, and the site still looks completely normal. A monthly traffic report will never tell you your lead tracking has been failing for weeks.
Across 600+ client sites, spanning many brands and platforms, we needed to:
- Catch code failures that never show up in traffic, ranking, or lead reports.
- Review the whole portfolio at once instead of one site at a time.
- Pin down who owns broken code when vendors say it isn’t theirs, then push those partners to finish the fix.
When code breaks, search engines can struggle to read the page, costing visibility and hurting the visitor experience.
Solution
Stream audited third-party code across client sites and pushed each finding to the appropriate channels: Paid Social used our agency partnership to reach a social platform’s engineers on a failing lead-tracking script, our Technical SEO Specialist spent two months working with an external vendor, and SEO stripped expired ad code off of around 120 sites.
Results
None of the identified problems showed up in a report or a client call. We found all three by digging into the code ourselves, fixed them across the portfolio, and two of the fixes landed at the source, so every affected client benefited at once.
First Finding:
Lead Tracking Was Quietly Failing
Who it Affected:
Nearly half of the clients in the 600+ site audit, across several brands.
We found broken code in the tool that passes lead data to a major social platform for ad reporting. On hundreds of client sites, those requests were coming back as 503 errors, page after page.
Fixing it meant working with that social platform directly, so our SEO team brought in our Paid Social team, who used our agency partnership to reach the platform’s engineers.
How We Fixed It
Raised the issue quickly:
We took the error to our own Development team and the platform’s engineering team at the same time.
Ruled out a subdomain issue:
Development confirmed it wasn’t a simple setup issue.
Uncovered the root cause:
The database behind the tool had run out of storage. Log files had piled up for months and were consuming the remaining space.
Confirmed the issue:
The platform’s engineers looked independently and found the same thing.
Provided an immediate fix:
The old logs were cleared out, storage came back, and tracking started working again.
Implemented a long-term solution:
The platform recommended moving to its managed cloud setup, which removes the database that caused the problem and lowers cost and upkeep.
Locked in next steps:
The platform sent migration documentation and offered engineering help with the move.
Why It Matters:
Hundreds of sites were losing lead data, and nobody knew until a hands-on audit found it.
Second Finding:
A Broken Script Nobody Would Claim
Who it Affected:
A different group of dealership clients using an outside service scheduling tool.
The second broken script came from a vendor’s service scheduling system. We contacted the vendor, who claimed it wasn’t theirs, and there was nothing they could do about it.
Our Technical SEO Specialist kept the conversation going for about two months and put the website platform providers and the vendor in the same email thread, so neither side could point at the other.
Once everyone was looking at the same evidence, the vendor and the platform teams found the cause together and fixed it.
Why It Matters:
The first answer you get isn’t always the right one. The fix was possible the whole time; it just required persistence and cross-team collaboration.
Third Finding:
Old Ad Code Nobody Had Cleaned Up
Who it Affected:
Roughly 120 websites, a third separate group of clients.
Our SEO team found and removed expired ad code still running on about 120 client websites. It belonged to a service these sites had stopped using. It slowed pages down, added another external request that could break, and did nothing to boost visibility.
With it gone from all 120 sites, those pages are lighter and cleaner
Why It Matters:
Old code doesn’t delete itself. Without someone checking, it just keeps piling up.
