og:url is missing
Your page has no og:url tag. It is one of the four properties the Open Graph spec marks required, and it is how platforms pool engagement across variants of the same URL.
What you are seeing: Share and reaction counts look lower than they should be, or the same page appears as several separate posts with counts split between them.
og:url is the page's canonical identity for social
The Open Graph protocol defines four required properties: og:title, og:type, og:image and og:url. og:url is the one people most often leave out, because unlike the other three it has no visible effect on the card.
Its job is identity. When someone shares your page, the platform stores engagement against the URL in og:url rather than the URL that was pasted. That is what lets a link shared with ?utm_source=newsletter, a link shared with a trailing slash, and a link shared from a mobile subdomain all count as the same page.
What happens without it
Each variant becomes a separate entity. Reaction and share counts split across them, and a page that has genuinely been shared widely reads as several lightly-shared pages. On Facebook this also means the two variants can hold different cached previews, so the same link looks different depending on which form someone shares.
What value to use
The absolute, canonical URL of the page — the same one you would put in rel=canonical, including scheme and host, with no tracking parameters and no session identifiers. Pick one form for trailing slashes and use it consistently.
Self-referencing is correct and expected: every page's og:url should point at itself. This is not a redirect and it will not send anyone anywhere.
Self-referencing, absolute, no parameters
<meta property="og:url" content="https://example.com/blog/open-graph" />Frequently asked
Is og:url the same as rel=canonical?
They usually hold the same value but they are read by different consumers. rel=canonical tells search engines which URL to index; og:url tells social platforms which URL to attribute a share to. Search crawlers do not read og:url, and social crawlers do not read rel=canonical, so setting only one leaves the other audience guessing.
Should og:url include query parameters?
No. Strip tracking parameters and anything session-specific. The entire purpose of the tag is to collapse variants of a URL into one identity, which a parameter would defeat.
Check your page
Run your URL through the checker to confirm the fix is live and see how the card renders on every platform.
Test a URL
ZippyStarter