All The Validators logoAll The Validators

web validator

Open Graph & Twitter Card SEO Validator

Validate rendered Open Graph and Twitter/X card tags for search-result snippets, social previews, share-card images, absolute URLs, and launch QA before publishing.

Results

Paste input and validate locally.
Status
Ready when you validate.
Details
Ready when you validate.
Missing tags
Ready when you validate.
Invalid URLs
Ready when you validate.

How to use this validator

  1. Copy the rendered head HTML or meta-tag block from your framework, CMS template, staging page, or production page source.
  2. Paste it into the validator and run the local check.
  3. Add missing title, description, image, URL, or card tags and ensure preview image URLs are absolute https:// URLs.
  4. Compare og:url with the canonical URL and make sure preview image URLs resolve on the production host.
  5. After the structural check passes, test the live URL with platform-specific debuggers or a real share to confirm image fetches, caching, crawler access, and crop behavior.

Rules & checks

Checks required Open Graph tags: og:title, og:description, og:image, and og:url for share-card completeness.

Checks required Twitter/X card tags: twitter:card, twitter:title, twitter:description, and twitter:image.

Validates og:url, og:image, and twitter:image as absolute, well-formed URLs so crawlers do not receive relative paths without page context.

Accepts meta tags using either property= or name= attributes, matching common static-site, CMS, and framework output.

Validates rendered markup rather than framework source because CMS plugins, Next.js metadata, and template overrides can change the final tags that crawlers see.

Does not fetch the page, render a preview, crawl redirects, refresh social caches, or verify image dimensions/content type.

Inputs explained

  • Rendered HTML head or social meta tags

    Paste the <head> section, rendered HTML, or the individual meta tags for the page you are about to publish. Include both Open Graph and Twitter/X tags when you want previews to work consistently across Facebook, LinkedIn, X, Slack, Discord, iMessage, and other unfurlers.

When to use it

  • QA blog posts, landing pages, product pages, and directory listings before launch.
  • Check static-site, Next.js, WordPress, Shopify, or headless CMS templates after metadata changes.
  • Debug why Discord, Slack, X, Facebook, LinkedIn, or iMessage previews are missing titles or images.
  • Audit generated pages at scale by validating representative rendered meta-tag snippets.
  • Confirm that staging or private launch pages do not need to be uploaded to a third-party preview checker for structural validation.
  • Catch mismatched social titles/images after CMS, Next.js metadata, canonical, or marketing-page updates.
  • Prepare public share cards before paid social, community launches, directory submissions, or partner announcements.

Common errors

  • Missing og:image, twitter:image, or og:url on otherwise valid pages.
  • Relative image paths such as /social-card.png instead of absolute https:// URLs.
  • Twitter/X tags omitted because the page only defines Open Graph tags.
  • Different title/description/image values between Open Graph and Twitter tags by accident.
  • og:url disagreeing with the canonical URL, sitemap URL, or preferred www/apex host.
  • Preview image URLs blocked by robots, auth, hotlink protection, redirects, or stale CDN cache even though the tag format is valid.
  • Pasting React/Next component source instead of rendered HTML meta tags.
  • Preview image URLs that are structurally valid but blocked, redirected, too small, too large, or cached by the social platform.

Limitations

  • Structural meta-tag check only; it does not fetch images, verify HTTP status, measure dimensions, inspect file type, or render social cards.
  • Does not decide whether the copy is compelling or whether the image crop is visually strong.
  • Does not simulate platform-specific precedence, caching, redirect handling, or crawler access restrictions.
  • A valid local snippet can still fail on a platform if the live page blocks crawlers or the image URL returns a bad status.
  • Does not judge whether the social image is visually compelling, cropped correctly, on-brand, or readable in small chat previews.

Tips

  • Use absolute https:// URLs for og:url, og:image, and twitter:image.
  • Keep social titles and descriptions concise enough to avoid awkward truncation in feeds and chat previews.
  • Use the same image for og:image and twitter:image unless you intentionally need platform-specific crops.
  • Pair this with canonical/hreflang, HTML meta, viewport, meta robots, JSON-LD, favicon, and manifest checks during launch QA.
  • If a live preview still looks stale after fixing tags, use the platform's debugger or cache refresh tool because social crawlers cache aggressively.

Examples

Complete large-image preview

  • <meta property="og:title" content="Launch Checklist" />
  • <meta property="og:description" content="A practical checklist for shipping a web page." />
  • <meta property="og:url" content="https://example.com/launch-checklist" />
  • <meta property="og:image" content="https://example.com/social/launch-checklist.jpg" />
  • <meta name="twitter:card" content="summary_large_image" />
  • <meta name="twitter:title" content="Launch Checklist" />
  • <meta name="twitter:description" content="A practical checklist for shipping a web page." />
  • <meta name="twitter:image" content="https://example.com/social/launch-checklist.jpg" />

Missing image tag

  • A page with og:title and og:description but no og:image is flagged because many platforms need an image to generate a rich card.

Relative preview image

  • og:image="/og-image.jpg" is flagged because social crawlers need an absolute URL such as https://example.com/og-image.jpg.

Deep dive

Open Graph and Twitter/X metadata are the public packaging layer for indexable pages: they decide how your title, description, canonical share URL, and image appear when people paste a link into feeds, chats, partner posts, and community launches.

Paste rendered HTML from a CMS, static site, or Next.js page to catch missing OG/Twitter card tags, relative image URLs, canonical/share URL drift, and stale template output before launch.

Use it after robots, sitemap.xml, meta robots, canonical/hreflang, HTML meta, and viewport checks, then follow with live platform debuggers to confirm crawlers can fetch the page and image assets.

The check is browser-local and format-focused, so private staging pages and unreleased metadata can be reviewed without sending snippets to a third-party preview service.

FAQs

Do you fetch my page or image?
No. This validator only inspects the HTML snippet you paste. It does not request the page, image URL, redirects, or social-preview cache.
Why do you require absolute image URLs?
Social crawlers usually need a full URL such as https://example.com/og-image.jpg. Relative paths like /og-image.jpg cannot be resolved without a page context.
Does this show exactly how the card will render on X, Slack, Discord, or Facebook?
No. It checks the required tags and URL structure. Each platform has its own crawler, cache, crop rules, and preview UI, so live testing is still useful after the structure passes.
Should og:url match my canonical URL?
Usually yes. Keep og:url aligned with the canonical URL, sitemap URL, and preferred www/apex host unless you intentionally need a different share URL.
Why did my live preview stay stale after fixing tags?
Many platforms cache previews. After the tags pass structurally, use each platform's debugger, cache refresh tool, or a fresh share test to confirm the new card is fetched.
Is my unpublished HTML stored?
No. Validation runs locally in your browser. The HTML snippet and preview URLs are not uploaded, logged, stored, or shared.

Related validators

web

Canonical & hreflang Validator

Validate canonical URLs, hreflang alternates, x-default fallbacks, absolute target URLs, and duplicate-content signals before search engines cluster or localize pages incorrectly.

web

HTML Meta SEO Validator

Validate rendered HTML document basics—charset, html lang, language targeting, and launch-readiness signals that support crawl, accessibility, and snippet QA.

web

Viewport Meta SEO Validator

Validate rendered viewport meta tags for mobile-friendly indexing, responsive rendering, Core Web Vitals QA, and accessible zoom behavior before launch.

web

Meta Robots / X-Robots-Tag SEO Validator

Validate page-level indexability signals across meta robots, X-Robots-Tag headers, canonical targets, snippet controls, and launch noindex cleanup.

web

JSON-LD SEO Validator & Rich Result Schema Checker

Validate rendered JSON-LD structured data for schema.org syntax, rich-result readiness, visible-content alignment, and crawlable schema blocks before publishing.

web

URL Validator & HTTP Link Parser

Validate HTTP and HTTPS URLs locally, parse host/path, and catch malformed links before publishing, importing, or sending them to APIs.

web

Favicon SEO Validator & Brand Icon Checker

Check favicon, apple-touch-icon, Safari mask-icon, and public brand icon declarations locally so browser tabs, bookmarks, mobile home screens, search snippets, and pinned tabs use the right assets.

web

Web App Manifest SEO Validator & PWA Install QA

Validate manifest.json locally for PWA installability, mobile install metadata, app names, start_url, display mode, theme colors, and icon entries before launch.

Open Graph and Twitter/X card validation runs entirely in your browser. Pasted HTML, staging URLs, draft titles, and unreleased social image URLs are not uploaded, fetched, logged, stored, or sent to a server.

This is a structural social-meta check. It does not fetch assets, render platform previews, refresh social caches, or guarantee that every crawler can access the live page.