Skip to content
https://www.rhenen.nl

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
88
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Checks
9
5 PASS 2 REVIEW 2 FIX
D
Image Optimization
Action
3 issues found across 5 images
FIX
3 issues found across 5 images
Warning::
5 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
3 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Warning::
All 4 images use legacy formats (JPEG/PNG/GIF)
WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
D
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.

D

46/100

Site name appears as

Page titleGemeente Rhenen
og:site_nameGemeente Rhenen
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

12/15

covers multiple sizes

Social share image

0/20

Meta completeness

14/20

Organization schema

0/15

Contact info discoverable

10/10

contact page + tel link

Findings

  • Missing brand name in: twitter:site, Organization.name
  • No social share image — shared links render as bare URLs
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • og:image 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.

C
Open Graph
Action
Open Graph tags are partially configured — some improvements recommended.
REVIEW
Open Graph tags are partially configured — some improvements recommended.
Warning::
Missing og:image
The og:image tag provides a preview image for social sharing.
Info::
Missing og:url
The og:url tag specifies the canonical URL for the shared content.
Info::
Missing og:type
The og:type tag helps social platforms categorize the content.

The og:image tag provides a preview image for social sharing.

Why this matters

No og:image means social shares are imageless — measurably less engaging than image-cards across every major platform.

Learn more ▾

Twitter, Facebook, and LinkedIn all use og:image (or twitter:image as a fallback) for share-card thumbnails. Without one, the post renders as a text-only card. A 1200x630px image (Twitter's preferred size) covers all platforms.

Source: Open Graph Protocol

The og:url tag specifies the canonical URL for the shared content.

Why this matters

Without og:url, social platforms infer the canonical URL — often picking a tracking-param variant that pollutes share counts.

Learn more ▾

og:url tells the social platform which URL to count this share against. Without it, platforms use the literal URL the user pasted (which may include utm_* parameters, ref codes, etc.). Setting og:url to the canonical form keeps share-count attribution clean.

Source: Open Graph Protocol

The og:type tag helps social platforms categorize the content.

Why this matters

Default og:type is 'website' but the right value (article, product, profile) unlocks richer metadata fields and higher engagement.

Learn more ▾

og:type controls which other og: fields a platform respects. og:type=article enables og:article:published_time, author, and section — surfaced in news cards. og:type=product enables price/availability fields surfaced by Pinterest and shopping integrations. Default 'website' silently disables those.

Source: Open Graph Protocol

Preview

No image set

www.rhenen.nl

Website van de gemeente Rhenen

Online service en informatie van de gemeente Rhenen. Wilt u langskomen? Maak eerst een afspraak op de website.

Preview quality · Twitter/X C · 65/100
  • twitter:card — summary
  • twitter:title — Home
  • twitter:description — Online service en informatie van de gemeente Rhenen. Wilt u langskomen? Maak eerst een afspraak op de website.
  • 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

WWW.RHENEN.NL

Website van de gemeente Rhenen

Online service en informatie van de gemeente Rhenen. Wilt u langskomen? Maak eerst een afspraak op de website.

Preview quality · Facebook F · 35/100
  • og:title — Website van de gemeente Rhenen
  • og:description — Online service en informatie van de gemeente Rhenen. Wilt u langskomen? Maak eerst een afspraak op de website.
  • 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 — Gemeente Rhenen

  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

Website van de gemeente Rhenen

www.rhenen.nl

Preview quality · LinkedIn C · 65/100
  • og:title — Website van de gemeente Rhenen
  • og:description — Online service en informatie van de gemeente Rhenen. Wilt u langskomen? Maak eerst een afspraak op de website.
  • og:image — Add og:image — preview card without an image looks broken

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

www.rhenen.nl

Website van de gemeente Rhenen

Online service en informatie van de gemeente Rhenen. Wilt u langskomen? Maak eerst een afspraak op de website.

Preview quality · Slack B · 80/100
  • og:title — Website van de gemeente Rhenen
  • og:description — Online service en informatie van de gemeente Rhenen. Wilt u langskomen? Maak eerst een afspraak op de website.
  • 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.

D · 61/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title———
twitter:description———
twitter:image———
B
Structured Data
1 JSON-LD block(s) found — some improvements recommended.
REVIEW
1 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: https://schema.org/ Expected: https://schema.org
Info::
Custom type "WebPage" — unable to validate specific properties
URL: https://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 : WebPage
2 properties Valid
Missing or invalid @context
{
  "@context": "https://schema.org/",
  "@graph": [
    {
      "@type": "WebPage",
      "@id": "https://www.rhenen.nl/#webpage",
      "dateModified": "2026-11-12T09:02:41+01:00",
      "datePublished": "2018-07-25T10:23:40+02:00",
      "description": "Online service en informatie van de gemeente Rhenen. Wilt u langskomen? Maak eerst een afspraak op de website.",
      "isPartOf": "https://www.rhenen.nl/#website",
      "name": "Gemeente Rhenen • Gemeente Rhenen",
      "primaryImageOfPage": {
        "@type": "ImageObject",
        "contentUrl": "https://www.rhenen.nl/fileadmin/gemeente_rhenen/HOME/Header/DJI_0100.JPG",
        "height": "2250px",
        "url": "https://www.rhenen.nl/fileadmin/gemeente_rhenen/HOME/Header/DJI_0100.JPG",
        "width": "4000px"
      },
      "url": "https://www.rhenen.nl/"
    },
    {
      "@type": "WebSite",
      "@id": "https://www.rhenen.nl/#website",
      "name": "Gemeente Rhenen",
      "potentialAction": {
        "@type": "SearchAction",
        "query": "required name=search_term_string",
        "target": "https://www.rhenen.nl/zoeken/?q={search_term_string}"
      },
      "publisher": {
        "@type": "GovernmentOrganization",
        "@id": "https://www.rhenen.nl/#organization",
        "logo": "/fileadmin/user_upload/Logo_Rhenen.svg",
        "name": "Gemeente Rhenen",
        "sameAs": [
          "https://www.facebook.com/GemeenteRhenen",
          "https://www.instagram.com/gemeenterhenen",
          "https://www.linkedin.com/company/Gemeente-Rhenen",
          "https://twitter.com/Gemeente_Rhenen"
        ]
      },
      "url": "https://www.rhenen.nl/"
    }
  ]
}
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 / Twitter Card Depth
1 OG/Twitter depth issue(s) detected
PASS
1 OG/Twitter depth issue(s) detected
Info::
1 Twitter Card field(s) differ from Open Graph counterparts
Twitter Cards inherit values from Open Graph tags when the Twitter-specific tag is absent (`twitter:title` falls back to `og:title`, etc.). Explicitly-set Twitter values that DIFFER from OG are usually stale -- the marketing team updates `og:title` for FB/LinkedIn previews and forgets to update `twitter:title` separately, leaving Twitter showing the old text. Mismatches: - title: twitter="Home", og="Website van de gemeente Rhenen" Fix: either remove the redundant Twitter-specific tags (rely on inheritance) or sync them when updating OG.
Got: 1 field(s) differ
A+
Rich Results Eligibility
1 JSON-LD block(s) declaring 2 schema type(s)
PASS
1 JSON-LD block(s) declaring 2 schema type(s)
Info::
SiteLinks Search Box markup detected
The page declares a `WebSite` schema with a `potentialAction` of `SearchAction`. This makes the homepage eligible for Google's in-SERP search box -- a high-visibility SERP feature for branded queries.
Info::
2 rich-result schema type(s) declared
Inventory of structured-data types on the page (each may unlock a different SERP feature): WebPage, WebSite Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.
A+
Autoplay Media
No autoplay media on the page
PASS
No autoplay media on the page
Info::
No autoplay media on the page
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback