Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
https://www.algolia.com/files/live/sites/algolia-assets/files/opengraph/algolia-opengraph-image.jpgThe 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
4 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
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.algolia.com
Home
18,000+ organizations trust Algolia to build intuitive, adaptive, high-performing experiences with a unified AI search & retrieval platform spanning agentic, generative, and search.

WWW.ALGOLIA.COM
Home
18,000+ organizations trust Algolia to build intuitive, adaptive, high-performing experiences with a unified AI search & retrieval platform spanning agentic, generative, and search.

Home
www.algolia.com
www.algolia.com
Home
18,000+ organizations trust Algolia to build intuitive, adaptive, high-performing experiences with a unified AI search & retrieval platform spanning agentic, generative, and search.

CStructured DataAction1 JSON-LD block(s) found — some improvements recommended.REVIEW
JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[\n {\n \"@context\": \"http://sc\n\t^...............................\n"
JSON-LD block fails to parse — Google ignores the entire block, so structured data effectively isn't there.
Learn more ▾ ▴
Common causes: trailing comma, single quotes instead of double, unescaped quote in a string value. Validate at https://validator.schema.org/ or Search Console's Rich Results Test.
Source: schema.org / Google Search Central
JSON-LD Blocks
[
{
"@context": "http://schema.org",
"@type": "Organization",
"name": "Algolia",
"url": "https://www.algolia.com/",
"logo": "https://www.algolia.com/algolia-logo-blue.svg",
"image": "https://www.algolia.com/files/live/sites/algolia-assets/files/opengraph/algolia-opengraph-image.jpg",
"description": "Fast, reliable and modern Search & Discovery",
"address": {
"@type": "PostalAddress",
"streetAddress": "3790 El Camino Real, Unit #518",
"addressLocality": "Palo Alto",
"addressRegion": "California",
"postalCode": "94306",
"addressCountry": "USA"
},
"sameAs": [
"https://www.linkedin.com/company/algolia/",
"https://www.facebook.com/algolia/",
"https://www.github.com/Algolia/",
"https://www.youtube.com/user/Algolia/",
"https://www.twitter.com/Algolia/",
"https://www.instagram.com/algoliahq/"
],
"contactPoint": [
{
"@type": "ContactPoint",
"url": "https://www.algolia.com/demorequest/",
"contactType": "prospects"
},
{
"@type": "ContactPoint",
"url": "https://www.algolia.com/contact/enterprise/",
"contactType": "enterprise"
},
{
"@type": "ContactPoint",
"url": "https://www.algolia.com/for-open-source/",
"contactType": "open source"
}
]
},
{
"@context": "http://schema.org",
"@type": "WebSite",
"url": "https://www.algolia.com/",
"name": "Algolia",
"alternateName": "AlgoliaSearch",
"potentialAction": [
{
"@type": "SearchAction",
"target": "https://www.algolia.com/search/?query={search_term_string}",
"query-input": "required name=search_term_string"
}
]
},
{
"@context": "http://schema.org",
"@type": "SpeakableSpecification",
"xpath": [
"/html/head/title",
"/html/head/meta[@name='description']/@content"
]
}
]CBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
C
62/100
Site name appears as
| Page title | Filter Icon | |
| og:site_name | — | |
| twitter:site | @algolia | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
8/15covers SVG
Social share image
20/20og:image + twitter:image set
Meta completeness
20/20Organization schema
4/15Organization schema present but missing all recommended fields
Contact info discoverable
5/10contact page
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
- 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.
ALinks200 links checked, 199 healthy, 1 brokenPASS
Broken Links (1)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://www.algolia.com/pt-br | <a> | Not Found |
Redirects (2)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://www.algolia.com/doc/ | https://www.algolia.com/doc/ | <a> | 0 |
| https://www.algolia.com/doc/guides/getti... | https://www.algolia.com/doc/guides/getti... | <a> | 0 |