Content - https://lencr.org BeaverCheck Audit

F

Brand Presence

Action

Site-name consistency, favicon, social image, meta tags, schema, and contact signals

FIX

Brand Presence

Partial brand coverage — a few channels are missing brand signals.

F

38/100

Site name appears as

Page title	Let's Encrypt
og:site_name	—
twitter:site	—
Organization.name	—

Consistent

Brand assets

Favicon

0/15

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

14/20

Organization schema

0/15

Contact info discoverable

5/10

contact page

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
No favicon link tags detected — browsers fall back to the generic globe
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.

C

Structured Data

Action

No structured data (JSON-LD) found.

REVIEW

No structured data (JSON-LD) found.

No structured data (JSON-LD) found

Adding structured data helps search engines understand your content and can enable rich results.

Why this matters

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

Learn more at schema.org

A

Links

67 links checked, 66 healthy, 1 broken

PASS

67 links checked, 66 healthy, 1 broken

66 of 67 links are healthy

Broken link: https://wiki.lspace.org/Lancre

Found in <a href>. Get "https://wiki.lspace.org/Lancre": context deadline exceeded

Got: unreachable

67 total 35 healthy 1 broken 31 redirects

Broken Links (1)

Status	URL	Found in	Error
ERR	https://wiki.lspace.org/Lancre	`<a>`	Get "https://wiki.lspace.org/Lancre": co...

Redirects (31)

200 https://lencr.org/ca/docs/lencr.org/ <a>

200 https://lencr.org/de/docs/lencr.org/ <a>

200 https://lencr.org/el/docs/lencr.org/ <a>

200 https://lencr.org/es/docs/lencr.org/ <a>

200 https://lencr.org/fr/docs/lencr.org/ <a>

200 https://lencr.org/he/docs/lencr.org/ <a>

200 https://lencr.org/hu/docs/lencr.org/ <a>

200 https://lencr.org/id/docs/lencr.org/ <a>

200 https://lencr.org/ja/docs/lencr.org/ <a>

200 https://lencr.org/ko/docs/lencr.org/ <a>

200 https://lencr.org/pl/docs/lencr.org/ <a>

200 https://lencr.org/pt-br/docs/lencr.org/ <a>

200 https://lencr.org/ru/docs/lencr.org/ <a>

200 https://lencr.org/sr/docs/lencr.org/ <a>

200 https://lencr.org/sv/docs/lencr.org/ <a>

200 https://lencr.org/ta/docs/lencr.org/ <a>

200 https://lencr.org/th/docs/lencr.org/ <a>

200 https://lencr.org/tr/docs/lencr.org/ <a>

A+

Mixed Content

No mixed content detected — all resources use HTTPS.

PASS

No mixed content detected — all resources use HTTPS.

No mixed content detected — all resources use HTTPS

A

Open Graph

Open Graph tags are well configured for social sharing.

PASS

Open Graph tags are well configured for social sharing.

og:title is short (9 characters)

Ideal length is 25–60 characters for social sharing previews.

Got: 9 chars Expected: 25–60 chars

og:description is long (494 characters)

Descriptions over 200 characters may be truncated in social sharing previews.

Got: 494 chars Expected: 55–200 chars

Missing og:site_name

The og:site_name tag displays the website name in social previews.

Missing twitter:card

Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

URL: 9 chars

Ideal length is 25–60 characters for social sharing previews.

Expected: 25–60 chars

Why this matters

og:title very short — may render with awkward whitespace in social cards.

Source: Open Graph Protocol

URL: 494 chars

Descriptions over 200 characters may be truncated in social sharing previews.

Expected: 55–200 chars

Why this matters

og:description borderline-too-long — social platforms truncate around ~200 chars.

Source: Open Graph Protocol

The og:site_name tag displays the website name in social previews.

Why this matters

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.

Why this matters

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

lencr.org

What’s lencr.org? lencr.org is a domain name owned by Let’s Encrypt. We use it to host data that is referenced inside the certificates we issue. Why is my computer fetching this data? Is it malicious? No, the data on lencr.org is never malicious. When a device connects to lencr.org, it’s because client software on that device (like a web browser or an app) connected to another site, saw a Let’s Encrypt certificate, and is trying to verify that it’s valid. This is routine for many clients.

Preview quality · Twitter/X F · 45/100

Description will be truncated (504 chars / 200 max)

twitter:card — Add <meta name="twitter:card" content="summary_large_image">
twitter:title — falling back from og:title
twitter:description — falling back from og:description
twitter:image — falling back from og:image

twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
Description will be truncated on Twitter/X (504 chars, max 200)
→ Tighten the description to ≤200 characters

LENCR.ORG

lencr.org

What’s lencr.org? lencr.org is a domain name owned by Let’s Encrypt. We use it to host data that is referenced inside the certificates we issue. Why is my computer fetching this data? Is it malicious? No, the data on lencr.org is never malicious. When a device connects to lencr.org, it’s because client software on that device (like a web browser or an app) connected to another site, saw a Let’s Encrypt certificate, and is trying to verify that it’s valid. This is routine for many clients.

Preview quality · Facebook B · 80/100

Description will be truncated (504 chars / 155 max)

og:title — lencr.org
og:description — What’s lencr.org? lencr.org is a domain name owned by Let’s Encrypt. We use it to host data that is referenced inside...
og:image — https://letsencrypt.org/images/LetsEncrypt-SocialShare.png
og:type — website
og:url — https://letsencrypt.org/docs/lencr.org/
og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

Description will be truncated on Facebook (504 chars, max 155)
→ Tighten og:description to ≤155 characters

lencr.org

Preview quality · LinkedIn A+ · 95/100

Description will be truncated (504 chars / 150 max)

og:title — lencr.org
og:description — What’s lencr.org? lencr.org is a domain name owned by Let’s Encrypt. We use it to host data that is referenced inside...
og:image — https://letsencrypt.org/images/LetsEncrypt-SocialShare.png

Description will be truncated on LinkedIn (504 chars, max 150)
→ Tighten og:description to ≤150 characters

lencr.org

What’s lencr.org? lencr.org is a domain name owned by Let’s Encrypt. We use it to host data that is referenced inside the certificates we issue. Why is my computer fetching this data? Is it malicious? No, the data on lencr.org is never malicious. When a device connects to lencr.org, it’s because client software on that device (like a web browser or an app) connected to another site, saw a Let’s Encrypt certificate, and is trying to verify that it’s valid. This is routine for many clients.

Preview quality · Slack A+ · 100/100

Description will be truncated (504 chars / 300 max)

og:title — lencr.org
og:description — What’s lencr.org? lencr.org is a domain name owned by Let’s Encrypt. We use it to host data that is referenced inside...
og:image — https://letsencrypt.org/images/LetsEncrypt-SocialShare.png

Long description may be shortened by Slack (504 chars, guideline ~300)
→ Consider tightening to ~300 chars for the cleanest unfurl

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

B · 80/100

Field	Twitter/X	Facebook	LinkedIn	Slack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card		—	—	—
twitter:title	⚠	—	—	—
twitter:description	⚠	—	—	—
twitter:image	⚠	—	—	—

URL	Destination	Found in
https://lencr.org/feed.xml	https://lencr.org/feed.xml	`<link>`
https://lencr.org/css/le-2025-theme-inpu...	https://lencr.org/css/le-2025-theme-inpu...	`<link>`
https://lencr.org/fontawesome-free-6.5.2...	https://lencr.org/fontawesome-free-6.5.2...	`<link>`
https://lencr.org/js/le-2025-theme.baca0...	https://lencr.org/js/le-2025-theme.baca0...	`<script>`
https://lencr.org/js/autoanchor.44783525...	https://lencr.org/js/autoanchor.44783525...	`<script>`
https://lencr.org/js/number-animation.13...	https://lencr.org/js/number-animation.13...	`<script>`
https://lencr.org/images/language-icon12...	https://lencr.org/images/language-icon12...	`<img>`
https://lencr.org/docs/lencr.org/	https://lencr.org/docs/lencr.org/	`<a>`
https://lencr.org/cs/docs/lencr.org/	https://lencr.org/cs/docs/lencr.org/	`<a>`
https://lencr.org/da/docs/lencr.org/	https://lencr.org/da/docs/lencr.org/	`<a>`
https://lencr.org/fi/docs/lencr.org/	https://lencr.org/fi/docs/lencr.org/	`<a>`
https://lencr.org/it/docs/lencr.org/	https://lencr.org/it/docs/lencr.org/	`<a>`
https://lencr.org/si/docs/lencr.org/	https://lencr.org/si/docs/lencr.org/	`<a>`
https://lencr.org/uk/docs/lencr.org/	https://lencr.org/uk/docs/lencr.org/	`<a>`
https://lencr.org/	https://lencr.org/	`<a>`
https://lencr.org/images/letsencrypt-log...	https://lencr.org/images/letsencrypt-log...	`<img>`
https://lencr.org/docs/	https://lencr.org/docs/	`<a>`
https://lencr.org/blog/	https://lencr.org/blog/	`<a>`
https://lencr.org/getinvolved/	https://lencr.org/getinvolved/	`<a>`
https://lencr.org/donate/	https://lencr.org/donate/	`<a>`
https://lencr.org/about/	https://lencr.org/about/	`<a>`
https://lencr.org/docs/faq/	https://lencr.org/docs/faq/	`<a>`
https://lencr.org/repository/	https://lencr.org/repository/	`<a>`
https://lencr.org/stats/	https://lencr.org/stats/	`<a>`
https://lencr.org/contact/	https://lencr.org/contact/	`<a>`
https://lencr.org/docs	https://lencr.org/docs	`<a>`
https://lencr.org/images/ISRG-Logo-Blue....	https://lencr.org/images/ISRG-Logo-Blue....	`<img>`
https://www.abetterinternet.org/terms-of...	https://www.abetterinternet.org/terms-of...	`<a>`
https://lencr.org/privacy/	https://lencr.org/privacy/	`<a>`
https://www.abetterinternet.org/trademar...	https://www.abetterinternet.org/trademar...	`<a>`
https://lencr.org/js/main.a572b61495f9d8...	https://lencr.org/js/main.a572b61495f9d8...	`<script>`