// admin tools · 27
Meta tag & OG preview
Write or fetch title, description and Open Graph tags, see how the page looks in search results and social cards, and copy a clean <head> block.
// --edit runs locally · --fetch sends only the URL you enter to likeapro.dev, which downloads the page for you · preview images load directly from their URL
Sends only this URL to likeapro.dev/tools/fetch.php, which downloads the page server-side (first 512 KB, up to 8 redirects) and returns it. The HTML is parsed here with DOMParser — it is never rendered or run.
audit
tags found
| tag | value |
|---|
previews · approximations of each platform's layout; images load directly from the og:image URL
<head> tags
How it works
What it does
Before you ship a page, this shows roughly how its title, description and Open Graph tags will look as a search result and as a link card on Facebook, LinkedIn, X, Slack and Discord. It then gives you a tidy <head> block to paste in. The --fetch mode reads an existing page's tags, audits them and loads them into the previews.
How to use it
- In --edit, type a title and description. The counters show characters and an estimated pixel width.
- Add the canonical URL, site name and an absolute
og:imageURL. The tool loads the image to report its real size and ratio. - Open social overrides if your share title should differ from the search title, or to set the card type,
twitter:sitehandle and theme colour. - Copy the generated tags. Or switch to --fetch, enter a live URL, and work from what the page already has.
How the length estimates work
Google cuts snippets by rendered width, not character count. The tool measures your text on a canvas in Arial 20px for titles and 14px for descriptions, the fonts Google's desktop results have long used. It compares those widths with about 580 px for titles and 920 px (roughly two lines) for descriptions. These are approximations: Google changes its layout, may rewrite titles and snippets, and mobile wraps differently. Treat amber as "check it" and red as "likely cut".
What the audit checks
- Missing, duplicated or over-long
<title>and meta description. - Missing
og:title,og:descriptionorog:image, relativeog:image/og:url, and declared image dimensions under 600×315 or far from 1.91:1. - Missing, multiple or relative canonical links, and
og:urldisagreeing with the canonical. noindex/nofollowin meta robots or theX-Robots-Tagheader.- Missing viewport,
lang, favicon link ortwitter:card, hreflang withoutx-defaultor with relative URLs, and invalid JSON-LD.
Privacy
--edit runs entirely in your browser. --fetch sends only the URL you enter to this site's proxy (likeapro.dev/tools/fetch.php). The proxy downloads the first 512 KB and follows up to 8 redirects. The HTML is parsed with DOMParser, so scripts never run and nothing from the page is rendered. Preview images load straight from the image URL with no referrer, so that server sees your IP address, as it would if you opened the image.
FAQ
What size should my og:image be?
1200 × 630 px (1.91:1) is the safe default for Facebook, LinkedIn and X large cards. Keep text away from the edges, because some platforms crop. Use an absolute https URL.
Why does a platform still show my old image?
Platforms cache link previews. Use the platform's own sharing debugger to re-scrape the URL, or change the image URL (for example by adding a version query string).
Do I need separate twitter:title and twitter:description?
No. X falls back to the Open Graph tags, so twitter:card plus the og:* tags is enough. Add twitter:site if you want your handle attributed.
Why doesn't --fetch work when I open the file locally?
Browsers block cross-site page reads, so fetching needs the server-side proxy, which only exists on the live site. Everything else works offline.