Maintenance rejim sahifa β bu sayt vaqtincha yopilganda foydalanuvchiga ko'rsatiladigan sahifa. Sabab: server update, deploy, ta'mirlash, migration, kritik bug fix. Yaxshi maintenance sahifa β foydalanuvchi sabr qiladi va qaytib keladi. Yomon esa β foydalanuvchi yo'qotish, SEO penalty, brand zarari.
Maintenance sahifa nima uchun kerak
Foydalanuvchi xabardor qilish β \"Sayt vaqtincha yopiq\", endi yo'qolgan deb o'ylamasin.
SEO himoya β Google to'g'ri status code (503) bilan vaqtinchalik ekanini biladi.
Brand image β foydalanuvchi professional kompaniya signal oladi.
Mijoz xizmati β \"Tez orada qaytamiz, sabr qiling\".
HTTP status code 503
503 Service Unavailable β sahifa vaqtincha mavjud emasligini ifoda qiluvchi status code.
Google bot 503 ko'rsa β kontentni o'chirmaydi, vaqtinchalik deb biladi.
Retry-After header β \"X soniyadan keyin qayta urinib ko'ring\".
PHP: http_response_code(503); header('Retry-After: 3600');
200 OK xato
Maintenance sahifa 200 OK status code bilan chiqsa β Google maintenance kontentini real kontent deb indekslaydi.
\"Sayt yopiq\" kontent Google'da chiqadi β yomon.
Albatta 503 ishlatish.
Maintenance sahifa elementlari
Logo β brand identity.
Xabar: \"Tez orada qaytamiz\" yoki \"Sayt yangilanmoqda\".
Tushuntirish: nima uchun yopiq, qancha vaqt.
Estimated time: \"30 daqiqada qaytamiz\".
Contact: muammo bo'lsa qanday bog'lanish.
Social media link.
Status page link β agar bor bo'lsa.
Estimated time
Aniq vaqt bersangiz β ishonchsiz bo'lishi mumkin (kechikish).
Range bersangiz: \"30-60 daqiqa\".
Yoki countdown timer.
Foydalanuvchi kutishi mumkinligini bilishi shart.
Apologetic tone
Xushmuomalalik bilan: \"Uzr so'raymiz\", \"Noqulayliklar uchun kechirim so'raymiz\".
Foydalanuvchi xafa bo'lmasin.
Maintenance image/icon
Tool icon, robot, working illustration.
Yumshoq tone β qattiq emas.
Lottie animation β \"working\" character.
Status page integration
Katta kompaniyalar uchun: dedicated status page (status.example.com).
Real-time service holati: API up/down, database, CDN.
Statuspage.io, Atlassian, Better Uptime.
Maintenance sahifa'dan status page'ga link.
Scheduled vs Emergency maintenance
Scheduled β rejalashtirilgan: oldindan e'lon, off-peak vaqtda (kechqurun).
Emergency β kutilmagan: kritik bug, security issue.
Sahifa har ikkalasi uchun bo'lishi shart.
Partial maintenance
Ba'zan butun sayt emas, faqat ba'zi qism (admin panel, checkout). \"Login muvaqqat ishlamayapti\".
Foydalanuvchi boshqa sahifalardan foydalanishi mumkin.
Bypass admin uchun
Admin maintenance vaqtida sayt'ga kirishi kerak β testing uchun.
IP whitelist yoki cookie bilan bypass.
WordPress'da .maintenance file mehanizmi.
Notification before maintenance
Foydalanuvchini oldindan xabardor qilish:
Site banner β \"Bugun 22:00 da maintenance bo'ladi\".
Email β registered foydalanuvchilarga.
Social media post.
Email notification after
Maintenance tugagandan keyin: \"Hammasi normal, rahmat sabr uchun\".
Affected mijozlarga, agar muhim bo'lsa.
SEO maintenance
503 status code majburiy.
Retry-After header.
Robots.txt o'zgartirmaslik β Google bot kirish ruxsat berishi shart.
Sitemap o'zgarmas.
WordPress maintenance
WordPress core update vaqtida β avtomatik .maintenance file.
Maintenance plugin'lari: Coming Soon Page, SeedProd, Maintenance.
Custom: wp-content/maintenance.php file.
Custom HTML maintenance
.htaccess'da redirect:
RewriteEngine on
RewriteCond %{REMOTE_ADDR} !^123\.123\.123\.123
RewriteCond %{REQUEST_URI} !^/maintenance\.html$
RewriteRule .* /maintenance.html [R=503,L]
Performance maintenance sahifa
Maintenance sahifa engil bo'lishi shart β server load ko'p.
Inline CSS, no external resources, minimal HTML.
CDN β agar mavjud bo'lsa.
Common maintenance xato
1. 200 OK status code β SEO zarar.
2. Estimated time yo'q β foydalanuvchi adashadi.
3. Contact yo'q β \"muammo bo'lsa qaerga?\".
4. Brand identity yo'q β generic sahifa.
5. Mobile ignorate.
Sayt.uz maintenance amaliyot
Sayt.uz da maintenance sahifa kam β uptime 99.9%+.
Yiliga 1-2 marta server upgrade β odatda kechqurun 02:00-03:00.
Custom maintenance sahifa: logo, xabar, estimated time, status page link, contact (Telegram channel).
503 status code va Retry-After header.
Cabinet admin IP whitelist bilan bypass β testing uchun.
Notification: registered foydalanuvchilarga email 24 soat oldin.
Social media (Telegram) β real-time updates.
Natija: foydalanuvchilar maintenance vaqtida sabr qiladi va qaytib keladi. Customer churn yo'q.