Skip to content
https://denverpost.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
88
GRADE
B
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.
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.denverpost.com/wp-content/uploads/2020/11/denverpost.jpg
Info::
og:title is short (15 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 15 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.
URL: https://www.denverpost.com/wp-content/uploads/2020/11/denverpost.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

URL: 15 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

denverpost.com

The Denver Post

Colorado breaking news, sports, business, weather, entertainment.

Preview quality · Twitter/X D · 55/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from og:title
  • twitter:description — falling back from og:description
  • twitter:image — https://www.denverpost.com/wp-content/uploads/2020/11/denverpost.jpg

  • twitter:card is missing

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

DENVERPOST.COM

The Denver Post

Colorado breaking news, sports, business, weather, entertainment.

Preview quality · Facebook A+ · 100/100
  • og:title — The Denver Post
  • og:description — Colorado breaking news, sports, business, weather, entertainment.
  • og:image — https://www.denverpost.com/wp-content/uploads/2020/11/denverpost.jpg
  • og:type — website
  • og:url — https://www.denverpost.com
  • og:site_name — The Denver Post

The Denver Post

denverpost.com

Preview quality · LinkedIn A+ · 100/100
  • og:title — The Denver Post
  • og:description — Colorado breaking news, sports, business, weather, entertainment.
  • og:image — https://www.denverpost.com/wp-content/uploads/2020/11/denverpost.jpg

denverpost.com

The Denver Post

Colorado breaking news, sports, business, weather, entertainment.

Preview quality · Slack A+ · 100/100
  • og:title — The Denver Post
  • og:description — Colorado breaking news, sports, business, weather, entertainment.
  • og:image — https://www.denverpost.com/wp-content/uploads/2020/11/denverpost.jpg

Social preview quality

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

A · 88/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 required property "author" for NewsArticle
The "author" property is required for the NewsArticle schema type.
Warning::
Missing required property "datePublished" for NewsArticle
The "datePublished" property is required for the NewsArticle schema type.
Info::
Missing recommended property "image" for NewsArticle
Adding "image" can improve how search engines display your content.
Info::
Missing recommended property "publisher" for NewsArticle
Adding "publisher" can improve how search engines display your content.
Info::
Missing recommended property "dateModified" for NewsArticle
Adding "dateModified" can improve how search engines display your content.
Info::
Custom type "NewsMediaOrganization" — unable to validate specific properties
Info::
2 JSON-LD blocks found

The "author" property is required for the NewsArticle schema type.

Why this matters

Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.

Learn more ▾

Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.

Source: Google Search Central / schema.org

The "datePublished" property is required for the NewsArticle schema type.

Why this matters

Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.

Learn more ▾

Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.

Source: Google Search Central / schema.org

Adding "image" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

Adding "publisher" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

Adding "dateModified" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

JSON-LD Blocks

Block 1 : NewsArticle
6 properties Valid
Missing required property: author
Missing required property: datePublished
{
  "@context": "https:\/\/schema.org",
  "@type": "NewsArticle",
  "headline": "The Denver Post",
  "url": "https:\/\/www.denverpost.com\/",
  "publication": "The Denver Post",
  "mainEntityOfPage": {
    "@id": "https:\/\/www.denverpost.com\/"
  }
}
Block 2 : NewsMediaOrganization
4 properties Valid
{
  "@context": "http:\/\/schema.org",
  "@type": "NewsMediaOrganization",
  "name": "The Denver Post",
  "contactPoint": []
}
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 title<!---->Close Cookie Preferences<!---->
og:site_nameThe Denver Post
twitter:site@denverpost
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
  • 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
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback