---
title: "Meta Tag Checker & Twitter Card Validator"
description: "Free meta tag checker and Twitter card validator: title, description, canonical, robots, hreflang, Open Graph, X cards and JSON-LD, checked against Google, ogp.me and X rules."
canonical: "https://browser-use.com/tools/meta-tag-checker"
last_updated: "2026-11-04"
---

# Meta Tag Checker & Twitter Card Validator

## Free Meta Tag Checker

Check a page's meta tags against Google, Open Graph and X rules. Each tag gets pass, warn, fail or info, plus one answer: can Google index it?

## How it works

### Enter a URL or paste HTML

We read the page's original HTML, its response headers and its robots.txt. Pasted HTML is checked in this tab.

### Read the verdicts

Each tag gets pass, warn, fail or info, the reason, and a link to the rule where there is one.

### Copy the report

Copy or download it as JSON for CI or an agent, or try a new title and image in Social Preview.

### Is there a length limit for titles and descriptions?

No. Google says there is no limit on either; both are truncated as needed to fit the device width. This tool counts characters but never fails a page on length.

Source: [Google: title links](https://developers.google.com/search/docs/appearance/title-link) · [Google: snippets](https://developers.google.com/search/docs/appearance/snippet)

### How do I validate a Twitter card now?

X's card validator (cards-dev.x.com/validator) now redirects to a login page. This tool checks the markup against X's archived card docs (removed from docs.x.com): card type, title up to 70 characters, description up to 200, no SVG image, image under 5MB when its host lets your browser see the size, and the Open Graph fallbacks. It can't show how X caches or renders the card.

Source: [X card markup (archived Jan 2026)](https://web.archive.org/web/20260116124848/https://developer.x.com/en/docs/x-for-websites/cards/overview/markup)

### When can't Google index a page?

When it returns a 4xx status, or a robots meta tag or X-Robots-Tag header says noindex or none. If robots.txt blocks Googlebot, Google can't read those tags at all. When rules conflict, the more restrictive one applies.

Source: [Google: HTTP status codes](https://developers.google.com/search/docs/crawling-indexing/http-network-errors) · [Google: robots meta tag](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag)

### What does it fetch?

For a URL, our server reads the page's original HTML (up to 5 redirects, the first 1 MiB) and its /robots.txt, as BrowserUseTools/1.0. It runs no JavaScript, fetches no images and stores nothing; images load in your browser from their host. Pasted HTML stays in this tab. If a site refuses our fetcher (401, 403, 429, 5xx or a bot challenge), the report says so and checks no tags. A site that serves Googlebot different HTML is not detected.

## Need the page after JavaScript runs?

Browser Use agents open pages in a real browser, including dynamic ones, and return structured data.

[See AI web scraping](https://browser-use.com/web-scraping)

InputWebsite URLPasted HTML

Website URL

Check meta tagsLoad example

---

BROWSER USE

- Browser Use Agents: give Browser Use a task and receive completed work. API V4 is current for new integrations.
- Browser Infrastructure: connect your agent or automation to managed browsers through SDK, REST, or CDP. Starts at $0.02/browser-hour.
- Developer tools: Open Source, Browser Harness, SDK, and MCP support the two products above.

[Developer Index](https://browser-use.com/index.md)
[Product Map](https://browser-use.com/llms.txt)
[Full Product Context](https://browser-use.com/llms-full.txt)
[Pricing](https://browser-use.com/pricing.md)
[Cloud Docs](https://docs.browser-use.com/cloud/quickstart)
[Open Source Docs](https://docs.browser-use.com/open-source/introduction)