SEO Meta Tags Guide: Title, Description & Open Graph
A practical guide to HTML meta tags for search and social sharing — how titles, descriptions, canonical URLs, and Open Graph tags affect clicks.
Meta tags live in the `<head>` of your HTML. Search engines and social platforms read them to understand what a page is about and how to display it in results. Good meta tags do not guarantee rankings, but weak or missing tags often mean lost clicks.
Dev Utility includes free meta tag generators and checkers in the SEO tools category — useful when you launch a landing page or audit an existing site.
Essential tags
`<title>` — shown as the blue link in Google results. Keep it unique per page, under ~60 characters when possible, and include the primary topic.
`<meta name="description">` — the snippet below the title. Write a clear summary in 150–160 characters; it should match page content, not keyword-stuff.
`<link rel="canonical">` — tells search engines which URL is the authoritative version when duplicates exist. One canonical per page prevents dilution from query strings or alternate paths.
Open Graph and Twitter cards
Open Graph tags (`og:title`, `og:description`, `og:image`, `og:url`) control how links look on Facebook, LinkedIn, Slack, and many messengers. Twitter/X uses `twitter:card`, `twitter:title`, and related fields.
Always set `og:image` to a high-quality image (1200×630 px is a common recommendation). Without it, platforms pick a random crop from your page, which often looks unprofessional.
Common mistakes
Duplicate titles across every page. Missing descriptions (Google may rewrite snippets from body text). Canonical pointing to the wrong URL. Blocking indexing with `noindex` on production pages by accident.
Use Dev Utility robots.txt generator and XML sitemap generator alongside meta tools when setting up a new domain.
Quick audit checklist
View page source or use browser DevTools → Elements → head. Confirm one title, one description, one canonical. Test social previews with each platform’s debugger tool after deploy.