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

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

Checks
7
5 PASS 1 REVIEW
B
Canonical URL
Minor issues
REVIEW
Minor issues
Info::
Canonical tag present
Got: https://grind.co.uk/pages/en-us
Warning::
Canonical does not match final URL (https://grind.co.uk)
Critical::
Canonical target returns 429
Search engines cannot follow this canonical, effectively orphaning this page.
Canonical URL Problem
Page URL https://grind.co.uk Canonical https://grind.co.uk/pages/en-us Match Points to a different page Target 429

Search engines cannot follow this canonical, effectively orphaning this page.

Why this matters

Canonical URL returns a non-200 status — Google can't follow the canonical to confirm the relationship.

Source: Google Search Central

A+
Meta Tags
Title optimized
PASS
Title optimized
Info::
Page title is set
Got: Grind Compostable Nespresso® Pods
Info::
Title length (34 chars) is optimal
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"Grind Compostable Nespresso® Pods"

34 characters Optimal ✓
Title: Grind Compostable Nespresso® Pods
H1: This is better coffee.
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
1541 words, Fairly Difficult
PASS
1541 words, Fairly Difficult
Info::
Page has 1541 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 9)
1541 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 9

Text-to-HTML Ratio

2% text 98% HTML

10 KB / 405 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
77 images, 72 descriptive filenames
PASS
77 images, 72 descriptive filenames
Info::
5 image(s) have hash/generic filenames
Info::
7 image(s) missing alt text — see Accessibility tab
72 descriptive
0 hash-based
5 generic
77 total
FilenameQualityAltIssues
.generic1
Homepage_Block4_FirstDelivery_trimmed_440x.pngdescriptive1
icon_thin_recycle.svgdescriptive1
icon_thin_carbon_neutral_shipping.svgdescriptive1
icon_thin_ocean_cleanup_project.svgdescriptive1
icon_thin_first_compostable_pod.svgdescriptive1
.generic1
.generic1
.generic1
personalised-tin-blank_1_2_750x.pngdescriptive1
0generic1
Current: 0
Suggested: action.jpg

See Accessibility tab for detailed alt text quality analysis.

A+
Schema Markup Audit
4 schema types detected
PASS

Rich result eligibility

Organization Eligible

Organization knowledge panel

Article Eligible

Article rich results

BreadcrumbList Eligible

Breadcrumb trail

Detected schema types

WebPage json-ld
0/0 required
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
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 — Signals freshness to the news algorithm
  • description — Add a description / dek string Used as the result snippet
Google's spec for this type
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

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