Skip to content
https://twincities.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
1
INFO
0
Checks
5
1 PASS 4 REVIEW
C
Open Graph
Action
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.twincities.com/wp-content/uploads/2020/08/TCFallback.jpg
Warning::
Missing og:description
The og:description tag controls the description in social sharing previews.
Info::
og:title is short (11 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 11 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.twincities.com/wp-content/uploads/2020/08/TCFallback.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: 11 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

twincities.com

Twin Cities

No description

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 <meta name=description>
  • twitter:image — https://www.twincities.com/wp-content/uploads/2020/08/TCFallback.jpg

  • twitter:card is missing

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

TWINCITIES.COM

Twin Cities

No description

Preview quality · Facebook A+ · 95/100
  • og:title — Twin Cities
  • og:description — falling back from <meta name=description>
  • og:image — https://www.twincities.com/wp-content/uploads/2020/08/TCFallback.jpg
  • og:type — website
  • og:url — https://www.twincities.com
  • og:site_name — Twin Cities

Twin Cities

twincities.com

Preview quality · LinkedIn A+ · 95/100
  • og:title — Twin Cities
  • og:description — falling back from <meta name=description>
  • og:image — https://www.twincities.com/wp-content/uploads/2020/08/TCFallback.jpg

twincities.com

Twin Cities

No description

Preview quality · Slack A+ · 95/100
  • og:title — Twin Cities
  • og:description — falling back from <meta name=description>
  • og:image — https://www.twincities.com/wp-content/uploads/2020/08/TCFallback.jpg

Social preview quality

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

A · 85/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
1 JSON-LD block(s) found — some improvements recommended.
REVIEW
1 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.

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": "Twin Cities",
  "url": "https:\/\/www.twincities.com\/",
  "publication": "Twin Cities",
  "mainEntityOfPage": {
    "@id": "https:\/\/www.twincities.com\/"
  }
}
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

58/100

Site name appears as

Page title<!---->Close Cookie Preferences<!---->
og:site_nameTwin Cities
twitter:site@pioneerpress
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

8/20

Organization schema

0/15

Contact info discoverable

10/10

contact page + mailto link

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

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