Skip to content
goflag
Documentation
Rule catalogue

og.image.absolute

og:image must be an absolute URL

warningper pagevendor-spec

Why it matters

A relative path works in every browser you test in, because a browser has the page to resolve it against. The crawler building the preview has only the tag. So the share looks exactly as broken as having no image at all — with the difference that the tag is there, and review moves on.

What the finding looks like

The message goflag prints, with example values substituted.

warn og.image.absolute Open Graph image URL is not absolute: og:image = /og.png. Crawlers cannot resolve it.

Give Next a metadataBase, or write the origin in

Written for the Next.js App Router. The finding is correct on any stack; only the remedy assumes one.

// app/layout.tsx — every relative metadata URL resolves against this.
export const metadata = {
  metadataBase: new URL(process.env.SITE_ORIGIN!),
  openGraph: { images: ["/og.png"] }, // emitted absolute
};

Says who?

This rule is vendor-spec, and it cites the documents below. Nothing here is goflag’s opinion of what a good page looks like — if you disagree with a finding, this is what you are disagreeing with.