Free tool, no account required

Free Meta Tag & Schema Checker

Check page title length, meta description, H1 heading structure, Open Graph social tags, and JSON-LD Schema.org structured data in real time.

Also known as: Meta tags checker, title and description, H1

Evidence shown with sourceNo account requiredNo invented metrics

Run a real check above

Submit a public URL, domain, or keyword. Novaverb will show only the evidence this tool can actually retrieve or measure.

Evidence model

Know what the result proves

This check proves what a page declares about itself: its title, meta description, heading hierarchy and the JSON-LD structured-data types present in the markup. It proves declaration, not display. Search engines rewrite titles and descriptions routinely, so a well-formed tag here is what you control, and the snippet a searcher sees is not.

1. Source

Live HTML response. The result identifies where its evidence came from.

2. Boundary

The checker reads the initial HTML response. Metadata or schema injected only after browser JavaScript runs may not appear.

3. Next action

Use the finding to verify a problem, then connect a workspace when you need history, monitoring, or site-wide analysis.

Meta tags explained

What a meta tag checker reads - and what it can't prove

This checker fetches a page's HTML and extracts the tags search engines and social platforms read: the title, meta description, headings, canonical, language, robots directive, Open Graph and Twitter/X cards, and any schema.org structured data. It reports what is present and how it is sized, but it does not guarantee a ranking or how Google will render your snippet.

How to read the numbers

Title & description: keep the title around 30–60 characters and the description around 70–158; both can be rewritten by Google to match the query.
Headings: use exactly one H1 that states the page topic; H2/H3 give it structure.
Canonical, robots, viewport: declare a canonical to avoid duplicate-URL confusion, keep the page indexable, and ship a mobile viewport.
Structured data: schema.org types unlock rich results and help AI answer engines understand the page.

Get the right answer

What to submit - and what to avoid

Submit one page address, not a domain, because metadata is a per-page property and the homepage's title says nothing about a product page's. Scheme, www, path and query are normalised. A page whose metadata is written by JavaScript after load may be reported as missing, which is what a non-rendering crawler also sees.

Use it like this

yourdomain.com/a-real-pageAny address form works - metadata is read from that exact page. http or https, with or without www, a bare domain or a full path - we normalize it for you.

https://www.yourdomain.com/blog/postA full URL with a path is ideal; we read that document's tags.

Avoid this

Expecting a site-wide audit from one URLWe read one page's tags; a full-site tag audit is a connected-workspace crawl, not this single fetch.

Public methodology

Exactly how this result is produced

The page is normalised and fetched, and the title, meta description and heading hierarchy are read from the returned HTML per the WHATWG standard. Length and presence are checked against common search-appearance guidance, which is treated as guidance and not a hard rule, and declared JSON-LD @type values are detected and listed.

We normalize and fetch the page, reading the title, meta description and heading hierarchy per the HTML standard.
We check length and presence against common search-appearance guidance (not a hard rule).
We detect declared JSON-LD structured-data @type values on the page.

Built on public standards

The international standards this check applies

The WHATWG HTML standard defines the elements this check reads and the heading outline it evaluates, and schema.org's JSON-LD vocabulary defines the structured-data types it detects. Length guidance is reported as guidance because no specification fixes a title length; the pixel width a search result allows is a rendering decision, not a rule.

WHATWGHTML

HTML Standard - document metadata

Reads the title, meta description and heading elements per the HTML standard.

Read the specification

schema.orgJSON-LD

Structured data vocabulary

Detects the structured-data @type values declared as JSON-LD.

Read the specification

We list a standard only where this tool genuinely reads or measures against it. Where a signal is outside a live check, the result says so instead of implying coverage.

Common questions

Meta Tag Checker FAQ

What does the Meta Tag Checker check?

It requests your page's live initial HTML and reports the title tag, meta description, H1 headings, the HTTP status code, and any JSON-LD structured-data schema types it detects in that response.

What is a meta description?

A meta description is an HTML tag summarizing a page's content. Search engines may show it as the snippet under your title in results, so a clear, relevant one can improve click-through even though it is not a direct ranking factor.

What is a good title tag length?

There is no universal character limit because result titles are constrained by rendered width and may be rewritten. Use the measured count as a review cue, keep the identifying words early, and judge clarity in context.

How do I fix a missing H1?

Add a single, descriptive H1 heading that states the page's main topic. The checker lists detected H1s, so if none appear or several compete, you can consolidate to one clear heading.

Why do title and meta description matter for SEO?

The title tag is a strong on-page relevance signal and the clickable headline in results; the meta description shapes the snippet. Together they influence whether searchers understand and click your listing.

What is JSON-LD structured data?

JSON-LD is a script format for embedding schema.org structured data in a page. It helps search engines understand entities like articles, products, or FAQs, and can enable rich results. The tool reports which schema types it detects.

Why does my schema not show in this checker?

It reads the initial HTML response only. If your title, description, or JSON-LD is injected after browser JavaScript runs, it may not appear here even though a full browser render would show it.

What's the difference between a title tag and an H1?

The title tag lives in the HTML head and appears in the browser tab and search results; the H1 is a visible on-page heading. They often align but serve different placements and audiences.

How many H1 tags should a page have?

One clear main heading is a useful editorial convention, but HTML permits multiple H1 elements. The checker reports what the initial HTML contains; whether the hierarchy is clear still requires review.

What HTTP status should my page return?

A 200 OK confirms the page is live and its metadata applies. Redirect or error statuses like 301 or 404 mean crawlers may not see the content you expect, so investigate those first.

More free checks