Skip to content
https://mikrorayonservis.az

SEO

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

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

Checks
14
12 PASS 1 REVIEW
B
Content Depth
522 words, Difficult
REVIEW
522 words, Difficult
Info::
Page has 522 words of content
Info::
Reading level: Difficult (grade 12)
522 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 12

Text-to-HTML Ratio

10% text 90% HTML

4 KB / 43 KB

A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://mikrorayonservis.az/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Canonical URL Configured
Page URL https://mikrorayonservis.az Canonical https://mikrorayonservis.az/ Match Self-referencing (correct) Target 200 ✓
A
Meta Tags
Title: 73 chars
PASS
Title: 73 chars
Info::
Page title is set
Got: Kondisioner və kombi ustası Bakı | Təmir, servis – MikrorayonServis
Warning::
Title is 73 characters — will be truncated in search results
Info::
Meta description is 173 characters — truncated on mobile (~160 char limit)
Info::
Title and H1 are well-aligned
Title

"Kondisioner və kombi ustası Bakı | Təmir, servis – MikrorayonServis"

73 characters Will truncate
Title: Kondisioner və kombi ustası Bakı | Təmir, servis – MikrorayonServis
H1: Kondisioner və kombi ustası Bakıda Tam təmir və servis
Match: Similar ✓
Robots: Indexable (no restrictions)
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 `Kondisioner və kombi ustası Bakı | Təmir, servis – Mikrorayo...` 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
5 images, 5 descriptive filenames
PASS
5 images, 5 descriptive filenames
Info::
All images have descriptive filenames
5 descriptive
0 hash-based
0 generic
5 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 (13/13 URLs have lastmod)
PASS
Sitemap updated within 90 days (13/13 URLs have lastmod)
Info::
Sitemap actively maintained — newest lastmod: 1 months ago
Got: 2026-10-12T00:00:00Z
A+
Sitemap × Robots Consistency
No sitemap-vs-robots conflicts in the URL sample
PASS
No sitemap-vs-robots conflicts in the URL sample
Info::
All 5 sampled sitemap URLs are crawlable per robots.txt
A+
Sitemap Hygiene
Sitemap structure / size look healthy (13 URLs, 4 KB)
PASS
Sitemap structure / size look healthy (13 URLs, 4 KB)
Info::
Sitemap structure / size look healthy (13 URLs)
A+
Markup Quality
1 markup-quality issue(s) detected
PASS
1 markup-quality issue(s) detected
Info::
3 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
5 schema types detected
PASS

Rich result eligibility

FAQPage Eligible

FAQ rich results

Organization Eligible

Organization knowledge panel

BreadcrumbList Eligible

Breadcrumb trail

Detected schema types

FAQPage json-ld → FAQ rich results
1/1 required
Required fields (Google)
  • mainEntity — Required — without this the FAQ schema is invalid
Google's spec for this type
Service json-ld
0/0 required
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
[LocalBusiness HVACBusiness] json-ld
0/0 required
BreadcrumbList json-ld → Breadcrumb trail
1/1 required
Required fields (Google)
  • itemListElement — Required — the breadcrumb chain renders nothing without this
Google's spec for this type

Missing schema opportunities

  • easy

    Article

    Page reads as an article (long body + headline) — add Article schema

    Eligible for top-stories carousel and Discover

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