Content
· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.DLinksAction182 links checked, 175 healthy, 6 brokenFIX
Broken Links (8)
| Status | URL | Found in | Error |
|---|---|---|---|
| ERR | https://b.pub.network/ | <link> | Get "https://b.pub.network/": resolve b.... |
| 404 | https://c.pub.network/ | <link> | Not Found |
| 404 | https://d.pub.network/ | <link> | Not Found |
| ERR | about:blank | <iframe> | Get "about:blank": unsupported protocol ... |
| 404 | https://d.turn.com/r/dd/id/L2NzaWQvMS9jaWQvMTc0ODI... | <img> | Not Found |
| 404 | https://www.upi.com/img/upi-fb.png | <meta> | Not Found |
| 403 | https://btloader.com/ | <link> | Forbidden |
| 403 | https://api.btloader.com/ | <link> | Forbidden |
Redirects (1)
| URL | Destination | Found in | Hops |
|---|---|---|---|
| https://eb2.3lift.com/sync? | https://eb2.3lift.com/sync? | <iframe> | 0 |
DOpen GraphActionOpen Graph tags need attention — social sharing previews may be incomplete.FIX
https://www.upi.com/img/upi-fb.pngThe 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
76 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
The og:url tag specifies the canonical URL for the shared content.
Without og:url, social platforms infer the canonical URL — often picking a tracking-param variant that pollutes share counts.
Learn more ▾ ▴
og:url tells the social platform which URL to count this share against. Without it, platforms use the literal URL the user pasted (which may include utm_* parameters, ref codes, etc.). Setting og:url to the canonical form keeps share-count attribution clean.
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

upi.com
Top News, Latest headlines, Latest News, World News & U.S News - UPI.com
No description
Title will be truncated (76 chars / 70 max)
- 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">
Title will be truncated on Twitter/X (76 chars, max 70)
→ Shorten the title to ≤70 characters

UPI.COM
Top News, Latest headlines, Latest News, World News & U.S News - UPI.com
No description
Title will be truncated (76 chars / 60 max)
- og:title — Top News, Latest headlines, Latest News, World News & U.S News - UPI.com
- og:description — falling back from <meta name=description>
- og:image — https://www.upi.com/img/upi-fb.png
- 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 — UPI
Title will be truncated on Facebook (76 chars, max 60)
→ Shorten og:title to ≤60 characters

Top News, Latest headlines, Latest News, World News & U.S News - UPI.com
upi.com
Description will be truncated (152 chars / 150 max)
- og:title — Top News, Latest headlines, Latest News, World News & U.S News - UPI.com
- og:description — falling back from <meta name=description>
- og:image — https://www.upi.com/img/upi-fb.png
Description will be truncated on LinkedIn (152 chars, max 150)
→ Tighten og:description to ≤150 characters
upi.com
Top News, Latest headlines, Latest News, World News & U.S News - UPI.com
No description

- og:title — Top News, Latest headlines, Latest News, World News & U.S News - UPI.com
- og:description — falling back from <meta name=description>
- og:image — https://www.upi.com/img/upi-fb.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 | ⚠ | — | — | — |
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
40/100
Site name appears as
| Page title | UPI.com | |
| og:site_name | UPI | |
| 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
0/15Contact 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
- 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.
A+Mixed ContentNo mixed content detected — all resources use HTTPS.PASS
A+Structured Data1 JSON-LD block(s) found — structured data is well configured.PASS
JSON-LD Blocks
{
"@context": "https://schema.org",
"@type": "Website",
"url": "https://www.upi.com",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://www.upi.com/",
"url": "https://www.upi.com/"
},
"publisher": {
"@type": "NewsMediaOrganization",
"name": "UPI",
"logo": {
"@type": "ImageObject",
"url": "https://www.upi.com/img/upi-logo.png",
"width": 448,
"height": 448
}
},
"potentialAction": {
"@type": "SearchAction",
"target": "https://www.upi.com/search?ss={search_term_string}",
"query-input": "required name=search_term_string"
}
}