Content
· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.FImage OptimizationAction6 issues found across 12 imagesFIX
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
42/100
Site name appears as
| Page title | Mine Unmineable Coins | |
| og:site_name | Mine Unmineable Coins | |
| twitter:site | @unmineablepepe | |
| Organization.name | — |
Inconsistent — names differ across channels
Brand assets
Favicon
15/15covers multiple sizes + apple-touch-icon
Social share image
14/20og:image set; twitter:image missing
Meta completeness
8/20Organization schema
0/15Contact info discoverable
0/10no contact info discoverable
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
- twitter:card missing
- No Organization schema — Google can't render your logo in the knowledge panel
- 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.
COpen GraphActionOpen Graph tags are partially configured — some improvements recommended.REVIEW
https://unmineable.wordpress.com/wp-content/uploads/2025/07/cropped-photo_2025-07-01_16-19-53-1.jpg?w=200The 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
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

unmineable.wordpress.com
crypto mining – Mine Unmineable Coins
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">

UNMINEABLE.WORDPRESS.COM
crypto mining – Mine Unmineable Coins
No description
- og:title — crypto mining – Mine Unmineable Coins
- og:description — falling back from <meta name=description>
- og:image — https://unmineable.wordpress.com/wp-content/uploads/2025/07/cropped-photo_2025-07-01_16-19-53-1.jpg?w=200
- og:type — website
- og:url — https://unmineable.wordpress.com/category/crypto-mining/
- og:site_name — Mine Unmineable Coins
og:image is below recommended size (200×200)
→ Upload an image ≥1200×630 for the large preview card

crypto mining – Mine Unmineable Coins
unmineable.wordpress.com
- og:title — crypto mining – Mine Unmineable Coins
- og:description — falling back from <meta name=description>
- og:image — https://unmineable.wordpress.com/wp-content/uploads/2025/07/cropped-photo_2025-07-01_16-19-53-1.jpg?w=200
unmineable.wordpress.com
crypto mining – Mine Unmineable Coins
No description

- og:title — crypto mining – Mine Unmineable Coins
- og:description — falling back from <meta name=description>
- og:image — https://unmineable.wordpress.com/wp-content/uploads/2025/07/cropped-photo_2025-07-01_16-19-53-1.jpg?w=200
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 | ⚠ | — | — | — |
CStructured DataActionNo structured data (JSON-LD) found.REVIEW
Adding structured data helps search engines understand your content and can enable rich results.
Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.
Learn more ▾ ▴
Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.
Source: Google Search Central / schema.org
No structured data found
Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.
Common types include:
- WebSite — your site identity and search box
- Organization — your company information
- Article — blog posts and news articles
- Product — e-commerce product pages
- BreadcrumbList — navigation paths
CRich Results EligibilityActionNo JSON-LD found -- no rich-result eligibilityREVIEW
A+Links200 links checked, 200 healthy, 0 brokenPASS
Broken Links (2)
| Status | URL | Found in | Error |
|---|---|---|---|
| 403 | https://wordpress.com/log-in/link?redirect_to=http... | <a> | Forbidden |
| 403 | https://www.quora.com/profile/0lqw-Qcab | <a> | Forbidden |