Content
· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FImage OptimizationAction5 issues found across 6 imagesFIX
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
35/100
Site name appears as
| Page title | Make A Webiste | |
| og:site_name | Make A Webiste | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
12/15covers apple-touch-icon
Social share image
0/20Meta completeness
8/20Organization schema
0/15Contact info discoverable
5/10tel link
Findings
- Missing brand name in: twitter:site, Organization.name
- 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
- No Organization schema — Google can't render your logo in the knowledge panel
- 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: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
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
21 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
Preview
www.sarasotarvrepair.com
Home | Make A Webiste
No description
- twitter:card — summary_large_image
- twitter:title — Home | Make A Webiste
- twitter:description — Add twitter:description to give the preview body text
- twitter:image — Add twitter:image — preview card without an image looks broken
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
WWW.SARASOTARVREPAIR.COM
Home | Make A Webiste
No description
- og:title — Home | Make A Webiste
- og:description — Add og:description to give the preview body text
- og:image — Add og:image — preview card without an image looks broken
- og:type — website
- og:url — https://www.sarasotarvrepair.com
- og:site_name — Make A Webiste
No preview image for Facebook
→ Add og:image (recommended 1200×630)
Home | Make A Webiste
www.sarasotarvrepair.com
- og:title — Home | Make A Webiste
- og:description — Add og:description to give the preview body text
- og:image — Add og:image — preview card without an image looks broken
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
www.sarasotarvrepair.com
Home | Make A Webiste
No description
- og:title — Home | Make A Webiste
- og:description — Add og:description to give the preview body text
- og:image — Add og:image — preview card without an image looks broken
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 | — | — | — |
BStructured Data1 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
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": "WebSite",
"name": "Make A Webiste",
"url": "https://www.sarasotarvrepair.com"
}