In one paragraph
og:url missing means the inspected page does not declare a non-empty Open Graph identity URL. Add the intended clean absolute address for that specific page and keep it consistent with your canonical strategy. Do not use a homepage default for unrelated content. The tag helps sharing consumers identify an object; it does not replace search canonicalisation or guarantee how every platform handles previews.
Why it matters
The Open Graph protocol lists og:url among its four basic required properties, alongside title, type, and image. It acts as a permanent identity for the graph object. Stable identity can help consumers treat tracking variants as the same shared page rather than unrelated objects.
Consumers differ in fetching, association, display, and caching. A missing value does not universally prevent sharing, because platforms can infer an identity from the pasted or retrieved URL. A wrong value can nevertheless associate content with the wrong object or preview, so correctness matters more than presence.
Rel=canonical serves search canonicalisation, while og:url serves Open Graph identity. They often use the same clean representative address on an ordinary page, but one is not a replacement for the other. Do not claim that adding og:url forces Google to index the chosen destination.
How WebAuditOS evaluates this finding
The supplied rule reads non-empty meta property="og:url" in served HTML on eligible parsed pages. Presence passes; missing or empty content warns informationally. Error and unparseable pages are not graded.
It does not validate whether the value is absolute, matches the page, agrees with canonical intent, or loads successfully. A homepage URL copied onto every page can pass. A name attribute or runtime-only insertion is outside its described matching. Read the evidence value instead of treating a pass as correct identity.
How to fix it
- Define the intended public identity of the current content. Consider the preferred scheme, hostname, language route, and meaningful path. Remove tracking parameters only when they do not identify genuinely different content.
- Generate the value from the same deliberate URL model used for relevant canonical output. For an ordinary self-representing page, an example is:
<link rel="canonical" href="https://example.com/pricing">
<meta property="og:url" content="https://example.com/pricing">Use the real destination for this page. Do not copy that example or the homepage address into every route.
- Fix the shared layout or metadata generator. A framework may accept a relative input and resolve it with a configured base; verify the final HTML is the intended absolute URL. Use trusted configuration rather than arbitrary request-host data.
- Review intentionally non-self-canonical content separately. A distribution or duplicate-content strategy can create a different relationship from a normal page. Check the platform's intended identity handling rather than mechanically assuming every unusual value is wrong.
- Keep title, description, type, and image consistent with the identified object. A stable URL associated with unrelated homepage artwork or another language's summary remains a confusing preview.
- Test deep routes, pagination, languages, and parameter variants. Confirm meaningful distinct pages do not all collapse to one default identity and that stale staging domains or HTTP addresses are not emitted accidentally.
- Inspect actual public responses and relevant platform preview tools. Follow the resulting retrieval and cached object behaviour where available. A platform can keep an older card after the source is fixed, so request a supported refresh before diagnosing another metadata bug.
- Rescan and retain tests for route-specific identity output. Check search canonical selection independently; this Open Graph presence rule cannot establish indexing or ranking outcomes.
What the fix can break
Changing an established identity can change cached previews or engagement associations on platforms that use it that way. Review important existing shared URLs before normalising formatting solely for cosmetic consistency.
A global default is the major template risk. Every new page can appear correct in a source check while identifying the wrong object. Test multiple routes before deployment.
Do not strip every query parameter without understanding your content model. Some parameters are tracking only; others distinguish the actual page. Stable identity should preserve the meaningful distinction.
Questions
Is og:url the same tag as rel=canonical?
No. They serve different consumers and roles, though ordinary page implementations commonly derive both from the same intended URL.
Does missing og:url make a page unindexable?
No. This is an Open Graph metadata finding, not an indexing eligibility test.
Why does a wrong homepage value still pass?
The supplied rule checks non-empty presence, not agreement with the current page or destination validity.
Which related checks help?
Review canonical tags, Open Graph coverage, and image URLs.