Skip to content
https://majed-phone-hub.base44.app

SEO

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

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

Checks
14
11 PASS 2 REVIEW
C
Content Depth
Action
780 words, Very Easy
REVIEW
780 words, Very Easy
Info::
Page has 780 words of content
Info::
Text-to-HTML ratio is 4%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Very Easy (grade 5)
780 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 5

Text-to-HTML Ratio

4% text 96% HTML

7 KB / 171 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.

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://majed-phone-hub.base44.app
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Canonical URL Configured
Page URL https://majed-phone-hub.base44.app Canonical https://majed-phone-hub.base44.app Match Self-referencing (correct) Target 200 ✓
A
Meta Tags
Title optimized
PASS
Title optimized
Info::
Page title is set
Got: الماجد فون | Al-Majed Phone
Info::
Title length (36 chars) is optimal
Info::
Meta description is 221 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

"الماجد فون | Al-Majed Phone"

36 characters Optimal ✓
Title: الماجد فون | Al-Majed Phone
H1: الماجد فون
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
1 title-style issue(s) detected
PASS
1 title-style issue(s) detected
Info::
Title uses 2 different separator characters: |, -
The page title `الماجد فون | Al-Majed Phone` 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+
Image SEO
31 images, 26 descriptive filenames
PASS
31 images, 26 descriptive filenames
Info::
5 image(s) have hash/generic filenames
26 descriptive
2 hash-based
3 generic
31 total
FilenameQualityAltIssues
9k=generic✓1
Current: 9k=
Suggested: ldaakaaqakaaqakiaoigcakiaqoawvaavfaaabaauaaaaaaaaaaaaaeavfaeauaebqbafeavaaaaeaurqaqaaaeaaaaaabaafaaabqaqafaaaaaaaaabqaaaabqaqbaaaajaaaabqbaaaaaaaaaaaaaaeaaaaaaaaaaaaaeaaabaaaaf.jpg
9k=generic✓1
Current: 9k=
Suggested: ldaakaaqakaaqakiaoigcakiaqoawvaavfaaabaauaaaaaaaaaaaaaeavfaeauaebqbafeavaaaaeaurqaqaaaeaaaaaabaafaaabqaqafaaaaaaaaabqaaaabqaqbaaaajaaaabqbaaaaaaaaaaaaaaeaaaaaaaaaaaaaeaaabaaaaf.jpg
2Q==generic✓1
Current: 2Q==
Suggested: hadpl2z5ozgrivayaataaaqaaaaaaaaaaf.jpg
1784700201972.pnghash✓1
Current: 1784700201972.png
Suggested: j2kk9hgs.png
1783669464536.pnghash✓1
Current: 1783669464536.png
Suggested: vtjdpvx4.png

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 (11 URLs, 2 KB)
PASS
Sitemap structure / size look healthy (11 URLs, 2 KB)
Info::
Sitemap structure / size look healthy (11 URLs)
A
Markup Quality
1 markup-quality issue(s) detected
PASS
1 markup-quality issue(s) detected
Info::
`<meta charset>` declared at byte 1255 -- past the 1024-byte spec window
The HTML5 spec requires the encoding declaration to appear in the first 1024 bytes. Browsers that started parsing in a default encoding and discover the real charset later DISCARD parsing state and re-parse from the top -- a measurable hit to First Contentful Paint. Move the `<meta charset>` tag to be the first child of `<head>`.
A+
Schema Markup Audit
2 schema types detected
PASS

Rich result eligibility

WebSite Eligible

Sitelinks search box

Organization Eligible

Organization knowledge panel

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 · 1/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 — Add sameAs URLs for social profiles 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

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