Generate your tags and inspect preview behavior
Fill the fields below. The generator updates the meta tags, validation checks, and preview simulations instantly.
Input details
Tip: keep your most important tags high in the <head>. Social crawlers can miss them if the page is bloated or the metadata appears too late.
Every important Open Graph tag explained
Open Graph is the shared language many platforms use to build link previews. These are the tags that matter most in normal web pages and articles.
Twitter card tags explained in practical terms
These tags help shape how the page appears when shared in X/Twitter-style cards. Even when Open Graph exists, many sites still include explicit twitter:* tags for predictable rendering.
Tags that do not create the preview, but still matter
Social cards are not only about OG/Twitter tags. Clean supporting tags reduce ambiguity and make your page easier to index and share correctly.
<link rel="canonical">
Declares the preferred page URL. It should normally match
og:url on a simple article page.
Do not point canonical to a different URL unless that is intentionally the master page.
<meta name="description">
Not the same as og:description, but usually
similar. Search engines use this for snippets more often than
social platforms do.
JSON-LD structured data
Does not replace Open Graph, but adds machine-readable meaning for search engines and richer indexing workflows.
How to choose a social share image that actually works
A broken card is often an image problem, not a tag problem. Use a dedicated share image, not a random in-page image.
| Rule | What to do | Why it matters |
|---|---|---|
| Use absolute HTTPS URLs |
Example:
https://www.learnwithchampak.live/assets/social/share.jpg
|
Relative URLs and mixed-content setups can break crawler access. |
| Use a large, dedicated image | Prefer a true social image around 1200×630 | Small images often produce poor or missing cards. |
| Keep important text centered | Leave safe margins around the edges | Platforms may crop differently. |
| Do not protect the image | No login, no blocked robots path, no cookie requirement | Scrapers must fetch it anonymously. |
| Use stable hosting | Keep the image on your public domain or a reliable public CDN | Broken assets create broken previews. |
| Set width and height tags |
Add og:image:width and
og:image:height
|
Reduces guessing and helps parsers resolve the media faster. |
A practical sequence for fixing wrong previews
Follow this order. It catches the most common issues without random guesswork.
Step-by-step workflow
- Open the page source and confirm the final HTML contains the right tags in the <head>.
-
Confirm
og:urland canonical point to the real public page URL. - Open the image URL directly in a private browser tab and confirm it loads publicly.
- Check that the image is large enough and not a tiny logo or compressed thumbnail.
- Use the official platform tools to force a refresh where available.
- Wait for new shares only. Old posts usually keep the old preview.
- When in doubt, simplify: one canonical URL, one primary image, one clear title.
Useful tools
This page also has an internal preview simulator, which is useful before you publish or while refining the title, description, and image.
The failures that cause most broken link cards
These are the issues that repeatedly waste time in production.
Wrong URL identity
og:url points to the home page, an old slug, a
redirected page, or a different protocol.
Tiny image
The image is technically valid but too small, heavily cropped, or visually unreadable in social contexts.
Image not public
The image loads for you in session, but a crawler cannot fetch it anonymously.
Meta tags injected too late
Client-side rendering, SPA-only head injection, or bulky head content can confuse crawlers.
Old cache
The page is fixed, but the platform still shows the previous scrape result.
Too many conflicting tags
Multiple titles, inconsistent images, duplicate canonicals, or unrelated OG blocks create ambiguity.
Questions people usually ask while debugging
These answers focus on practical behavior rather than theory.
Do I need both Open Graph tags and Twitter tags?
For robust sharing behavior, yes. Open Graph covers many
consumers, while explicit twitter:* tags still
give you a cleaner, more controlled setup for X/Twitter-style
cards.
Should canonical and og:url be the same?
On a normal article or blog page, usually yes. Both should point to the same public URL that represents the page.
Why did I update the tags but the old preview still appears?
Cached metadata. Use the debugger or inspector where available, then test with a new share. Old posts may keep the old preview.
Can I use my site logo as og:image?
You can, but it is usually a poor choice. A dedicated 1200×630 visual with readable branding and context performs much better.
What is the safest default setup for a blog article?
Use: title, meta description, canonical,
og:title, og:type=article,
og:description, og:url,
og:image, og:image:width,
og:image:height, og:image:alt,
og:site_name, twitter:card,
twitter:title, twitter:description,
twitter:image, and JSON-LD.