Skip to content
https://www.squarespace.com

SEO

· 7 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
94
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
C
Schema Markup Audit
Action
5 schema types detected
REVIEW

Rich result eligibility

WebSite Eligible

Sitelinks search box

Organization Not eligible

Organization knowledge panel

Missing: name, url

LocalBusiness Not eligible

Local business rich results

Missing: name, image

HowTo Eligible

How-to rich results

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
0/2 required · 1/4 recommended
Required fields (Google)
  • name — Add the organization name Required for the knowledge panel
  • url — Add the canonical organization URL Required for entity matching
Recommended fields
  • logo — Add a logo URL (square, ≥112px) 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
LocalBusiness json-ld → Local business rich results
1/3 required · 1/6 recommended
Required fields (Google)
  • name — Add the business name Required for local business rich results
  • address — Required for the local pack and map cards
  • image — Add a storefront photo URL Required — local pack always shows an image
Recommended fields
  • telephone — Add the public-facing phone number Enables click-to-call from search results
  • url — Add the canonical website URL Required for the website-link button
  • openingHours — Shows the open/closed badge
  • aggregateRating — Add aggregateRating with ratingValue and reviewCount Enables star ratings in the local pack
  • geo — Add a GeoCoordinates with latitude and longitude Improves map placement accuracy
  • priceRange — Add priceRange (e.g. "$$") Shows the affordability badge
Google's spec for this type
HowTo json-ld → How-to rich results
2/2 required · 0/3 recommended
Required fields (Google)
  • name — Required for the how-to rich result
  • step — Required — the carousel renders one step per entry
Recommended fields
  • image — Add an image URL for the overall how-to Strongly recommended for visual prominence
  • totalTime — Add totalTime in ISO 8601 duration format Shows the time-to-complete badge
  • estimatedCost — Add MonetaryAmount with currency and value Shows cost expectations to users
Google's spec for this type
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

Your Organization structured data is missing required fields for Google's Organization knowledge panel. Without these, the page won't qualify for rich results.

Why this matters

Schema entity missing required properties — Google's rich-result eligibility check fails; the schema is in source but never renders enhanced.

Source: Google Search Central

Your LocalBusiness structured data is missing required fields for Google's Local business rich results. Without these, the page won't qualify for rich results.

Why this matters

Schema entity missing required properties — Google's rich-result eligibility check fails; the schema is in source but never renders enhanced.

Source: Google Search Central

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

A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://www.squarespace.com/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Canonical URL Configured
Page URL https://www.squarespace.com Canonical https://www.squarespace.com/ Match Self-referencing (correct) Target 200 ✓
A+
Meta Tags
Title: 66 chars
PASS
Title: 66 chars
Info::
Page title is set
Got: Website Builder – Easily Create Your Own Website — Squarespace
Info::
Title is 66 characters — may be truncated in search results
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"Website Builder – Easily Create Your Own Website — Squarespace"

66 characters Will truncate
Title: Website Builder – Easily Create Your Own Website — Squarespace
H1: A website makes it real
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
4006 words, Difficult
PASS
4006 words, Difficult
Info::
Page has 4006 words — good depth for search engines
Info::
Text-to-HTML ratio is 4%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Difficult (grade 14)
4006 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 14

Text-to-HTML Ratio

4% text 96% HTML

26 KB / 633 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
86 images, 75 descriptive filenames
PASS
86 images, 75 descriptive filenames
Info::
11 image(s) have hash/generic filenames
Info::
1 image(s) missing alt text — see Accessibility tab
75 descriptive
0 hash-based
11 generic
86 total
FilenameQualityAltIssues
.generic✗2
.generic✓1
.generic✓1
.generic✓1
.generic✓1
.generic✓1
.generic✓1
.generic✓1
.generic✓1
.generic✓1
.generic✓1

See Accessibility tab for detailed alt text quality analysis.

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