Skip to content
https://uw.edu.pl

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
2
PASS
3
INFO
0
Checks
5
3 PASS 2 REVIEW
C
Structured Data
Action
No structured data (JSON-LD) found.
REVIEW
No structured data (JSON-LD) found.
Info::
No structured data (JSON-LD) found
Adding structured data helps search engines understand your content and can enable rich results.

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
C
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
REVIEW

Brand Presence

Your brand name differs across channels — visitors see inconsistent identity.

C

57/100

Site name appears as

Page title| Uniwersytet Warszawski
og:site_nameUniwersytet Warszawski
twitter:site
Organization.name

Inconsistent — names differ across channels

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

20/20

og:image + twitter:image set

Meta completeness

20/20

Organization schema

0/15

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Brand name differs across channels — users see inconsistent identity
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • 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.

A+
Mixed Content
No mixed content detected — all resources use HTTPS.
PASS
No mixed content detected — all resources use HTTPS.
Info::
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.
Critical::
og:image is not reachable
The og:image URL could not be fetched. Social platforms won't be able to display it.
Got: https://www.uw.edu.pl/wp-content/uploads/2016/12/logo-uw-1.jpg
Info::
og:title is short (13 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 13 chars Expected: 25–60 chars
Info::
og:description is short (13 characters)
Ideal length is 55–200 characters for social sharing previews.
Got: 13 chars Expected: 55–200 chars
URL: https://www.uw.edu.pl/wp-content/uploads/2016/12/logo-uw-1.jpg

The og:image URL could not be fetched. Social platforms won't be able to display it.

Why this matters

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

URL: 13 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: 13 chars

Ideal length is 55–200 characters for social sharing previews.

Expected: 55–200 chars
Why this matters

og:description very short — provides little context in social cards.

Source: Open Graph Protocol

Preview

uw.edu.pl

Strona główna

Strona główna

Preview quality · Twitter/X A+ · 100/100
  • twitter:card — summary_large_image
  • twitter:title — Strona główna
  • twitter:description — Strona główna
  • twitter:image — https://www.uw.edu.pl/wp-content/uploads/2016/12/logo-uw-1.jpg

UW.EDU.PL

Strona główna

Strona główna

Preview quality · Facebook A+ · 100/100
  • og:title — Strona główna
  • og:description — Strona główna
  • og:image — https://www.uw.edu.pl/wp-content/uploads/2016/12/logo-uw-1.jpg
  • og:type — website
  • og:url — https://www.uw.edu.pl
  • og:site_name — Uniwersytet Warszawski

Strona główna

uw.edu.pl

Preview quality · LinkedIn A+ · 100/100
  • og:title — Strona główna
  • og:description — Strona główna
  • og:image — https://www.uw.edu.pl/wp-content/uploads/2016/12/logo-uw-1.jpg

uw.edu.pl

Strona główna

Strona główna

Preview quality · Slack A+ · 100/100
  • og:title — Strona główna
  • og:description — Strona główna
  • og:image — https://www.uw.edu.pl/wp-content/uploads/2016/12/logo-uw-1.jpg

Social preview quality

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

A+ · 100/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card
twitter:title
twitter:description
twitter:image
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback