Skip to content
https://msdmanuals.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
1
PASS
5
INFO
1

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

Checks
7
5 PASS 1 REVIEW
C
Content Depth
Action
534 words, Very Difficult
REVIEW
534 words, Very Difficult
Info::
Page has 534 words of content
Info::
Text-to-HTML ratio is 1%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Very Difficult (grade 17)
534 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 17

Text-to-HTML Ratio

1% text 99% HTML

3 KB / 354 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+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://www.msdmanuals.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://msdmanuals.com Canonical https://www.msdmanuals.com Match Self-referencing (correct) Target 200 ✓
A+
Meta Tags
Title optimized
PASS
Title optimized
Info::
Page title is set
Got: The Trusted Provider of Medical Information since 1899
Info::
Title length (54 chars) is optimal
Info::
Title and H1 are identical
Consider differentiating — the title is for search results, the H1 is for the page.
Title

"The Trusted Provider of Medical Information since 1899"

54 characters Optimal ✓
Title: The Trusted Provider of Medical Information since 1899
H1: The Trusted Provider of Medical Information since 1899
Match: Similar ✓
Robots: Indexable (no restrictions)

Consider differentiating — the title is for search results, the H1 is for the page.

Why this matters

Title and H1 match exactly — internally consistent but misses an opportunity to optimize each for its audience (Title for SERP CTR, H1 for on-page).

Learn more ▾

Title and H1 don't have to be identical — and often shouldn't be. The Title competes for SERP click-through (lead with keyword + value prop), while the H1 confirms to the visitor they're on the right page (more conversational is fine). Differentiating gains both surfaces.

Source: Google Search Central / on-page SEO

A+
Image SEO
27 images, 18 descriptive filenames
PASS
27 images, 18 descriptive filenames
Info::
9 image(s) have hash/generic filenames
18 descriptive
0 hash-based
9 generic
27 total
FilenameQualityAltIssues
%3egeneric✓1
Current: %3e
Suggested: svg2720version27112720width27322720height273227.jpg
%3egeneric✓1
Current: %3e
Suggested: svg2720version27112720width27702720height277027.jpg
%3egeneric✓1
Current: %3e
Suggested: svg2720version27112720width271802720height2718827.jpg
%3egeneric✓1
Current: %3e
Suggested: svg2720version27112720width271892720height277127.jpg
%3egeneric✓1
Current: %3e
Suggested: svg2720version27112720width27302720height273027.jpg
%3egeneric✓1
Current: %3e
Suggested: svg2720version27112720width27752720height272827.jpg
%3egeneric✓1
Current: %3e
Suggested: svg2720version27112720width27752720height272827.jpg
%3egeneric✓1
Current: %3e
Suggested: svg2720version27112720width27802720height272527.jpg
%3egeneric✓1
Current: %3e
Suggested: svg2720version27112720width27322720height273227.jpg

See Accessibility tab for detailed alt text quality analysis.

A+
Schema Markup Audit
3 schema types detected
PASS

Rich result eligibility

BreadcrumbList Eligible

Breadcrumb trail

Organization Eligible

Organization knowledge panel

WebSite Eligible

Sitelinks search box

Detected schema types

BreadcrumbList json-ld → Breadcrumb trail
1/1 required
Required fields (Google)
  • itemListElement — Required — the breadcrumb chain renders nothing without this
Google's spec for this type
Organization json-ld → Organization knowledge panel
2/2 required · 3/4 recommended
Required fields (Google)
  • name — Required for the knowledge panel
  • url — Required for entity matching
Recommended fields
  • logo — Strongly recommended — appears in the knowledge panel header
  • sameAs — Connects the entity across the web
  • contactPoint — Add ContactPoint with telephone and contactType Enables direct contact from the knowledge panel
  • description — Used as the panel summary
Google's spec for this type
WebSite json-ld → Sitelinks search box
2/2 required · 0/1 recommended
Required fields (Google)
  • 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

Adding these recommended fields improves chances of getting Organization knowledge panel 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

Adding these recommended fields improves chances of getting Sitelinks search box 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

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