Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FLinksAction132 links checked, 112 healthy, 20 brokenFIX
Broken Links (25)
| Status | URL | Found in | Error |
|---|---|---|---|
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/designs/discoverycom/fav... | <link> | Forbidden |
| 403 | https://discovery.com/etc/clientlibs/assets/images... | <img> | Forbidden |
| 403 | https://discovery.com/content/dam/images/discovery... | <img> | Forbidden |
| ERR | about:blank | <iframe> | Get "about:blank": unsupported protocol ... |
| 403 | https://www.discovery.com | <link> | Forbidden |
| 403 | https://discovery.sndimg.com | <link> | Forbidden |
| 403 | https://hgtvhome.sndimg.com/etc/clientlibs/assets/... | <link> | Forbidden |
| 403 | https://hgtvhome.sndimg.com/etc/clientlibs/ad-spec... | <link> | Forbidden |
| 403 | https://hgtvhome.sndimg.com/etc/clientlibs/user-co... | <script> | Forbidden |
Redirects (4)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://sb.scorecardresearch.com/cs/6035... | https://sb.scorecardresearch.com/cs/6035... | <script> | 0 |
| https://play.discoveryplus.com/show/f2cc... | https://play.discoveryplus.com/show/f2cc... | <a> | 0 |
| https://play.discoveryplus.com/show/3473... | https://play.discoveryplus.com/show/3473... | <a> | 0 |
| https://play.discoveryplus.com/show/376c... | https://play.discoveryplus.com/show/376c... | <a> | 0 |
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
51/100
Site name appears as
| Page title | Filter Icon | |
| og:site_name | Discovery | |
| twitter:site | — | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
14/20og:image set; twitter:image missing
Meta completeness
8/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
- Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
- twitter:card 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
https://discovery.sndimg.com/content/dam/images/discovery/editorial/branding/2019/2/1/Discovery-default-search-image-4x3.jpg.rend.hgtvcom.616.462.suffix/1561760738182.jpegThe og:image URL could not be fetched. Social platforms won't be able to display it.
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.
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
4 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
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

discovery.com
Home
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 — falling back from og:image
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">

DISCOVERY.COM
Home
No description
- og:title — Home
- og:description — falling back from <meta name=description>
- og:image — https://discovery.sndimg.com/content/dam/images/discovery/editorial/branding/2019/2/1/Discovery-default-search-image-...
- og:type — fullwidth
- og:url — https://www.discovery.com
- og:site_name — Discovery

Home
discovery.com
- og:title — Home
- og:description — falling back from <meta name=description>
- og:image — https://discovery.sndimg.com/content/dam/images/discovery/editorial/branding/2019/2/1/Discovery-default-search-image-...
discovery.com
Home
No description

- og:title — Home
- og:description — falling back from <meta name=description>
- og:image — https://discovery.sndimg.com/content/dam/images/discovery/editorial/branding/2019/2/1/Discovery-default-search-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 | ⚠ | — | — | — |
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[{\"@context\":\"http://schema.org\"\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
[
{
"@context": "http://schema.org",
"@type": "Organization",
"name": "Discovery",
"url": "https://www.discovery.com",
"logo": {
"@type": "ImageObject",
"url": "https://discovery.sndimg.com/content/dam/images/discovery/editorial/branding/discovery-logo-amp.png",
"height": "60",
"width": "60"
},
"image": {
"@type": "ImageObject",
"url": "https://discovery.sndimg.com/content/dam/images/discovery/editorial/branding/discovery-logo-amp.png",
"height": "60",
"width": "60"
},
"parentOrganization": {
"@type": "Organization",
"image": "https://hgtvhome.sndimg.com/content/dam/images/hgtv/fullset/wbd_logo.png",
"logo": "https://hgtvhome.sndimg.com/content/dam/images/hgtv/fullset/wbd_logo.png",
"url": "https://wbd.com",
"name": "Warner Bros. Discovery, Inc.",
"description": "Warner Bros. Discovery, a premier global media and entertainment company, offers audiences the world's most differentiated and complete portfolio of content, brands and franchises across television, film, streaming and gaming. The new company combines WarnerMedia's premium entertainment, sports and news assets with Discovery's leading non-fiction and international entertainment and sports businesses.",
"sameAs": [
"https://en.wikipedia.org/wiki/Warner_Bros._Discovery",
"https://twitter.com/wbd/",
"https://www.instagram.com/wbd/",
"https://www.facebook.com/WBD",
"https://youtube.com/wbd/",
"https://www.linkedin.com/company/warner-bros-discovery/"
]
}
}
]