Skip to content
https://adweek.com

SEO

· 7 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
90
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.adweek.com
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target reachable (self-referencing)
Info::
Canonical points to a different domain
Canonical URL Problem
Page URL https://adweek.com Canonical https://www.adweek.com Match Self-referencing (correct)
A
Meta Tags
Title: 6 chars
PASS
Title: 6 chars
Info::
Page title is set
Got: ADWEEK
Warning::
Title is only 6 characters — consider expanding
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"ADWEEK"

6 characters Too short
Title: ADWEEK
H1: After Building In-House Agencies for Brands, Jeffrey Gorder Is Back Leading One
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
3368 words, Very Difficult
PASS
3368 words, Very Difficult
Info::
Page has 3368 words — good depth for search engines
Info::
Text-to-HTML ratio is 3%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Very Difficult (grade 25)
3368 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 25

Text-to-HTML Ratio

3% text 97% HTML

20 KB / 737 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
143 images, 142 descriptive filenames
PASS
143 images, 142 descriptive filenames
Info::
1 image(s) have hash/generic filenames
142 descriptive
0 hash-based
1 generic
143 total
FilenameQualityAltIssues
g.gifgeneric✓1

See Accessibility tab for detailed alt text quality analysis.

A+
Schema Markup Audit
9 schema types detected
PASS

Rich result eligibility

WebSite Eligible

Sitelinks search box

NewsArticle Eligible

Article rich results

NewsArticle Eligible

Article rich results

NewsArticle Eligible

Article rich results

NewsArticle Eligible

Article rich results

NewsArticle Eligible

Article rich results

NewsArticle Eligible

Article rich results

Detected schema types

NewsMediaOrganization json-ld
0/0 required
WebPage json-ld
0/0 required
WebSite json-ld → Sitelinks search box
2/2 required · 1/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 — Enables the in-SERP search box
Google's spec for this type
NewsArticle json-ld → Article rich results
4/4 required · 0/2 recommended
Required fields (Google)
  • headline — Required by Google's structured data spec
  • image — Required by Google's structured data spec
  • author — Required by Google's structured data spec
  • datePublished — 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
NewsArticle json-ld → Article rich results
4/4 required · 0/2 recommended
Required fields (Google)
  • headline — Required by Google's structured data spec
  • image — Required by Google's structured data spec
  • author — Required by Google's structured data spec
  • datePublished — 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
NewsArticle json-ld → Article rich results
4/4 required · 0/2 recommended
Required fields (Google)
  • headline — Required by Google's structured data spec
  • image — Required by Google's structured data spec
  • author — Required by Google's structured data spec
  • datePublished — 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
NewsArticle json-ld → Article rich results
4/4 required · 0/2 recommended
Required fields (Google)
  • headline — Required by Google's structured data spec
  • image — Required by Google's structured data spec
  • author — Required by Google's structured data spec
  • datePublished — 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
NewsArticle json-ld → Article rich results
4/4 required · 0/2 recommended
Required fields (Google)
  • headline — Required by Google's structured data spec
  • image — Required by Google's structured data spec
  • author — Required by Google's structured data spec
  • datePublished — 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
NewsArticle json-ld → Article rich results
4/4 required · 0/2 recommended
Required fields (Google)
  • headline — Required by Google's structured data spec
  • image — Required by Google's structured data spec
  • author — Required by Google's structured data spec
  • datePublished — 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

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

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

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

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

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

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

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