Skip to content
https://questionpro.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
3
PASS
1
INFO
0
Checks
5
1 PASS 3 REVIEW 1 FIX
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.
Warning::
Missing og:title
The og:title tag controls the title shown in social sharing previews.
Warning::
Missing og:description
The og:description tag controls the description in social sharing previews.
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.
Info::
Missing og:site_name
The og:site_name tag displays the website name in social previews.
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

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

questionpro.com

No title set

No description

Preview quality · Twitter/X D · 50/100
  • 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">

QUESTIONPRO.COM

No title set

No description

Preview quality · Facebook F · 40/100

Description will be truncated (170 chars / 155 max)

  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — https://questionpro.com/images/qphome/questionpro-thumbnail.png
  • 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 (170 chars, max 155)

    → Tighten og:description to ≤155 characters

No title set

questionpro.com

Preview quality · LinkedIn A · 85/100

Description will be truncated (170 chars / 150 max)

  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — https://questionpro.com/images/qphome/questionpro-thumbnail.png

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

    → Tighten og:description to ≤150 characters

questionpro.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://questionpro.com/images/qphome/questionpro-thumbnail.png

Social preview quality

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

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

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

The "name" property is required for the Organization 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

Adding "logo" 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

Adding "sameAs" 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 : Organization
11 properties Valid
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "QuestionPro",
  "url": "https://www.questionpro.com",
  "logo": "https://www.questionpro.com/images/logo/questionpro-logo.svg",
  "description": "Our free survey platform features 80+ question types, ready-made templates, and more! Discover QuestionPro, the best online survey software to create surveys!",
  "sameAs": [
    "https://www.facebook.com/questionpro",
    "https://x.com/questionpro",
    "https://linkedin.com/company/questionpro",
    "https://www.youtube.com/user/QuestionPro"
  ],
  "contactPoint": [
    {
      "@type": "ContactPoint",
      "telephone": "+1-800-531-0228",
      "contactType": "customer support",
      "areaServed": "Worldwide",
      "availableLanguage": [
        "English",
        "Spanish"
      ]
    }
  ],
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "9450 SW Gemini Dr #62790",
    "addressLocality": "Beaverton",
    "addressRegion": "OR",
    "postalCode": "97008-7105",
    "addressCountry": "US"
  },
  "founder": {
    "@type": "Person",
    "name": "Vivek Bhaskaran"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "1500"
  }
}
Block 2 : WebSite
4 properties Valid
Missing required property: name
{
  "@context": "http://schema.org",
  "@type": "WebSite",
  "url": "https://www.questionpro.com/",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://www.questionpro.com/a/search.do?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
Block 3 : Organization
5 properties Valid
{
  "@context": "http://schema.org",
  "@type": "Organization",
  "name": "QuestionPro",
  "url": "https://www.questionpro.com",
  "sameAs": [
    "https://www.facebook.com/questionpro",
    "https://twitter.com/questionpro",
    "https://linkedin.com/company/questionpro",
    "https://www.youtube.com/user/QuestionPro"
  ]
}
Block 4 : Organization
4 properties Valid
Missing required property: name
{
  "@context": "http://schema.org",
  "@type": "Organization",
  "url": "https://www.questionpro.com",
  "logo": "https://www.questionpro.com/images/logo/questionpro-logo.svg"
}
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

60/100

Site name appears as

Page titleFilter Icon
og:site_name—
twitter:site—
Organization.nameQuestionPro

Inconsistent — names differ across channels

Brand assets

Favicon

8/15

single size only

Social share image

14/20

og:image set; twitter:image missing

Meta completeness

8/20

Organization schema

15/15

has name, logo + url

Contact info discoverable

10/10

contact page + tel 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
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • og:title missing
  • twitter:card missing

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