Skip to content
https://cutt.ly

SEO

· 7 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
95
GRADE
A
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://cutt.ly
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Critical::
Canonical target returns 403
Search engines cannot follow this canonical, effectively orphaning this page.
Canonical URL Problem
Page URL https://cutt.ly Canonical https://cutt.ly Match Self-referencing (correct) Target 403

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: URL Shortener with Branded Short Links & QR Codes | Cuttly
Info::
Title length (58 chars) is optimal
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"URL Shortener with Branded Short Links & QR Codes | Cuttly"

58 characters Optimal ✓
Title: URL Shortener with Branded Short Links & QR Codes | Cuttly
H1: The URL shortener that does more.
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
3137 words, Difficult
PASS
3137 words, Difficult
Info::
Page has 3137 words — good depth for search engines
Info::
Reading level: Difficult (grade 12)
3137 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 12

Text-to-HTML Ratio

10% text 90% HTML

20 KB / 199 KB

A+
Image SEO
28 images, 28 descriptive filenames
PASS
28 images, 28 descriptive filenames
Info::
All images have descriptive filenames
28 descriptive
0 hash-based
0 generic
28 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

WebSite Eligible

Sitelinks search box

Organization Eligible

Organization knowledge panel

FAQPage Eligible

FAQ rich results

Detected schema types

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
Organization json-ld → Organization knowledge panel
2/2 required · 3/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 — Used as the panel summary
Google's spec for this type
WebPage json-ld
0/0 required
WebApplication json-ld
0/0 required
SoftwareApplication json-ld
0/0 required
DefinedTerm json-ld
0/0 required
FAQPage json-ld → FAQ rich results
1/1 required
Required fields (Google)
  • mainEntity — Required — without this the FAQ schema is invalid
Google's spec for this type

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

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