Skip to content
https://kcl.ac.uk

SEO

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

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

Checks
7
4 PASS 2 REVIEW
B
Canonical URL
Minor issues
REVIEW
Minor issues
Warning::
No canonical tag found
Search engines will determine the canonical URL themselves, which may cause duplicate content issues.
No Canonical URL Set
Page URL https://kcl.ac.uk Canonical (not set)

Search engines will determine the canonical URL themselves, which may cause duplicate content issues.

Why this matters

Without a canonical, Google may treat each URL variant (with/without slash, with tracking params, http/https) as duplicate content and split ranking.

Learn more ▾

A canonical link tells Google which URL is the 'real' one when multiple URLs serve identical content. Without it, link equity gets split across variants and none of them rank as well as a single canonical version would. One <link rel="canonical"> tag in <head> covers it.

Source: Google Search Central

B
Content Depth
788 words, Very Difficult
REVIEW
788 words, Very Difficult
Info::
Page has 788 words of content
Info::
Reading level: Very Difficult (grade 30)
788 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 30

Text-to-HTML Ratio

6% text 94% HTML

5 KB / 96 KB

A
Meta Tags
Title: 8 chars
PASS
Title: 8 chars
Info::
Page title is set
Got: link-ico
Warning::
Title is only 8 characters — consider expanding
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"link-ico"

8 characters Too short
Title: link-ico
H1: Carousel of recent news articles
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+
Image SEO
15 images, 15 descriptive filenames
PASS
15 images, 15 descriptive filenames
Info::
All images have descriptive filenames
15 descriptive
0 hash-based
0 generic
15 total
All images have descriptive filenames and proper SEO attributes.

See Accessibility tab for detailed alt text quality analysis.

A+
Schema Markup Audit
7 schema types detected
PASS

Rich result eligibility

Article Eligible

Article rich results

Article Eligible

Article rich results

Article Eligible

Article rich results

Event Eligible

Event rich results

Event Eligible

Event rich results

Event Eligible

Event rich results

Organization Eligible

Organization knowledge panel

Detected schema types

Article json-ld → Article rich results
4/4 required · 1/2 recommended
Required fields (Google)
  • headline — Required — used as the rich result title
  • image — Required for top-stories carousel eligibility
  • author — Required by Google's E-E-A-T guidelines
  • datePublished — Required for time-sensitive rich results
Recommended fields
  • dateModified — Add dateModified when the article is edited Signals freshness to the news algorithm
  • description — Used as the result snippet
Google's spec for this type
Article json-ld → Article rich results
4/4 required · 1/2 recommended
Required fields (Google)
  • headline — Required — used as the rich result title
  • image — Required for top-stories carousel eligibility
  • author — Required by Google's E-E-A-T guidelines
  • datePublished — Required for time-sensitive rich results
Recommended fields
  • dateModified — Add dateModified when the article is edited Signals freshness to the news algorithm
  • description — Used as the result snippet
Google's spec for this type
Article json-ld → Article rich results
4/4 required · 1/2 recommended
Required fields (Google)
  • headline — Required — used as the rich result title
  • image — Required for top-stories carousel eligibility
  • author — Required by Google's E-E-A-T guidelines
  • datePublished — Required for time-sensitive rich results
Recommended fields
  • dateModified — Add dateModified when the article is edited Signals freshness to the news algorithm
  • description — Used as the result snippet
Google's spec for this type
Event json-ld → Event rich results
3/3 required · 3/5 recommended
Required fields (Google)
  • name — Required for event rich results
  • startDate — Required for the event card
  • location — Required — events without location are filtered out
Recommended fields
  • description — Used as the snippet under the event title
  • image — Strongly recommended for visual prominence
  • endDate — Helps Google decide when to stop showing the event
  • organizer — Add organizer Person or Organization with name Adds trust signal in the event card
  • offers — Add Offer with url, price, priceCurrency, availability Enables ticket booking links
Google's spec for this type
Event json-ld → Event rich results
3/3 required · 3/5 recommended
Required fields (Google)
  • name — Required for event rich results
  • startDate — Required for the event card
  • location — Required — events without location are filtered out
Recommended fields
  • description — Used as the snippet under the event title
  • image — Strongly recommended for visual prominence
  • endDate — Helps Google decide when to stop showing the event
  • organizer — Add organizer Person or Organization with name Adds trust signal in the event card
  • offers — Add Offer with url, price, priceCurrency, availability Enables ticket booking links
Google's spec for this type
Event json-ld → Event rich results
3/3 required · 3/5 recommended
Required fields (Google)
  • name — Required for event rich results
  • startDate — Required for the event card
  • location — Required — events without location are filtered out
Recommended fields
  • description — Used as the snippet under the event title
  • image — Strongly recommended for visual prominence
  • endDate — Helps Google decide when to stop showing the event
  • organizer — Add organizer Person or Organization with name Adds trust signal in the event card
  • offers — Add Offer with url, price, priceCurrency, availability Enables ticket booking links
Google's spec for this type
Organization json-ld → Organization knowledge panel
2/2 required · 2/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 — Add an organization description Used as the panel summary
Google's spec for this type

Missing schema opportunities

  • moderate

    LocalBusiness

    Page describes a local business (address element) — add LocalBusiness schema

    Eligible for the local pack and Google Maps results

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 Event 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 Event 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 Event 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 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

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