RevealTheme logo

Open Graph Inspector

Fetch any public URL and see the raw Open Graph and Twitter Card meta tags it exposes, plus a preview of its og:image.

How to use this tool

  1. 1

    Paste the full URL of the page you want to inspect, including https://, into the input field.

  2. 2

    Click Analyze. Our server fetches the page's HTML and parses its meta tags.

  3. 3

    Read the extracted Open Graph and Twitter Card values side by side, and check the rendered og:image preview below them.

  4. 4

    Adjust the tags in your site's HTML head, redeploy, then re-run the tool to confirm the changes are live.

What are Open Graph and Twitter Card tags?

Open Graph is a protocol Facebook introduced so that any web page can describe how it should look when shared. It uses <meta> tags in the document head with a property attribute such as og:title, og:description, og:image, og:url, and og:type. Twitter Card tags do the same job for Twitter/X using name attributes like twitter:card, twitter:title, and twitter:image. When someone pastes your link into a post or chat, the platform's crawler fetches the page, reads these tags, and builds the preview card — so the tags, not the visible page, decide how your link looks. This inspector requests the page from our server, downloads the raw HTML, and extracts every meta tag whose property starts with og: and every meta tag whose name starts with twitter:. It also pulls the title, meta description, and canonical link. Because it reads the HTML as delivered, without running JavaScript, tags your site injects client-side after load will not appear here — which is exactly how most social crawlers behave too. The og:image is rendered as a plain preview so you can confirm it loads, but the tool does not validate its dimensions or aspect ratio.

Common use cases

  • Debugging why a freshly published blog post shows a blank or wrong thumbnail when shared on LinkedIn or Facebook.

  • Confirming a CMS or framework actually emitted the og:image and og:description you configured before you announce a launch.

  • Checking that a single-page app renders its meta tags server-side, since tags added only by client JavaScript will be missing from the results.

  • Auditing a batch of marketing landing pages so each has a distinct title, description, and share image.

  • Verifying twitter:card is set to summary_large_image so a post displays a wide image rather than a small thumbnail.

  • Spotting when a redirect or stale cache is serving old meta tags after you changed them, since the tool shows the final fetched URL's HTML.

Frequently asked questions

Does this tool run in my browser or send data to a server?
It sends the URL to our server, which fetches the target page and parses it. The page content is not processed in your browser. We only request the URL you submit; we do not store the page.
Why are my Open Graph tags not showing up?
The tool only detects og: tags written as <meta property="og:...">. If your tags use a name attribute instead of property, or are added by JavaScript after the page loads, they will not appear here because the server reads the raw HTML without executing scripts.
What's the recommended OG image size?
1200x630 pixels (a 1.91:1 ratio) works across Facebook and LinkedIn. For Twitter/X summary_large_image cards, 1200x675 (16:9) is common. This tool previews whether og:image loads but does not check its dimensions, so verify the size separately.
Do I need both Open Graph and Twitter tags?
Not always. Twitter/X falls back to Open Graph tags when its own twitter: tags are missing, so og:title and og:image often suffice. Set twitter:card and the twitter: tags explicitly when you want different text or images on Twitter than elsewhere.
Can it inspect a page that needs login or is on my local network?
No. It can only reach publicly accessible pages. Private, loopback, and internal-network addresses are blocked for security, and redirects to such addresses are rejected, so pages behind a login or on localhost cannot be scanned.
Why does the preview differ from what Facebook or LinkedIn actually shows?
Each platform applies its own caching, image cropping, and fallback rules, and some re-scrape on a delay. This tool shows the tags as currently served; the real card may lag until the platform refreshes its cache, which you can often force with the platform's own sharing debugger.
Are there limits on the page it fetches?
Yes. The fetch times out after about 20 seconds, caps the download at 5 MB, tries HTTPS first then HTTP, and follows up to five redirects. Very large or very slow pages may fail to load.

Related tools