Skip to content
https://tass.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
1
INFO
0
Checks
5
1 PASS 4 REVIEW
B
Open Graph
Open Graph tags are partially configured — some improvements recommended.
REVIEW
Open Graph tags are partially configured — some improvements recommended.
Warning::
Missing og:description
The og:description tag controls the description in social sharing previews.
Info::
og:title is short (24 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 24 chars Expected: 25–60 chars
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

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: 24 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

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

tass.com

TASS Russian News Agency

No description

Preview quality · Twitter/X D · 50/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from og:title
  • twitter:description — falling back from <meta name=description>
  • twitter:image — falling back from og:image

  • twitter:card is missing

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

TASS.COM

TASS Russian News Agency

No description

Preview quality · Facebook A · 90/100

Description will be truncated (177 chars / 155 max)

  • og:title — TASS Russian News Agency
  • og:description — falling back from <meta name=description>
  • og:image — https://tass.com/img/blocks/common/tass_logo_share_eng.png
  • og:type — article
  • og:url — https://tass.com/
  • og:site_name — TASS

  • Description will be truncated on Facebook (177 chars, max 155)

    → Tighten og:description to ≤155 characters

TASS Russian News Agency

tass.com

Preview quality · LinkedIn A · 90/100

Description will be truncated (177 chars / 150 max)

  • og:title — TASS Russian News Agency
  • og:description — falling back from <meta name=description>
  • og:image — https://tass.com/img/blocks/common/tass_logo_share_eng.png

  • Description will be truncated on LinkedIn (177 chars, max 150)

    → Tighten og:description to ≤150 characters

tass.com

TASS Russian News Agency

No description

Preview quality · Slack A+ · 95/100
  • og:title — TASS Russian News Agency
  • og:description — falling back from <meta name=description>
  • og:image — https://tass.com/img/blocks/common/tass_logo_share_eng.png

Social preview quality

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

B · 81/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description⚠⚠⚠
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image⚠———
B
Structured Data
2 JSON-LD block(s) found — some improvements recommended.
REVIEW
2 JSON-LD block(s) found — some improvements recommended.
Warning::
Missing or invalid @context in block #1
The @context should be "https://schema.org" for search engines to recognize the data.
Got: https://schema.org/ Expected: https://schema.org
Info::
Custom type "SiteNavigationElement" — unable to validate specific properties
Info::
2 JSON-LD blocks found
URL: https://schema.org/

The @context should be "https://schema.org" for search engines to recognize the data.

Expected: https://schema.org
Why this matters

JSON-LD without @context is invalid structured data — Google ignores the entire block.

Learn more ▾

@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.

Source: JSON-LD spec / schema.org

JSON-LD Blocks

Block 1 : Organization
6 properties Valid
Missing or invalid @context
{
  "@context": "https://schema.org/",
  "@type": "Organization",
  "url": "https://tass.com",
  "name": "TASS",
  "logo": {
    "@type": "ImageObject",
    "url": "https://tass.com/newtass/img/blocks/common/tass-logo.jpg",
    "width": 60,
    "height": 60
  },
  "sameAs": [
    "https://www.facebook.com/tassagency",
    "https://www.youtube.com/channel/UCEyGP84v6qbsZy9-pL6Jx2g",
    "https://vk.com/tassagency",
    "https://ok.ru/tassagency",
    "https://www.instagram.com/tass_agency/",
    "https://twitter.com/tass_agency"
  ]
}
Block 2 : SiteNavigationElement
2 properties Valid
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@context": "https://schema.org",
      "@type": "SiteNavigationElement",
      "@id": "#menu-sections",
      "name": "Russian Politics & Diplomacy",
      "url": "https://tass.com/politics"
    },
    {
      "@context": "https://schema.org",
      "@type": "SiteNavigationElement",
      "@id": "#menu-sections",
      "name": "World",
      "url": "https://tass.com/world"
    },
    {
      "@context": "https://schema.org",
      "@type": "SiteNavigationElement",
      "@id": "#menu-sections",
      "name": "Business & Economy",
      "url": "https://tass.com/economy"
    },
    {
      "@context": "https://schema.org",
      "@type": "SiteNavigationElement",
      "@id": "#menu-sections",
      "name": "Military & Defense",
      "url": "https://tass.com/defense"
    },
    {
      "@context": "https://schema.org",
      "@type": "SiteNavigationElement",
      "@id": "#menu-sections",
      "name": "Science & Space",
      "url": "https://tass.com/science"
    },
    {
      "@context": "https://schema.org",
      "@type": "SiteNavigationElement",
      "@id": "#menu-sections",
      "name": "Emergencies ",
      "url": "https://tass.com/emergencies"
    },
    {
      "@context": "https://schema.org",
      "@type": "SiteNavigationElement",
      "@id": "#menu-sections",
      "name": "Society & Culture",
      "url": "https://tass.com/society"
    },
    {
      "@context": "https://schema.org",
      "@type": "SiteNavigationElement",
      "@id": "#menu-sections",
      "name": "Press Review",
      "url": "https://tass.com/pressreview"
    },
    {
      "@context": "https://schema.org",
      "@type": "SiteNavigationElement",
      "@id": "#menu-sections",
      "name": "Sports",
      "url": "https://tass.com/sports"
    }
  ]
}
C
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
REVIEW

Brand Presence

Your brand name differs across channels — visitors see inconsistent identity.

C

62/100

Site name appears as

Page titleTASS Russian News Agency
og:site_nameTASS
twitter:site—
Organization.nameTASS

Inconsistent — names differ across channels

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

8/20

Organization schema

15/15

has name, logo + url

Contact info discoverable

5/10

contact page

Findings

  • Brand name differs across channels — users see inconsistent identity
  • Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
  • twitter:card missing
  • Consider adding contactPoint — helps appear in "contact us" rich results
  • 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
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback