What this preview checks
A Google result and a share card are built from a few tags in the page head. We read them as-is and rebuild the display:
- Title: presence, length in characters and estimated width in pixels (desktop and mobile), consistency with the h1.
- Meta description: presence, length, estimated truncation on desktop and mobile.
- Share card: og:title, og:description, og:image (HTTP answer, dimensions read from the file header, minimum and recommended size), og:site_name, og:url, twitter:card.
- Indexability: robots tag (noindex), canonical, lang attribute, number of h1.
This is not a screenshot: Google sometimes rewrites titles and picks its own snippets, networks crop images. The preview shows what your tags offer them.
SEOForge methodology v1 (September 2026)
The score is the weighted average of four elements scored out of 100. It ranks the fixes; it does not predict a ranking.
| Element | Weight | Why |
|---|---|---|
| Title | 30 | The link people click: the first driver of a good or bad click-through rate. |
| Meta description | 25 | The snippet that convinces or not, when Google uses it. |
| Share card | 30 | What your prospects see when a link is shared on LinkedIn, WhatsApp or Slack. |
| Indexability | 15 | A noindex or badly canonicalised page does not appear, whatever its title. |
How truncation is estimated
We measure text width with a character-width table of the Arial font (advance widths, in thousandths of an em): 20 px for the title, 14 px for the description. Limits used: title 600 px on desktop and 720 px on mobile (two lines), description 990 px on desktop and 1000 px on mobile. The character guides (60 and 160) are indicative. This is an approximation within a few percent; Google's real limits vary by device, language and query, and Google sometimes rewrites titles.
How the share image is checked
A single request to the og:image URL, limited to the first kilobytes: we check that it answers (HTTP status) and read its dimensions from the file header (PNG, JPEG, GIF, WebP). Below 200 px on a side it is flagged too small; 1200 × 630 px is the recommended size. The file is neither stored nor shown anywhere but in your preview.
What this preview does not do
- Predict the title Google shows: it may rewrite it from the h1, the page text or inbound links.
- Render the page in a browser: tags injected with JavaScript are not read (as with social network robots).
- Check rich results (stars, prices, FAQ): they depend on structured data, covered by the GEO test and the audit.
- Simulate each network: the share card is generic; LinkedIn, Facebook, X and WhatsApp each crop differently.
This preview vs on-page SEO
The preview shows what a page offers; on-page SEO decides what it should say, page by page, and writes it in your code.
| Free preview | On-page SEO | |
|---|---|---|
| Scope | One page at a time | Every page that matters, prioritised by traffic and intent |
| Titles and descriptions | Presence, length, truncation | Rewritten for search intent and the click, tested, no duplicates across pages |
| Sharing | Open Graph tags and image checked | Share images produced in the right format, tags per page template |
| Structure | h1, canonical, lang, noindex | Heading structure, structured data, internal links, fixes implemented |
Frequently asked questions
Is the preview exactly what Google shows?
No, and no tool can guarantee it. We rebuild the result from your tags with truncation estimated in pixels; Google adapts the display to device, language and query, sometimes picks another snippet from the page and rewrites some titles. The preview shows what you offer it, which is what you control.
How long should the title and description be?
The limits are widths in pixels, not character counts: a title in capitals or wide letters is cut earlier. Practical guides: 50 to 60 characters for the title, 120 to 160 for the description, the essential in the first words. The preview measures your text in pixels and shows where it would be cut.
Why does my share image not show when I share a link?
Frequent cases: no og:image tag, a relative or http URL, an image behind authentication or a firewall blocking the networks' robots, an image too small, or a network cache holding an old version. The preview checks the first four; for the cache, use each network's refresh tools.
Which dimensions for the Open Graph image?
1200 × 630 pixels (1.91:1 ratio) in JPEG or PNG suits LinkedIn, Facebook, X and most messaging apps. Below 200 pixels on a side, several networks show nothing or a thumbnail. A file under 1 MB loads faster.
What do you keep from a preview?
The URL entered and the final URL, the date, the score, the per-element scores and the codes of the points found, the duration and, for 30 days, a truncated, irreversible fingerprint of your IP address to detect abuse. Neither the page content nor the image is stored; the preview is rebuilt on demand for one hour (cache). This data is deleted after 24 months. If you request the report by e-mail, the preview is attached to your request.
Title and description are useless if the page is not read: also check its speed and its AI readability with the other tools.