Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FOpen GraphActionOpen Graph tags need attention — social sharing previews may be incomplete.FIX
https://au.com/adobe/dynamicmedia/deliver/dm-aid--4cdb48de-4176-4301-bc9f-e57af18db5d4/au_logo_400x400.gif?preferwebp=true&quality=90The 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:title tag controls the title shown in social sharing previews.
Without og:title, social shares fall back to the <title> tag — usually awkwardly truncated or branded for SEO not social.
Learn more ▾ ▴
og:title controls what appears as the headline in social-share cards (Twitter, Facebook, LinkedIn, Slack, iMessage). When omitted, platforms fall back to <title>, which is usually optimized for SEO (longer, brand-suffixed) and reads badly in social context. A 50-60-character og:title gives a clean preview.
Source: Open Graph Protocol
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:site_name tag displays the website name in social previews.
Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.
Learn more ▾ ▴
og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.
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
au.com
No title set
No description
- 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 — falling back from og:image
twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
AU.COM
No title set
No description
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://au.com/adobe/dynamicmedia/deliver/dm-aid--4cdb48de-4176-4301-bc9f-e57af18db5d4/au_logo_400x400.gif?preferwebp...
- og:type — company
- og:url — https://www.au.com/
- og:site_name — Add og:site_name — Recommended — site-level brand line in the preview
No title set
au.com
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://au.com/adobe/dynamicmedia/deliver/dm-aid--4cdb48de-4176-4301-bc9f-e57af18db5d4/au_logo_400x400.gif?preferwebp...
au.com
No title set
No description
- og:title — falling back from <title>
- og:description — falling back from <meta name=description>
- og:image — https://au.com/adobe/dynamicmedia/deliver/dm-aid--4cdb48de-4176-4301-bc9f-e57af18db5d4/au_logo_400x400.gif?preferwebp...
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
Partial brand coverage — a few channels are missing brand signals.
F
39/100
Site name appears as
| Page title | au | |
| og:site_name | — | |
| twitter:site | — | |
| Organization.name | — |
Consistent
Brand assets
Favicon
8/15single size only
Social share image
14/20og:image set; twitter:image missing
Meta completeness
8/20Organization schema
4/15has logo + url
Contact info discoverable
0/10no contact info discoverable
Findings
- Missing brand name in: og:site_name, twitter:site, Organization.name
- 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
- og:title missing
- twitter:card missing
- 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.
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 "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",
"@type": "Organization",
"url": "https://www.au.com/",
"logo": "https://www.au.com/etc.clientlibs/au-com/clientlibs/clientlib-site/resources/images/header/header_au_logo.png"
}