Skip to content
https://www.edwardsmoda.it

SEO

· 14 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
97
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://www.edwardsmoda.it/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Canonical URL Configured
Page URL https://www.edwardsmoda.it Canonical https://www.edwardsmoda.it/ Match Self-referencing (correct) Target 200 ✓
A+
Meta Tags
Title optimized
PASS
Title optimized
Info::
Page title is set
Got: Abbigliamento da donna ad Alba Adriatica (TE) | Edward's
Info::
Title length (56 chars) is optimal
Info::
Meta description length (152 chars) is optimal
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"Abbigliamento da donna ad Alba Adriatica (TE) | Edward's"

56 characters Optimal ✓
Title: Abbigliamento da donna ad Alba Adriatica (TE) | Edward's
H1: THE NEW FASHION MOOD
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
2545 words, Very Difficult
PASS
2545 words, Very Difficult
Info::
Page has 2545 words — good depth for search engines
Info::
Text-to-HTML ratio is 5%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Very Difficult (grade 14)
2545 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 14

Text-to-HTML Ratio

5% text 95% HTML

16 KB / 349 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
25 images, 25 descriptive filenames
PASS
25 images, 25 descriptive filenames
Info::
All images have descriptive filenames
25 descriptive
0 hash-based
0 generic
25 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 (773/773 URLs have lastmod)
PASS
Sitemap updated within 90 days (773/773 URLs have lastmod)
Info::
Sitemap actively maintained — newest lastmod: 1 months ago
Got: 2026-10-16T00:00:00Z
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 (773 URLs, 185 KB)
PASS
Sitemap structure / size look healthy (773 URLs, 185 KB)
Info::
Sitemap structure / size look healthy (773 URLs)
A+
Markup Quality
1 markup-quality issue(s) detected
PASS
1 markup-quality issue(s) detected
Info::
1 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
2 schema types detected
PASS

Rich result eligibility

WebSite Eligible

Sitelinks search box

LocalBusiness Eligible

Local business 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
LocalBusiness json-ld → Local business rich results
3/3 required · 3/6 recommended
Required fields (Google)
  • name — Required for local business rich results
  • address — Required for the local pack and map cards
  • image — Required — local pack always shows an image
Recommended fields
  • telephone — Enables click-to-call from search results
  • url — Required for the website-link button
  • openingHours — Add openingHoursSpecification entries Shows the open/closed badge
  • aggregateRating — Add aggregateRating with ratingValue and reviewCount Enables star ratings in the local pack
  • geo — Improves map placement accuracy
  • priceRange — Add priceRange (e.g. "$$") Shows the affordability badge
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 Local business 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