Link rel attribute auditor: sponsored, ugc, nofollow
Audit the links in pasted HTML against Google's rel qualifiers: sponsored for paid links, ugc for user content and nofollow when neither applies.
Preview how a title, description and image will render as a Facebook or LinkedIn link card and as an X summary_large_image card.
Runs entirely in your browser. Nothing you enter is uploaded, logged or stored.
A shared link card is built from meta tags in the page head, not from anything visible in the
article itself. Facebook and LinkedIn read the og:title, og:description, og:image and
og:site_name properties defined by the Open Graph protocol. X uses its own twitter:card,
twitter:title, twitter:description and twitter:image tags, and falls back to the matching
og: tag for any one of those it does not find. A page that sets only og: tags still gets a
usable X card through that fallback; a page that sets conflicting og: and twitter: values will
show different text on each platform.
The Open Graph protocol specification at ogp.me defines og:title and og:description as plain
strings with no length constraint, and it does not document a recommended image ratio, only the
optional og:image:width and og:image:height fields for stating the image’s actual pixel
dimensions. The truncation a viewer sees comes from each platform’s own rendering, which none of
them documents precisely and all of them can change without notice. A tool that claims an exact
cutoff is presenting an inference as a fact; the counters here are labelled as a guide for that
reason.
Paste the tags as they will actually ship, including the real image URL, and check both card layouts before publishing. A card that reads well cropped to a wide image and a couple of lines of text will survive most platform rendering differences; a card that only works at full, untruncated length will not.
There isn't one. The Open Graph protocol at ogp.me does not define a character limit for either property. Platforms truncate in their own rendering, and none of them publishes the exact cutoff, so any specific number quoted elsewhere is an observed approximation, not a documented rule.
The protocol defines og:image:width and og:image:height as optional metadata describing the image you provide, not a requirement or a recommended ratio. In practice a landscape image works best, because large-image card layouts on every platform crop the image into a wide box rather than a square.
No. Facebook and LinkedIn read only the og: family of tags. X reads its own twitter: tags first, for example twitter:title and twitter:image, and falls back to the matching og: tag when a twitter: tag is missing.
Audit the links in pasted HTML against Google's rel qualifiers: sponsored for paid links, ugc for user content and nofollow when neither applies.
Preview a title and meta description as Google renders them, measured in pixels rather than characters, on desktop and mobile.
Score pasted text with the Flesch reading ease formula and estimate reading time, computed live in your browser from real, cited constants.
Compare titles or H1s across your own pages and flag near-duplicate pairs using Jaccard word-overlap similarity, entirely in your browser.
The Open Graph protocol does not mandate an image ratio; it only defines
og:image:widthandog:image:heightas optional metadata. A landscape image renders best, since every large-image card here crops to a wide box.