Content
· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FImage OptimizationAction5 issues found across 88 imagesFIX
BOpen GraphOpen Graph tags are partially configured — some improvements recommended.REVIEW
https://eemeli.ee/img/EEMELI_og.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
63 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
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
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.
Without twitter:card, Twitter renders posts as plain text — no preview image, no structured layout.
Learn more ▾ ▴
Twitter requires `<meta name="twitter:card" content="summary_large_image">` (or summary) to render share-cards at all. Without it, links appear as raw text and engagement plummets vs cards. Twitter also falls back to og:image if twitter:image isn't set, so configure both.
Source: Twitter Developer Platform
Preview
www.eemeli.ee
E-pood: tööriistad, varuosad, aia- ja tööstuskaubad - Eemeli OÜ
Eemeli veebipood – Stiilne. Praktiline. Uuenduslik. Soodsad hinnad ja lai kaubavalik! Lihtne ostuprotsess ja kiire tarne! Järelmaks mõne sekundiga! Teil on toodet vaja - meil on olemas!
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from og:title
- twitter:description — falling back from og:description
- twitter:image — falling back from og:image
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
WWW.EEMELI.EE
E-pood: tööriistad, varuosad, aia- ja tööstuskaubad - Eemeli OÜ
Eemeli veebipood – Stiilne. Praktiline. Uuenduslik. Soodsad hinnad ja lai kaubavalik! Lihtne ostuprotsess ja kiire tarne! Järelmaks mõne sekundiga! Teil on toodet vaja - meil on olemas!
Title will be truncated (68 chars / 60 max)
Description will be truncated (190 chars / 155 max)
- og:title — E-pood: tööriistad, varuosad, aia- ja tööstuskaubad - Eemeli OÜ
- og:description — Eemeli veebipood – Stiilne. Praktiline. Uuenduslik. Soodsad hinnad ja lai kaubavalik! Lihtne ostuprotsess ja kiire ta...
- og:image — https://eemeli.ee/img/EEMELI_og.jpg
- og:type — website
- og:url — https://eemeli.ee
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview
Title will be truncated on Facebook (68 chars, max 60)
→ Shorten og:title to ≤60 characters
Description will be truncated on Facebook (190 chars, max 155)
→ Tighten og:description to ≤155 characters
E-pood: tööriistad, varuosad, aia- ja tööstuskaubad - Eemeli OÜ
www.eemeli.ee
Description will be truncated (190 chars / 150 max)
- og:title — E-pood: tööriistad, varuosad, aia- ja tööstuskaubad - Eemeli OÜ
- og:description — Eemeli veebipood – Stiilne. Praktiline. Uuenduslik. Soodsad hinnad ja lai kaubavalik! Lihtne ostuprotsess ja kiire ta...
- og:image — https://eemeli.ee/img/EEMELI_og.jpg
Description will be truncated on LinkedIn (190 chars, max 150)
→ Tighten og:description to ≤150 characters
www.eemeli.ee
E-pood: tööriistad, varuosad, aia- ja tööstuskaubad - Eemeli OÜ
Eemeli veebipood – Stiilne. Praktiline. Uuenduslik. Soodsad hinnad ja lai kaubavalik! Lihtne ostuprotsess ja kiire tarne! Järelmaks mõne sekundiga! Teil on toodet vaja - meil on olemas!
- og:title — E-pood: tööriistad, varuosad, aia- ja tööstuskaubad - Eemeli OÜ
- og:description — Eemeli veebipood – Stiilne. Praktiline. Uuenduslik. Soodsad hinnad ja lai kaubavalik! Lihtne ostuprotsess ja kiire ta...
- og:image — https://eemeli.ee/img/EEMELI_og.jpg
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 DataAction1 JSON-LD block(s) found — some improvements recommended.REVIEW
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
{
"\u003C?php $__contextArgs = [];\nif (context()-\u003Ehas($__contextArgs[0])) :\nif (isset($value)) { $__contextPrevious[] = $value; }\n$value = context()-\u003Eget($__contextArgs[0]); ?\u003E": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://eemeli.ee#org",
"name": "Eemeli OÜ",
"url": "https://eemeli.ee",
"logo": "https://eemeli.ee/img/eemeli_logo.png",
"email": "epood@eemeli.ee",
"sameAs": [
"https://www.facebook.com/Eemeli-As-946956348660890/"
]
},
{
"@type": "Store",
"@id": "https://eemeli.ee#store-johvi",
"name": "Eemeli Jõhvi kauplus",
"url": "https://eemeli.ee",
"image": "https://eemeli.ee/img/eemeli_logo.png",
"telephone": "+372 5662 4624",
"email": "johvi@eemeli.ee",
"address": {
"@type": "PostalAddress",
"streetAddress": "Jordi tee 1",
"addressLocality": "Jõhvi",
"addressCountry": "EE"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "08:00",
"closes": "17:00"
}
],
"parentOrganization": {
"@id": "https://eemeli.ee#org"
}
},
{
"@type": "Store",
"@id": "https://eemeli.ee#store-narva",
"name": "Eemeli Narva kauplus",
"url": "https://eemeli.ee",
"image": "https://eemeli.ee/img/eemeli_logo.png",
"telephone": "+372 5650 9123",
"email": "narva@eemeli.ee",
"address": {
"@type": "PostalAddress",
"streetAddress": "Peaalajaama 8",
"addressLocality": "Narva",
"addressCountry": "EE"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "08:30",
"closes": "17:30"
}
],
"parentOrganization": {
"@id": "https://eemeli.ee#org"
}
},
{
"@type": "WebSite",
"@id": "https://eemeli.ee#website",
"name": "Eemeli e-pood",
"url": "https://eemeli.ee",
"inLanguage": "et",
"publisher": {
"@id": "https://eemeli.ee#org"
},
"potentialAction": {
"@type": "SearchAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https://eemeli.ee/et/search?search={search_term_string}"
},
"query-input": "required name=search_term_string"
}
}
]
}CBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsREVIEW
Brand Presence
Partial brand coverage — a few channels are missing brand signals.
C
57/100
Site name appears as
| Page title | Eemeli OÜ | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
14/20og:image set; twitter:image missing
Meta completeness
14/20Organization schema
4/15Organization schema present but missing all recommended fields
Contact info discoverable
5/10mailto link + tel link
Findings
- Missing brand name in: og:site_name, twitter:site, Organization.name
- Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
- 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.