Skip to content
Live check · fetches your URL server-side

Website Metadata Checker

Render your page as Google, Twitter, LinkedIn and Slack see it — side by side.

Metadata is the layer of tags that tells search engines, social platforms, and browsers how to display your page. Most checkers list tags in a table. This website metadata checker fetches your page, extracts the title, meta description, Open Graph tags, Twitter card tags, JSON-LD schema, hreflang, canonical, viewport, and favicon, then renders preview cards showing exactly how the page appears in Google search results, Twitter/X, LinkedIn, and Slack-side by side.

Generate the whole content, not just check it.

BlazeHive writes SEO articles end to end from a single keyword. Outline, draft, meta, schema, internal links. Free trial, no card.

Start with BlazeHive Free trial

What a website metadata checker actually does

A metadata checker sends an HTTP request to your URL, parses the HTML <head> section, and extracts every relevant meta tag. It looks for <title>, <meta name="description">, <meta property="og:...">, <meta name="twitter:...">, <link rel="canonical">, <link rel="icon">, <link rel="alternate" hreflang="...">, <meta name="viewport">, and any <script type="application/ld+json"> blocks. It displays each tag with the attribute name and content value in a structured report.

Then it goes one step further. It renders a SERP preview card using the title and meta description as they would appear in Google search on desktop and mobile. It renders a Twitter card preview using the twitter:title, twitter:description, and twitter:image tags. It renders a LinkedIn preview using Open Graph tags. And it shows a Slack unfurl preview, which uses OG tags by default but falls back to page title if OG is missing.

Two problems are invisible until you see the preview. The first is truncation-titles longer than 60 characters or meta descriptions longer than 160 characters get cut off in Google. The second is missing images. A page might have a title and description but no og:image, so the Twitter card appears text-only and looks broken. Previews catch both instantly.

How to use this website metadata checker

  1. Paste the page URL into Page URL. Use the canonical version if you know it-https, www if applicable, no UTM parameters.
  2. Pick a User-agent from the dropdown if you want to see how metadata differs for mobile users or Googlebot. Desktop Chrome is the default. Mobile Chrome and Googlebot are useful for testing mobile-first indexing or JavaScript-rendered metadata.
  3. Paste a second URL into Compare with if you want to see your metadata next to a competitor's or check consistency across language versions of the same page.
  4. Hit Check metadata. You get a table of extracted tags, warnings for missing or invalid tags, and four rendered preview cards-Google SERP, Twitter/X, LinkedIn, and Slack.
  5. Expand the Warnings section if any rows are flagged. We report missing og:image, truncated titles, viewport misconfigurations, invalid schema, and hreflang errors.

Try checking a blog post URL. If the page has no Open Graph image, you see a Google preview with title and description, but the Twitter and LinkedIn previews show broken image placeholders. Add an og:image tag pointing to a 1200x630 PNG, re-check, and the previews update to show the hero image.

Why rendered previews matter more than raw tags

A tag can be technically present and still fail in practice. A title with 80 characters passes validation but gets truncated in Google at 60, so the last 20 characters are invisible to searchers. An og:image URL can return 404, making the tag useless even though it exists. A twitter:card set to summary_large_image requires a 2:1 aspect ratio image, but if the image is square, Twitter falls back to the small summary card.

Three practical consequences.

Click-through rate. Truncated titles and missing images hurt CTR in search and social. A polished preview with a clear title, benefit-driven description, and striking image gets more clicks than a plain-text snippet. Testing before publishing lets you fix layout before traffic is lost.

Brand consistency. If your homepage has perfect metadata but product pages have no OG image or fall back to the site logo, the user experience is inconsistent. Bulk-checking templates reveals which page types need fixes.

Platform differences. Google reads the title tag and meta description. Twitter reads twitter:title and twitter:description, or falls back to OG tags. LinkedIn reads OG tags only. Slack reads OG tags and sometimes the favicon. One missing tag can break the preview on one platform but not others. Seeing all four previews at once shows the gaps.

Open Graph vs Twitter Card vs schema.org

Open Graph tags were invented by Facebook and are now used by LinkedIn, Slack, Discord, and most social platforms. The core tags are og:title, og:description, og:image, og:url, and og:type. Setting these controls how links look when shared.

Twitter Card tags-twitter:card, twitter:title, twitter:description, twitter:image-override OG tags on Twitter/X. If both are present, Twitter reads the Twitter tags first. If only OG tags are present, Twitter uses them. Most sites set OG tags and skip Twitter tags because the fallback works. The exception is twitter:card, which should be set to summary_large_image if you want the big-image preview.

Schema.org structured data lives in JSON-LD scripts in the <head> or <body>. It tells Google what type of content the page contains-Article, Product, Recipe, Event, FAQ-and provides machine-readable fields like author, publish date, price, and rating. Google uses this for rich results like star ratings in search. Our checker validates JSON-LD syntax and reports the schema types found.

Hreflang, canonical, and viewport

Hreflang tags declare language and regional variants of a page. If you have English, Spanish, and French versions of /about, each should have <link rel="alternate" hreflang="es" href="..."> tags pointing to the others. Google uses these to serve the correct language in search results. Our checker lists every hreflang tag and flags common errors: missing return links, incorrect language codes, or hreflang pointing to a 404.

The canonical tag tells Google which URL is the original when duplicates exist. A metadata checker reports the canonical and whether it is self-referencing or points elsewhere. If you see a canonical pointing to a different domain or a 404, that is a red flag. Use our canonical checker for deeper canonical diagnostics.

The viewport meta tag-<meta name="viewport" content="width=device-width, initial-scale=1">-controls mobile rendering. If it is missing, mobile browsers render the page at desktop width and scale it down, making text tiny. Google penalizes pages without a viewport tag in mobile-first indexing. Our checker flags the absence or reports the content value if present.

Common mistakes

  • Setting OG title different from the HTML title. If <title> is 70 characters and og:title is 40, your Google snippet and social-share card have different copy. This confuses users. Keep them aligned unless you have a strong reason to differ.
  • Using a square image for og:image. Twitter and LinkedIn expect 1200x630 or a 1.91:1 ratio. A square image gets cropped or letterboxed. Use the same aspect ratio everywhere.
  • Forgetting og:url. This tag tells platforms the canonical URL to associate with the share. Without it, URL parameters like ?ref=twitter might become the shared URL, creating duplicate engagement across variants.
  • No alt text on the OG image. Platforms do not display alt text for OG images, but screen readers and accessibility tools rely on it. If you use an img tag in your markup for the same image, set alt text there.
  • Setting twitter:card to summary when you want the large image. The default is a small square thumbnail. Change it to summary_large_image to get the hero layout.
  • Deploying with test metadata. "Test post title" or "Lorem ipsum" in production happens more often than you think. A quick check before publishing catches this.

Advanced tips

  • Use the Compare with field to diff your metadata against a competitor's top-ranking page. If their title is shorter, their description more specific, and they have schema while you do not, you know what to fix.
  • Test the same URL with Desktop Chrome and Googlebot as user-agents. If metadata differs, your page is cloaking or serving different content to bots, which violates Google's guidelines.
  • Check one page per template: homepage, product, category, blog post, landing page. Metadata errors are usually template-level, not page-level, so fixing one fixes hundreds.
  • Look at the schema section. If you have multiple JSON-LD blocks, make sure they are valid and do not conflict. Two conflicting @type declarations can cause Google to ignore both.
  • Test hreflang on multi-language sites. A missing return link-where the Spanish page points to the English page but the English page does not point back-breaks hreflang entirely.
  • Download the report as JSON and diff it against a previous check. Use it in CI to catch metadata regressions when deploying a new theme or page builder.

After checking metadata, if warnings mention missing canonicals or hreflang mismatches, run the canonical checker to bulk-test URL variants. If schema warnings appear, re-validate with Google's Rich Results Test. To see how Googlebot actually renders the page-JavaScript execution, blocked resources, visible text-the google crawler simulator shows the raw and JS-rendered HTML side by side. For a broader on-page SEO audit that includes metadata, title length, H1, and internal links, use the SEO checklist.

Generate the whole content, not just check it.

BlazeHive writes SEO articles end to end from a single keyword. Outline, draft, meta, schema, internal links. Free trial, no card.

Start with BlazeHive Free trial

Frequently Asked Questions

What is website metadata?

Website metadata is structured information embedded in a page's HTML that describes the content, authorship, and presentation to search engines, social platforms, and browsers. It lives in the head section and includes title tags, meta descriptions, Open Graph tags (for Facebook, LinkedIn), Twitter Card tags (for X), canonical tags, robots meta directives, viewport settings, schema.org structured data, and hreflang declarations. Metadata is invisible to users but shapes how your content appears in search results, social shares, and link previews. The title tag becomes the blue clickable headline in Google's SERP, the meta description becomes the snippet text below it, and OG tags control the image, title, and description when someone shares your page. Good metadata is concise, accurate, keyword-aware, and platform-specific. Poor metadata (missing, duplicated, over-length, or generic) reduces click-through rate and confuses search engines. Our tool fetches your Page URL, parses the HTML, extracts every metadata element, and generates preview cards showing how your page renders in Google, X, LinkedIn, and Slack.

How do I check the metadata of a website?

Right-click any page and select View Page Source (or press Ctrl+U on Windows, Cmd+Option+U on Mac), then search for <meta in the HTML. You'll see a list of meta tags covering description, robots, Open Graph, Twitter Card, and other properties. This method works but is slow. Easier: paste the Page URL into our tool, and we fetch the page, extract all metadata, validate format and length, and render preview cards for Google SERP, X, LinkedIn, and Slack so you see exactly how your page looks when shared or indexed. We flag common issues: missing meta description, title over 60 characters, missing OG image or incorrect dimensions, missing Twitter Card tags, conflicting canonical declarations, or missing mobile viewport tag. If you want to compare your metadata to a competitor, enter their URL in Compare with. For bulk checks, use Screaming Frog or Sitebulk to export metadata for your entire site. For single-page validation, our tool is faster and shows visual previews.

What are five examples of metadata?

Title tag: the clickable headline in search results and the browser tab label, 50 to 60 characters, includes primary keyword. Meta description: the snippet text below the title in search results, 145 to 160 characters, summarizes the page and entices clicks. Open Graph title and description: control how the page appears when shared on Facebook, LinkedIn, or Slack, often identical to the SEO title and meta description. OG image: the thumbnail image displayed in social previews, ideally 1200x630 pixels, must be an absolute URL. Canonical tag: tells search engines the preferred URL when duplicates exist. Robots meta: controls indexing with values like index, follow or noindex, nofollow, overrides site-wide robots.txt. Viewport meta: ensures mobile-friendly rendering with width=device-width, initial-scale=1, required for responsive design. These seven elements are the minimum every page needs. Add schema.org structured data for rich results, Twitter Card tags if X traffic matters, and hreflang tags if you serve multiple languages. Our tool checks all of these.

What is an example of website metadata?

Here's a complete metadata block from a blog post about keyword research. Title tag: <title>Free Keyword Research Tool | 50 Keywords with Volume</title> (59 characters, includes primary keyword, fits Google's display). Meta description: <meta name="description" content="Free keyword research tool. Enter a seed keyword, get 50 related terms with search volume, CPC, difficulty, and intent, auto-clustered into content pillars."> (158 characters, includes CTA and value prop). Open Graph title: <meta property="og:title" content="Free Keyword Research Tool | 50 Keywords with Volume">. OG description: <meta property="og:description" content="Free keyword research tool. Enter a seed keyword, get 50 related terms with search volume, CPC, difficulty, and intent.">. OG image: <meta property="og:image" content="https://example.com/images/keyword-tool-preview.jpg"> (1200x630 pixels). Canonical: <link rel="canonical" href="https://example.com/tools/keyword-research"> (self-referencing). Viewport: <meta name="viewport" content="width=device-width, initial-scale=1">. This block ensures Google indexes the page correctly, social shares show the right image and text, and mobile users get a responsive layout. Use our tool to verify all metadata is present before you publish.

Can incorrect meta tags hurt my SEO?

Yes, incorrect meta tags can hurt click-through rate, indexing, and rankings. A title tag over 60 characters gets truncated in Google's SERP, cutting off your keyword or CTA and reducing clicks. A missing or generic meta description costs clicks because searchers pick the result that best answers their query. A meta robots tag with noindex accidentally left on a published page tells Google not to index it, removing the page from search results entirely. A missing canonical tag on pages with duplicate content splits ranking authority across multiple URLs, causing all of them to underperform. A missing viewport tag makes your site unusable on mobile, which hurts rankings because Google uses mobile-first indexing. Keyword stuffing in the meta description looks spammy and may hurt CTR. Mismatched Open Graph tags reduce social shares and referral traffic. Our tool flags all of these issues: paste your Page URL, and we check title length, description presence, canonical correctness, robots meta directives, viewport tag, and OG tag completeness.

How do I see the metadata of a website?

View the page source by right-clicking anywhere on the page and selecting View Page Source, then search for <meta using Ctrl+F or Cmd+F. You'll see a list of all meta tags in the head section, including title, description, Open Graph, Twitter Card, robots, and viewport tags. You can also open browser DevTools (F12 or Cmd+Option+I), click the Elements tab, expand the <head> tag, and browse the meta tags interactively. For a faster and more visual method, paste the Page URL into our tool, and we extract all metadata, validate it, and show preview cards for how the page renders in Google search results, X, LinkedIn, and Slack. This is faster than manual inspection and catches errors like truncated titles, missing OG images, or incorrect canonical tags. If you want to check metadata for multiple pages, use a crawler like Screaming Frog or Ahrefs Site Audit. For single-page validation or pre-publish checks, our tool is the fastest option and shows real previews.

What is the difference between Open Graph and Twitter Card tags?

Open Graph (OG) tags control how your page renders when shared on Facebook, LinkedIn, Slack, and most other platforms. Twitter Card tags control how your page renders on X (formerly Twitter). Both serve the same purpose (provide a title, description, and image for link previews) but use different tag names. OG tags use property attributes: <meta property="og:title" content="...">, <meta property="og:description" content="...">, <meta property="og:image" content="...">. Twitter Card tags use name attributes: <meta name="twitter:card" content="summary_large_image">, <meta name="twitter:title" content="...">, <meta name="twitter:description" content="...">, <meta name="twitter:image" content="...">. X falls back to OG tags if Twitter Card tags are missing, so at minimum you need OG tags on every page. Add Twitter Card tags only if you want X-specific customization. The summary_large_image card shows a large image above the title and description. The summary card shows a small thumbnail. Most sites use OG tags site-wide and add Twitter Card tags on high-traffic pages. Our tool checks for both and flags missing or incomplete tags.

What is JSON-LD schema and why does it matter?

JSON-LD (JavaScript Object Notation for Linked Data) is a schema.org structured data format you embed in a script tag to tell search engines what entities exist on your page. It sits in the head or body as a <script type="application/ld+json"> block and describes things like articles (headline, author, publish date), products (name, price, availability), FAQs, how-to guides, reviews, events, and organizations. Search engines parse this structured data and use it to generate rich results: enhanced SERP snippets with images, star ratings, event dates, or FAQ dropdowns that earn higher click-through rates. An article with Article schema is eligible for Google's Top Stories carousel. A product with Product schema shows price and review stars inline. An FAQ page with FAQPage schema renders as expandable questions in the SERP. Adding schema does not guarantee rich results, but pages without schema are never eligible. JSON-LD is easier to implement than inline Microdata or RDFa. Our checker validates JSON-LD presence, type correctness, and required fields.

Why is my page showing a different title in Google than my title tag?

Google rewrites title tags when the original does not match the query, is too generic, keyword-stuffed, or poorly formatted. Common triggers: title is over 60 characters and gets truncated. Title is stuffed with keywords, so Google replaces it with the H1 or a cleaner version. Title is generic ("Home") or missing, so Google pulls text from the page content. Title does not match the query, so Google generates a new one using the page's H1, first paragraph, or anchor text from links. To fix this, write a clear, concise title under 60 characters that includes your primary keyword near the start and matches the H1. Avoid keyword stuffing, filler words, or brand repetition. Ensure the title reflects what the page is about. After updating, request re-indexing via Google Search Console. If Google still rewrites it, revise the title to better align with the content. Our tool shows your current title tag, flags if it is over 60 characters, and generates a preview of how it renders in Google's SERP.

What are commonly misused meta tags?

The keywords meta tag is the most misused because it has no effect on rankings (Google has ignored it since 2009), yet sites still stuff it with hundreds of keywords. Delete it, as it signals outdated SEO knowledge. Duplicate title tags (same title on every page) waste the most valuable on-page SEO signal by failing to differentiate pages. Write unique titles for every page. Empty meta descriptions force Google to generate snippets from page content, which often reads poorly and reduces CTR. Write custom descriptions for high-traffic pages. Over-length titles (70+ characters) get truncated in search results, cutting off the keyword or CTA. Keep titles under 60 characters. Keyword-stuffed descriptions look spammy and hurt CTR. Write for humans, not bots. Robots meta tags with noindex left on published pages deindex the page entirely. Always verify robots meta is set to index, follow before launch. Missing canonical tags split authority across duplicate URLs. Add self-referencing canonicals to every page. Our tool flags all of these issues automatically.

Related free tools

All tools →