What it is
Open Graph tags are HTML metadata placed inside the page <head>. They help declare the preferred title, description, image, URL, and type for link previews when a page is shared on social platforms, messaging apps, collaboration tools, or other preview systems.
The main tags commonly used look like this:
<meta property="og:title" content="Example page title">
<meta property="og:description" content="Short page summary">
<meta property="og:image" content="https://example.com/image.jpg">
<meta property="og:url" content="https://example.com/page/">
<meta property="og:type" content="website">
Each tag declares a specific property. Together they help external systems build a more coherent preview of the shared page.
Why it matters
Open Graph can help make link previews more consistent, reducing the chance that external platforms show random text fragments or unrepresentative images extracted automatically from the page body.
These metadata can be useful for:
- Preview control: they help declare which text and image should represent the page outside the site;
- Preview consistency: they help keep shared previews aligned with the page title tag, meta description, and other page signals;
- Content sharing: they can make shared links easier to understand in chats, social platforms, and collaborative tools.
Open Graph does not guarantee visibility, clicks, ranking, traffic, or indexing. External platforms may ignore, modify, crop, cache, or delay updates to this data. Missing Open Graph is not automatically a severe problem, especially for pages that are rarely shared. Inconsistent Open Graph, however, can be more misleading than having no Open Graph metadata.
How this is checked
The scanner analyzes the page <head> to detect Open Graph metadata and map the values declared by the page.
The current check verifies:
- whether commonly used tags such as
og:title,og:description,og:image,og:url, andog:typeare present; - whether declared values are empty;
- whether the URLs in
og:urlandog:imageappear formally valid; - whether the declared image uses HTTP instead of HTTPS;
- whether the value in
og:urlappears consistent with the analyzed page; - whether duplicate or conflicting tags of the same type are present.
The scanner observes the metadata declared by the page. It does not decide how an external platform will actually render the final preview.
Possible findings
Each finding should be read as a review signal, not as an automatic penalty.
Missing Open Graph tags
No Open Graph metadata was detected on the page. This is not always a severe issue, but it may be worth addressing on pages that are shared more often.
Empty Open Graph tags
The tags exist in the code, but the declared content values are empty.
Missing og:title
The preview title is not declared.
Missing og:description
The preview description is not declared.
Missing og:image
The page does not declare a dedicated Open Graph image.
Missing og:url
The page does not declare a preferred sharing URL.
Missing og:type
No resource type was declared through og:type.
Invalid image or page URL
The URL declared in og:image or og:url appears malformed or structurally invalid.
Non-HTTPS Open Graph image
The image declared in og:image uses HTTP instead of HTTPS, which can make previews less reliable on some systems.
Inconsistency between Open Graph and SEO metadata
The preview title or description differs sharply from the page title tag or meta description, suggesting a possible oversight or a choice worth reviewing.
Inconsistent Open Graph URL
The declared value in og:url points to an address that does not seem aligned with the analyzed page.
Duplicate tags
The page contains multiple Open Graph tags of the same type with different values, which can make interpretation less clear for external systems.
Recommended action
- Prioritize where it matters: focus first on pages most often shared in chats, social platforms, or collaborative tools.
- Fill in the main tags: declare title, description, image, URL, and type with clear and coherent values.
- Use a valid HTTPS image: avoid broken files, random visuals, or non-secure image URLs.
- Keep metadata aligned: compare Open Graph values with the title tag, meta description, and page context when useful.
- Account for external cache: updates may not appear immediately on every platform; debugger tools can help in some cases, but they do not guarantee an instant refresh everywhere.
- Work gradually: start from core templates or the pages most exposed to public sharing.
How to fix it
Static HTML
If you manage the HTML directly, add the meta tags inside the <head> and use absolute URLs with the full protocol:
<meta property="og:title" content="Example page title">
<meta property="og:description" content="Short page summary">
<meta property="og:image" content="https://example.com/image.jpg">
<meta property="og:url" content="https://example.com/page/">
<meta property="og:type" content="website">
WordPress / SEO plugins
Many SEO or social plugins generate these tags automatically from the page title, summary, and featured image.
- Open the page or post editor.
- Look for the plugin tab related to social sharing or preview settings.
- If needed, enter a dedicated social title, description, or image.
- After saving, clear site cache if caching layers are in place.
CMS / E-commerce
In dynamic CMS setups or ecommerce platforms, Open Graph is often built from templates.
- Check that
og:imageuses the correct dynamic variable, such as the main product or content image. - Verify that
og:titleandog:descriptiondo not inherit text that is too generic or repetitive. - Make sure archive pages, filters, or categories do not reuse the homepage image without a clear reason.
How it appears in the report
In the report, the Open Graph check shows the detected metadata, the declared text values, and any links associated with title, description, image, URL, and type.
The scanner helps compare these values with the page's other metadata so you can spot omissions or meaningful differences. It does not judge the marketing appeal of the preview, but it provides a clear technical picture for assessing preview consistency.
When to run a new scan
Run a new scan after configuring social plugins, updating featured images, or changing CMS templates. This helps confirm that the tags are present in the code and that the declared URLs look valid and coherent.