Nine Months of Social Shares Promoting the Wrong Brand

A B2B company noticed that some of their social shares were rendering with the wrong logo. The brand showing up on LinkedIn and Facebook previews was a partner company's logo, not theirs. Nobody could figure out how it had been going on or for how long.

Their og:image had been returning 404 for nine months. The theme had hardcoded an uploads path that never existed (the file had been moved during a media reorganization, and the og:image meta tag was never updated). When Facebook, LinkedIn, and Bing's crawlers fetched the page and could not load the og:image, they fell back to the next available image tag on the page. The next available image tag happened to be a partner company's logo in the footer. For nine months, every share of the site on every social network had been displaying that partner's logo as the brand.

Nobody had caught it because the platforms do not warn you. A 404 og:image silently degrades to whatever image the platform can find. The site looked fine to humans visiting it. Only people who shared a link saw the problem, and most of them assumed it was the platform's fault.

Step one was running the live site through three social share previewers (Facebook Sharing Debugger, LinkedIn Post Inspector, X Card Validator). All three returned the same fallback image. None of them flagged the og:image as broken. They just showed the next-best image they could find.

Step two was inspecting the page source. The og:image meta tag pointed at a hardcoded path: /wp-content/uploads/2024/social-default.jpg. A direct request to that URL returned 404.

Step three was tracing why. The site had been through a media library reorganization. The image was moved into a different folder structure. The og:image path in the theme was never updated. Nine months passed.

Step four was finding the right image and updating the path. Three minutes from diagnosis to fix. Push, scrape, verify.

All three previewers immediately picked up the corrected og:image after a manual rescrape. Every share thereafter rendered with the correct brand. Facebook's cached fallback was forced to refresh through the Sharing Debugger. LinkedIn's cache cleared on its own within hours.

Nine months of social shares promoting the wrong brand stopped within an hour of diagnosis.

The Setup

A B2B company noticed something off about their social shares. The brand rendering on LinkedIn and Facebook previews was not theirs. It was a partner company’s logo. They asked us to figure out what was happening and how long it had been going on.

What We Found

The og:image had been returning 404 for nine months.

The theme had a hardcoded uploads path that no longer existed. The file had been moved during a media library reorganization. The og:image meta tag was never updated to match. When Facebook, LinkedIn, and Bing crawled the page and could not load the og:image, they fell back to the next available image tag. That next image was a partner company’s logo in the footer. Every share for nine months rendered with that partner’s logo as the brand.

Nobody caught it because the platforms do not warn you. A broken og:image silently degrades to whatever the platform can scrape. The site looked correct to anyone visiting it. Only people who shared a link saw the wrong logo, and most assumed the platform was at fault.

The Diagnostic

Four steps. The whole audit took fifteen minutes.

1. Run the live site through three previewers. Facebook Sharing Debugger, LinkedIn Post Inspector, X Card Validator. All three returned the same fallback image. None of them flagged the og:image as broken. They simply rendered the best image they could find.
2. Inspect the page source. The og:image meta tag pointed at /wp-content/uploads/2024/social-default.jpg. A direct request to that URL returned 404.
3. Trace the cause. A media library reorganization had moved the file. The hardcoded theme reference was never updated.
4. Find the right image and update the path. Replace, push, rescrape, verify.

The Fix

Three minutes from diagnosis to fix.

• Updated the og:image path in the theme to a real, current asset.
• Forced a Facebook rescrape through the Sharing Debugger.
• Verified LinkedIn picked up the new image (its cache cleared on its own within hours).
• Verified Bing on a fresh share.

Outcome

Nine months of social shares promoting the wrong brand stopped within an hour. Every share thereafter rendered with the correct logo. The fix that took three minutes had been costing brand exposure across three networks for the better part of a year.

Lessons

• A broken og:image does not throw an error. It silently degrades. Every social platform falls back to a different image, and none of them tell you the og:image was the intended one.
• Media reorganizations break hardcoded paths. Anything in a theme file that points at /wp-content/uploads/... is fragile. A move or rename anywhere in the media library can break the reference without warning.
• Run share previewers as part of every audit. Facebook Sharing Debugger, LinkedIn Post Inspector, X Card Validator. Each one takes thirty seconds. They are the only place where a 404 og:image becomes visible.
• The fallback image matters more than people think. When your og:image fails, the platform picks the next one on the page. If that happens to be a partner logo, a sponsor, or an ad, your brand is replaced by theirs in every share.

Brent’s Take

Nine months of free brand exposure went to a partner company because nobody opened the Sharing Debugger after a media reorganization. The fix took three minutes. The cost of not catching it was nine months of social-share inventory pointed at the wrong logo.