Softonic

Metadata Extractor

Step 1 / 2
Extract

Enter a URL and the extractor fetches the page, parses the <head>, and lays out everything that matters for how your link appears elsewhere: the SEO title and meta description, the canonical URL, Open Graph tags Facebook and LinkedIn use for link previews, Twitter Card tags, favicon and app icons, JSON-LD structured data (Schema.org, Article, Product, FAQ). Useful for SEO audits, link-preview debugging and checking what a freshly-published page actually exposes to crawlers.

How metadata is extracted

  1. 1

    Enter the URL

    Full URL including protocol. The tool follows one redirect hop.

  2. 2

    The page is fetched server-side

    The raw HTML is parsed; JavaScript-rendered pages may not expose client-side metadata.

  3. 3

    Sections grouped by standard

    SEO, Open Graph, Twitter, Schema.org, icons, mobile, PWA.

  4. 4

    Each entry shows value and length

    Titles and descriptions get length warnings if they exceed Google or Twitter limits.

  5. 5

    Preview the link card

    Renders a mock Facebook / LinkedIn / Twitter share card from the extracted tags.

What’s in the <head> that matters

Core SEO

Tag Purpose
<title> Browser tab, Google result title
<meta name="description"> Google result snippet, social fallback
<link rel="canonical"> Canonical URL, duplicate-content signal
<meta name="robots"> index/noindex, follow/nofollow rules
<meta name="viewport"> Mobile viewport

Open Graph (Facebook, LinkedIn, Discord, Slack)

Tag Purpose
og:title Share-card title
og:description Share-card description
og:image Share-card image (1200×630 recommended)
og:type website / article / video.other
og:url Canonical URL for the share
og:site_name Site name shown in card

Twitter Card

Tag Purpose
twitter:card summary / summary_large_image
twitter:title Falls back to og:title
twitter:description Falls back to og:description
twitter:image Large-image card
twitter:site / twitter:creator Publisher / author handles

Schema.org (JSON-LD)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "...",
  "author": { "@type": "Person", "name": "..." },
  "datePublished": "2026-04-18"
}
</script>

Article, Product, Recipe, FAQ, Event, Organization, Breadcrumb are the most impactful for search rich results.

Red flags in an audit

  • Missing og:image. Your links look naked when shared to Slack or Discord.
  • Title over 60 characters. Truncated in Google search results.
  • Description over 160 characters. Truncated in Google’s snippet.
  • No canonical tag. Risk of duplicate-content ranking confusion between /page and /page/.
  • Both og:image and twitter:image missing. No social preview card renders.
  • noindex on a page that should rank. Happens all the time on staging servers that went live without removing the tag.

Debug workflow

  1. Extract on the staging URL first.
  2. Cross-check the live URL after deploy.
  3. Clear Facebook’s scraper cache (Sharing Debugger) and Twitter’s card validator after a change, they cache aggressively.
  4. Test in an incognito window in case a logged-in cookie reveals different content.

Frequently Asked Questions

Partially. The extractor fetches the server-rendered HTML. If your meta tags are injected by client-side JavaScript (SPA frameworks without SSR), they won’t appear, which is also how Google sees the page without JavaScript execution on first crawl.

Common causes: the URL is behind a login, the image is too small (< 200×200), or Facebook cached an older version. Clear the cache in the Sharing Debugger and retry.

It helps for specific content types (Article, Product, Recipe, FAQ, Breadcrumb) because Google uses it for rich results. Generic marketing pages don’t need it. Add schema when the content type has an associated rich-result format.

<link rel="canonical"> tells search engines which version of a page to index. og:url tells social platforms what URL the share represents. They’re usually identical, but not required to be.

Through a server-side fetcher, your browser can’t fetch arbitrary external URLs due to CORS restrictions. The fetcher uses a generic user-agent and does not authenticate.

Related Tools

Meta Description Length Checker

Measure a meta description in characters and estimated pixels, compare editorial ranges, and inspect illustrative desktop and mobile previews.

Canonical Tag Generator

Generate a valid rel=canonical link tag for any URL. Includes URL validation and the common mistakes to avoid.

Google SERP Simulator

Preview an approximate Google-style search snippet with character limits for mobile and desktop. Your draft stays in this browser session.

HTTP Security Headers Checker

Paste HTTP response headers and review HSTS, CSP, clickjacking, MIME, referrer and cross-origin policies locally in your browser.

XML Sitemap Validator

Check sitemap XML in your browser for parse errors, missing locations, duplicate URLs, and common sitemap field values.

Broken Link Checker

Paste a page URL and check its outbound links for 404s and other HTTP errors, with the status code for each link.

Tool available in other languages