Designer·Live· URL fetched on our server, never logged
OG Inspector
Paste any URL. See exactly how it appears when shared on Twitter / X, LinkedIn, Facebook, Slack, Discord, and iMessage — and get specific recommendations on what to fix.
Try:
Public URLs only · 50/day free
Frequently asked questions
What does the OG Inspector check?
It parses your page's `og:*` (Open Graph) tags, `twitter:*` (Twitter Card) tags, the standard `<title>` and `<meta name="description">`, the `<link rel="canonical">`, and any favicon link. Each missing or oversized field surfaces as a recommendation labeled Critical, Improve, or Suggested — with the exact fix to make.
Why does it matter to preview before publishing?
Click-through on social shares is dominated by the OG card — title, image, and description. A missing or wrongly-sized image gets you a blank thumbnail or a tiny summary card; oversized titles get truncated mid-word. Most posts only get one share at peak time, so a broken card on launch is wasted reach. Inspect before you publish.
Is this different from Twitter's old card validator?
Yes — Twitter retired `cards-dev.twitter.com` years ago. This tool covers Twitter / X plus LinkedIn, Facebook, Slack, Discord, and iMessage in a single pass. You don't need separate validators for each platform; we render all six previews from one fetch.
What size should an OG image be?
1200×630 pixels. That's the spec all major platforms (Twitter, Facebook, LinkedIn, Slack, Discord) target as the default. Smaller images get upscaled and look pixelated; larger ones get downscaled with no benefit. Declare the dimensions explicitly in `og:image:width` and `og:image:height` so platforms can pre-allocate the layout.
Does this work on private or internal sites?
No — for security, the inspector rejects localhost, 127.0.0.1, RFC1918 private ranges (10/8, 172.16/12, 192.168/16), link-local 169.254/16, IPv6 loopback / ULA / link-local, and `.local` / `.internal` hostnames. Inspect public URLs only. To test a local site, deploy to a preview URL (Vercel, Netlify, ngrok) first and inspect that.
Why did my fetch fail?
Common causes: the site is behind Cloudflare bot protection, requires JavaScript to render the page (we only see the HTML response), returns a non-200 status to non-browser user agents, or has a slow Time To First Byte that hits our 8-second timeout. Try the URL in an incognito window — if it works there, the site is gating bots.
Is the URL I submit logged?
No. The URL is fetched once on our server, parsed, and discarded. We don't store URLs, response bodies, or screenshots. Only an IP-based rate-limit counter is kept (50 inspections per IP per 24 hours), and that counter contains no information about which URLs you inspected.
Can I auto-generate a missing og:image?
Yes — Tinkr's free OG Image Generator at /og-image produces a 1200×630 PNG you can drop into a `<meta property="og:image">` tag. If the inspector finds no og:image, the snippet section links you to the generator so you can fill the gap in seconds.
What does the AI deep-dive add over the basic recommendations?
The basic recommendations check rule-of-thumb things — is og:image present, is the title under 70 chars, etc. The AI deep-dive adds a 0–100 share-quality score (broken down by title / description / image / completeness), 4–8 ranked critique points specific to YOUR meta tags, AI-rewritten title and description tuned for click-through, and a low/medium/high CTR prediction with reasoning. Free 10/day per IP. Built on Gemini 2.5 Flash.
Are there usage limits on the AI analysis?
Yes — 10 AI analyses per 24 hours per IP, separate from the 50/day basic-inspection limit so a runaway AI cost can't burn the inspector's free tier. Each analysis sends only your scraped meta tags (title, description, og:*, twitter:*, etc.) to Gemini — never the full page HTML. No signup, no credit card required.
Will the AI analyze the OG image itself?
Currently the AI analyzes the meta tags, declared image dimensions, and how the title / description / image work together — but it doesn't open and look at the og:image pixels. Vision-based image analysis ("is this image visually compelling?") is a planned upgrade. For now, the score reflects metadata quality and completeness, which empirically drives 80%+ of OG-card CTR.
Can I jump straight from the inspector to the OG image generator?
Yes — after the previews and the AI deep-dive, three CTA cards link straight into the OG Image Generator with this page's title and description prefilled. 'Customize an OG image' opens the template picker. 'Drop your image into Canvas' opens Canvas mode with your existing og:image as the background. 'Generate with AI' opens AI Custom mode with a prompt seeded from the inspected page. One click and you're designing — no retyping.