Skip to content
https://slate.com

SEO

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

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

Checks
7
4 PASS 1 REVIEW 1 FIX
F
Schema Markup Audit
Action
1 schema types detected
FIX

Rich result eligibility

NewsArticle Not eligible

Article rich results

Missing: headline, image, author, datePublished

Detected schema types

NewsArticle json-ld → Article rich results
0/4 required · 0/2 recommended
Required fields (Google)
  • headline — Add a headline value to the NewsArticle schema Required by Google's structured data spec
  • image — Add a image value to the NewsArticle schema Required by Google's structured data spec
  • author — Add a author value to the NewsArticle schema Required by Google's structured data spec
  • datePublished — Add a datePublished value to the NewsArticle schema Required by Google's structured data spec
Recommended fields
  • dateModified — Consider adding dateModified to enrich the NewsArticle schema Recommended for stronger rich result eligibility
  • description — Consider adding description to enrich the NewsArticle schema Recommended for stronger rich result eligibility
Google's spec for this type

Missing schema opportunities

  • easy

    FAQPage

    Page has Q&A-style content (questions in headings) that could be marked up as FAQPage

    FAQ rich results take 2-3× more SERP real estate

Your NewsArticle structured data is missing required fields for Google's Article rich results. 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

B
Image SEO
26 images, 6 descriptive filenames
REVIEW
26 images, 6 descriptive filenames
Warning::
77% of images have non-descriptive filenames
Search engines use filenames as a signal. Rename to descriptive names like 'team-photo.jpg'.
6 descriptive
4 hash-based
16 generic
26 total
FilenameQualityAltIssues
6e3808f9-ec9a-4a69-8cdd-33c90c03f908.jpeghash1
Current: 6e3808f9-ec9a-4a69-8cdd-33c90c03f908.jpeg
Suggested: images.jpeg
0544c37e-627e-4d69-b759-94dbe21c30e8.jpeghash1
Current: 0544c37e-627e-4d69-b759-94dbe21c30e8.jpeg
Suggested: images.jpeg
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1
6e3808f9-ec9a-4a69-8cdd-33c90c03f908.jpeghash1
Current: 6e3808f9-ec9a-4a69-8cdd-33c90c03f908.jpeg
Suggested: images.jpeg
28d60c5d-27c9-416c-b799-f7dd6d1956b3.gifhash1
Current: 28d60c5d-27c9-416c-b799-f7dd6d1956b3.gif
Suggested: images.gif
.generic1
.generic1
.generic1
.generic1
.generic1
.generic1

See Accessibility tab for detailed alt text quality analysis.

Search engines use filenames as a signal. Rename to descriptive names like 'team-photo.jpg'.

Why this matters

Most image filenames are non-descriptive (hash/IMG_X) — small SEO miss for Image Search ranking.

Source: Google Image SEO

A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://slate.com/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target reachable (self-referencing)
Canonical URL Problem
Page URL https://slate.com Canonical https://slate.com/ Match Self-referencing (correct)
A
Meta Tags
Title: 20 chars
PASS
Title: 20 chars
Info::
Page title is set
Got: The Slate Group logo
Warning::
Title is only 20 characters — consider expanding
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"The Slate Group logo"

20 characters Too short
Title: The Slate Group logo
H1: Get Slate in Your Inbox
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
1996 words, Fairly Difficult
PASS
1996 words, Fairly Difficult
Info::
Page has 1996 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: Fairly Difficult (grade 8)
1996 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 8

Text-to-HTML Ratio

2% text 98% HTML

12 KB / 794 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.

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