Plain definition
Definition of Open Graph Tags
Metadata properties in a page's HTML head defined by the Open Graph protocol that control the title, description, canonical link, and preview image shown when a URL is shared.
Required properties (ogp.me): og:title | og:type | og:image | og:url (plus recommended og:description and og:site_name)Worked example
According to the Open Graph protocol specification at ogp.me, turning a web page into a rich graph object requires four basic properties placed inside the HTML head: og:title, og:type, og:image, and og:url. Most social networks and chat apps also read optional properties such as og:description, og:site_name, og:image:width, and og:image:height to render complete preview cards.
Say a made-up podcast clipper called WaveSnip ships its v1 and shares its homepage link in Slack, Discord, LinkedIn, and X. Its document head declares og:title as "WaveSnip: Turn podcast episodes into captioned clips", og:type as "website", og:url as "https://wavesnip.example/", and og:image pointing to an absolute HTTPS 1200x630 PNG showing the actual waveform editor. Instead of rendering a bare blue URL or a stretched favicon, every platform displays a crisp visual card that explains the product before anyone clicks.
Why it matters when you launch
Most early launch traffic arrives through shared links in group chats, newsletters, social feeds, and direct messages rather than organic search. Your Open Graph card is effectively your billboard inside every feed where someone pastes your URL. A broken image, a generic "Create Next App" title, or a cropped screenshot wastes the brief second of attention a stranger gives your post.
Testing your Open Graph tags before launch day ensures that every key route, including your homepage, pricing page, and main blog post, renders a sharp, readable card across desktop and mobile apps. Make sure your og:image URL is publicly reachable without authentication and loads over HTTPS.
Common mistakes
- Setting og:image to a relative path like /og.png instead of a full absolute HTTPS URL, causing scrapers on social platforms to drop the preview image.
- Reusing the exact same homepage og:title and og:image across every blog post, documentation page, and product page on the site.
- Placing key text near the edges of your preview graphic where square or mobile crops slice off half of your headline.
- Updating your Open Graph image on launch morning without changing the filename or busting platform caches, leaving stale previews stuck in Slack, X, or LinkedIn.
Tools and guides that use it
Free tool
Open Graph & Social Card PreviewerSimulate how your product links and preview images appear on X, LinkedIn, Google Search, and Slack.Free tool
Meta Tag GeneratorPreview your Google result and social cards, and copy the tags for Next.js or HTML.Founder guide
How to Fix Broken Link Previews on X, LinkedIn, Slack and iMessage (2026)The Open Graph and card tags platforms actually read, the image dimensions that stop cropping, the Next.js mistakes that silently drop your card, and how to clear stale caches.Founder guide
The Next.js Technical SEO Launch Checklist (2026)What to check before and after launch day: crawlability, metadata, canonical URLs, structured data, sitemaps, internal links, Core Web Vitals and AI crawlers.Related glossary terms
Official sources
Pritam Ghosh runs Hauntboard and maintains this glossary.
Published · Updated
Building something real? Launch it in public.
A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.