og:url is a relative path

Name

og:url is a relative path og-url-relative

og:url must be absolute so shares always point to the same identity regardless of the request URL.

How to fix

Set og:url to the full HTTPS canonical URL of the page.

Example fix:

<meta property="og:url" content="https://example.com/page" />

Copy or download

# og-url-relative — og:url is a relative path

- **Name:** og:url is a relative path

## Description

og:url must be absolute so shares always point to the same identity regardless of the request URL.

## How to fix

Set og:url to the full HTTPS canonical URL of the page.

### Example fix:

```html
<meta property="og:url" content="https://example.com/page" />
```

## Rule docs

https://ogkit.akr.moe/rules/og-url-relative

What this is

og:url is a relative path. OGKit rule og-url-relative (error). The id is a public API for the docs URL and CI --disable key; do not rename it.

Search phrases that should land on this page:

• All URLs must be absolute
• I want my og:url or og:image tags to use relative URLs, but the debugger complains about this.
• og:url is a relative path
• relative og:url

Why it matters

og:url must be absolute so shares always point to the same identity regardless of the request URL.

Which platforms are affected

All OGKit platform profiles, including major social, chat, and search crawlers that consume these tags.

Platform-specific crawler budgets and field priority live in the platform behaviour reference.

How to reproduce

1. Read og:url. Relative paths like `/page` fail this check.

Related rules

• og-url-not-https — og:url is not HTTPS
• og-url-canonical-mismatch — og:url does not match canonical
• og-url-final-url-mismatch — og:url does not match final URL after redirects
• robots-blocks-social-crawlers — robots / X-Robots-Tag blocks social previews
• ua-content-diverged — Different User-Agents received different HTML
• og-tags-require-javascript — OG tags appear to require client-side JavaScript