Why Ecommerce Stores Need an Open Graph Audit
Open Graph tags control how your product pages, category pages, and homepage appear when shared on Facebook, LinkedIn, Pinterest, and messaging apps like iMessage. A missing or malformed tag means social shares render as plain text links with no image, no title, and no description — a direct loss of click-through traffic you already earned.
An audit is not a one-time fix. New product launches, theme updates, and app installations frequently overwrite or duplicate Open Graph tags without any visible warning. Running this 12-item checklist after any major site change catches regressions before they compound into weeks of degraded social performance.
The 12-Item Open Graph Audit Checklist
1. og:title present on every page. PASS: A unique og:title tag exists in the <head> of every product, category, and landing page. FAIL: The tag is absent or duplicated more than once on the same page.
2. og:title length under 90 characters. PASS: Every og:title is 90 characters or fewer so Facebook does not truncate it in the feed. FAIL: Any page title exceeds 90 characters.
3. og:description present and non-empty. PASS: Every indexable page carries an og:description with meaningful text. FAIL: The tag is missing, empty, or contains template placeholder text like '{{product.description}}'.
4. og:description length 120–300 characters. PASS: Descriptions fall within this range, long enough to inform but short enough to display fully on most platforms. FAIL: Descriptions are under 60 characters (too thin) or over 300 characters (truncated).
5. og:image specified on every product page. PASS: A valid, absolute URL to an image appears in og:image for every product page. FAIL: The tag is absent, uses a relative path, or points to a broken URL.
6. og:image dimensions 1200×630 pixels minimum. PASS: All og:images are at least 1200×630 px. FAIL: Images are smaller than 600×315 px, which triggers Facebook's small-image fallback and reduces display size dramatically.
7. og:image file size under 8 MB. PASS: Every og:image is under 8 MB (Facebook's hard limit). FAIL: Any image exceeds this limit and will not render.
8. og:type set correctly by page type. PASS: Product pages use og:type = 'product' or at minimum 'website'; the homepage uses 'website'. FAIL: The tag is absent or all pages share an identical, incorrect type.
9. og:url matches the canonical URL. PASS: The og:url value exactly matches the <link rel='canonical'> URL on the same page, including protocol (https) and no trailing slash discrepancies. FAIL: The two values differ, causing platform crawlers to index duplicate content under multiple URLs.
10. No duplicate Open Graph tags. PASS: Each og: property appears exactly once per page. FAIL: The same og: tag appears twice or more, which causes unpredictable rendering as platforms pick one value arbitrarily.
11. Facebook App ID (fb:app_id) or domain verification present. PASS: An fb:app_id meta tag or Facebook domain verification record exists, enabling Facebook Insights data for shared URLs. FAIL: Neither is present and Facebook Insights shows no data for your domain.
12. Open Graph tags validated through Facebook Sharing Debugger and at least one other tool. PASS: All critical pages return no errors in Facebook's Sharing Debugger and render correctly in a second validator such as LinkedIn Post Inspector or Opengraph.xyz. FAIL: Any page returns a scrape error, a missing required property warning, or an image fetch failure.
How to Run the Audit Efficiently
Start by crawling your entire site with a tool that exports meta tags — Screaming Frog, Sitebulb, or any crawler that reads raw HTML. Export the og:title, og:description, og:image, og:url, and og:type columns into a spreadsheet. Sort by character count and blank values to surface failures across hundreds of pages in minutes rather than checking each page manually.
After fixing template-level issues in your theme or CMS, spot-check high-traffic pages individually in Facebook's Sharing Debugger. The Debugger forces a fresh crawl of Facebook's cache, which is essential after edits — without a forced re-scrape, Facebook continues serving the old cached version for days.
Pinterest and LinkedIn each have their own inspection tools. Product-heavy stores with a Pinterest audience should also run the Pinterest Rich Pins Validator because Pinterest reads og:image and og:title alongside its own Product Pin schema.
The Highest-Impact Failures to Fix First
Broken og:image URLs and missing og:images cause the most visible damage because they produce imageless social cards. Prioritize fixing these on your top 20 products by traffic or revenue before addressing character-length fine-tuning.
Duplicate tags are the second-highest-priority fix. They appear most commonly on Shopify stores that use both a theme's built-in Open Graph output and a third-party SEO app that injects its own tags. Disable one source at the theme level or app settings — do not delete tags from theme files without confirming the app covers every page type.
Mismatched og:url and canonical URL values are subtle but consequential. When these differ, Facebook and Pinterest attribute social share counts to different URLs, fragmenting the social proof count that appears on share buttons.
Maintaining a Clean Open Graph Implementation Over Time
Schedule a lightweight version of this audit quarterly or after any major theme update, app installation, or platform migration. Limit the recurring check to five items: og:image presence, og:image load status, duplicate tag count, og:url versus canonical match, and a sample of ten pages through Facebook's Sharing Debugger.
Document which system owns each Open Graph tag — the theme, a meta-tag app, or a headless front end. When two systems can write the same tag, pick one authoritative source and disable the other. That single rule prevents the majority of duplicate-tag failures that reappear after routine updates.