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
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
61 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
Preview
fareharbor.com
FareHarbor | Online Booking Software for Tours and Activities
No description
- twitter:card — summary
- twitter:title — FareHarbor | Online Booking Software for Tours and Activities
- twitter:description — falling back from <meta name=description>
- twitter:image — https://pages.fareharbor.com/wp-content/uploads/sites/278/2016/10/fh-og-250.png
FAREHARBOR.COM
FareHarbor | Online Booking Software for Tours and Activities
No description
Title will be truncated (61 chars / 60 max)
Description will be truncated (157 chars / 155 max)
- og:title — FareHarbor | Online Booking Software for Tours and Activities
- og:description — falling back from <meta name=description>
- og:image — https://pages.fareharbor.com/wp-content/uploads/sites/278/2016/10/fh-og-250.png
- og:type — website
- og:url — https://fareharbor.com/
- og:site_name — FareHarbor
Title will be truncated on Facebook (61 chars, max 60)
→ Shorten og:title to ≤60 characters
Description will be truncated on Facebook (157 chars, max 155)
→ Tighten og:description to ≤155 characters
FareHarbor | Online Booking Software for Tours and Activities
fareharbor.com
Description will be truncated (157 chars / 150 max)
- og:title — FareHarbor | Online Booking Software for Tours and Activities
- og:description — falling back from <meta name=description>
- og:image — https://pages.fareharbor.com/wp-content/uploads/sites/278/2016/10/fh-og-250.png
Description will be truncated on LinkedIn (157 chars, max 150)
→ Tighten og:description to ≤150 characters
fareharbor.com
FareHarbor | Online Booking Software for Tours and Activities
No description
- og:title — FareHarbor | Online Booking Software for Tours and Activities
- og:description — falling back from <meta name=description>
- og:image — https://pages.fareharbor.com/wp-content/uploads/sites/278/2016/10/fh-og-250.png
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 | — | — | — |
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
58/100
Site name appears as
| Page title | Filter Icon | |
| og:site_name | FareHarbor | |
| twitter:site | @fareharbor | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
20/20og:image + twitter:image set
Meta completeness
14/20Organization schema
4/15has logo + url
Contact info discoverable
0/10no contact info discoverable
Findings
- Brand name differs across channels — users see inconsistent identity
- 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.
ALinks108 links checked, 107 healthy, 1 brokenPASS
Broken Links (1)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://core.service.elfsight.com | <link> | Not Found |
Redirects (3)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://ajax.googleapis.com | https://ajax.googleapis.com | <link> | 0 |
| https://compass.fareharbor.com/ | https://compass.fareharbor.com/ | <a> | 0 |
| https://fareharbor.com/legal/ | https://fareharbor.com/legal/ | <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 "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": "http://schema.org",
"@type": "Organization",
"url": "https://fareharbor.com",
"logo": "https://pages.fareharbor.com/wp-content/uploads/sites/278/2016/10/fh-og-250.png"
}