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:title tag controls the title shown in social sharing previews.
Without og:title, social shares fall back to the <title> tag — usually awkwardly truncated or branded for SEO not social.
Learn more ▾ ▴
og:title controls what appears as the headline in social-share cards (Twitter, Facebook, LinkedIn, Slack, iMessage). When omitted, platforms fall back to <title>, which is usually optimized for SEO (longer, brand-suffixed) and reads badly in social context. A 50-60-character og:title gives a clean preview.
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
1 charsIdeal length is 55–200 characters for social sharing previews.
55–200 charsog:description very short — provides little context in social cards.
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
osti.gov
No title set
Title will be truncated (83 chars / 70 max)
- twitter:card — summary
- twitter:title — falling back from <title>
- twitter:description — falling back from og:description
- twitter:image — Add twitter:image — preview card without an image looks broken
Title will be truncated on Twitter/X (83 chars, max 70)
→ Shorten the title to ≤70 characters
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
OSTI.GOV
No title set
Title will be truncated (83 chars / 60 max)
- og:title — falling back from <title>
- og:description —
- og:image — Add og:image — preview card without an image looks broken
- og:type — article
- og:url — https://www.osti.gov/
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview
Title will be truncated on Facebook (83 chars, max 60)
→ Shorten og:title to ≤60 characters
No preview image for Facebook
→ Add og:image (recommended 1200×630)
og:image is below recommended size (200×200)
→ Upload an image ≥1200×630 for the large preview card
No title set
osti.gov
- og:title — falling back from <title>
- og:description —
- og:image — Add og:image — preview card without an image looks broken
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
osti.gov
No title set
- og:title — falling back from <title>
- og:description —
- 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 | — | — | — |
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
26/100
Site name appears as
| Page title | U.S. Department of Energy Office of Scientific and Technical Information | |
| og:site_name | — | |
| twitter:site | @ostigov | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
8/15single size only
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
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- og:title missing
- 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.
CStructured DataActionNo structured data (JSON-LD) found.REVIEW
Adding structured data helps search engines understand your content and can enable rich results.
Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.
Learn more ▾ ▴
Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.
Source: Google Search Central / schema.org
No structured data found
Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.
Common types include:
- WebSite — your site identity and search box
- Organization — your company information
- Article — blog posts and news articles
- Product — e-commerce product pages
- BreadcrumbList — navigation paths