Skip to content
https://artigianmobiliremanzacco.cfd

SEO

· 14 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
2
PASS
10
INFO
1

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

Checks
14
10 PASS 2 REVIEW 1 FIX
D
Sitemap Freshness
Action
Sitemap appears abandoned (no lastmod within 1 year)
FIX
Sitemap appears abandoned (no lastmod within 1 year)
Warning::
Sitemap appears abandoned -- newest lastmod is 3 years ago
No URL in the sitemap has been updated in the last year. Search engines treat this as a signal the site is no longer maintained and may deprioritize crawling. Either update the sitemap with current lastmod values or remove it entirely if the site is intentionally static.
B
Canonical URL
Minor issues
REVIEW
Minor issues
Info::
Canonical tag present
Got: https://www.artigianmobiliremanzacco.cfd/
Warning::
Canonical does not match final URL (https://artigianmobiliremanzacco.cfd)
Info::
Canonical target returns 200
Info::
Canonical points to a different domain
Warning::
Canonical www-ness doesn't match the final URL
Either the canonical has 'www.' and the final URL doesn't, or vice versa. Search engines may index both forms as duplicates. Pick one and use it consistently in the canonical AND the redirect target.
Info::
Page not found in sitemap.xml
Got: https://artigianmobiliremanzacco.cfd
Canonical URL Configured
Page URL https://artigianmobiliremanzacco.cfd Canonical https://www.artigianmobiliremanzacco.cfd/ Match Points to a different page Target 200 ✓

Either the canonical has 'www.' and the final URL doesn't, or vice versa. Search engines may index both forms as duplicates. Pick one and use it consistently in the canonical AND the redirect target.

Why this matters

Canonical has 'www.' and final URL doesn't (or vice versa). Search engines may index both forms as duplicates.

Learn more ▾

Pick one form -- with or without www -- and use it consistently in the canonical AND the redirect target. Both forms can resolve, but unless one redirects to the other AND the canonical agrees, search engines may treat them as duplicate-content variants.

Source: Google Search Central

C
Content Depth
Action
540 words, Very Difficult
REVIEW
540 words, Very Difficult
Info::
Page has 540 words of content
Info::
Text-to-HTML ratio is 2%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Very Difficult (grade 19)
540 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 19

Text-to-HTML Ratio

2% text 98% HTML

4 KB / 161 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+
Meta Tags
Title optimized
PASS
Title optimized
Info::
Page title is set
Got: Arredi personalizzati | Remanzacco, UD | Artigian Mobili
Info::
Title length (56 chars) is optimal
Info::
Meta description length (154 chars) is optimal
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"Arredi personalizzati | Remanzacco, UD | Artigian Mobili"

56 characters Optimal ✓
Title: Arredi personalizzati | Remanzacco, UD | Artigian Mobili
H1: Falegnami per arredamento su misura a Remanzacco
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+
Image SEO
7 images, 7 descriptive filenames
PASS
7 images, 7 descriptive filenames
Info::
All images have descriptive filenames
7 descriptive
0 hash-based
0 generic
7 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 × 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 (4 URLs, 994 bytes)
PASS
Sitemap structure / size look healthy (4 URLs, 994 bytes)
Info::
Sitemap structure / size look healthy (4 URLs)
A
Markup Quality
2 markup-quality issue(s) detected
PASS
2 markup-quality issue(s) detected
Info::
2 deprecated HTML4 element(s) used
Elements removed from the HTML spec: <center>, <font>. Modern browsers still render these for backward-compat, but accessibility tools and HTML validators flag them as errors. Replace `<center>` with CSS `text-align: center` or flexbox; `<font>` with CSS color/font-family/font-size; `<marquee>` with CSS animation; `<frameset>`/`<frame>` with iframes or modern layout primitives.
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
1 schema types detected
PASS

Rich result eligibility

WebSite Eligible

Sitelinks search box

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

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