lintpageincident.log
checksenvironmentstoolsblogfaq
sign inget started
~/blog/meta-tag-mistakes-seo
SEOMeta Tags

5 Meta Tag Mistakes That Silently Kill Your SEO

Marius Orzaru·January 20, 2026·6 min read·updated February 20, 2026

The invisible tags that control your traffic

Meta tags sit in the <head> of your HTML where no visitor ever sees them. But Google sees them on every crawl, and they directly influence whether your page shows up in search results - and what it looks like when it does.

Most developers get them "mostly right" and move on. The problem is that "mostly right" in meta tags often means "silently broken." Here are the five mistakes we see most often when scanning sites with LintPage.

1. Missing or duplicate title tags

The title tag is the single most important on-page SEO element. It's the blue link in search results. It's the text in the browser tab. And yet we regularly scan sites where pages share the same generic title - or have no title at all.

<!-- Bad: generic title on every page -->
<title>My App</title>

<!-- Good: unique, descriptive title -->
<title>Pricing Plans - My App | Start Free</title>

Every page needs a unique title of 50–60 characters, with the primary keyword near the beginning. If your title gets truncated in search results, the most important words should already be visible.

2. Meta descriptions that are too long, too short, or missing

Google doesn't use meta descriptions as a ranking signal, but they do control the snippet text below your title in search results. A compelling description directly impacts click-through rates.

The sweet spot is 150–160 characters. Too short and you waste valuable preview space. Too long and Google truncates it with an ellipsis - or ignores it entirely and generates its own.

<meta
  name="description"
  content="Check your site for SEO issues before launch.
  Catch NOINDEX tags, broken robots.txt, missing meta tags,
  and dozens of other problems in 30 seconds."
/>

Write descriptions that are action-oriented. Tell the searcher what they'll get by clicking. Skip the keyword stuffing - Google can tell.

3. The viewport tag that breaks mobile

If you're building a modern web app, you probably have a viewport meta tag. But we've seen sites with subtly broken configurations that cause layout issues on mobile without any visible errors in dev tools.

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

<!-- This blocks pinch-to-zoom (accessibility issue) -->
<meta
  name="viewport"
  content="width=device-width, initial-scale=1,
  maximum-scale=1, user-scalable=no"
/>

The user-scalable=no and maximum-scale=1 properties are accessibility violations. They prevent users from zooming in, which is a WCAG failure. Google's mobile-friendliness checks flag this.

4. Missing canonical URL

Canonical URLs tell search engines which version of a page is the "real" one. Without them, Google might index your page at multiple URLs - splitting your ranking signals across duplicates.

This is especially common with sites that have trailing slashes, query parameters, or www vs non-www versions:

<!-- Without canonical, all of these compete with each other -->
https://example.com/pricing https://example.com/pricing/
https://example.com/pricing?ref=nav https://www.example.com/pricing

<!-- Fix: add a canonical tag -->
<link
  rel="canonical"
  href="https://example.com/pricing"
/>

Set a canonical URL on every page. Your framework probably has a built-in way to do this - in Next.js, use the alternates.canonical metadata field.

5. Accidental noindex in production

This is the one that costs real traffic. A noindex robots meta tag tells Google to drop your page from the index entirely. It's common on staging environments and often makes it to production by accident.

<!-- This single line removes your page from Google -->
<meta
  name="robots"
  content="noindex, nofollow"
/>

We built LintPage specifically because this happened to us. A noindex tag shipped to production and went unnoticed for 47 days. By the time we caught it, our organic traffic had dropped to zero.

The fix is simple: check for noindex before every deploy. That's exactly what the LintPage Meta Tag Checker does - paste your URL, and it flags robots directives in seconds.

§ try this tool
Meta Tag Checker
Check your page title, meta description, viewport, charset, and robots tags.
try it free →

Don't wait for traffic to drop

These five mistakes are common because they're invisible. You can't spot a missing meta description by looking at your site. You need to actively check for them - either manually in the HTML source, or automatically with a tool.

Run your site through the Meta Tag Checker now. It takes 10 seconds and catches all five of these issues (plus more). If you want the full picture - all 60 SEO checks at once - sign up for a free LintPage account.

§ about the author
Marius OrzaruFounder, LintPage (BludeskSoft)

I built LintPage after a single stray noindex tag slipped into production and quietly cost us 47 days of organic traffic. It now runs the 60 automated checks I wish we had run before that deploy.

LinkedIn →

Get notified when we publish new posts.

§ run all 60 checks at once

Want the full picture? Stop checking one thing at a time.

Get a complete pre-launch SEO audit of your site with a single click.

run a full audit →
lintpage

Pre-launch SEO linting for developers. Catch disasters before they ship.

Product

  • Overview
  • Pre-launch checks
  • Full audit

Free tools

  • Meta tag checker
  • Robots.txt validator
  • AI crawler checker
  • OG preview
  • Sitemap validator
  • Heading checker
  • SSL checker
  • Redirect checker
  • Structured data validator
  • Broken link checker
  • Core Web Vitals checker
  • Security headers checker
  • Canonical tag checker
  • All tools →

Resources

  • Blog
  • About
  • RSS feed
  • Contact

Legal

  • Privacy
  • Terms
© 2026 lintpage. All rights reserved.built after one too many post-mortems.