Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DOpen GraphActionOpen Graph tags need attention — social sharing previews may be incomplete.FIX
The og:description tag controls the description in social sharing previews.
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
The og:image tag provides a preview image for social sharing.
No og:image means social shares are imageless — measurably less engaging than image-cards across every major platform.
Learn more ▾ ▴
Twitter, Facebook, and LinkedIn all use og:image (or twitter:image as a fallback) for share-card thumbnails. Without one, the post renders as a text-only card. A 1200x630px image (Twitter's preferred size) covers all platforms.
Source: Open Graph Protocol
The og:type tag helps social platforms categorize the content.
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
csmonitor.com
Christian Science Monitor
No description
- twitter:card — summary_large_image
- twitter:title — Christian Science Monitor
- twitter:description — Add twitter:description to give the preview body text
- twitter:image — Add twitter:image — preview card without an image looks broken
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
CSMONITOR.COM
Christian Science Monitor
No description
- og:title — Christian Science Monitor
- og:description — Add og:description to give the preview body text
- og:image — Add og:image — preview card without an image looks broken
- og:type — Add og:type — Recommended — tells Facebook the content category
- og:url — https://www.csmonitor.com/
- og:site_name — The Christian Science Monitor
No preview image for Facebook
→ Add og:image (recommended 1200×630)
Christian Science Monitor
csmonitor.com
- og:title — Christian Science Monitor
- og:description — Add og:description to give the preview body text
- og:image — Add og:image — preview card without an image looks broken
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
csmonitor.com
Christian Science Monitor
No description
- og:title — Christian Science Monitor
- og:description — Add og:description to give the preview body text
- og:image — Add og:image — preview card without an image looks broken
No preview image — Slack unfurl will be text-only
→ Add og:image or twitter:image
Social preview quality
Averaged across Twitter/X, Facebook, LinkedIn, and Slack.
| Field | Twitter/X | Slack | ||
|---|---|---|---|---|
| og:title | ||||
| og:description | ||||
| og:image | ||||
| og:type | ||||
| og:url | ||||
| og:site_name | ||||
| twitter:card | — | — | — | |
| twitter:title | — | — | — | |
| twitter:description | — | — | — | |
| twitter:image | — | — | — |
FStructured DataAction2 JSON-LD block(s) found — issues found that may affect search visibility.FIX
The @context should be "https://schema.org" for search engines to recognize the data.
https://schema.orgJSON-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
Search engines need @type to understand the structured data.
JSON-LD without @type is invalid — Google can't determine which schema to validate against.
Learn more ▾ ▴
Every JSON-LD block must declare @type (Article, Product, Organization, etc.). Without it, the block is structurally valid JSON but not valid schema.org. Add @type matching the content (e.g., '@type': 'Article' for blog posts).
Source: schema.org / Google Search Central
The "author" property is required for the Article schema type.
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 Article schema type.
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.
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.
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
{
"contentobject_id": 1081397,
"node_id": 2,
"class_identifier": "frontpage",
"contentclass_id": 23,
"sections": [],
"title_addition": "0",
"result_page": "",
"story_source": "",
"authors": [],
"staff_line": "",
"aspect_format": "www",
"view_mode": "full",
"remote_id": "f377e351d63e1ab417ffc1ce8a38ca26",
"keyword_tags": [],
"kickers": "",
"word_count": 0,
"tags": [],
"ddp": false,
"publish_date": "2019-04-15",
"updated_date": "2026-03-04 08:20"
}{
"@context": "http:\/\/schema.org",
"@type": "Article",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https:\/\/www.csmonitor.com\/",
"copyrightHolder": {
"@type": "Organization",
"name": "The Christian Science Monitor"
}
},
"headline": "",
"publisher": {
"@type": "Organization",
"name": "The Christian Science Monitor",
"logo": {
"@type": "ImageObject",
"url": "\/images\/logo_white_250x63.png",
"width": 250,
"height": 60
}
}
}FBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
F
33/100
Site name appears as
| Page title | CSMonitor.com | |
| og:site_name | The Christian Science Monitor | |
| twitter:site | @csmonitor | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
0/20Meta completeness
8/20Organization schema
0/15Contact info discoverable
5/10contact page
Findings
- Brand name differs across channels — users see inconsistent identity
- No social share image — shared links render as bare URLs
- og:image 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.
ALinks200 links checked, 195 healthy, 0 brokenPASS
Redirects (6)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://www.csmonitor.com/auth/sso_login | https://www.csmonitor.com/auth/sso_login | <a> | 0 |
| https://www.csmonitor.com/The-Culture | https://www.csmonitor.com/The-Culture | <a> | 0 |
| https://www.csmonitor.com/The-Culture/Fa... | https://www.csmonitor.com/The-Culture/Fa... | <a> | 0 |
| https://csmonitor.com/The-Culture | https://csmonitor.com/The-Culture | <a> | 0 |
| https://csmonitor.com/Editorials/A-Chris... | https://csmonitor.com/Editorials/A-Chris... | <a> | 0 |
| https://csmonitor.com/auth/sso_login | https://csmonitor.com/auth/sso_login | <a> | 0 |