If you want to rank in Google, look professional on social, and avoid the five accidental ways a site can self-sabotage its SEO, you need a disciplined meta tag setup. This is the full checklist we use when auditing our own sites and clients — 15 items, each with why it matters, what good looks like, and a copy-paste example. Save it, print it, or use it as the spec for your next CMS template.

Prefer to automate all this? Paste any URL into checkmymeta.app and we'll run every check on this list in under three seconds.

Part 1: The Essentials (must-haves)

1. Title tag

The #1 on-page SEO signal. Every page needs a unique, descriptive title of 50-60 characters with the primary keyword in the first five words.

<title>How to Improve Page Speed in 2026 — Guide | Example.com</title>

2. Meta description

Controls your SERP snippet. Target 140-160 characters. Front-load the value prop; Google truncates around 120 chars on mobile.

<meta name="description" content="Learn how to make your site faster in 2026 with Core Web Vitals tactics, image optimization, caching, CDN setup, and a free audit tool." />

3. Canonical tag

Prevents duplicate-content penalties by telling Google which URL is authoritative. Non-negotiable if your site has query parameters, pagination, or any URL variations.

<link rel="canonical" href="https://example.com/page" />

4. Exactly one H1

Each page should have exactly one H1 that matches your title tag's intent (not identical wording — just the same topic). Multiple H1s confuse Google's topic extraction.

<h1>How to Improve Page Speed in 2026</h1>

5. Substantive body content (300+ words)

Google's quality signals heavily penalize thin content. Landing pages with less than 300 words of unique text rarely rank for competitive queries.

Part 2: Social & Sharing

6. Open Graph (Facebook, LinkedIn, iMessage, Slack)

Universal social previews. Six tags cover every major platform.

<meta property="og:title" content="How to Improve Page Speed in 2026" />
<meta property="og:description" content="Free guide to Core Web Vitals optimization." />
<meta property="og:image" content="https://example.com/og-image.png" />
<meta property="og:url" content="https://example.com/page" />
<meta property="og:type" content="website" />
<meta property="og:site_name" content="Example" />

og:image must be absolute, HTTPS, 1200×630, under 8MB. Full details in our Open Graph deep dive.

7. Twitter Card

Twitter falls back to og:* but prefers its own namespace. Almost every site should use summary_large_image.

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="How to Improve Page Speed in 2026" />
<meta name="twitter:description" content="Free guide to Core Web Vitals optimization." />
<meta name="twitter:image" content="https://example.com/og-image.png" />
<meta name="twitter:site" content="@yourbrand" />

Note the attribute: name= for twitter:*, but property= for og:*. Mixing them silently breaks previews.

Part 3: Technical Hygiene

8. Viewport meta

Without this, your site renders at 960px on mobile, zoomed way out, and fails Google's Mobile-Friendly test. Skipping this is one of the most common and most damaging SEO mistakes.

<meta name="viewport" content="width=device-width, initial-scale=1" />

9. Charset

Must be the first element in <head>. Declares text encoding before any content is parsed. Always UTF-8 in 2026.

<meta charset="UTF-8" />

10. html lang attribute

Required for accessibility (screen readers) and for Google to know what language to match queries against. Also mandatory for passing WCAG 2.2 audits.

<html lang="en">
<!-- or en-US, fr, de-CH, etc. -->

11. Robots meta

Most pages don't need this at all — the default is "index, follow". Only add it to exclude pages from search (staging URLs, login pages, thank-you pages).

<!-- Only if you want to hide the page from search engines -->
<meta name="robots" content="noindex, follow" />

Warning:a stray "noindex" from a CMS default or a staging config is one of the most common reasons traffic suddenly disappears. Always audit your robots meta on production pages.

12. Favicon + apple-touch-icon

Google started showing favicons in SERPs in 2019 and now shows them on both desktop and mobile. A missing favicon makes you look like an abandoned site. Provide at least a 48×48 PNG and a 180×180 PNG for iOS.

<link rel="icon" href="/favicon.ico" sizes="48x48" />
<link rel="icon" href="/favicon.svg" type="image/svg+xml" />
<link rel="apple-touch-icon" href="/apple-touch-icon.png" />
<link rel="manifest" href="/manifest.json" />

13. Structured data (JSON-LD)

The single biggest SERP upgrade most sites ignore. Schema.org JSON-LD unlocks rich results: star ratings, FAQ accordions, breadcrumbs, sitelinks. Lifts CTR by 20-35%.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Improve Page Speed in 2026",
  "author": { "@type": "Person", "name": "Jane Doe" },
  "datePublished": "2026-04-16",
  "image": "https://example.com/og-image.png"
}
</script>

The most useful types: Organization, WebSite, Article, Product, FAQPage, BreadcrumbList, Review.

14. hreflang (international sites only)

If you have English, French, and German versions of the same page, hreflang tells Google which URL to serve to which audience. Don't add this unless you actually have language variants — it can cause more harm than good when misconfigured.

<link rel="alternate" hreflang="en" href="https://example.com/page" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />
<link rel="alternate" hreflang="de" href="https://example.com/de/page" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page" />

Every page in the set must reference every other page — including itself. And every referenced URL must return a 200 status code. One missing back-reference breaks the entire hreflang cluster.

15. Image alt attributes

Every meaningful <img> needs an alt attribute. Google's image search ranks by alt text. Screen readers depend on it. Decorative images should have alt="" explicitly — never no alt attribute at all.

<!-- Meaningful image -->
<img src="page-speed-chart.png" alt="Line chart showing page speed improvement from 4s to 1.2s over six months" />

<!-- Decorative image -->
<img src="divider.svg" alt="" />

The audit process

Run through this on every important page once a quarter. On a large site, automate the first pass with a tool like checkmymeta.appand then manually verify the top 20 traffic drivers. The checklist takes about 5 minutes per page once you know what you're looking for.

Pay special attention to:

Staging leakage: any chance your staging environment is publicly indexed? Search site:staging.example.com in Google.
Accidental noindex: scan every production page's robots meta.
Duplicate titles: Google Search Console flags these. Fix every one.
Broken canonicals: self-referencing canonicals are fine; canonicals pointing to 404s or 301s destroy ranking.
og:image 404s: crawlers only fetch the image once and cache for days. A 404 on launch day is a long time to look broken.

The 30-second quick audit

Need to eyeball a page in half a minute? Open DevTools and check:

Is there a <title> and <meta name="description">? Are they under the right lengths?
Is there a <link rel="canonical"> pointing to the clean URL?
Is there an og:title, og:description, og:image, and og:url?
Is there exactly one <h1>?
Is the viewport meta present?
Is the robots meta absent (or at least not "noindex")?

If all six are yes, the page is 80% of the way there. The other 20% is structured data, Twitter Cards, and image alt attributes — which move the needle but rarely break anything.

Automate the whole checklist

checkmymeta.app runs every single item on this list — plus measures pixel widths, detects structured data types, and renders live previews. In under three seconds. Free.

Run the audit →

← Open Graph Tags Explained