Skip to content
https://en.wikipedia.org/wiki/Octopus

Content

· 8 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
75
GRADE
C
FIX
4
REVIEW
0
PASS
4
INFO
0
Checks
8
4 PASS 4 FIX
D
Open Graph
Action
Open Graph tags need attention — social sharing previews may be incomplete.
FIX
Open Graph tags need attention — social sharing previews may be incomplete.
Critical::
og:image is not reachable
The og:image URL could not be fetched. Social platforms won't be able to display it.
Got: https://upload.wikimedia.org/wikipedia/commons/thumb/5/57/Octopus2.jpg/1280px-Octopus2.jpg
Warning::
Missing og:description
The og:description tag controls the description in social sharing previews.
Info::
og:title is short (19 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 19 chars Expected: 25–60 chars
Info::
Missing og:url
The og:url tag specifies the canonical URL for the shared content.
Info::
Missing og:site_name
The og:site_name tag displays the website name in social previews.
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.
URL: https://upload.wikimedia.org/wikipedia/commons/thumb/5/57/Octopus2.jpg/1280px-Octopus2.jpg

The og:image URL could not be fetched. Social platforms won't be able to display it.

Why this matters

An unreachable og:image URL (404, DNS fail, slow timeout) means social platforms cache the failure and serve no image for hours.

Learn more ▾

Social platforms (Facebook, Twitter) cache OG metadata aggressively — including failed image fetches. A momentarily-broken og:image can leave your shares imageless for hours. Test og:image URLs in Facebook's Sharing Debugger to force re-cache after fixing.

Source: Open Graph Protocol / Facebook Sharing Debugger

The og:description tag controls the description in social sharing previews.

Why this matters

No og:description means social cards either show no subtitle or scrape the first paragraph — usually unflattering.

Learn more ▾

Without og:description, social platforms either render no subtitle or pull whatever text appears first on the page. The first paragraph is rarely written for share-card context. A purpose-written 150-200 character og:description gives a polished card.

Source: Open Graph Protocol

URL: 19 chars

Ideal length is 25–60 characters for social sharing previews.

Expected: 25–60 chars
Why this matters

og:title very short — may render with awkward whitespace in social cards.

Source: Open Graph Protocol

The og:url tag specifies the canonical URL for the shared content.

Why this matters

Without og:url, social platforms infer the canonical URL — often picking a tracking-param variant that pollutes share counts.

Learn more ▾

og:url tells the social platform which URL to count this share against. Without it, platforms use the literal URL the user pasted (which may include utm_* parameters, ref codes, etc.). Setting og:url to the canonical form keeps share-count attribution clean.

Source: Open Graph Protocol

The og:site_name tag displays the website name in social previews.

Why this matters

Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.

Learn more ▾

og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.

Source: Open Graph Protocol

Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

Why this matters

Without twitter:card, Twitter renders posts as plain text — no preview image, no structured layout.

Learn more ▾

Twitter requires `<meta name="twitter:card" content="summary_large_image">` (or summary) to render share-cards at all. Without it, links appear as raw text and engagement plummets vs cards. Twitter also falls back to og:image if twitter:image isn't set, so configure both.

Source: Twitter Developer Platform

Preview

en.wikipedia.org

Octopus - Wikipedia

No description

Preview quality · Twitter/X F · 40/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from og:title
  • twitter:description — Add twitter:description to give the preview body text
  • twitter:image — falling back from og:image

  • twitter:card is missing

    → Add <meta name="twitter:card" content="summary_large_image">

EN.WIKIPEDIA.ORG

Octopus - Wikipedia

No description

Preview quality · Facebook D · 55/100
  • og:title — Octopus - Wikipedia
  • og:description — Add og:description to give the preview body text
  • og:image — https://upload.wikimedia.org/wikipedia/commons/thumb/5/57/Octopus2.jpg/1280px-Octopus2.jpg
  • og:type — website
  • og:url — Add og:url — Recommended — canonical URL for the share
  • og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

Octopus - Wikipedia

en.wikipedia.org

Preview quality · LinkedIn A · 85/100
  • og:title — Octopus - Wikipedia
  • og:description — Add og:description to give the preview body text
  • og:image — https://upload.wikimedia.org/wikipedia/commons/thumb/5/57/Octopus2.jpg/1280px-Octopus2.jpg

en.wikipedia.org

Octopus - Wikipedia

No description

Preview quality · Slack A · 85/100
  • og:title — Octopus - Wikipedia
  • og:description — Add og:description to give the preview body text
  • og:image — https://upload.wikimedia.org/wikipedia/commons/thumb/5/57/Octopus2.jpg/1280px-Octopus2.jpg

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

C · 66/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description———
twitter:image⚠———
F
Image Optimization
Action
6 issues found across 57 images
FIX
6 issues found across 57 images
Warning::
13 images significantly larger than display size
Resizing to display dimensions could save approximately 51 KB.
Got: ~51 KB wasted
Warning::
1 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
49 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Warning::
All 52 images use legacy formats (JPEG/PNG/GIF)
WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
Warning::
22 images missing alt text
Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
Info::
1 image(s) rendered at a different aspect ratio than the source
The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://upload.wikimedia.org/wikipedia/commons/thumb/d/d2/Wikidata-logo-without-paddings.svg/120px-Wikidata-logo-without-paddings.svg.png.
D
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
FIX

Brand Presence

Partial brand coverage — a few channels are missing brand signals.

D

44/100

Site name appears as

Page titleWikipedia
og:site_name—
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

8/20

Organization schema

0/15

Contact info discoverable

5/10

contact page

Findings

  • Missing brand name in: og:site_name, twitter:site, Organization.name
  • Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • twitter:card missing
  • No Organization schema — Google can't render your logo in the knowledge panel
  • Only partial contact info discoverable — consider adding a dedicated contact page or mailto/tel link

How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.

A+
Mixed Content
No mixed content detected — all resources use HTTPS.
PASS
No mixed content detected — all resources use HTTPS.
Info::
No mixed content detected — all resources use HTTPS
A+
Structured Data
1 JSON-LD block(s) found — structured data is well configured.
PASS
1 JSON-LD block(s) found — structured data is well configured.

JSON-LD Blocks

Block 1 : Article
12 properties Valid
{
  "@context": "https:\/\/schema.org",
  "@type": "Article",
  "name": "Octopus",
  "url": "https:\/\/en.wikipedia.org\/wiki\/Octopus",
  "sameAs": "http:\/\/www.wikidata.org\/entity\/Q40152",
  "mainEntity": "http:\/\/www.wikidata.org\/entity\/Q40152",
  "author": {
    "@type": "Organization",
    "name": "Contributors to Wikimedia projects"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Wikimedia Foundation, Inc.",
    "logo": {
      "@type": "ImageObject",
      "url": "https:\/\/www.wikimedia.org\/static\/images\/wmf-hor-googpub.png"
    }
  },
  "datePublished": "2002-01-02T14:32:50Z",
  "dateModified": "2026-04-24T15:02:39Z",
  "image": "https:\/\/upload.wikimedia.org\/wikipedia\/commons\/5\/57\/Octopus2.jpg",
  "headline": "order of molluscs"
}
A+
Rich Results Eligibility
1 JSON-LD block(s) declaring 1 schema type(s)
PASS
1 JSON-LD block(s) declaring 1 schema type(s)
Info::
1 rich-result schema type(s) declared
Inventory of structured-data types on the page (each may unlock a different SERP feature): Article Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.
A+
Autoplay Media
2 media element(s) found, none autoplay
PASS
2 media element(s) found, none autoplay
Info::
2 media element(s) found, none autoplay
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback