Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FOpen 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
14 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
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.
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
britishmuseum.org
British Museum
No description
- 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 — Add twitter:image — preview card without an image looks broken
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
BRITISHMUSEUM.ORG
British Museum
No description
- og:title — British Museum
- og:description — falling back from <meta name=description>
- 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)
British Museum
britishmuseum.org
- og:title — British Museum
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
britishmuseum.org
British Museum
No description
- og:title — British Museum
- og:description — falling back from <meta name=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
Partial brand coverage — a few channels are missing brand signals.
F
38/100
Site name appears as
| Page title | British Museum | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
0/20Meta completeness
8/20Organization schema
0/15Contact info discoverable
10/10contact page + tel link
Findings
- Missing brand name in: og:site_name, twitter:site, Organization.name
- No social share image — shared links render as bare URLs
- og:image missing
- 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.
CLinksAction200 links checked, 194 healthy, 6 brokenREVIEW
Broken Links (7)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://googletagmanager.com | <link> | Not Found |
| 429 | https://www.accurat.ai/legal/privacy-centre | <a> | Too Many Requests |
| 429 | https://www.accurat.ai/legal/legitimate-interest | <a> | Too Many Requests |
| ERR | https://admaxmedia.io/privacy-policy/ | <a> | Get "https://admaxmedia.io/privacy-polic... |
| 404 | https://adnuntius.com/resources/privacy-policy/ | <a> | Not Found |
| 404 | https://www.adzymic.ai/privacy | <a> | Not Found |
| 403 | https://www.britishmuseum.org/cookies | <a> | Forbidden |
Redirects (17)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://www.blackbaud.com/privacy-policy... | https://www.blackbaud.com/privacy-policy... | <a> | 0 |
| https://www.paypal.com/uk/webapps/mpp/ua... | https://www.paypal.com/uk/webapps/mpp/ua... | <a> | 0 |
| https://vimeo.com/privacy | https://vimeo.com/privacy | <a> | 0 |
| https://www.tiktok.com/legal/privacy-pol... | https://www.tiktok.com/legal/privacy-pol... | <a> | 0 |
| https://www.33across.co.uk/privacy-polic... | https://www.33across.co.uk/privacy-polic... | <a> | 0 |
| https://3q.video/en/help-center/datensch... | https://3q.video/en/help-center/datensch... | <a> | 0 |
| https://www.abcsinsights.com/privacy/ad-... | https://www.abcsinsights.com/privacy/ad-... | <a> | 0 |
| https://www.ad-alliance.de/datenschutz/ | https://www.ad-alliance.de/datenschutz/ | <a> | 0 |
| https://www.adbility-media.com/datenschu... | https://www.adbility-media.com/datenschu... | <a> | 0 |
| https://www.advanced-store.com/en/data-p... | https://www.advanced-store.com/en/data-p... | <a> | 0 |
| https://adverty.com/privacy-policy/ | https://adverty.com/privacy-policy/ | <a> | 0 |
| https://www.advisible.com/privacy | https://www.advisible.com/privacy | <a> | 0 |
| https://audiostack.ai/legal/privacy-poli... | https://audiostack.ai/legal/privacy-poli... | <a> | 0 |
| https://www.alkimi.org/privacy-policy | https://www.alkimi.org/privacy-policy | <a> | 0 |
| https://www.allmediadesk.com/en/legal-in... | https://www.allmediadesk.com/en/legal-in... | <a> | 0 |
| https://alphalyr.fr/en/privacy-policy/ | https://alphalyr.fr/en/privacy-policy/ | <a> | 0 |
| https://www.amazon.co.uk/gp/help/custome... | https://www.amazon.co.uk/gp/help/custome... | <a> | 0 |
CStructured DataAction1 JSON-LD block(s) found — some improvements recommended.REVIEW
JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[]\n\t^.\n"
JSON-LD block fails to parse — Google ignores the entire block, so structured data effectively isn't there.
Learn more ▾ ▴
Common causes: trailing comma, single quotes instead of double, unescaped quote in a string value. Validate at https://validator.schema.org/ or Search Console's Rich Results Test.
Source: schema.org / Google Search Central
JSON-LD Blocks
[]