How this check works
Scanaris looks in your page's <head> for three Open Graph tags: og:title, og:description and og:image. If all three are there with content, there is nothing to say. If any is missing, it opens an informational finding naming which; if all three are missing, the finding simply says the page has no Open Graph. It is informational, so it costs no points: it is not a security or indexing flaw, it is a missed opportunity every time someone shares your site.
Why it matters
When someone pastes your link into WhatsApp, X, LinkedIn, Slack, Discord, iMessage or Telegram, the app visits the URL, reads these tags and builds the preview card: large image, title and description. Without them, the card shows no image, the raw URL or a random chunk of text from the page. The difference in clicks between a link with a card and one without is large, especially on mobile, where the card fills the screen. And the image you choose is, for many people, the first impression of your brand.
How to fix it
<meta property="og:title" content="Security scanner for AI-built apps">
<meta property="og:description" content="Scan your site in 60 seconds and get every flaw with its fix.">
<meta property="og:image" content="https://yourdomain.com/og/home.png">
<meta property="og:url" content="https://yourdomain.com/">
<meta property="og:type" content="website">
<meta name="twitter:card" content="summary_large_image">
- The image goes as an absolute HTTPS URL, 1200 by 630 pixels, in JPG or PNG and under 1 MB so every platform accepts it. A brand background, the page title in large type and the logo is the formula that works.
- One per page, not the same everywhere. An article with its headline in the image gets shared more than one with the site's generic image. Nuxt has a module that generates these images from a template; Next.js does it with an
opengraph-image.tsxfile in each route. - Nuxt:
useSeoMeta({ ogTitle, ogDescription, ogImage, twitterCard: 'summary_large_image' }). Next.js:metadata.openGraphandmetadata.twitter. WordPress: Yoast and Rank Math generate them per post from the featured image. - twitter:card is the only tag of its own that X needs; for title, description and image it uses the
og:ones if it does not find its own.
Platforms cache the card the first time they see a URL. After changing the tags, request a re-scrape in Facebook's Sharing Debugger, LinkedIn's Post Inspector or X's validator; WhatsApp and Telegram refresh it on their own after a while.
Check it is fixed
curl -s https://yourdomain.com | grep -oE '<meta (property|name)="(og:|twitter:)[^"]+" content="[^"]*"'
curl -s -o /dev/null -w "%{http_code} %{content_type}\n" "$(curl -s https://yourdomain.com | grep -oE 'og:image" content="[^"]+"' | cut -d'"' -f3)"
The first lists the tags; the second downloads the image and should give 200 with an image type. Then paste the URL in a chat with yourself and look at the card.
Frequently asked questions
I already have a title and a meta description. Do they not work?
Some platforms use them as a fallback, but none shows an image without og:image, and the image is what makes the jump in clicks. The og: tags also let you set a title different from Google's, shorter and more direct.
Does it count for SEO?
Not directly: Google does not use Open Graph for ranking. It counts for people sharing and clicking, which ends up as links and traffic. What Google does read is reviewed by SEO metadata.
My image looks cropped in some apps.
Each platform crops to its own ratio. With 1200 by 630 and the important content centred, with margin at the edges, it looks fine everywhere. Avoid small text pushed into the corners.