Skip to content
https://www.notebookcheck.net

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
3
PASS
2
INFO
0
Checks
5
2 PASS 3 REVIEW
B
Open Graph
Open Graph tags are partially configured — some improvements recommended.
REVIEW
Open Graph tags are partially configured — some improvements recommended.
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.notebookcheck.net/fileadmin/Notebooks/Sonstiges/Notebookcheck/logo_nbc_small_shaded_png_smaller.png
Info::
og:title is long (68 characters)
Titles over 60 characters may be truncated in social sharing previews.
Got: 68 chars Expected: 25–60 chars
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.
URL: https://www.notebookcheck.net/fileadmin/Notebooks/Sonstiges/Notebookcheck/logo_nbc_small_shaded_png_smaller.png

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: 68 chars

Titles over 60 characters may be truncated in social sharing previews.

Expected: 25–60 chars
Why this matters

og:title borderline-too-long — Facebook/LinkedIn may truncate. Aim for ~60-70 characters max.

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

www.notebookcheck.net

Expert Reviews and News on Laptops, Smartphones and Tech Innovations

Notebookcheck provides in depth reviews, technical articles like benchmark comparisons, and news on laptops / notebooks, smartphones, tablets and tech innovations.

WWW.NOTEBOOKCHECK.NET

Expert Reviews and News on Laptops, Smartphones and Tech Innovations

Notebookcheck provides in depth reviews, technical articles like benchmark comparisons, and news on laptops / notebooks, smartphones, tablets and tech innovations.

Expert Reviews and News on Laptops, Smartphones and Tech Innovations

www.notebookcheck.net

www.notebookcheck.net

Expert Reviews and News on Laptops, Smartphones and Tech Innovations

Notebookcheck provides in depth reviews, technical articles like benchmark comparisons, and news on laptops / notebooks, smartphones, tablets and tech innovations.

C
Structured Data
Action
2 JSON-LD block(s) found — some improvements recommended.
REVIEW
2 JSON-LD block(s) found — some improvements recommended.
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
Warning::
Missing required property "name" for WebSite
The "name" property is required for the WebSite schema type.
Info::
Missing recommended property "description" for WebSite
Adding "description" can improve how search engines display your content.
Info::
2 JSON-LD blocks found
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

The "name" property is required for the WebSite schema type.

Why this matters

Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.

Learn more

Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.

Source: Google Search Central / schema.org

Adding "description" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

JSON-LD Blocks

Block 1 : Article
11 properties Valid
Missing or invalid @context
{
  "@context": "http://schema.org/",
  "@type": "Article",
  "mainEntityOfPage": "https://www.notebookcheck.net/",
  "inLanguage": "en",
  "headline": "Expert Reviews and News on Laptops, Smartphones and Tech Innovations",
  "datePublished": "2005-09-11T11:19:00+02:00",
  "dateModified": "2025-11-21T10:15:31+01:00",
  "description": "Notebookcheck provides in depth reviews, technical articles like benchmark comparisons, and news on laptops / notebooks, smartphones, tablets and tech innovations.",
  "author": {
    "@type": "Person",
    "name": "Notebookcheck",
    "url": "https://www.notebookcheck.net/Notebookcheck-Team.212978.0.html?tx_nbc2journalist_pi1%5Bmode%5D=show&tx_nbc2journalist_pi1%5Buid%5D=1&cHash=24137047be676cd90bb522247abcd034"
  },
  "publisher": {
    "@type": "Organization",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.notebookcheck.com/fileadmin/templates/images/nbc_logo_small.png"
    },
    "name": "Notebookcheck"
  },
  "image": {
    "@type": "ImageObject",
    "width": "1920",
    "height": "1457",
    "url": "https://www.notebookcheck.net/fileadmin/Notebooks/Sonstiges/Notebookcheck/logo_nbc_small_shaded_png_smaller.png"
  }
}
Block 2 : WebSite
4 properties Valid
Missing required property: name
{
  "@context": "http://schema.org",
  "@type": "WebSite",
  "url": "https://www.notebookcheck.net/",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://www.notebookcheck.net/Google-Search.36690.0.html?q={search_term}",
    "query-input": "required name=search_term"
  }
}
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

58/100

Site name appears as

Page titleNotebookCheck.net
og:site_nameNotebookcheck
twitter:site
Organization.name

Inconsistent — names differ across channels

Brand assets

Favicon

15/15

covers multiple sizes, apple-touch-icon + SVG

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

14/20

Organization schema

0/15

Contact info discoverable

10/10

contact page + mailto link

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

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
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback