NewSiteCheck
Home / Resources / Release case study
FIRST-PARTY RELEASE CASE STUDY · OCTOBER 14, 2026

Our social preview pointed at an image that did not exist.

A transparent example from NewSiteCheck’s own release audit: what we saw, what we changed, and what the check could and could not prove.

What happened

While reviewing a large release of new tool and guide pages, we found that 31 HTML pages declared an Open Graph image URL ending in share-card.svg. The package contained share-card.png, but no SVG with that name. A visitor clicking the page could still use the tool; the mismatch affected the image that social services might request when someone shared its link.

The gap was easy to miss in an ordinary page review because the Open Graph URL sits in the HTML head. A visual browser check of the page body would not necessarily reveal it. We found it by comparing the declared URLs across pages with the actual files in the release archive.

How we fixed it

  1. We identified the 31 pages pointing to the absent SVG path.
  2. We updated each declaration to the real PNG image URL and kept the rest of the page metadata page-specific.
  3. We reran an internal path audit, verified that the image asset existed in the Cloudflare upload package, and checked the ZIP for extraction errors.

This was a source and package check. We did not measure a change in social clicks, and social platforms can cache earlier previews. After deploying a fix like this, the final check is to share a live URL with the intended platform’s preview tool.

Why this matters for a site launch

The mistake illustrates a useful launch sequence: find a concrete discrepancy, change the one system that owns it, then verify the published result. Similar checks apply to canonical URLs, missing page titles, noindex settings and redirects. A scanner can provide evidence, but it cannot guarantee Google indexing or a perfect social preview on every platform.

NewSiteCheck now shows guided steps for visible findings and lets you recheck the public URL after you publish a change. The metadata checker shows declared social fields, while the indexability checker covers a different class of launch mistakes. The launch checklist helps keep these checks together.

What we learned

Test the packaged files and public URLs, not only the page you see in your own browser. Reused page templates make publishing faster, but one wrong shared reference can spread to dozens of pages. A short repeatable release check can catch that before a promotion campaign sends people to the site.

This is our own release example, not a customer testimonial. The number 31 refers to source pages with the missing reference in the reviewed package. No traffic or revenue outcome is claimed.