Meta Tag Analyser

Why You Should Audit Your Meta Tags

Meta tags are invisible to visitors but control how search engines and social media platforms understand your pages. A missing og:image means no preview image on Facebook. A missing twitter:card means a plain text link on Twitter. A misconfigured robots tag can deindex your entire site. Broken meta tags silently cost you traffic every day, and most developers never check them after the initial deployment.

What This Tool Checks

The analyser fetches your page exactly the way social media crawlers do - as an anonymous HTTP request without JavaScript execution. It extracts every <meta> tag, the <title>, and <link rel="canonical">, then validates the essential tags that control search results and social sharing. This approach reveals what crawlers actually see, which may differ from what you see in a browser if your tags are injected by JavaScript.

The Complete Meta Tag Taxonomy

Meta tags are not a single standard - they are a collection of overlapping specifications from different organisations. Understanding which tags belong to which standard helps you decide what to implement.

For most websites, you need HTML standard tags + Open Graph + Twitter Cards. Dublin Core is only relevant for specific sectors. Schema.org is not technically a meta tag - it uses JSON-LD script blocks - but it serves a similar purpose of providing machine-readable metadata about your page.

Essential Tags for Every Page

Use our Open Graph Generator to create all of these tags in the correct format, ready to paste into your HTML.

The Robots Meta Tag

The robots meta tag is one of the most powerful - and dangerous - tags on your page. It controls what search engines can and cannot do with your content.

A common and catastrophic mistake: deploying a staging site to production with <meta name="robots" content="noindex"> still in the template. This single tag can deindex your entire site. Always verify the robots tag during deployment.

What Happens When Tags Conflict

When og:title and <title> contain different text, which one wins? It depends on the consumer. Search engines use <title> for rankings but may display the OG title in social features. Social platforms always prefer og:title over <title>. Twitter prefers twitter:title over og:title, which in turn wins over <title>.

This hierarchy means you can intentionally set different values. Your <title> can include your brand name for SEO (UUID Generator - RichDevTools), while og:title uses a shorter, punchier version for social sharing (UUID Generator). Check how each version looks with our Social Media Preview tool.

How Search Engines Use Meta Tags in 2026

The role of meta tags has shifted over the years. Here is what search engines actually use and what they ignore.

The most important takeaway: meta keywords is dead. If your site still has it, remove it. Google has not used it since 2009. Bing has confirmed it treats keyword stuffing as a potential spam indicator. The tag serves no purpose and adds unnecessary clutter to your HTML.

Structured Data vs Meta Tags

Meta tags and structured data (Schema.org JSON-LD) serve different purposes and are not interchangeable. Meta tags provide basic page-level information: title, description, image, indexing rules. Structured data describes the content semantically: this is a recipe with ingredients, an article with an author, a product with a price.

Google uses structured data to generate rich results - enhanced search listings with star ratings, FAQ accordions, recipe cards, and event details. These rich results significantly improve click-through rates. Meta tags do not trigger rich results. You need both: meta tags for baseline SEO and social sharing, structured data for enhanced search features.

Automating Meta Tag Checks in CI/CD

Manually checking meta tags on every deploy is unsustainable. For production sites, consider automating the audit in your deployment pipeline.

A minimal approach using a headless browser in your CI:

# Fetch and check key meta tags in CI
curl -s https://your-site.com | grep -E '(og:title|og:description|og:image|twitter:card)' | wc -l
# Expect at least 4 matches - fail the build if not

For more thorough validation, tools like Lighthouse CI include SEO audits that check meta tags, canonical URLs, and robots directives. Running Lighthouse in CI catches regressions before they reach production - like that staging noindex tag slipping through a merge.

Common Problems We Find

• Duplicate titles - every page uses the same og:title as the homepage. Each page needs unique, descriptive tags that reflect its specific content.
• Missing Twitter Card - Open Graph tags cover Facebook and LinkedIn, but Twitter needs twitter:card explicitly to show image previews.
• Relative image URLs - og:image must be an absolute URL starting with https://. Relative paths like /img/og.jpg are silently ignored by every platform.
• No canonical URL - without <link rel="canonical">, search engines may index duplicate versions of your page (www vs non-www, HTTP vs HTTPS, query parameter variations).
• Missing viewport tag - without <meta name="viewport">, Google's mobile-first indexing may penalise your page. This tag is required for proper mobile rendering.
• Stale cached previews - updating tags does not immediately update social previews. Each platform caches for different durations. Use platform-specific debug tools to force a refresh after deploying changes.

Run your site through this analyser after every significant deployment. The two minutes it takes to verify your meta tags can save you weeks of lost traffic from a broken preview or an accidental noindex directive.