Content - https://Bissell.com BeaverCheck Audit

F

Open Graph

Action

Open Graph tags need attention — social sharing previews may be incomplete.

FIX

Open Graph tags need attention — social sharing previews may be incomplete.

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.bissell.fr/static/version1777374587/frontend/Wise/bissell-ecom/fr_FR/images/logo-bg.jpg

Missing og:title

The og:title tag controls the title shown in social sharing previews.

Missing og:description

The og:description tag controls the description in social sharing previews.

Missing og:url

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

Missing og:type

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

Missing og:site_name

The og:site_name tag displays the website name in social previews.

Missing twitter:card

Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

URL: https://www.bissell.fr/static/version1777374587/frontend/Wise/bissell-ecom/fr_FR/images/logo-bg.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

The og:title tag controls the title shown in social sharing previews.

Why this matters

Without og:title, social shares fall back to the <title> tag — usually awkwardly truncated or branded for SEO not social.

Learn more ▾

og:title controls what appears as the headline in social-share cards (Twitter, Facebook, LinkedIn, Slack, iMessage). When omitted, platforms fall back to <title>, which is usually optimized for SEO (longer, brand-suffixed) and reads badly in social context. A 50-60-character og:title gives a clean preview.

Source: Open Graph Protocol

The og:description tag controls the description in social sharing previews.

Why this matters

No og:description means social cards either show no subtitle or scrape the first paragraph — usually unflattering.

Learn more ▾

Without og:description, social platforms either render no subtitle or pull whatever text appears first on the page. The first paragraph is rarely written for share-card context. A purpose-written 150-200 character og:description gives a polished card.

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

The og:site_name tag displays the website name in social previews.

Why this matters

Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.

Learn more ▾

og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.

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

Bissell.com

No title set

No description

Preview quality · Twitter/X F · 45/100

Description will be truncated (221 chars / 200 max)

twitter:card — Add <meta name="twitter:card" content="summary_large_image">
twitter:title — falling back from <title>
twitter:description — falling back from <meta name=description>
twitter:image — falling back from og:image

twitter:card is missing
→ Add <meta name="twitter:card" content="summary_large_image">
Description will be truncated on Twitter/X (221 chars, max 200)
→ Tighten the description to ≤200 characters

BISSELL.COM

No title set

No description

Preview quality · Facebook F · 40/100

Description will be truncated (221 chars / 155 max)

og:title — falling back from <title>
og:description — falling back from <meta name=description>
og:image — https://www.bissell.fr/static/version1777374587/frontend/Wise/bissell-ecom/fr_FR/images/logo-bg.jpg
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 (221 chars, max 155)
→ Tighten og:description to ≤155 characters

No title set

Bissell.com

Preview quality · LinkedIn A · 85/100

Description will be truncated (221 chars / 150 max)

og:title — falling back from <title>
og:description — falling back from <meta name=description>
og:image — https://www.bissell.fr/static/version1777374587/frontend/Wise/bissell-ecom/fr_FR/images/logo-bg.jpg

Description will be truncated on LinkedIn (221 chars, max 150)
→ Tighten og:description to ≤150 characters

Bissell.com

No title set

No description

Preview quality · Slack A · 90/100

og:title — falling back from <title>
og:description — falling back from <meta name=description>
og:image — https://www.bissell.fr/static/version1777374587/frontend/Wise/bissell-ecom/fr_FR/images/logo-bg.jpg

Social preview quality

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

C · 65/100

Field	Twitter/X	Facebook	LinkedIn	Slack
og:title		⚠	⚠	⚠
og:description		⚠	⚠	⚠
og:image
og:type
og:url
og:site_name
twitter:card		—	—	—
twitter:title	⚠	—	—	—
twitter:description	⚠	—	—	—
twitter:image	⚠	—	—	—

F

Image Optimization

Action

6 issues found across 40 images

FIX

6 issues found across 40 images

3 images significantly larger than display size

Resizing to display dimensions could save approximately 165 KB.

Got: ~165 KB wasted

40 images missing explicit width/height

Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.

1 below-fold images missing loading="lazy"

Lazy loading defers below-fold images, reducing initial page weight.

All 31 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.

20 images missing alt text

Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.

2 image(s) rendered at a different aspect ratio than the source

The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://www.bissell.fr/media/wysiwyg/26-01/National_Day_Image_3840x998_FR.png, https://www.bissell.fr/media/cache/FR/promos/spring-2025/Formulas_3_1_Add_to_cart_523x262_2_FR-450xbw0c0q70.png.

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

52/100

Site name appears as

Page title	mastercard
og:site_name	—
twitter:site	—
Organization.name	—

Consistent

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

8/20

Organization schema

0/15

Contact info discoverable

10/10

contact page + tel link

Findings

Missing brand name in: og:site_name, twitter:site, Organization.name
Add twitter:image — Twitter falls back to og:image only when it's larger than 300×157
og:title missing
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.

C

Structured Data

Action

No structured data (JSON-LD) found.

REVIEW

No structured data (JSON-LD) found.

No structured data (JSON-LD) found

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

Rich Results Eligibility

Action

No JSON-LD found -- no rich-result eligibility

REVIEW

No JSON-LD found -- no rich-result eligibility

No JSON-LD structured data on the page

No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.

A

Links

200 links checked, 199 healthy, 1 broken

PASS

200 links checked, 199 healthy, 1 broken

199 of 200 links are healthy

Broken link: https://api.bazaarvoice.com/

Found in <link href>. Returns HTTP 404.

Got: HTTP 404

200 total 199 healthy 1 broken

Broken Links (1)

Status	URL	Found in	Error
404	https://api.bazaarvoice.com/	`<link>`	Not Found

200 https://www.gstatic.com/recaptcha/releases/U5VsmTDhJM1iOJUyw... <script>

200 https://www.googletagmanager.com/gtag/destination?id=DC-1060... <script>

200 https://www.googletagmanager.com/gtag/destination?id=AW-7853... <script>

200 https://www.google-analytics.com/analytics.js <script>

200 https://www.googletagmanager.com/gtag/js?id=G-PHDYTV9D8V&cx=... <script>

200 https://www.googletagmanager.com/gtm.js?id=GTM-M7C2CMW <script>

200 https://www.bissell.fr/static/version1777374587/frontend/Wis... <link>

200 https://www.bissell.fr/static/version1777374587/frontend/Wis... <script>

200 https://widget.trustpilot.com/bootstrap/v5/tp.widget.bootstr... <script>

200 https://www.bissell.fr/static/version1777374587/frontend/Wis... <link>

200 https://www.bissell.fr/media/favicon/stores/4/favicon-32x32.... <link>

200 https://sleeknotecustomerscripts.sleeknote.com/190583.js <script>

200 https://d5yoctgpv4cpx.cloudfront.net/RUM-9D898BE3D8/v4-www.b... <script>

200 https://cdn.shared.bissell.io/scripts/legal-notices.min.js <script>

200 https://global.ketchcdn.com/web/v3/config/bissell/bissell_fr... <script>

200 https://www.bissell.fr/static/version1777374587/frontend/Wis... <script>

A+

Mixed Content

No mixed content detected — all resources use HTTPS.

PASS

No mixed content detected — all resources use HTTPS.

No mixed content detected — all resources use HTTPS

A+

Open Graph / Twitter Card Depth

OG image dimensions and Twitter card configuration look healthy

PASS

OG image dimensions and Twitter card configuration look healthy

OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid

A+

Autoplay Media

No autoplay media on the page

PASS

No autoplay media on the page