WordPress 7.1 media processing can change filenames, orientation, derivatives, animated GIF companion posters, and attachment metadata. An origin fix does not prove that CDN edges, Open Graph tags, or social preview providers fetched the corrected bytes and crop.
Use this when a featured image or animated media poster looks correct in WordPress but Facebook, LinkedIn, X, Slack, iMessage, or another sharing client still shows an old orientation, crop, format, or missing image.
Quick answer
Record the attachment ID, source hash, final poster URL, dimensions, MIME type, metadata, CDN validators, and Open Graph output. Fetch the URL from origin and CDN, use each provider's refresh or sharing tool where available, then record fetch time and rendered crop. If one stable URL cannot be purged reliably, publish a versioned filename and update the canonical post metadata before retiring the old asset.
What to check first
- Record original, processed image, responsive derivatives, animated-video poster, attachment metadata, featured-image relationship, Open Graph plugin output, canonical post URL, and any image proxy URL.
- Compare bytes, dimensions, MIME type, EXIF orientation, content length, ETag, last-modified, cache-control, age, redirect chain, and status at origin and multiple CDN edges.
- Inspect raw crawler HTML for one og:image, og:image:width, og:image:height, og:image:type, Twitter image, and canonical URL that all identify the intended poster.
- Refresh or rescrape Facebook, LinkedIn, X, Slack, iMessage, and any campaign or messaging tool used by the business, then capture the displayed crop and fetch time.
- If a stable name stays stale, publish a versioned object, update all metadata and structured references, purge the post and asset paths, verify providers, then retain the prior object through the rollback window.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Identify one intended poster version | Record original, processed image, responsive derivatives, animated-video poster, attachment metadata, featured-image relationship, Open Graph plugin output, canonical post URL, and any image proxy URL. | Origin and CDN return the intended hash, status, content type, and dimensions. |
| Compare origin and CDN bytes | Compare bytes, dimensions, MIME type, EXIF orientation, content length, ETag, last-modified, cache-control, age, redirect chain, and status at origin and multiple CDN edges. | Raw HTML contains one coherent set of canonical and social image tags. |
| Validate raw social metadata | Inspect raw crawler HTML for one og:image, og:image:width, og:image:height, og:image:type, Twitter image, and canonical URL that all identify the intended poster. | Each important provider shows the intended poster and a recorded refresh time. |
| Refresh each provider | Refresh or rescrape Facebook, LinkedIn, X, Slack, iMessage, and any campaign or messaging tool used by the business, then capture the displayed crop and fetch time. | Rollback can restore the prior metadata and object without leaving broken versioned references. |
Why this usually happens
- Social providers cache image bytes independently from the page and CDN.
- A filename can stay the same while orientation or generated bytes change.
- Open Graph plugins, object cache, page cache, and prerendered HTML can disagree about the selected image.
- A redirect or unsupported MIME type can make one provider reject an image that browsers display.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
curl -sS -I https://example.com/media/poster-v3.webp
curl -sS https://example.com/post/example | grep -Ei 'og:image|twitter:image|canonical'
sha256sum poster-v3.webp
# Record provider, scrape time, displayed crop, and final fetched URL in the matrix.
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Identify one intended poster version
- Compare origin and CDN bytes
- Validate raw social metadata
- Refresh each provider
- Version the URL when purge is unreliable
Decision rule
Pass when the canonical page, attachment metadata, origin, CDN, Open Graph tags, and every important sharing provider identify the intended poster version with correct dimensions, orientation, crop, and MIME type.
What to tell the client or owner
Give the owner the affected versions, exact workflow, observed result, business impact, evidence location, temporary control, named owner, and next review time. Remove credentials and personal data from shared screenshots and logs.
Production verification checklist
- Origin and CDN return the intended hash, status, content type, and dimensions.
- Raw HTML contains one coherent set of canonical and social image tags.
- Each important provider shows the intended poster and a recorded refresh time.
- Rollback can restore the prior metadata and object without leaving broken versioned references.
Mistakes to avoid
- Do not change several plugins, cache rules, or infrastructure settings before preserving a baseline.
- Do not treat one successful test as proof for retries, alternate clients, background work, or mixed-version fleets.
- Do not paste secrets, personal data, complete production payloads, or customer files into tickets or screenshots.
- Do not close the test until the final user-visible state and the server-side evidence agree.
Questions teams ask during testing
Does a CDN purge refresh Facebook or LinkedIn?
No. Provider caches are separate and may need their own rescrape or a new versioned URL.
Should the old poster be deleted immediately?
Keep it through a measured rollback and cache-expiry window unless it exposes sensitive or unsafe content.
When HandL WP should help
Bring in HandL WP when a production checkout, form, editor, security gate, media pipeline, or paid lead workflow is at risk. We can preserve evidence, isolate the failing layer, make the smallest corrective change, and verify the result across WordPress, connected services, logs, and the user journey.
If this is active on a production site, fix stale WordPress social previews.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references