Skip to content
https://Mainstreetestatesales.com

SEO

· 14 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
9
INFO
1

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

Checks
14
9 PASS 4 REVIEW
B
Meta Tags
Title: 98 chars
REVIEW
Title: 98 chars
Info::
Page title is set
Got: Main Street Home | Vintage, Antique, New | Boutique Consignment Store – Main Street Estate Sales
Warning::
Title is 98 characters — will be truncated in search results
Info::
Meta description is 305 characters — truncated on mobile (~160 char limit)
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"Main Street Home | Vintage, Antique, New | Boutique Consignment Store\n– Main Street Estate Sales"

98 characters Will truncate
Title: Main Street Home | Vintage, Antique, New | Boutique Consignment Store – Main Street Estate Sales
H1: .item-1{ display:true; white-space: nowrap; } @media(max-width:1600px){ .item-1{ display:none; }
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

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

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 8

Text-to-HTML Ratio

3% text 97% HTML

4 KB / 122 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.

B
Image SEO
10 images, 2 descriptive filenames
REVIEW
10 images, 2 descriptive filenames
Warning::
80% of images have non-descriptive filenames
Search engines use filenames as a signal. Rename to descriptive names like 'team-photo.jpg'.
2 descriptive
0 hash-based
8 generic
10 total
FilenameQualityAltIssues
.generic1
m1.jpggeneric1
Current: m1.jpg
Suggested: files.jpg
m2.jpggeneric1
Current: m2.jpg
Suggested: files.jpg
m4.jpggeneric1
Current: m4.jpg
Suggested: files.jpg
.generic1
.generic1
.generic1
.generic1

See Accessibility tab for detailed alt text quality analysis.

Search engines use filenames as a signal. Rename to descriptive names like 'team-photo.jpg'.

Why this matters

Most image filenames are non-descriptive (hash/IMG_X) — small SEO miss for Image Search ranking.

Source: Google Image SEO

C
Sitemap Freshness
Action
Sitemap exists but no <lastmod> entries
REVIEW
Sitemap exists but no <lastmod> entries
Info::
Sitemap has no <lastmod> entries
Without lastmod, Google can't tell which URLs have changed since the last crawl -- it falls back to crawling everything periodically. Adding lastmod (date or ISO 8601 timestamp) on each <url> entry signals freshness so the crawler prioritizes recently-modified pages.
A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://mainstreetestatesales.com/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Canonical URL Configured
Page URL https://Mainstreetestatesales.com Canonical https://mainstreetestatesales.com/ Match Self-referencing (correct) Target 200 ✓
A
Title Style Depth
1 title-style issue(s) detected
PASS
1 title-style issue(s) detected
Info::
Title uses 2 different separator characters: |, –
The page title `Main Street Home | Vintage, Antique, New | Boutique Consignm...` uses multiple separator characters (|, –). Consistent separator use is a soft signal of careful editorial control; mixed separators usually mean the title was assembled from multiple template fragments (CMS title + brand + section) without a normalization step. Pick one separator (commonly `|`, `-`, or `:`) and stick with it across the whole site.
Got: 2 separators: | –
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 (6 URLs, 1 KB)
PASS
Sitemap structure / size look healthy (6 URLs, 1 KB)
Info::
Sitemap structure / size look healthy (6 URLs)
A+
Markup Quality
1 markup-quality issue(s) detected
PASS
1 markup-quality issue(s) detected
Info::
5 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

Organization Eligible

Organization knowledge panel

WebSite Eligible

Sitelinks search box

Detected schema types

Organization json-ld → Organization knowledge panel
2/2 required · 2/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 — Add an organization description Used as the panel summary
Google's spec for this type
WebSite json-ld → Sitelinks search box
2/2 required · 1/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 — Enables the in-SERP search box
Google's spec for this type

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