Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DLinksAction118 links checked, 110 healthy, 8 brokenFIX
Broken Links (8)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://securepubads.g.doubleclick.net | <link> | Not Found |
| 400 | https://storage.googleapis.com | <link> | Bad Request |
| 404 | https://www.yourdictionary.com/about/terms-of-use.... | <a> | Not Found |
| 404 | https://www.yourdictionary.com/about/privacy.html | <a> | Not Found |
| 404 | https://wordfinder.yourdictionary.com/saved-words/ | <a> | Not Found |
| 404 | https://www.yourdictionary.com/about/contact.html | <a> | Not Found |
| 404 | https://www.yourdictionary.com/about/editorial-pol... | <a> | Not Found |
| ERR | about:blank | <iframe> | Get "about:blank": unsupported protocol ... |
FOpen GraphActionNo Open Graph tags found — social sharing previews will be generic.FIX
Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.
Without Open Graph tags, social shares show a broken or empty preview card.
Learn more ▾ ▴
When someone shares your URL on Facebook, LinkedIn, Slack, iMessage, or any modern chat app, the preview comes from <meta property="og:*"> tags. Without them you get either no card or whatever fragment the social platform guesses — usually unflattering. The four core og: tags (title, description, image, url) cover what every major platform actually reads.
Source: Open Graph Protocol
Preview
yourdictionary.com
No title set
No description
Title will be truncated (85 chars / 70 max)
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from <title>
- twitter:description — falling back from <meta name=description>
- twitter:image — Add twitter:image — preview card without an image looks broken
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
Title will be truncated on Twitter/X (85 chars, max 70)
→ Shorten the title to ≤70 characters
No preview image for Twitter/X
→ Add og:image or twitter:image (≥300×157 for summary_large_image)
YOURDICTIONARY.COM
No title set
No description
Title will be truncated (85 chars / 60 max)
Description will be truncated (166 chars / 155 max)
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
- og:type — Add og:type — Recommended — tells Facebook the content category
- og:url — Add og:url — Recommended — canonical URL for the share
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview
Title will be truncated on Facebook (85 chars, max 60)
→ Shorten og:title to ≤60 characters
Description will be truncated on Facebook (166 chars, max 155)
→ Tighten og:description to ≤155 characters
No preview image for Facebook
→ Add og:image (recommended 1200×630)
No title set
yourdictionary.com
Description will be truncated (166 chars / 150 max)
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — Add og:image — preview card without an image looks broken
Description will be truncated on LinkedIn (166 chars, max 150)
→ Tighten og:description to ≤150 characters
No preview image for LinkedIn
→ Add og:image (recommended 1200×627)
yourdictionary.com
No title set
No description
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- 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 | — | — | — |
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
37/100
Site name appears as
| Page title | YourDictionary: Definitions and Meanings From Over a Dozen Trusted Dictionary Sources | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | YourDictionary |
Inconsistent — names differ across channels
Brand assets
Favicon
8/15single size only
Social share image
0/20Meta completeness
4/20Organization schema
15/15has name, logo + url
Contact info discoverable
5/10contact page
Findings
- Brand name differs across channels — users see inconsistent identity
- No social share image — shared links render as bare URLs
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- og:title missing
- og:image missing
- twitter:card missing
- 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.
BStructured Data2 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
JSON-LD Blocks
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "YourDictionary",
"url": "https://www.yourdictionary.com/",
"logo": "https://cdn.yourdictionary.com/images/logo.png",
"address": {
"@type": "PostalAddress",
"addressLocality": "Vero Beach, FL",
"postalCode": "32960-4706",
"streetAddress": "1275 US Highway 1 Unit 2-6084"
},
"email": "admin@yourdictionary.com",
"sameAs": [
"https://www.facebook.com/yourdictionary",
"https://x.com/YourDictionary",
"https://www.instagram.com/your_dictionary/",
"https://www.linkedin.com/showcase/your_dictionary/",
"https://www.pinterest.com/yourdictionary/",
"https://www.crunchbase.com/organization/yourdictionary"
],
"publishingPrinciples": "https://www.yourdictionary.com/about/editorial-policy",
"parentOrganization": {
"@type": "Organization",
"@id": "https://www.lovetoknowmedia.com/",
"name": "LoveToKnow Media",
"url": "https://www.lovetoknowmedia.com/",
"sameAs": [
"https://www.linkedin.com/company/lovetoknowmedia/",
"https://www.instagram.com/lovetoknowmedia/",
"https://www.facebook.com/lovetoknowmedia/about",
"https://x.com/lovetoknowmedia",
"https://www.crunchbase.com/organization/lovetoknow-corp"
],
"logo": {
"@type": "ImageObject",
"url": "https://www.lovetoknowmedia.com/wp-content/uploads/2021/05/LTK_MEDIA_Logo-2.png"
},
"address": {
"@type": "PostalAddress",
"addressLocality": "Vero Beach, FL",
"postalCode": "32960-4706",
"streetAddress": "1275 US Highway 1 Unit 2-6084"
}
}
}{
"@context": "https://schema.org/",
"@type": "WebSite",
"url": "https://www.yourdictionary.com",
"name": "YourDictionary",
"potentialAction": {
"@type": "SearchAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https://www.yourdictionary.com/search/result?q={search_term_string}"
},
"query-input": "required name=search_term_string"
}
}