To get a meta tag from Facebook, you either inspect the Open Graph and HTML head tags Facebook's crawler already reads on a shared URL, or you create the basic HTML head tags your own page needs so Facebook can render a clean link preview. Facebook's crawler reads the Open Graph vocabulary — og:title, og:description, og:image, og:url — that you place in your page head, and falls back to the ordinary element and when Open Graph values are missing or empty. A browser-side tool like the Meta Tag Generator produces the standards-aligned foundational block — UTF-8 charset, responsive viewport, title, description, and optional author — that complements Facebook-specific Open Graph markup rather than replacing it. Because the basic block omits canonical, robots, and social tags, the resulting head stays auditable and free of duplicate or contradictory declarations. Inspecting what is already there requires only a browser view-source and the Sharing Debugger, while building what should be there takes three small inputs and one copy operation.
What Meta Tags Facebook Actually Reads
When a Facebook user pastes a link into a post, Facebook's crawler fetches the page HTML and looks for two parallel vocabularies inside the document . The first is Open Graph, a property-based namespace originally designed for Facebook that begins with og:. The minimum Open Graph set Facebook documents include og:title, og:description, og:image, and og:url, plus an og:type that declares the content category such as website or article. The second vocabulary is the standard HTML metadata defined by WHATWG HTML semantics: the element and . If Open Graph tags are missing or empty, Facebook falls back to the HTML title and description, and then to other visible on-page text such as heading content. This dual-track behavior is the reason pages benefit from both a clean basic block and a dedicated Open Graph block.
Other tags sometimes appear in tutorials but are not the focus here. rel=canonical belongs to a separate indexing decision, robots directives govern crawl and index behavior, and Twitter Card markup is its own platform vocabulary. Mixing them all into a single block is exactly what makes a copied snippet unreliable, because a theme, plugin, or deployment platform may add a competing value for any one of them.
How to Inspect Meta Tags on a Shared Facebook URL
Before changing anything on your own page, it pays to see what Facebook currently reads from a target URL. There are two practical inspection paths that work without server access.
- Open the page in any modern browser and choose View Source (Ctrl+U on Windows/Linux, Cmd+Option+U on macOS). Read the contents of the block and note the element, the if present, and every og: property. The order matters less than the values.
- Paste the same URL into the Meta Sharing Debugger if you have access. The debugger shows the exact Open Graph values Facebook's crawler fetched at last crawl and reports warnings for missing properties and similar issues. It does not show the standard or description — only the Open Graph layer Facebook surfaces in feeds.
- Compare both views. If the debugger shows a different og:title than the page source, the deployed HTML has changed since Facebook last crawled it, and a fresh publish or explicit recrawl is needed before any new value will appear.
This inspection step is the practical answer to "getting" a meta tag from Facebook: it reveals the values the platform already has, separates them from values Facebook never sees, and tells you what to change on your own server next.
How to Build the Basic Meta Tags for Facebook Sharing
The basic head block a page needs for a clean Facebook fallback is small, and the Meta Tag Generator produces it from three inputs. The block stays narrow on purpose so it never collides with Open Graph, canonical, or robots values placed by other tooling.
- Enter one accurate document title in the Title field — the text a browser tab and a search-result title link would show. Keep it human-readable and avoid keyword stuffing.
- Enter a concise page description in the Description field — one or two sentences that summarize what a visitor actually receives. This is the same value Facebook's crawler falls back to when og:description is missing.
- Enter an optional author name only if the page maintains one meaningful value across the site. Skip the field when authorship metadata would be empty or misleading.
- Generate the block. The output is an escaped HTML head snippet containing a UTF-8 declaration, a fixed responsive , the element, the , and the optional .
- Copy the snippet into the of the page template, above any theme or framework metadata, and save. The generator performs all escaping locally, so ampersands, angle brackets, and attribute-delimiter quotes arrive correctly encoded.
- After deployment, re-open the page source, confirm only one and one description are present, and remove duplicates your CMS may have added. Then visit the page at mobile width and re-trigger the Sharing Debugger if a social preview matters for the change.
The character limits enforced by the tool — 200 for title, 500 for description, 120 for author — are bounds the copy operation enforces, not ranking targets. Pages that exceed them are rejected with a clear message rather than silently truncated.
Why Open Graph and Basic Tags Stay Separate
Keeping the basic block separate from Open Graph markup is a deliberate design choice rather than an oversight. Open Graph carries four required properties plus a type, and each expresses a Facebook-specific rendering decision: og:image must clear a minimum pixel size for a usable preview, og:url can differ from the canonical URL when tracking parameters belong in the share but not the index, and og:locale affects how Facebook composes certain UI strings. None of those decisions belong in the same form field as a basic .
For the Open Graph side, follow the Facebook Graph metadata guide and use a dedicated Open Graph generator so image dimensions, locale, and site-name values stay reviewable on their own. The basic block from Meta Tag Generator sits beneath that layer; together they form a complete head without contradiction.
| Tag | Vocabulary | Decision it carries |
|---|---|---|
| <title> | HTML standard | Document name; browser tab and search-result title link |
| <meta name="description"> | HTML standard | Short summary used as Facebook fallback and as a snippet input |
| <meta charset="utf-8"> | HTML standard | Character encoding for the document |
| <meta name="viewport"> | HTML standard | Layout viewport width; does not restrict zoom |
| og:title, og:description, og:image, og:url | Open Graph | Facebook-specific preview rendering |
| rel=canonical | Search engines | Preferred indexable URL; not a social tag |
Field Limits, Escaping, and What to Verify After Deployment
Every value the generator accepts is trimmed, length-bounded, checked for control characters, and HTML-escaped before output. Ampersands become &, angle brackets become < and >, and any quote that could terminate an attribute value is encoded. The UTF-8 declaration is emitted first inside the copied block; the responsive viewport follows. After pasting into a template, the order should be preserved so the encoding line is parsed before any textual metadata.
Two follow-up checks matter and cannot be done by the generator itself. First, inspect the delivered source — view-source after deployment — and confirm the page contains exactly one element and exactly one description metadata tag. Themes, SEO plugins, and framework defaults frequently inject duplicates; remove any duplicate. Second, view the page at a 360-pixel-wide mobile viewport and confirm the layout responds. The fixed viewport content is width=device-width, initial-scale=1 with no zoom restriction; if the page is unusable at mobile width, the issue is CSS, not the meta tag block.
The tool does not fetch the page, update a CMS, or change a deployment. Treat the copied block as the correct starting syntax, not a guarantee of any particular search snippet, Facebook preview, or indexing behavior. Per Google's title link guidance, search systems may rewrite a generated title based on the query, surrounding headings, and on-page links — a fact that applies to Facebook fallback behavior as well.
Common Pitfalls When Copying a Meta Tag Block for Facebook
A handful of recurring mistakes show up when teams copy meta tag snippets into production pages. Avoiding them is faster than debugging later, and each is something the basic block design avoids by construction.
- Duplicate title or description. Themes, SEO plugins, and deployment platforms commonly inject their own or values. The browser keeps the first valid one for display, but Facebook's crawler may keep the last. Audit the deployed source and delete duplicates.
- Twice-escaped characters. When a snippet is pasted through an editor that re-escapes ampersands or angle brackets, values render as literal text on the page. The generator's local escape step produces correct encoding once; let the editor leave it alone.
- Viewport with zoom restrictions. Adding maximum-scale=1 or user-scalable=no to a viewport tag can harm accessibility. The basic block omits those attributes on purpose, so the responsive baseline remains usable.
- Wrong encoding declaration. If the server response also sets a different charset, the browser applies one rule and the page may render with broken text. Confirm HTTP headers match the line.
- Mixing Facebook-only values into the basic block. og:image pixel minimums, og:url tracking parameters, and og:locale strings all belong in Open Graph markup. The basic block is deliberately too small to hold them, which keeps the audit clean.
For a deeper look, see How to Get Facebook Graph API Access for Shares.