SEO
· 7 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.Cross-tab audit — SEO, performance, crawlability, mobile, structured data
ACanonical URLMinor issuesPASS
A+Meta TagsTitle optimizedPASS
"HONOR 香港 - HONOR 智能手機"
Consider differentiating — the title is for search results, the H1 is for the page.
Title and H1 match exactly — internally consistent but misses an opportunity to optimize each for its audience (Title for SERP CTR, H1 for on-page).
Learn more ▾ ▴
Title and H1 don't have to be identical — and often shouldn't be. The Title competes for SERP click-through (lead with keyword + value prop), while the H1 confirms to the visitor they're on the right page (more conversational is fine). Differentiating gains both surfaces.
Source: Google Search Central / on-page SEO
AContent Depth1161 words, Very DifficultPASS
Good depth
Reading level
Grade 24
Text-to-HTML Ratio
8 KB / 569 KB
Very low ratio suggests heavy framework overhead or boilerplate.
Informational: ratio of visible text bytes to total HTML bytes. Very low ratios suggest excessive markup overhead.
A+Internal Links374 internal, 74 externalPASS
Link Distribution
Anchor Text Quality
Most Linked Internal Pages
| # | URL | Links |
|---|---|---|
| 1 | /hk/phones/honor-600-pro/ | 22 |
| 2 | /hk/laptops/honor-magicbook-art-14-2025/ | 19 |
| 3 | /hk/wearables/honor-watch-fit/ | 15 |
| 4 | /hk/tablets/honor-pad-x8b/ | 15 |
| 5 | /hk/wearables/honor-watch-5-ultra/ | 13 |
| 6 | /hk/audio/honor-earbuds-open/ | 13 |
| 7 | javascript:void(0) | 11 |
| 8 | /hk/phones/honor-600-lite/ | 11 |
| 9 | 9 | |
| 10 | /hk/tablets/comparison/ | 8 |
Top External Domains
| Domain | Links |
|---|---|
| honor-hk.com | 52 |
| honor-eshop.omniwe.site | 8 |
| www.honor.com | 6 |
| agreement.itsec.honor.com | 5 |
| www.facebook.com | 1 |
| www.instagram.com | 1 |
| www.youtube.com | 1 |
A+Image SEO314 images, 283 descriptive filenamesPASS
| Filename | Quality | Alt | Issues |
|---|---|---|---|
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| star.svg | descriptive | ✗ | 1 |
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| 6.svg | generic | ✓ | 1 |
Current: 6.svg Suggested: header-svg.svg | |||
| star.svg | descriptive | ✗ | 1 |
| star-mov.webp | descriptive | ✗ | 1 |
| star-mov.webp | descriptive | ✗ | 1 |
| . | generic | ✓ | 1 |
| star-mov.webp | descriptive | ✗ | 1 |
| star-mov.webp | descriptive | ✗ | 1 |
| star-mov.webp | descriptive | ✗ | 1 |
| . | generic | ✓ | 1 |
| star-mov.webp | descriptive | ✗ | 1 |
| star-mov.webp | descriptive | ✗ | 1 |
| . | generic | ✗ | 2 |
See Accessibility tab for detailed alt text quality analysis.
A+Schema Markup Audit1 schema types detectedPASS
Rich result eligibility
Organization knowledge panel
Detected schema types
Organization json-ld → Organization knowledge panel2/2 required · 3/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 — Used as the panel summary
Adding these recommended fields improves chances of getting Organization knowledge panel in search results.
Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).
Source: Google Search Central
Hreflang0 hreflang tagsINFO
No hreflang tags detected.
Hreflang tags are only needed for multilingual or multi-regional sites.