Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DOpen GraphActionOpen Graph tags need attention — social sharing previews may be incomplete.FIX
https://www.instructure.com/sites/default/files/image/2025-07/2025-Meta-OG-thumb-ENG_0.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
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
8 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
The og:type tag helps social platforms categorize the content.
Default og:type is 'website' but the right value (article, product, profile) unlocks richer metadata fields and higher engagement.
Learn more ▾ ▴
og:type controls which other og: fields a platform respects. og:type=article enables og:article:published_time, author, and section — surfaced in news cards. og:type=product enables price/availability fields surfaced by Pinterest and shopping integrations. Default 'website' silently disables those.
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
instructure.com
Homepage
No description
- twitter:card — Add <meta name="twitter:card" content="summary_large_image">
- twitter:title — falling back from og:title
- twitter:description — falling back from <meta name=description>
- twitter:image — falling back from og:image
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
INSTRUCTURE.COM
Homepage
No description
Description will be truncated (163 chars / 155 max)
- og:title — Homepage
- og:description — falling back from <meta name=description>
- og:image — https://www.instructure.com/sites/default/files/image/2025-07/2025-Meta-OG-thumb-ENG_0.jpg
- og:type — Add og:type — Recommended — tells Facebook the content category
- og:url — https://www.instructure.com/node/1426
- og:site_name — Instructure
Description will be truncated on Facebook (163 chars, max 155)
→ Tighten og:description to ≤155 characters
Homepage
instructure.com
Description will be truncated (163 chars / 150 max)
- og:title — Homepage
- og:description — falling back from <meta name=description>
- og:image — https://www.instructure.com/sites/default/files/image/2025-07/2025-Meta-OG-thumb-ENG_0.jpg
Description will be truncated on LinkedIn (163 chars, max 150)
→ Tighten og:description to ≤150 characters
instructure.com
Homepage
No description
- og:title — Homepage
- og:description — falling back from <meta name=description>
- og:image — https://www.instructure.com/sites/default/files/image/2025-07/2025-Meta-OG-thumb-ENG_0.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 | ⚠ | — | — | — |
DBrand PresenceActionSite-name consistency, favicon, social image, meta tags, schema, and contact signalsFIX
Brand Presence
Your brand name differs across channels — visitors see inconsistent identity.
D
44/100
Site name appears as
| Page title | Instructure: Leading EdTech for K–12, Higher Ed & Business | |
| og:site_name | Instructure | |
| twitter:site | — | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
8/15single size only
Social share image
14/20og:image set; twitter:image missing
Meta completeness
8/20Organization schema
4/15Organization schema present but missing all recommended fields
Contact info discoverable
5/10contact page
Findings
- Brand name differs across channels — users see inconsistent identity
- Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
- Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
- 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.
ALinks200 links checked, 198 healthy, 2 brokenPASS
Broken Links (2)
| Status | URL | Found in | Error |
|---|---|---|---|
| 404 | https://fonts.googleapis.com | <link> | Not Found |
| 404 | https://fonts.gstatic.com | <link> | Not Found |
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 "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
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://www.instructure.com",
"url": "https://www.instructure.com",
"name": "Instructure",
"sameAs": [
"https://www.youtube.com/user/Instructure",
"https://www.facebook.com/Instructure/",
"https://x.com/Instructure",
"https://www.linkedin.com/company/instructure/"
],
"description": "Instructure is a leading educational technology company dedicated to helping people learn and grow. We provide innovative learning platforms, including Canvas LMS and Bridge, for schools, universities, and businesses.",
"telephone": "+1 801-869-5000",
"contactPoint": {
"@type": "PostalAddress",
"telephone": "+1 801-869-5000",
"email": "info@instructure.com",
"url": "https://www.instructure.com",
"contactType": "customer service"
},
"image": {
"@type": "ImageObject",
"representativeOfPage": "True",
"url": "https://www.instructure.com/sites/default/files/Instructure-logo.svg"
},
"logo": {
"@type": "ImageObject",
"representativeOfPage": "True",
"url": "https://www.instructure.com/sites/default/files/Instructure-logo.svg"
},
"address": {
"@type": "PostalAddress",
"streetAddress": "6330 S 3000 E Suite 700",
"addressLocality": "Salt Lake City",
"addressRegion": "UT",
"postalCode": "84121",
"addressCountry": "USA"
},
"brand": {
"@type": "Brand",
"name": "Instructure",
"url": "https://www.instructure.com"
}
},
{
"@type": "WebPage",
"breadcrumb": []
}
]
}