Content
· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FImage OptimizationAction5 issues found across 19 imagesFIX
FBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
F
39/100
Site name appears as
| Page title | FPV Дрон ком'юніті | |
| og:site_name | Socialdroneua | |
| twitter:site | — | |
| Organization.name | SocialDroneUA |
Inconsistent — names differ across channels
Brand assets
Favicon
12/15covers apple-touch-icon + SVG
Social share image
0/20Meta completeness
14/20Organization schema
8/15has name + url
Contact info discoverable
0/10no contact info discoverable
Findings
- Brand name differs across channels — users see inconsistent identity
- No social share image — shared links render as bare URLs
- Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
- og:image missing
- Organization schema missing logo — add a logo property pointing to a square PNG
- Consider adding contactPoint — helps appear in "contact us" rich results
- 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: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
270 charsDescriptions over 200 characters may be truncated in social sharing previews.
55–200 charsog:description borderline-too-long — social platforms truncate around ~200 chars.
Source: Open Graph Protocol
Preview
socialdrone.com.ua
SocialDroneUA | FPV Дрон ком'юніті
В ком'юніті ви можете навчитись збирати FPV-дрони своїми руками для наповнення війська додатковими дронам, максимально зменшуючи вартість дрона, оскільки не треба оренду платити, заробітню платню і т.і. Дрони обов'язково проходять тестування перед відправкою у військо.
Description will be truncated (493 chars / 200 max)
- twitter:card — summary_large_image
- twitter:title — SocialDroneUA | FPV Дрон ком'юніті
- twitter:description — В ком'юніті ви можете навчитись збирати FPV-дрони своїми руками для наповнення війська додатковими дронам, максимальн...
- twitter:image — Add twitter:image — preview card without an image looks broken
Description will be truncated on Twitter/X (493 chars, max 200)
→ Tighten the description to ≤200 characters
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
SOCIALDRONE.COM.UA
SocialDroneUA | FPV Дрон ком'юніті
В ком'юніті ви можете навчитись збирати FPV-дрони своїми руками для наповнення війська додатковими дронам, максимально зменшуючи вартість дрона, оскільки не треба оренду платити, заробітню платню і т.і. Дрони обов'язково проходять тестування перед відправкою у військо.
Description will be truncated (493 chars / 155 max)
- og:title — SocialDroneUA | FPV Дрон ком'юніті
- og:description — В ком'юніті ви можете навчитись збирати FPV-дрони своїми руками для наповнення війська додатковими дронам, максимальн...
- og:image — Add og:image — preview card without an image looks broken
- og:type — website
- og:url — https://www.socialdrone.com.ua
- og:site_name — Socialdroneua
Description will be truncated on Facebook (493 chars, max 155)
→ Tighten og:description to ≤155 characters
No preview image for Facebook
→ Add og:image (recommended 1200×630)
SocialDroneUA | FPV Дрон ком'юніті
socialdrone.com.ua
Description will be truncated (493 chars / 150 max)
- og:title — SocialDroneUA | FPV Дрон ком'юніті
- og:description — В ком'юніті ви можете навчитись збирати FPV-дрони своїми руками для наповнення війська додатковими дронам, максимальн...
- og:image — Add og:image — preview card without an image looks broken
Description will be truncated on LinkedIn (493 chars, max 150)
→ Tighten og:description to ≤150 characters
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
socialdrone.com.ua
SocialDroneUA | FPV Дрон ком'юніті
В ком'юніті ви можете навчитись збирати FPV-дрони своїми руками для наповнення війська додатковими дронам, максимально зменшуючи вартість дрона, оскільки не треба оренду платити, заробітню платню і т.і. Дрони обов'язково проходять тестування перед відправкою у військо.
Description will be truncated (493 chars / 300 max)
- og:title — SocialDroneUA | FPV Дрон ком'юніті
- og:description — В ком'юніті ви можете навчитись збирати FPV-дрони своїми руками для наповнення війська додатковими дронам, максимальн...
- og:image — Add og:image — preview card without an image looks broken
Long description may be shortened by Slack (493 chars, guideline ~300)
→ Consider tightening to ~300 chars for the cleanest unfurl
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 | — | — | — |
CStructured DataAction2 JSON-LD block(s) found — some improvements recommended.REVIEW
https://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
https://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
Adding "telephone" 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 "openingHours" 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 "description" 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 "potentialAction" 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/",
"@type": "LocalBusiness",
"name": "SocialDroneUA",
"url": "https://www.socialdrone.com.ua",
"address": {
"@type": "PostalAddress",
"addressCountry": "UA"
}
}{
"@context": "https://schema.org/",
"@type": "WebSite",
"name": "Socialdroneua",
"url": "https://www.socialdrone.com.ua"
}BAutoplay Media1 autoplay media element(s) -- all mutedREVIEW
A+Links61 links checked, 61 healthy, 0 brokenPASS
Redirects (1)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://sdua.tech/request | https://sdua.tech/request | <a> | 0 |