Skip to content
https://deseret.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
1
PASS
3
INFO
0
Checks
5
3 PASS 1 REVIEW 1 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://www.deseret.com/pf/resources/deseretnews/assets/images/pb/fallbackImage.png?d=348
Warning::
Missing og:description
The og:description tag controls the description in social sharing previews.
Info::
og:title is short (12 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 12 chars Expected: 25–60 chars
Info::
Missing og:url
The og:url tag specifies the canonical URL for the shared content.
Info::
Missing og:type
The og:type tag helps social platforms categorize the content.
URL: https://www.deseret.com/pf/resources/deseretnews/assets/images/pb/fallbackImage.png?d=348

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: 12 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:type tag helps social platforms categorize the content.

Why this matters

Default og:type is 'website' but the right value (article, product, profile) unlocks richer metadata fields and higher engagement.

Learn more

og:type controls which other og: fields a platform respects. og:type=article enables og:article:published_time, author, and section — surfaced in news cards. og:type=product enables price/availability fields surfaced by Pinterest and shopping integrations. Default 'website' silently disables those.

Source: Open Graph Protocol

Preview

deseret.com

Deseret News

No description

Preview quality · Twitter/X A · 85/100
  • twitter:card — summary_large_image
  • twitter:title — Deseret News
  • twitter:description — Add twitter:description to give the preview body text
  • twitter:image — https://www.deseret.com/pf/resources/deseretnews/assets/images/pb/fallbackImage.png?d=348

DESERET.COM

Deseret News

No description

Preview quality · Facebook D · 55/100
  • og:title — Deseret News
  • og:description — Add og:description to give the preview body text
  • og:image — https://www.deseret.com/pf/resources/deseretnews/assets/images/pb/fallbackImage.png?d=348
  • og:type — Add og:type — Recommended — tells Facebook the content category
  • og:url — Add og:url — Recommended — canonical URL for the share
  • og:site_name — Deseret News

Deseret News

deseret.com

Preview quality · LinkedIn A · 85/100
  • og:title — Deseret News
  • og:description — Add og:description to give the preview body text
  • og:image — https://www.deseret.com/pf/resources/deseretnews/assets/images/pb/fallbackImage.png?d=348

deseret.com

Deseret News

No description

Preview quality · Slack A · 85/100
  • og:title — Deseret News
  • og:description — Add og:description to give the preview body text
  • og:image — https://www.deseret.com/pf/resources/deseretnews/assets/images/pb/fallbackImage.png?d=348

Social preview quality

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

B · 77/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card
twitter:title
twitter:description
twitter:image
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

59/100

Site name appears as

Page titleFilter Icon
og:site_nameDeseret News
twitter:site@deseret
Organization.name

Inconsistent — names differ across channels

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

20/20

og:image + twitter:image set

Meta completeness

14/20

Organization schema

0/15

Contact info discoverable

5/10

contact page

Findings

  • Brand name differs across channels — users see inconsistent identity
  • 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.
Info::
Custom type "WebPage" — unable to validate specific properties

JSON-LD Blocks

Block 1 : WebPage
9 properties Valid
{
  "@context": "http://schema.org",
  "@type": "WebPage",
  "url": "https://www.deseret.com",
  "description": "",
  "name": "",
  "speakable": {
    "@type": "SpeakableSpecification",
    "xpath": [
      "/html/head/title",
      "/html/head/meta[@name='description']/@content"
    ]
  },
  "publisher": {
    "@type": "NewsMediaOrganization",
    "foundingDate": "1850-06-15",
    "url": "https://www.deseret.com",
    "name": "Deseret News",
    "sameAs": [
      "https://twitter.com/deseret",
      "https://www.facebook.com/deseretnews",
      "https://www.instagram.com/deseretnews/"
    ],
    "logo": {
      "@type": "ImageObject",
      "url": "https://uploads.deseret.com/deseretnews/deseret-logo.svg",
      "height": 68,
      "width": 600
    }
  },
  "datePublished": "",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://www.deseret.com"
  }
}
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback