Why do I see no tags for a page that clearly has them?

We parse static HTML — we don't run JavaScript. Sites that inject meta tags client-side (some SPAs) won't show tags here, and they also won't show up to social crawlers, which is itself useful information.

What's the largest page you'll fetch?

Responses are capped at 1.5 MB. Meta tags live in the , which is almost always within the first ten kilobytes, so the cap rarely matters.

Do you store the URLs I inspect?

No. The URL is fetched, parsed, and the result returned. We don't keep request logs that include URLs.

Why is the og:image URL different from what I set?

We resolve relative paths against the final URL after redirects, so '/og.png' on https://example.com/blog/post becomes 'https://example.com/og.png'. That's the URL the social crawler will actually request.

Developer Tools

URL Meta & Open Graph Inspector

Fetch any URL and see its title, description, Open Graph image, Twitter card, canonical link, and full meta tag set.

Securely processed on our servers

Files are deleted automatically within 1 hour.

About URL Meta & Open Graph Inspector

URL Meta & Open Graph Inspector pulls a remote page over HTTPS and parses out everything search engines and social platforms read: the <title>, meta description, Open Graph tags (og:title, og:description, og:image, og:type, og:site_name), Twitter card tags, canonical link, favicon, and the manifest pointer. The og:image is rendered so you can see exactly what a Slack, iMessage, X, or LinkedIn unfurl will show. This is a server-side tool. Browsers block JavaScript from fetching arbitrary domains because of the same-origin policy, so a tiny serverless endpoint does the fetch for you. Nothing is logged or stored — the page is requested, parsed, and the result is returned. Common use cases: confirming a freshly-deployed page actually has the OG tags you wrote; debugging why a link unfurl shows the wrong image; checking a competitor's title/description format for SEO research; auditing a site after a CMS migration to make sure canonical links survived; verifying that a redirect chain ends where you expect it to. The fetch follows up to five redirects, caps the response body at 1.5 MB, and times out after ten seconds. Local and private IP addresses are blocked.

How URL Meta & Open Graph Inspector works

Paste any public URL (with or without https://).
The server fetches the page with a regular browser User-Agent and follows redirects.
The HTML is parsed for <title>, meta tags, and link tags — no headless browser, so JavaScript-rendered metadata won't appear.
Open Graph and Twitter card tags are grouped separately from the basic meta block.
The og:image URL is resolved against the final URL so the preview works for relative paths.

When to use URL Meta & Open Graph Inspector

Verify Open Graph tags ship correctly after a new deploy.
Debug why Slack/iMessage/Twitter shows the wrong preview image for your link.
Audit canonical link tags after a site migration.
Reverse-engineer a competitor's title/description format.
Check the redirect chain a marketing URL takes before landing.
Pull the meta description for an article you're about to share.

Why choose Utilix URL Meta & Open Graph Inspector

Renders the actual og:image so you see what social will show, not just the URL.
Resolves relative og:image paths against the final URL — most inspectors don't.
Shows the full redirect chain with status codes, not just the final destination.
Free, no signup, no rate limits beyond fair use.
We do not log inspected URLs.