Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.CLinksAction132 links checked, 127 healthy, 4 brokenREVIEW
Broken Links (5)
| Status | URL | Found in | Error |
|---|---|---|---|
| 410 | https://next.tnwcdn.com/ | <link> | HTTP 410 |
| 404 | https://thenextweb.homerun.co/ | <a> | Not Found |
| ERR | https://www.mckinsey.com/ | <a> | Get "https://www.mckinsey.com/": context... |
| ERR | https://next.thenextweb.com/ | <a> | Get "https://next.thenextweb.com/": reso... |
| 403 | https://cdn0.tnwcdn.com/ | <link> | Forbidden |
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
AOpen GraphOpen Graph tags are well configured for social sharing.PASS
https://s3.eu-west-1.amazonaws.com/tnw.events/hardfork-2018/uploads/social/tnw_191007_110526.pngThe 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
23 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
52 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
Preview

thenextweb.com
TNW | The heart of tech
We inform, inspire, and connect people who love tech
- twitter:card — summary_large_image
- twitter:title — TNW | The heart of tech
- twitter:description — We inform, inspire, and connect people who love tech
- twitter:image — https://s3.eu-west-1.amazonaws.com/tnw.events/hardfork-2018/uploads/social/tnw_191007_110526.png

THENEXTWEB.COM
TNW | The heart of tech
We inform, inspire, and connect people who love tech
- og:title — TNW | The heart of tech
- og:description — We inform, inspire, and connect people who love tech
- og:image — https://s3.eu-west-1.amazonaws.com/tnw.events/hardfork-2018/uploads/social/tnw_191007_110526.png
- og:type — website
- og:url — https://thenextweb.com/
- og:site_name — TNW | The heart of tech

TNW | The heart of tech
thenextweb.com
- og:title — TNW | The heart of tech
- og:description — We inform, inspire, and connect people who love tech
- og:image — https://s3.eu-west-1.amazonaws.com/tnw.events/hardfork-2018/uploads/social/tnw_191007_110526.png
thenextweb.com
TNW | The heart of tech
We inform, inspire, and connect people who love tech

- og:title — TNW | The heart of tech
- og:description — We inform, inspire, and connect people who love tech
- og:image — https://s3.eu-west-1.amazonaws.com/tnw.events/hardfork-2018/uploads/social/tnw_191007_110526.png
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 | — | — | — |
A+Structured Data2 JSON-LD block(s) found — structured data is well configured.PASS
Adding "description" 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": "http:\/\/schema.org",
"@type": "WebSite",
"@id": "https:\/\/thenextweb.com\/#website",
"name": "The Next Web",
"alternateName": "TNW",
"url": "https:\/\/thenextweb.com\/",
"publisher": {
"@type": "Organization",
"@id": "http:\/\/data.thenextweb.com\/tnw\/entity\/the_next_web",
"name": "The Next Web",
"sameAs": [
"https:\/\/en.wikipedia.org\/wiki\/The_Next_Web",
"https:\/\/www.facebook.com\/thenextweb",
"https:\/\/www.twitter.com\/thenextweb",
"https:\/\/instagram.com\/thenextweb",
"https:\/\/www.youtube.com\/user\/thenextweb",
"https:\/\/www.pinterest.com\/thenextweb\/",
"https:\/\/www.linkedin.com\/company\/the-next-web",
"https:\/\/vine.co\/thenextweb",
"https:\/\/thenextweb.tumblr.com",
"https:\/\/soundcloud.com\/thenextweb",
"https:\/\/vimeo.com\/thenextweb",
"https:\/\/vk.com\/thenextweb",
"https:\/\/www.slideshare.net\/thenextweb",
"https:\/\/flipboard.com\/@thenextweb",
"https:\/\/storify.com\/thenextweb",
"https:\/\/www.stumbleupon.com\/channel\/thenextweb",
"https:\/\/www.flickr.com\/photos\/thenextweb\/",
"https:\/\/foursquare.com\/thenextweb"
]
},
"potentialAction": {
"@type": "SearchAction",
"target": "https:\/\/thenextweb.com\/?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}{
"@context": "https:\/\/schema.org",
"@id": "#Publisher",
"@type": "Organization",
"name": "The Next Web",
"logo": "https:\/\/cdn0.tnwcdn.com\/plus\/img\/tnw-brandmark.svg",
"url": "https:\/\/thenextweb.com",
"sameAs": [
"https:\/\/en.wikipedia.org\/wiki\/The_Next_Web",
"https:\/\/www.facebook.com\/thenextweb",
"https:\/\/www.twitter.com\/thenextweb",
"https:\/\/instagram.com\/thenextweb",
"https:\/\/www.youtube.com\/user\/thenextweb",
"https:\/\/www.pinterest.com\/thenextweb\/",
"https:\/\/www.linkedin.com\/company\/the-next-web",
"https:\/\/vine.co\/thenextweb",
"https:\/\/thenextweb.tumblr.com",
"https:\/\/soundcloud.com\/thenextweb",
"https:\/\/vimeo.com\/thenextweb",
"https:\/\/vk.com\/thenextweb",
"https:\/\/www.slideshare.net\/thenextweb",
"https:\/\/flipboard.com\/@thenextweb",
"https:\/\/storify.com\/thenextweb",
"https:\/\/www.stumbleupon.com\/channel\/thenextweb",
"https:\/\/www.flickr.com\/photos\/thenextweb\/",
"https:\/\/foursquare.com\/thenextweb"
]
}ABrand PresenceSite-name consistency, favicon, social image, meta tags, schema, and contact signalsPASS
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
A
85/100
Site name appears as
| Page title | The heart of tech | |
| og:site_name | TNW | The heart of tech | |
| twitter:site | @thenextweb | |
| Organization.name | The Next Web |
Inconsistent — names differ across channels
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
20/20og:image + twitter:image set
Meta completeness
20/20Organization schema
15/15has name, logo + url
Contact info discoverable
10/10contact page + mailto link
Findings
- Brand name differs across channels — users see inconsistent identity
- Consider adding contactPoint — helps appear in "contact us" rich results
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.