Problem

WordPress Social Preview Metadata Audit

Check Open Graph and social card metadata so shared WordPress pages show the right title, description, URL, and image.

Problem

Shared pages show weak, wrong, or missing social previews.

For: WordPress site owners, SEO teams, agencies, and publishers improving organic discovery.

Workflow

What to review

Start With Evidence

Inspect Open Graph/X Card title, description, image, canonical URL, and image accessibility. Capture the exact symptom before changing settings so the next person can see what was tested.

Fix The Owner

Set accurate metadata, clear caches, and test representative page types. Keep the change narrow, reversible, and tied to the layer that actually owns the problem.

WPlura Fit

Web Plura Site Discovery Checker - Brand, Prompt, and Competitor Tracking can help organize the local review, evidence, or handoff path where the product documentation verifies that workflow. Free WordPress.org plugins should be the first step when the local workflow is enough.

Search & DiscoverySeverity: MediumLast reviewed: 2026-09-16

Diagnosis

Symptoms, causes, checks, and fixes

Symptoms

  • Shared pages show weak, wrong, or missing social previews.
  • The issue is visible during routine WordPress, WooCommerce, or client review work.
  • Owners need a clear next step before changing plugins, settings, payment flows, or content.

Most Common Causes

  • Themes, SEO plugins, caches, and missing featured images can create poor previews.
  • Recent updates, configuration drift, cache/CDN behavior, plugin settings, or incomplete operational review can hide the owner of the issue.
  • Teams may be relying on assumptions instead of order notes, logs, local diagnostics, public response checks, or documented handoff evidence.

How To Confirm The Cause

  • Inspect Open Graph/X Card title, description, image, canonical URL, and image accessibility.
  • Record the affected URL, user role, workflow, plugin, order, product, or report section before changing settings.
  • Compare the current result with the expected WordPress or WooCommerce behavior and preserve useful screenshots or exportable evidence.

Fixes

  • Set accurate metadata, clear caches, and test representative page types.
  • Apply the smallest reversible fix first, then clear only the relevant cache or retry only the affected workflow.
  • Use a local report, CSV export, support-safe summary, or checklist when a developer, host, client, or payment provider needs evidence.

How To Verify The Fix

  • Repeat the same workflow that exposed the issue.
  • Confirm the visible status, report, order, product, page, or email path now matches the expected result.
  • Document the final owner and next monitoring step so the issue does not quietly return.

When To Contact Support

Escalate when the issue involves hosting/network controls, payment-provider account state, private customer data, destructive restore work, or a code-level failure that cannot be safely confirmed from wp-admin.

References

Official references