In one paragraph
Open Graph tags missing means the scanned HTML lacks some or all of the title, description, and image properties this check expects. Add accurate page-specific metadata and the protocol's other basic identity properties, then verify the public image and relevant preview consumers. Metadata can improve how links are represented, but it does not guarantee a card, additional clicks, or search indexing.
Why it matters
Sharing services often retrieve a page to assemble a preview. Open Graph gives them an explicit description of the object rather than requiring them to infer every field from visible content. Actual platform support, retrieval, display, and caching still vary.
The Open Graph protocol lists title, type, image, and URL as basic required properties; description is a useful optional property in the protocol. WebAuditOS's three-field rule is therefore a practical subset with its own requirements, not a complete protocol validator.
Do not frame this as a binary search-ranking requirement. Search systems can also use some social metadata as corroborating presentation signals, while ordinary indexing eligibility depends on other factors. The central task is an accurate, accessible, retrievable preview for content people share.
How WebAuditOS evaluates this finding
The supplied rule reads served-HTML meta property values for og:title, og:description, and og:image. All three non-empty values pass, one or two missing values warn, and all three absent fail at the documented low severity. Error or unparseable responses are not graded.
It does not validate image retrieval, useful content, actual card display, or the full protocol's required set. A name attribute or runtime-only insertion is outside its described input. Image URL absoluteness and og:url have separate checks. A pass is metadata presence, not preview verification.
How to fix it
- Inspect the final source for every Open Graph generator. Identify whether the theme, CMS plugin, framework, or custom head code should own output. Remove unintended conflicting duplicates rather than adding another layer.
- Populate each shared page from real content. A basic example is:
<meta property="og:title" content="Pricing and plan comparison">
<meta property="og:description" content="Compare available features and billing options.">
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/pricing">
<meta property="og:image" content="https://example.com/images/share-pricing.jpg">Use actual URLs and truthful wording. A different content type may need a different appropriate og:type and related properties.
- Generate the identity and image addresses from trusted configuration. Resolve relative framework inputs into the intended absolute output and keep staging hosts out of production metadata.
- Make the image publicly retrievable without interactive authentication or a browser-only challenge. Check status, content type, dimensions, file size, and visual crop against the requirements of the platforms that matter to you.
- Add useful image alternative text and accurate structured image properties where relevant. Preserve logical order when multiple images are supplied; do not assume a scanner's chosen value equals every consumer's preference.
- Review language variants, deep routes, pages without featured images, and intentionally private content. A generic fallback can be appropriate in limited cases, but every article should not silently identify the homepage.
- Test platform previews using supported inspection or refresh tools. Distinguish a stale cached card from current source metadata and public resource delivery.
- Rescan the source checks and retain representative preview tests. Also inspect title tags and search snippets separately rather than assuming Open Graph replaces them.
What the fix can break
Metadata does not normally change the rendered page, but incorrect values can misrepresent content widely when shared. A misleading title or stale price can matter more than a missing card.
A blanket homepage identity can collapse unrelated destinations for consumers that use og:url. Test several routes before shipping a global template.
Do not expose private account details in public metadata. A scraper may retrieve the public response without your session and retain preview data after the source changes.
Questions
Are the three scanner fields the whole protocol?
No. Open Graph's basic required set includes type and URL; the scanner's subset also requires description for its pass.
Do tags guarantee a preview on every service?
No. Retrieval, support, platform policy, and caching also affect presentation.
Can tags added only by JavaScript be missed?
Yes. The documented rule reads the served HTML, and consumers differ in rendering support. Publish important preview metadata reliably in the public response.
Which related checks help?
Review image addresses, og:url, and card metadata.