Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
D
43/100
Site name appears as
| Page title | Independent news and analysis on the U.S. Supreme Court | SCOTUSblog | |
| og:site_name | — | |
| twitter:site | @SCOTUSblog | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
15/15covers multiple sizes, apple-touch-icon + SVG
Social share image
0/20Meta completeness
14/20Organization schema
4/15Organization schema present but missing all recommended fields
Contact 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
- Organization schema missing logo — add a logo property pointing to a square PNG
- Organization schema missing url — point it at the canonical homepage
- 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.
COpen GraphActionOpen Graph tags are partially configured — some improvements recommended.REVIEW
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
10 charsIdeal length is 25–60 characters for social sharing previews.
25–60 charsog: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.
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.
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
The og:site_name tag displays the website name in social previews.
Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.
Learn more ▾ ▴
og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.
Source: Open Graph Protocol
Preview
scotusblog.com
SCOTUSblog
Independent news and analysis on the U.S. Supreme Court.
- twitter:card — summary_large_image
- twitter:title — SCOTUSblog
- twitter:description — Independent news and analysis on the U.S. Supreme Court.
- 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)
SCOTUSBLOG.COM
SCOTUSblog
Independent news and analysis on the U.S. Supreme Court.
- og:title — SCOTUSblog
- og:description — Independent news and analysis on the U.S. Supreme Court.
- 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 — Add og:url — Recommended — canonical URL for the share
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview
No preview image for Facebook
→ Add og:image (recommended 1200×630)
SCOTUSblog
scotusblog.com
- og:title — SCOTUSblog
- og:description — Independent news and analysis on the U.S. Supreme Court.
- og:image — Add og:image — preview card without an image looks broken
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
scotusblog.com
SCOTUSblog
Independent news and analysis on the U.S. Supreme Court.
- og:title — SCOTUSblog
- og:description — Independent news and analysis on the U.S. Supreme Court.
- 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 | — | — | — |
ALinks120 links checked, 119 healthy, 1 brokenPASS
Broken Links (1)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://www.gstatic.com | <link> | Not Found |
Redirects (12)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://experience.tinypass.com | https://experience.tinypass.com | <link> | 0 |
| https://api.piano.io | https://api.piano.io | <link> | 0 |
| https://scotusblog.com/author/scotusblog... | https://scotusblog.com/author/scotusblog... | <a> | 0 |
| https://scotusblog.com/author/amy-howe | https://scotusblog.com/author/amy-howe | <a> | 0 |
| https://scotusblog.com/author/stephanie-... | https://scotusblog.com/author/stephanie-... | <a> | 0 |
| https://scotusblog.com/author/taraleigh-... | https://scotusblog.com/author/taraleigh-... | <a> | 0 |
| https://scotusblog.com/author/kelsey-dal... | https://scotusblog.com/author/kelsey-dal... | <a> | 0 |
| https://scotusblog.com/author/zachary-sh... | https://scotusblog.com/author/zachary-sh... | <a> | 0 |
| https://scotusblog.com/author/nora-colli... | https://scotusblog.com/author/nora-colli... | <a> | 0 |
| https://scotusblog.com/author/ronald-man... | https://scotusblog.com/author/ronald-man... | <a> | 0 |
| https://scotusblog.com/author/john-elwoo... | https://scotusblog.com/author/john-elwoo... | <a> | 0 |
| https://scotusblog.com/author/mark-walsh | https://scotusblog.com/author/mark-walsh | <a> | 0 |
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
AStructured Data1 JSON-LD block(s) found — structured data is well configured.PASS
The "name" property is required for the Organization 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 "url" 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 "logo" 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 "sameAs" 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
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://www.scotusblog.com/#organization",
"name": "SCOTUSblog",
"url": "https://www.scotusblog.com/",
"sameAs": [
"https://twitter.com/SCOTUSblog",
"https://bsky.app/profile/scotusblog.com"
],
"logo": {
"@type": "ImageObject",
"url": "https://www.scotusblog.com/logo.png"
}
},
{
"@type": "WebSite",
"@id": "https://www.scotusblog.com/#website",
"url": "https://www.scotusblog.com/",
"name": "SCOTUSblog",
"publisher": {
"@id": "https://www.scotusblog.com/#organization"
},
"potentialAction": {
"@type": "SearchAction",
"target": "https://www.scotusblog.com/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}
]
}