Skip to content
https://au.dk

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
63
GRADE
D
FIX
3
REVIEW
2
PASS
0
INFO
0
Checks
5
2 REVIEW 3 FIX
F
Open Graph
Action
No Open Graph tags found — social sharing previews will be generic.
FIX
No Open Graph tags found — social sharing previews will be generic.
Warning::
No Open Graph meta tags found
Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

Why this matters

Without Open Graph tags, social shares show a broken or empty preview card.

Learn more

When someone shares your URL on Facebook, LinkedIn, Slack, iMessage, or any modern chat app, the preview comes from <meta property="og:*"> tags. Without them you get either no card or whatever fragment the social platform guesses — usually unflattering. The four core og: tags (title, description, image, url) cover what every major platform actually reads.

Source: Open Graph Protocol

Preview

No image set

au.dk

No title set

No description

Preview quality · Twitter/X D · 55/100
  • twitter:card — summary
  • twitter:title — falling back from <title>
  • twitter:description — falling back from <meta name=description>
  • twitter:image — Add twitter:image — preview card without an image looks broken
  • No preview image for Twitter/X

    → Add og:image or twitter:image (≥300×157 for summary_large_image)

No image set

AU.DK

No title set

No description

Preview quality · Facebook F · 5/100

Description will be truncated (177 chars / 155 max)

  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — Add og:image — preview card without an image looks broken
  • 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 — Add og:site_name — Recommended — site-level brand line in the preview
  • Description will be truncated on Facebook (177 chars, max 155)

    → Tighten og:description to ≤155 characters

  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

No title set

au.dk

Preview quality · LinkedIn D · 50/100

Description will be truncated (177 chars / 150 max)

  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — Add og:image — preview card without an image looks broken
  • Description will be truncated on LinkedIn (177 chars, max 150)

    → Tighten og:description to ≤150 characters

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

au.dk

No title set

No description

Preview quality · Slack C · 70/100
  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — Add og:image — preview card without an image looks broken
  • No preview image — Slack unfurl will be text-only

    → Add og:image or twitter:image

Social preview quality

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

F · 45/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card
twitter:title
twitter:description
twitter:image
D
Structured Data
Action
2 JSON-LD block(s) found — issues found that may affect search visibility.
FIX
2 JSON-LD block(s) found — issues found that may affect search visibility.
Critical::
Malformed JSON-LD block #2
JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[{\"@context\":\"https:\\/\\/www.sche\n\t^...............................\n"
Warning::
Missing or invalid @context in block #1
The @context should be "https://schema.org" for search engines to recognize the data.
Got: http://schema.org/ Expected: https://schema.org
Info::
Custom type "School" — unable to validate specific properties
Info::
2 JSON-LD blocks found

JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[{\"@context\":\"https:\\/\\/www.sche\n\t^...............................\n"

Why this matters

JSON-LD block fails to parse — Google ignores the entire block, so structured data effectively isn't there.

Learn more

Common causes: trailing comma, single quotes instead of double, unescaped quote in a string value. Validate at https://validator.schema.org/ or Search Console's Rich Results Test.

Source: schema.org / Google Search Central

URL: http://schema.org/

The @context should be "https://schema.org" for search engines to recognize the data.

Expected: https://schema.org
Why this matters

JSON-LD without @context is invalid structured data — Google ignores the entire block.

Learn more

@context must be 'https://schema.org' (or the schema-specific URL). Without it, the block isn't parseable as schema.org JSON-LD and Google skips it. Most schema generators handle this; manual edits sometimes drop the field.

Source: JSON-LD spec / schema.org

JSON-LD Blocks

Block 1 : School
5 properties Valid
Missing or invalid @context
{
  "@context": "http://schema.org/",
  "@type": "School",
  "name": "Aarhus Universitet",
  "url": "https://www.au.dk",
  "sameAs": [
    "https://www.facebook.com/UniAarhus",
    "https://www.linkedin.com/company/aarhus-university-denmark",
    "https://www.youtube.com/user/AarhusUniversity",
    "https://instagram.com/AarhusUni",
    "https://bsky.app/profile/au.dk",
    "https://twitter.com/AarhusUni"
  ]
}
Block 2 : WebSite
0 properties Invalid
Invalid JSON: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[{\"@context\":\"https:\\/\\/www.sche\n\t^...............................\n"
[
  {
    "@context": "https:\/\/www.schema.org",
    "@type": "WebSite",
    "url": "https:\/\/www.au.dk",
    "name": "Aarhus Universitet"
  },
  {
    "@context": "https:\/\/www.schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      {
        "@type": "ListItem",
        "position": 1,
        "item": {
          "@id": "https:\/\/auinstallation40.cs.au.dk\/",
          "name": "TYPO3"
        }
      },
      {
        "@type": "ListItem",
        "position": 2,
        "item": {
          "@id": "https:\/\/www.au.dk\/",
          "name": "Aarhus Universitet"
        }
      }
    ]
  }
]
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

26/100

Site name appears as

Page titleAarhus Universitet
og:site_name
twitter:site
Organization.name

Consistent

Brand assets

Favicon

8/15

single size only

Social share image

0/20

Meta completeness

8/20

Organization schema

0/15

Contact info discoverable

5/10

mailto link

Findings

  • Missing brand name in: og:site_name, twitter:site, Organization.name
  • No social share image — shared links render as bare URLs
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • og:title missing
  • og:image 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.

B
Mixed Content
1 HTTP resource(s) loaded on HTTPS page
REVIEW
1 HTTP resource(s) loaded on HTTPS page
Critical::
HTTP link loaded on HTTPS page
Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.
Got: http://purl.org/dc/elements/1.1/ Expected: https://purl.org/dc/elements/1.1/
URL: http://purl.org/dc/elements/1.1/

Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.

Expected: https://purl.org/dc/elements/1.1/
Why this matters

Mixed content — HTTP resource on HTTPS page. Browser may block silently or warn user.

Source: Google Chrome Security

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback