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
Your brand name differs across channels — visitors see inconsistent identity.
D
47/100
Site name appears as
| Page title | Google Workspace Updates: New community features for Google Chat and an update on Currents | |
| og:site_name | Workspace Updates Blog | |
| twitter:site | Google Workspace Updates | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
8/15single size only
Social share image
20/20og:image + twitter:image set
Meta completeness
14/20Organization schema
0/15Contact info discoverable
0/10no contact info discoverable
Findings
- Brand name differs across channels — users see inconsistent identity
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- No Organization schema — Google can't render your logo in the knowledge panel
- No discoverable contact info — trust signal is weak, legal risk is higher in regulated regions
How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.
BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
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
91 charsTitles over 60 characters may be truncated in social sharing previews.
25–60 charsog:title borderline-too-long — Facebook/LinkedIn may truncate. Aim for ~60-70 characters max.
Source: Open Graph Protocol
Preview
.png)
plus.google.com
Google Workspace Updates: New community features for Google Chat and an update on Currents
No description
Title will be truncated (91 chars / 70 max)
- twitter:card — summary
- twitter:title — Google Workspace Updates: New community features for Google Chat and an update on Currents
- twitter:description — Add twitter:description to give the preview body text
- twitter:image — https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEil-tQSvWkISdvbujn818sEroZRYYKpRGceE-TwpWRdVewQPlU0imIwcmg0...
Title will be truncated on Twitter/X (91 chars, max 70)
→ Shorten the title to ≤70 characters
.png)
PLUS.GOOGLE.COM
Google Workspace Updates: New community features for Google Chat and an update on Currents
No description
Title will be truncated (91 chars / 60 max)
- og:title — Google Workspace Updates: New community features for Google Chat and an update on Currents
- og:description — Add og:description to give the preview body text
- og:image — https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEil-tQSvWkISdvbujn818sEroZRYYKpRGceE-TwpWRdVewQPlU0imIwcmg0...
- og:type — article
- og:url — http://workspaceupdates.googleblog.com/2023/04/new-community-features-for-google-chat-and-an-update-currents%20.html
- og:site_name — Workspace Updates Blog
Title will be truncated on Facebook (91 chars, max 60)
→ Shorten og:title to ≤60 characters
.png)
Google Workspace Updates: New community features for Google Chat and an update on Currents
plus.google.com
- og:title — Google Workspace Updates: New community features for Google Chat and an update on Currents
- og:description — Add og:description to give the preview body text
- og:image — https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEil-tQSvWkISdvbujn818sEroZRYYKpRGceE-TwpWRdVewQPlU0imIwcmg0...
plus.google.com
Google Workspace Updates: New community features for Google Chat and an update on Currents
No description
.png)
- og:title — Google Workspace Updates: New community features for Google Chat and an update on Currents
- og:description — Add og:description to give the preview body text
- og:image — https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEil-tQSvWkISdvbujn818sEroZRYYKpRGceE-TwpWRdVewQPlU0imIwcmg0...
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 DataActionNo structured data (JSON-LD) found.REVIEW
Adding structured data helps search engines understand your content and can enable rich results.
Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.
Learn more ▾ ▴
Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.
Source: Google Search Central / schema.org
No structured data found
Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.
Common types include:
- WebSite — your site identity and search box
- Organization — your company information
- Article — blog posts and news articles
- Product — e-commerce product pages
- BreadcrumbList — navigation paths
ALinks139 links checked, 137 healthy, 0 brokenPASS
Redirects (1)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://developers.googleblog.com/2023/0... | https://developers.googleblog.com/2023/0... | <a> | 0 |