0 / 120 title 0 / 320 description
Previews
Twitter / X summary_large_image · 1200 x 600
example.com
A clear, specific title
LinkedIn / Facebook og:image · 1200 x 627
EXAMPLE.COM
A clear, specific title
One or two sentences. 50 to 160 characters reads best.
Discord embed card
example.com
A clear, specific title
One or two sentences.
Slack unfurl side-stripe card
example
A clear, specific title
One or two sentences.
Google search desktop SERP snippet
example.com › post
A clear, specific title
One or two sentences. 50 to 160 characters reads best.
Generated meta tags
Why this exists
Most social card previewers route your URL through a server, hit rate limits, sell you a paid tier, or bake their own watermark into the preview. SEO renders everything from your inputs in the browser and matches the way each platform actually composes the card. No upload, no fetch, no signup.
Frequently asked questions
- What is SEO for?
- When you ship a new page and want to know how it will look when shared on Twitter, LinkedIn, or Discord before you actually share it. Fill the fields or paste the head of your page, scan the previews, fix what looks wrong, copy the corrected meta tags, paste them back into your site.
- Why these specific platforms?
- Twitter / X and Facebook / LinkedIn all use Open Graph and Twitter Cards meta tags, and the previews here mirror what each platform renders today within a few pixels. Discord and Slack both unfurl Open Graph too. Google search uses different inputs (title, meta description, URL) but the same fields cover it.
- Do you fetch my URL?
- No. Nothing leaves your browser. If you want to preview a live page, view-source on that page, copy the head, paste it into the Parse tab. The tool reads only what you give it.
- What size should the OG image be?
- 1200 by 630 pixels is the safe modern default. Twitter / X uses summary_large_image at the same aspect. LinkedIn requires at least 1200 by 627. Discord crops to roughly 4:3 but is forgiving. Use 1200x630 unless you have a reason to differ.
- What is the difference between Compose and Parse?
- Compose lets you author meta tags from scratch by filling form fields. Parse lets you paste an HTML head block from a real page and pulls the meta tags out for you. Both feed the same set of previews.
- Does it track me or use cookies?
- No. No analytics, no third-party scripts, no telemetry. Your values stay in your browser, persisted to localStorage so they survive a page reload.