Skip to content
https://pcpclaim-uk.co.uk

SEO

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

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

Checks
14
13 PASS
A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://pcpclaim-uk.co.uk/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Canonical URL Configured
Page URL https://pcpclaim-uk.co.uk Canonical https://pcpclaim-uk.co.uk/ Match Self-referencing (correct) Target 200 ✓
A
Meta Tags
Title: 1 chars
PASS
Title: 1 chars
Info::
Page title is set
Got: X
Warning::
Title is only 1 characters — consider expanding
Info::
Meta description length (137 chars) is optimal
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"X"

1 characters Too short
Title: X
H1: PCP Claims: Get Specialist Advice & Compensation
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+
Title Style Depth
Title style is clean -- consistent separator, no stale year, no keyword stuffing
PASS
Title style is clean -- consistent separator, no stale year, no keyword stuffing
Info::
Title style is clean
A+
Content Depth
5463 words, Difficult
PASS
5463 words, Difficult
Info::
Page has 5463 words — good depth for search engines
Info::
Reading level: Difficult (grade 13)
5463 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 13

Text-to-HTML Ratio

21% text 79% HTML

33 KB / 161 KB

A+
Image SEO
26 images, 26 descriptive filenames
PASS
26 images, 26 descriptive filenames
Info::
All images have descriptive filenames
26 descriptive
0 hash-based
0 generic
26 total
All images have descriptive filenames and proper SEO attributes.

See Accessibility tab for detailed alt text quality analysis.

A+
Hreflang URL Quality
No hreflang tags on the page
PASS
No hreflang tags on the page
Info::
No hreflang tags on the page
A+
Hreflang Completeness
No hreflang tags on this page -- check is N/A (single-language site or unannotated)
PASS
No hreflang tags on this page -- check is N/A (single-language site or unannotated)
Info::
No hreflang tags found -- completeness check is N/A
A+
Sitemap Freshness
Sitemap updated within 90 days (2/2 URLs have lastmod)
PASS
Sitemap updated within 90 days (2/2 URLs have lastmod)
Info::
Sitemap actively maintained — newest lastmod: 3 days ago
Got: 2026-05-08T10:44:14Z
A+
Sitemap × Robots Consistency
No sitemap-vs-robots conflicts detected
PASS
No sitemap-vs-robots conflicts detected
Info::
Sitemap URLs are not blocked by robots.txt
A+
Sitemap Hygiene
Sitemap structure / size look healthy (2 URLs, 532 bytes)
PASS
Sitemap structure / size look healthy (2 URLs, 532 bytes)
Info::
Sitemap structure / size look healthy (2 URLs)
A+
Markup Quality
1 markup-quality issue(s) detected
PASS
1 markup-quality issue(s) detected
Info::
2 redundant ARIA role attribute(s) on native semantic element(s)
The W3C "ARIA in HTML" spec calls this its first rule: don't use ARIA when a native HTML element already conveys the semantics. `<button role="button">`, `<a href role="link">`, `<nav role="navigation">`, `<main role="main">` -- the role attribute either does nothing or shadows the native semantic, occasionally breaking assistive-tech behaviors. Remove the redundant role.
A+
Schema Markup Audit
3 schema types detected
PASS

Rich result eligibility

Organization Eligible

Organization knowledge panel

WebSite Eligible

Sitelinks search box

Detected schema types

Organization json-ld → Organization knowledge panel
2/2 required · 4/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 — 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
FinancialService json-ld
0/0 required

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

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