Skip to content
https://expressvpn.com

SEO

· 7 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
0
PASS
6
INFO
1

Cross-tab audit — SEO, performance, crawlability, mobile, structured data

Checks
7
6 PASS
A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://www.expressvpn.com/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Info::
Canonical points to a different domain
Canonical URL Configured
Page URL https://expressvpn.com Canonical https://www.expressvpn.com/ Match Self-referencing (correct) Target 200 ✓
A
Meta Tags
Title: 10 chars
PASS
Title: 10 chars
Info::
Page title is set
Got: ExpressVPN
Warning::
Title is only 10 characters — consider expanding
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"ExpressVPN"

10 characters Too short
Title: ExpressVPN
H1: World’s #1 VPN. Now at $2.79/mo.
Match: Very different
Robots: Indexable (no restrictions)

Alignment helps users confirm they've reached the right page.

Why this matters

Title and H1 disagree significantly — Google may treat one as the canonical topic and the other as off-topic, weakening ranking.

Learn more

Title is the SERP headline; H1 is the on-page headline. They should describe the same page. Large divergence (different topics, different keywords) signals confusion and Google may rewrite the title in SERP. Align both to the same primary topic.

Source: Google Search Central / on-page SEO

A
Content Depth
2777 words, Difficult
PASS
2777 words, Difficult
Info::
Page has 2777 words — good depth for search engines
Info::
Text-to-HTML ratio is 2%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Difficult (grade 11)
2777 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 11

Text-to-HTML Ratio

2% text 98% HTML

17 KB / 689 KB

Very low ratio suggests heavy framework overhead or boilerplate.

Why this matters

Informational: ratio of visible text bytes to total HTML bytes. Very low ratios suggest excessive markup overhead.

A+
Image SEO
99 images, 55 descriptive filenames
PASS
99 images, 55 descriptive filenames
Info::
44 image(s) have hash/generic filenames
55 descriptive
0 hash-based
44 generic
99 total
FilenameQualityAltIssues
img2.jpggeneric1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
img2.jpggeneric1
img1.pnggeneric1
Current: img1.png
Suggested: images.png

See Accessibility tab for detailed alt text quality analysis.

A
Schema Markup Audit
4 schema types detected
PASS

Rich result eligibility

VideoObject Eligible

Video rich results

FAQPage Eligible

FAQ rich results

WebSite Not eligible

Sitelinks search box

Missing: name

Detected schema types

VideoObject json-ld → Video rich results
4/4 required · 2/3 recommended
Required fields (Google)
  • name — Required — used as the carousel title
  • description — Required for any video rich result
  • thumbnailUrl — Required for the video thumbnail
  • uploadDate — Required for date display
Recommended fields
  • contentUrl — Lets Google index the actual video bytes
  • duration — Shows duration in the carousel
  • embedUrl — Add embedUrl for the iframe-friendly URL Enables in-SERP playback
Google's spec for this type
FAQPage json-ld → FAQ rich results
1/1 required
Required fields (Google)
  • mainEntity — Required — without this the FAQ schema is invalid
Google's spec for this type
WebSite json-ld → Sitelinks search box
1/2 required · 0/1 recommended
Required fields (Google)
  • name — Add the site name Required for the sitelinks search box
  • url — Required to anchor the search box to your domain
Recommended fields
  • potentialAction — Add a SearchAction with target and query-input Enables the in-SERP search box
Google's spec for this type
WebPage json-ld
0/0 required

Adding these recommended fields improves chances of getting Video rich results in search results.

Why this matters

Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).

Source: Google Search Central

Your WebSite structured data is missing required fields for Google's Sitelinks search box. Without these, the page won't qualify for rich results.

Why this matters

Schema entity missing required properties — Google's rich-result eligibility check fails; the schema is in source but never renders enhanced.

Source: Google Search Central

Hreflang
0 hreflang tags
INFO
0 hreflang tags

No hreflang tags detected.

Hreflang tags are only needed for multilingual or multi-regional sites.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback