Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.BLinks200 links checked, 197 healthy, 3 brokenREVIEW
Broken Links (4)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://fonts.googleapis.com | <link> | Not Found |
| 404 | https://fonts.gstatic.com | <link> | Not Found |
| 429 | https://www.instagram.com/typeform/ | <a> | Too Many Requests |
| 403 | https://cdn.prod.website-files.com | <link> | Forbidden |
Redirects (4)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://www.typeform.com/pricing/talent | https://www.typeform.com/pricing/talent | <a> | 0 |
| https://admin.typeform.com/login/ | https://admin.typeform.com/login/ | <a> | 0 |
| https://admin.typeform.com/login/logout | https://admin.typeform.com/login/logout | <a> | 0 |
| https://www.typeform.com/partners/startu... | https://www.typeform.com/partners/startu... | <a> | 0 |
BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
https://cdn.prod.website-files.com/66ffe2174aa8e8d5661c2708/6889ccfec828e151ddd96537_ogimage.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
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

typeform.com
Typeform: People-Friendly Forms and Surveys
Build beautiful, interactive forms — get more responses. No coding needed. Templates for quizzes, research, feedback, lead generation, and more. Sign up FREE.
- twitter:card — summary_large_image
- twitter:title — falling back from og:title
- twitter:description — falling back from og:description
- twitter:image — falling back from og:image

TYPEFORM.COM
Typeform: People-Friendly Forms and Surveys
Build beautiful, interactive forms — get more responses. No coding needed. Templates for quizzes, research, feedback, lead generation, and more. Sign up FREE.
Description will be truncated (160 chars / 155 max)
- og:title — Typeform: People-Friendly Forms and Surveys
- og:description — Build beautiful, interactive forms — get more responses. No coding needed. Templates for quizzes, research, feedback,...
- og:image — https://cdn.prod.website-files.com/66ffe2174aa8e8d5661c2708/6889ccfec828e151ddd96537_ogimage.png
- og:type — website
- og:url — https://www.typeform.com/
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview
Description will be truncated on Facebook (160 chars, max 155)
→ Tighten og:description to ≤155 characters

Typeform: People-Friendly Forms and Surveys
typeform.com
Description will be truncated (160 chars / 150 max)
- og:title — Typeform: People-Friendly Forms and Surveys
- og:description — Build beautiful, interactive forms — get more responses. No coding needed. Templates for quizzes, research, feedback,...
- og:image — https://cdn.prod.website-files.com/66ffe2174aa8e8d5661c2708/6889ccfec828e151ddd96537_ogimage.png
Description will be truncated on LinkedIn (160 chars, max 150)
→ Tighten og:description to ≤150 characters
typeform.com
Typeform: People-Friendly Forms and Surveys
Build beautiful, interactive forms — get more responses. No coding needed. Templates for quizzes, research, feedback, lead generation, and more. Sign up FREE.

- og:title — Typeform: People-Friendly Forms and Surveys
- og:description — Build beautiful, interactive forms — get more responses. No coding needed. Templates for quizzes, research, feedback,...
- og:image — https://cdn.prod.website-files.com/66ffe2174aa8e8d5661c2708/6889ccfec828e151ddd96537_ogimage.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 | ⚠ | — | — | — |
BStructured Data2 JSON-LD block(s) found — some improvements recommended.REVIEW
http://schema.org/The @context should be "https://schema.org" for search engines to recognize the data.
https://schema.orgJSON-LD without @context is invalid structured data — Google ignores the entire block.
Learn more ▾ ▴
@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.
Source: JSON-LD spec / schema.org
JSON-LD Blocks
{
"@context": "http://schema.org/",
"@id": "https://fast.wistia.net/embed/iframe/5oojlzngxc",
"@type": "VideoObject",
"duration": "PT24S",
"name": "Hero",
"thumbnailUrl": "https://embed-ssl.wistia.com/deliveries/1273dae15b1dcfdcb497ff4c3d696d0002150da6.jpg?image_crop_resized=960x448",
"embedUrl": "https://fast.wistia.net/embed/iframe/5oojlzngxc",
"uploadDate": "2025-10-21T15:24:35.000Z",
"description": "a Homepage_10/25 video",
"contentUrl": "https://embed-ssl.wistia.com/deliveries/5b62f270cf8bae6ffd6e9f0a1a86dc3f5e2ba8dd.m3u8"
}{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Typeform",
"url": "https://www.typeform.com",
"logo": "https://cdn.prod.website-files.com/66ffe2174aa8e8d5661c2708/6889ccfec828e151ddd96537_ogimage.png",
"sameAs": [
"https://www.linkedin.com/company/typeform-/",
"https://www.facebook.com/typeform/",
"https://www.twitter.com/typeform/",
"https://www.instagram.com/typeform/",
"https://www.youtube.com/channel/UC2nRv6J0FsJVePJTLhUDKgg/"
],
"description": "Build beautiful, interactive forms — get more responses. No coding needed. Templates for quizzes, research, feedback, lead generation, and more. Sign up FREE.",
"foundingDate": "2012",
"founder": [
{
"@type": "Person",
"name": "Robert Muñoz",
"url": "https://www.linkedin.com/in/robertmunoztypeform"
},
{
"@type": "Person",
"name": "David Okuniev",
"url": "https://www.linkedin.com/in/david-okuniev-a845b66/"
}
],
"address": {
"@type": "PostalAddress",
"addressCountry": "ES",
"addressLocality": "Barcelona",
"postalCode": "08017",
"streetAddress": "Carrer de Can Rabia 3 - 5, 4th floor"
}
}BBrand PresenceSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
B
71/100
Site name appears as
| Page title | Filter Button | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | Typeform |
Inconsistent — names differ across channels
Brand assets
Favicon
12/15covers apple-touch-icon
Social share image
14/20og:image set; twitter:image missing
Meta completeness
20/20Organization schema
15/15has name, logo + url
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
- Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
- 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.