yandex.com

Readiness by lane

Green: yandex.com. Thin bar: Search Engines peer median.

Priority fixes for yandex.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Enable

   Mobile viewport configured

   Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

   Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

   What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

   83% of Search Engines peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Responsive Web Design Checklist for Real Devices

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for yandex.com was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   51% of Search Engines peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   30% of Search Engines peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   60% of Search Engines peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

What yandex.com already does well

Practices fewer than half of Search Engines peers use.

• security.txt publishedsecurity.txt with a contact found.11% of peers
• Content Security Policy presentContent-Security-Policy present.28% of peers
• CAA records limit who can issue certificatesCAA limits issuance to globalsign.com.37% of peers

What we saw

Homepage checked

https://yandex.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 181-day validity, expiring 2027-04-04

DNS operators

Yandex DNS

DMARC policy

p=none

Homepage HTML

322 KB, br

Images on homepage

1

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Search Engines sites

• 1881.no60
• google.com63
• rambler.ru64
• s2earch.io60
• tgramsearch.com64

Search Engines readiness benchmark