url.other-host
og:url is on a different host. Level: Warning.
When it is raised
Raised when og:url is set and its host differs from the host of the page's final URL, after redirects. Hosts are compared including any port, so www.example.com, example.com and example.com:8080 are three different hosts; the scheme is not compared. A value that is not an absolute URL with a scheme (for example /about or example.com/about) cannot be parsed, so it is compared as written against the page's host, and unless it is exactly that host this check is raised.
What it does to a shared link
The card names an address on another host as the page's canonical address. The finding shows both hosts: the one in og:url and the one the page was fetched from.
How to fix it
- Set og:url to an absolute URL on the host the page is served from, including the scheme.
- If the page was fetched through a redirect, use the host of the page's final URL, after redirects.
- Where one build serves several hosts (a staging or preview deployment, or both www and the bare domain), generate og:url from the canonical host deliberately and expect this warning on the others.
<meta property="og:url" content="https://www.example.com/page/">