Skip to content
https://proquest.com

Content

· 5 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
74
GRADE
C
FIX
3
REVIEW
0
PASS
2
INFO
0
Checks
5
2 PASS 3 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

proquest.com

No title set

No description

Preview quality · Twitter/X F · 45/100

Description will be truncated (217 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 (217 chars, max 200)

    → Tighten the description to ≤200 characters

PROQUEST.COM

No title set

No description

Preview quality · Facebook F · 35/100

Title will be truncated (61 chars / 60 max)

Description will be truncated (217 chars / 155 max)

  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — https://proquest.com/assets/ctx/62e722af/images/pagelayout/PQ_logo_top_level.gif
  • 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

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

    → Shorten og:title to ≤60 characters

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

    → Tighten og:description to ≤155 characters

No title set

proquest.com

Preview quality · LinkedIn A · 85/100

Description will be truncated (217 chars / 150 max)

  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — https://proquest.com/assets/ctx/62e722af/images/pagelayout/PQ_logo_top_level.gif

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

    → Tighten og:description to ≤150 characters

proquest.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://proquest.com/assets/ctx/62e722af/images/pagelayout/PQ_logo_top_level.gif

Social preview quality

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

D · 63/100
FieldTwitter/XFacebookLinkedInSlack
og:title⚠⚠⚠
og:description⚠⚠⚠
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image⚠———
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

51/100

Site name appears as

Page titleBetter research, better learning, better insights.
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

4/15

has logo + url

Contact info discoverable

5/10

contact page

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
  • 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
Structured Data
1 JSON-LD block(s) found — structured data is well configured.
PASS
1 JSON-LD block(s) found — structured data is well configured.
Warning::
Missing required property "name" for Organization
The "name" property is required for the Organization schema type.
Info::
Missing recommended property "sameAs" for Organization
Adding "sameAs" can improve how search engines display your content.

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 "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
5 properties Valid
Missing required property: name
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "url": "https://www.proquest.com/",
  "logo": "https://www.proquest.com/assets/ctx/e965c3b9/images/pq-logo.jpg",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://www.proquest.com/runsearch?query={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback