Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Partial brand coverage — a few channels are missing brand signals.
D
52/100
Site name appears as
| Page title | Transifex | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | Transifex |
Consistent
Brand assets
Favicon
8/15covers SVG
Social share image
0/20Meta completeness
14/20Organization schema
15/15has name, logo + url
Contact info discoverable
5/10contact page
Findings
- Missing brand name in: og:site_name, twitter:site
- 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:image missing
- 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
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
21 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
21 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: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
Preview
www.transifex.com
Home Page - Transifex
Home Page - Transifex
WWW.TRANSIFEX.COM
Home Page - Transifex
Home Page - Transifex
Home Page - Transifex
www.transifex.com
www.transifex.com
Home Page - Transifex
Home Page - Transifex
BStructured Data1 JSON-LD block(s) found — some improvements recommended.REVIEW
https://www.schema.orgThe @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": "https://www.schema.org",
"@type": "Organization",
"name": "Transifex",
"url": "https://www.transifex.com",
"logo": "https://www.transifex.com/hubfs/Transifex%20Website/Transifex%20by%20XTM%20Logos/transifex_by_xtm_logo_dark_vertical.svg",
"sameAs": [
"https://www.linkedin.com/company/transifex/",
"https://twitter.com/transifex",
"https://www.facebook.com/Transifex/"
],
"description": "Transifex is a cloud-based localization platform designed to help businesses and developers manage the translation of digital content and software across multiple languages. It supports continuous localization with robust API integration, collaboration tools, and automated workflows.",
"address": {
"@type": "PostalAddress",
"streetAddress": "101 Jefferson Drive, 1st Floor",
"addressLocality": "Menlo Park",
"addressRegion": "CA",
"postalCode": "94025",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "37.4832505",
"longitude": "-122.1743908"
},
"contactPoint": {
"@type": "ContactPoint",
"contactType": "Customer Support",
"email": "support@transifex.com"
}
}A+Links200 links checked, 200 healthy, 0 brokenPASS
Redirects (2)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://docs.github.com/en/github/site-p... | https://docs.github.com/en/github/site-p... | <a> | 0 |
| https://www.intercom.com/terms-and-polic... | https://www.intercom.com/terms-and-polic... | <a> | 0 |