Skip to content
https://hellomagazine.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
2
PASS
2
INFO
0
Checks
5
2 PASS 2 REVIEW 1 FIX
C
Structured Data
Action
1 JSON-LD block(s) found — some improvements recommended.
REVIEW
1 JSON-LD block(s) found — some improvements recommended.
Critical::
Malformed JSON-LD block #1
JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[{\"@context\":\"https://schema.org\n\t^...............................\n"

JSON parse error: Mismatch type map[string]interface {} with value array "at index 0: mismatched type with value\n\n\t[{\"@context\":\"https://schema.org\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

JSON-LD Blocks

Block 1 : Organization
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://schema.org\n\t^...............................\n"
[
  {
    "@context": "https://schema.org",
    "@graph": [
      {
        "@type": "Organization",
        "@id": "https://www.hellomagazine.com/#organization",
        "url": "https://www.hellomagazine.com/",
        "name": "HELLO!",
        "legalName": "Hello Ltd",
        "address": {
          "@type": "PostalAddress",
          "streetAddress": "69-71 Upper Ground",
          "addressLocality": "London",
          "postalCode": "SE1 9PQ",
          "addressCountry": "GB"
        },
        "contactPoint": {
          "@type": "ContactPoint",
          "contactType": "customer support",
          "telephone": "[+44 2076678721]",
          "email": "digitalteam@hellomagazine.com"
        },
        "sameAs": [
          "https://www.facebook.com/hello",
          "https://instagram.com/hellomag/",
          "https://twitter.com/hellomag",
          "https://www.linkedin.com/company/hello-magazine",
          "https://www.pinterest.co.uk/hellomag/",
          "https://www.youtube.com/user/HelloTVuk",
          "https://en.wikipedia.org/wiki/Hello!_(magazine)"
        ],
        "logo": {
          "@type": "ImageObject",
          "@id": "https://www.hellomagazine.com/#logo",
          "url": "https://www.hellomagazine.com/hellocom.png",
          "caption": "HELLO!",
          "width": 187,
          "height": 60
        },
        "image": {
          "@id": "https://www.hellomagazine.com/#logo"
        },
        "alternateName": "HELLO! Magazine"
      },
      {
        "@type": "WebSite",
        "@id": "https://www.hellomagazine.com/#website",
        "url": "https://www.hellomagazine.com/",
        "name": "HELLO!",
        "publisher": {
          "@id": "https://www.hellomagazine.com/#organization"
        },
        "alternateName": "HELLO! Magazine"
      },
      {
        "@type": "WebPage",
        "@id": "https://www.hellomagazine.com/#webpage",
        "url": "https://www.hellomagazine.com/",
        "inLanguage": "en",
        "isPartOf": {
          "@id": "https://www.hellomagazine.com/#website"
        },
        "about": {
          "@id": "https://www.hellomagazine.com/#organization"
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      {
        "@type": "ListItem",
        "position": 1,
        "name": "HELLO!",
        "item": {
          "@id": "https://www.hellomagazine.com/",
          "@type": "CollectionPage"
        }
      }
    ]
  }
]
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

69/100

Site name appears as

Page titleHELLO! - Daily royal, celebrity, fashion, beauty & lifestyle news
og:site_nameHELLO!
twitter:site@hellomag
Organization.name—

Inconsistent — names differ across channels

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

20/20

og:image + twitter:image set

Meta completeness

20/20

Organization schema

4/15

Organization schema present but missing all recommended fields

Contact info discoverable

5/10

contact page

Findings

  • Brand name differs across channels — users see inconsistent identity
  • Organization schema missing logo — add a logo property pointing to a square PNG
  • Organization schema missing url — point it at the canonical homepage
  • Consider adding contactPoint — helps appear in "contact us" rich results
  • 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.

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.hellomagazine.com/hello-fb-logo.png
Info::
og:title is long (65 characters)
Titles over 60 characters may be truncated in social sharing previews.
Got: 65 chars Expected: 25–60 chars
URL: https://www.hellomagazine.com/hello-fb-logo.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: 65 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

Preview

hellomagazine.com

HELLO! - Daily royal, celebrity, fashion, beauty & lifestyle news

HELLO! brings you the latest celebrity & royal news from the UK & around the world, magazine exclusives, fashion, beauty, lifestyle news, celeb babies, weddings, pregnancies and more!

Preview quality · Twitter/X A+ · 100/100
  • twitter:card — summary
  • twitter:title — HELLO! - Daily royal, celebrity, fashion, beauty & lifestyle news
  • twitter:description — HELLO! brings you the latest celebrity & royal news from the UK & around the world, magazine exclusives, fashion, bea...
  • twitter:image — https://www.hellomagazine.com/hello-fb-logo.png

HELLOMAGAZINE.COM

HELLO! - Daily royal, celebrity, fashion, beauty & lifestyle news

HELLO! brings you the latest celebrity & royal news from the UK & around the world, magazine exclusives, fashion, beauty, lifestyle news, celeb babies, weddings, pregnancies and more!

Preview quality · Facebook A · 90/100

Title will be truncated (65 chars / 60 max)

Description will be truncated (183 chars / 155 max)

  • og:title — HELLO! - Daily royal, celebrity, fashion, beauty & lifestyle news
  • og:description — HELLO! brings you the latest celebrity & royal news from the UK & around the world, magazine exclusives, fashion, bea...
  • og:image — https://www.hellomagazine.com/hello-fb-logo.png
  • og:type — website
  • og:url — https://www.hellomagazine.com/
  • og:site_name — HELLO!

  • Title will be truncated on Facebook (65 chars, max 60)

    → Shorten og:title to ≤60 characters

  • Description will be truncated on Facebook (183 chars, max 155)

    → Tighten og:description to ≤155 characters

HELLO! - Daily royal, celebrity, fashion, beauty & lifestyle news

hellomagazine.com

Preview quality · LinkedIn A+ · 95/100

Description will be truncated (183 chars / 150 max)

  • og:title — HELLO! - Daily royal, celebrity, fashion, beauty & lifestyle news
  • og:description — HELLO! brings you the latest celebrity & royal news from the UK & around the world, magazine exclusives, fashion, bea...
  • og:image — https://www.hellomagazine.com/hello-fb-logo.png

  • Description will be truncated on LinkedIn (183 chars, max 150)

    → Tighten og:description to ≤150 characters

hellomagazine.com

HELLO! - Daily royal, celebrity, fashion, beauty & lifestyle news

HELLO! brings you the latest celebrity & royal news from the UK & around the world, magazine exclusives, fashion, beauty, lifestyle news, celeb babies, weddings, pregnancies and more!

Preview quality · Slack A+ · 100/100
  • og:title — HELLO! - Daily royal, celebrity, fashion, beauty & lifestyle news
  • og:description — HELLO! brings you the latest celebrity & royal news from the UK & around the world, magazine exclusives, fashion, bea...
  • og:image — https://www.hellomagazine.com/hello-fb-logo.png

Social preview quality

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

A+ · 96/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