For many businesses, LinkedIn, Facebook, WhatsApp and industry communities are high-quality referral channels. A single post from a founder, team member, agency partner or customer can send several hundred targeted visitors to a page. But if the Open Graph tags on that page are wrong or missing, every one of those shares looks broken.
Open Graph tags (og:title, og:description, og:image, og:url) are read by LinkedIn, Facebook, WhatsApp and every other platform that generates a link preview. They are completely separate from your regular title and description tags. You can have a perfect meta title and still show a broken LinkedIn preview if your og:title is missing. Most website builders do not add these tags automatically. WordPress without an SEO plugin adds none of them.
The og:image tag deserves special attention. When your content is shared, the image is the first thing people see before they read the headline. A page with no og:image shows a small, low-resolution preview or no image at all, depending on the platform. A page with a well-designed 1200 by 630 pixel image gets the full-width card treatment. We have seen the same article generate 3x more LinkedIn clicks after adding a proper og:image, with no change to the content or the headline.
Twitter Card tags work similarly but control the preview on X (formerly Twitter). For businesses where founders, executives, creators or agencies are active on X, these tags determine whether your shared link looks professional or anonymous. The twitter:card tag set to summary_large_image gives you the full-width image treatment. Without it, you get a small thumbnail that most people scroll past.
og:url is the most overlooked social tag. It specifies the canonical URL for the shared content. Without it, some platforms generate the share URL from the browser address bar, which may include campaign tracking parameters. That can result in duplicate analytics entries and broken caching of previews across different share sessions. Test all your social previews in one place using the OG tag previewer.
Where you add meta tags depends on what your website is built with. The HTML is the same everywhere. The location where you paste it changes.
WordPress with Yoast or Rank Math. Open any page or post in the editor. Scroll to the SEO plugin panel below the content. The title and description fields are in the main tab. Open Graph and Twitter Card tags are in the Social tab. The plugin handles the HTML output. You never touch code. If you need to add custom tags the plugin does not cover, use the Rank Math Code Editor or Yoast's wp_head action hook.
WordPress without an SEO plugin. Edit your theme's header.php file. Add the meta tags inside the <head> section. Better approach: use the Create Tags tab above, copy the output, and paste it into a child theme header or a custom code plugin like WPCode. This avoids losing your tags when the theme updates.
Shopify. Go to Online Store, then Themes, then edit the theme code. Open the theme.liquid file. Find the <head> section. Shopify generates title and description from the page editor fields automatically. For custom OG tags, add the HTML directly in theme.liquid or use a meta tag app from the Shopify App Store. The Create Tags output above works directly in Shopify's code editor.
Squarespace. Page Settings has a dedicated SEO tab with title and description fields. For Open Graph images, Squarespace uses the page thumbnail by default. For custom OG and Twitter tags, go to Settings, then Advanced, then Code Injection, and paste meta tags in the Header field. This applies site-wide. For page-specific tags, use the per-page Code Injection in the page settings panel.
Webflow. Each page has an SEO Settings panel in the Page Settings. Title, description and OG image fields are all built in. Webflow also has a dedicated Open Graph section where you set og:title, og:description and og:image per page. For custom tags not covered by the UI, use the Custom Code field in the page's head section.
Next.js and React. Use the <Head> component from next/head (Next.js) or react-helmet. Add meta tags as JSX inside the component. For Next.js App Router, export a metadata object from page.tsx. The Create Tags output above gives you the raw HTML. Convert each tag to JSX format (self-closing tags, className instead of class). For static sites built with Astro, add meta tags directly in the frontmatter layout component.
HTML sites (no framework). Open your HTML file. Find or create the <head> section between <html> and <body>. Paste the Create Tags output directly. Save and upload. This is the simplest case. No plugins, no build steps, no configuration files.
Every meta tag your page might need, what it does, and whether it is required or optional. Bookmark this reference.
Required. <title> (50 to 60 characters). The single most important tag. Controls your Google headline and what browsers show in the tab. Write it for the searcher, not for the brand.
Required. <meta name="description"> (140 to 160 characters). The snippet Google shows below your title. Include your target keyword naturally and give a reason to click. Not a ranking factor, but directly affects click-through rate.
Required. <link rel="canonical">. Points to the single official URL for this page. Self-referencing on every page. Prevents duplicate content issues from URL parameters, www vs non-www, and trailing slashes. Learn how it works in the canonical URL guide and use the canonical tag checker to verify yours.
Required. <meta name="viewport">. Always set to width=device-width, initial-scale=1. Without this, mobile browsers render the page at desktop width and scale down. Breaks mobile usability and harms mobile rankings.
Required. <meta charset="UTF-8">. Declares text encoding. Should be the first tag inside <head>. Prevents character display issues.
Strongly recommended. <meta property="og:title">, og:description, og:image, og:url, og:type. Controls how LinkedIn, Facebook and WhatsApp display your page when shared. The og:image should be 1200x630 pixels with an absolute URL. Use the OG tag previewer to test before publishing.
Strongly recommended. <meta name="twitter:card">, twitter:title, twitter:description, twitter:image. Controls X (Twitter) link previews. Set twitter:card to summary_large_image for full-width image cards.
Optional. <meta name="robots">. Only add when you need to override default behaviour. Default is index, follow. Use noindex for staging pages, admin areas, or thin content you do not want Google to index. Use nofollow on pages with many untrusted outbound links.
Optional. <meta name="author">. Names the page author. Useful for articles and blog posts. Strengthens E-E-A-T signals when combined with Person schema. AI systems use this to attribute content.
Optional. <meta property="og:site_name">. Appears as the site label above the title in some social previews. Should match your brand name exactly.
For structured data beyond meta tags, use the schema generator to add JSON-LD markup. Meta tags are the display layer. Technical SEO schema is the semantic layer. Both are part of the same Revenue Infrastructure that Groew builds for businesses and agencies.