Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FOpen GraphActionNo Open Graph tags found — social sharing previews will be generic.FIX
Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.
Without Open Graph tags, social shares show a broken or empty preview card.
Learn more ▾ ▴
When someone shares your URL on Facebook, LinkedIn, Slack, iMessage, or any modern chat app, the preview comes from <meta property="og:*"> tags. Without them you get either no card or whatever fragment the social platform guesses — usually unflattering. The four core og: tags (title, description, image, url) cover what every major platform actually reads.
Source: Open Graph Protocol
Preview
zend.com
No title set
No description
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from <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)
ZEND.COM
No title set
No description
Title will be truncated (63 chars / 60 max)
- og:title — falling back from <title>
- 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
Title will be truncated on Facebook (63 chars, max 60)
→ Shorten og:title to ≤60 characters
No preview image for Facebook
→ Add og:image (recommended 1200×630)
No title set
zend.com
- og:title — falling back from <title>
- 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)
zend.com
No title set
No description
- og:title — falling back from <title>
- 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
33/100
Site name appears as
| Page title | Zend | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
0/20Meta completeness
4/20Organization schema
4/15Organization schema present but missing all recommended fields
Contact info discoverable
5/10contact page
Findings
- Missing brand name in: og:site_name, twitter:site, Organization.name
- No social share image — shared links render as bare URLs
- og:title missing
- og:image missing
- 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.
CStructured DataAction2 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
The "name" property is required for the Organization schema type.
Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.
Learn more ▾ ▴
Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.
Source: Google Search Central / schema.org
Adding "url" 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
Adding "logo" 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
Adding "sameAs" 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/",
"@id": "https://fast.wistia.net/embed/iframe/rzc8i1qjg6",
"@type": "VideoObject",
"duration": "PT1M51S",
"name": "Zend Enterprise Web Platform",
"thumbnailUrl": "https://embed-ssl.wistia.com/deliveries/d1199b30b4b79e6216e91f44a317f3f2.jpg?image_crop_resized=640x360",
"embedUrl": "https://fast.wistia.net/embed/iframe/rzc8i1qjg6",
"uploadDate": "2025-12-02T14:09:42.000Z",
"description": "The Zend Enterprise Web Platform unifies security, scaling, and observability for mission‑critical PHP apps. Reduce complexity, stop firefighting, and modernize with confidence.",
"contentUrl": "https://embed-ssl.wistia.com/deliveries/59a45a3f77b7c146bcdd3743d936a061f468c7eb.m3u8",
"transcript": "Enterprise PHP applications are the backbone of your business. But managing large deployments means constant challenges, security threats, performance bottlenecks, and no clear path forward as you plan for future growth. It's time for a simplified approach. Meet the Zend Enterprise Web Platform, a custom-configured command center for securing, scaling, and observing mission-critical PHP applications.\n\nThe Enterprise Web Platform collects everything, delivering the simplicity of PaaS and PHP secure runtimes, auto-scaling, and real time observability, all without lock-in or unexpected costs.\n\nGain complete observability with unified metrics, logging, and real-time code tracing, all accessible from an easy to use and customizable dashboard. Harden your applications with a security-first architecture built on CIS-benchmarked images and long-term support for EOL PHP versions.\n\nSimplify scaling via separate web and queue worker pools, data caching, static content caching, and session clustering. \n\nAnd get turnkey configuration services and expert-led onboarding alongside on-demand support from the team who built the platform.\n\nThe Enterprise Web Platform gives a predictable, managed experience while you preserve full control of your environment, meaning you can deploy anywhere, scale effortlessly, and stay compliant with zero operational overhead. Stop firefighting, reduce complexity, and modernize with confidence. See everything and fix anything. Schedule your custom demo today.",
"potentialAction": {
"@type": "SeekToAction",
"target": "https://www.zend.com/?wtime={seek_to_second_number}",
"startOffset-input": "required name=seek_to_second_number"
}
}{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://www.zend.com",
"sameAs": "https://www.linkedin.com/company/perforce-zend/,https://www.youtube.com/user/ZendTechnologies",
"description": "Zend by Perforce delivers enterprise-grade PHP solutions designed to support mission-critical applications. With long-term supported runtimes, performance tuning, and robust development tools, Zend empowers organizations to build, deploy, and maintain secure, scalable PHP environments with confidence.",
"name": "Perforce Zend",
"url": "https://www.zend.com",
"logo": {
"@type": "ImageObject",
"representativeOfPage": "True",
"url": "https://www.zend.com/sites/default/files/logo-zend-reg.svg"
}
}
]
}