Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.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
36/100
Site name appears as
| Page title | Brevo: Email & SMS Marketing, CRM & Automation Platform | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
8/15covers SVG
Social share image
0/20Meta completeness
14/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
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- og:image 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.
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
The og:url tag specifies the canonical URL for the shared content.
Without og:url, social platforms infer the canonical URL — often picking a tracking-param variant that pollutes share counts.
Learn more ▾ ▴
og:url tells the social platform which URL to count this share against. Without it, platforms use the literal URL the user pasted (which may include utm_* parameters, ref codes, etc.). Setting og:url to the canonical form keeps share-count attribution clean.
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.brevo.com
Brevo: Email & SMS Marketing, CRM & Automation Platform
Brevo is the most intuitive all-in-one customer engagement platform: email and SMS marketing, automation, CRM, live chat, and transactional email. Try it free.
WWW.BREVO.COM
Brevo: Email & SMS Marketing, CRM & Automation Platform
Brevo is the most intuitive all-in-one customer engagement platform: email and SMS marketing, automation, CRM, live chat, and transactional email. Try it free.
Brevo: Email & SMS Marketing, CRM & Automation Platform
www.brevo.com
www.brevo.com
Brevo: Email & SMS Marketing, CRM & Automation Platform
Brevo is the most intuitive all-in-one customer engagement platform: email and SMS marketing, automation, CRM, live chat, and transactional email. Try it free.
ALinks200 links checked, 199 healthy, 1 brokenPASS
Broken Links (1)
| Status | URL | Found in | Error |
|---|---|---|---|
| 400 | https://metrics.brevo.com | <link> | Bad Request |
Redirects (1)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://www.brevo.com/en | https://www.brevo.com/en | <a> | 0 |
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
AStructured Data1 JSON-LD block(s) found — structured data is well configured.PASS
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": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"name": "Brevo",
"url": "https://www.brevo.com/",
"logo": false,
"sameAs": [
"https://www.linkedin.com/company/brevo/",
"https://x.com/brevo_official",
"https://www.instagram.com/brevo/",
"https://www.youtube.com/@brevo_official",
"https://www.facebook.com/brevo.official"
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "",
"contactType": "Customer Service"
},
"address": {
"@type": "PostalAddress",
"streetAddress": "823 Congress Avenue Suite 300",
"addressLocality": "Austin",
"postalCode": "TX 78701",
"addressCountry": "United States"
}
}
]
}