Scanned sites / ascentech.ru

SEO report for ascentech.ru DR 0

The latest Site Spider scan of ascentech.ru, with 1 scan on record. Each scan is at its own address, for example /domain/ascentech-ru/2026-11-02-0647.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Latest scan

Scanned 2026-11-02 06:47:17 UTC, finished 2026-11-02 07:20:22 UTC

Site: https://ascentech.ru/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

90/ 100Excellent

On November 2, 2026 the Site Spider crawled 113 pages and 257 assets of ascentech.ru, starting from https://ascentech.ru/. It scored 90 out of 100, an excellent result. 5 of 33 checks found something to fix, led by meta descriptions (83), title tags (35), indexability (5); 22 checks passed. Most of the points went to meta descriptions (−5.9), title tags (−3.1), indexability (−0.4). 6 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: Medium1 medium and 1 info findings. See the security findings ↓

Pages crawled
113
Assets fetched
257
Status
Completed
Checks with issues
5 of 33
CoverageComplete crawl

370 of 370 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 3 link destinations on other sites were checked.

  • Title tags35 issues
    35 of 113 pages have title issues.
    −3.1 points
  • Meta descriptions83 issues
    83 of 113 pages have meta description issues.
    −5.9 points
  • HeadingsOK
    0 of 113 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sitesOK
    0 destinations answered with an error, of 3 destinations checked.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responses1 noted
    1 URL did not return a 2xx response. 0 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability5 issues
    5 of 113 indexable pages have indexability warnings.
    −0.4 points
  • Image alt textOK
    0 of 681 image references have no alt attribute. 221 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 257 fetched assets.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage5 issues
    1 sitemap listing 108 URLs: 5 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −0.3 points
  • Internal link countsOK
    Internal link counts for 113 pages; none is a dead end or buried.
  • Thin content1 issue
    1 of 113 pages have fewer than 200 words.
    −0.1 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 113 page URLs are plain lowercase addresses without parameters.
  • Canonicals5 noted
    5 of 113 pages have a canonical worth checking.
  • Robots directives108 noted
    108 pages carry a robots directive; 5 carry none.
  • Anchor textOK
    Every internal link has descriptive, followed anchor text.
  • Title and heading structure15 noted
    15 of 113 pages could use the title, heading and snippet space better.
  • Image weight and alt length42 noted
    41 images over 100 KB; 1 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 113 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    108 of 113 indexable pages carry structured data: Organization (108), ListItem (108), BreadcrumbList (107), WebPage (64), CreativeWork (38). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 113 pages with enough text to compare.
  • Soft 404sOK
    None of 113 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positions1 noted
    1 of 113 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 16 response headers recorded across 370 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 113 pages; 88 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • SpellingOK
    No unfamiliar lower-case words on 113 pages (English pages only).

Where this site sits among all scanned sites

2561 sites, median 80%, average 78%

ascentech.ru scores 90%, higher than 88% of the 2561 scanned sites. See the full ranking.

0601190%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 9 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 12 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 31 sites66%: 38 sites67%: 39 sites68%: 38 sites69%: 48 sites70%: 48 sites71%: 74 sites72%: 72 sites73%: 76 sites74%: 76 sites75%: 80 sites76%: 93 sites77%: 103 sites78%: 115 sites79%: 103 sites80%: 119 sites81%: 112 sites82%: 116 sites83%: 116 sites84%: 118 sites85%: 95 sites86%: 81 sites87%: 85 sites88%: 66 sites89%: 71 sites90%: 47 sites91%: 56 sites92%: 40 sites93%: 28 sites94%: 20 sites95%: 13 sites96%: 15 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites90% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Your site is performing well with a health score of 90/100. However, there are critical areas to address, including title and meta description issues, missing canonical tags, and sitemap updates for certain pages.

  1. 1

    Fix Non-200 Response

    Why: Improving the status of the non-200 asset can enhance user experience.

    How: Remove or correct the asset at https://ascentech.ru/assets/css/%23n causing a 404 error.

    Checks: status-codes

  2. 2

    Optimize Title Tags

    Why: Improving title tags can boost click-through rates and rankings.

    How: Revise the 35 pages with long (>60 characters) title tags to be concise and within 60 characters.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: Better meta descriptions can lead to higher CTR and engagement.

    How: Update the 83 pages with meta description issues to be brief and informative, ideally under 155 characters.

    Checks: meta-descriptions

  4. 4

    Add Canonical Tags

    Why: Canonical tags help prevent duplicate content issues.

    How: Add canonical tags to the 5 pages flagged for 'No canonical'. Ensure they point to the preferred URL.

    Evidence: 5 pages flagged: No canonical.

    5 pages affected

    Depends on: Confirm the pages really share a cause before changing them together.

    Checks: indexability

  5. 5

    Update Sitemap Coverage

    Why: Including all relevant pages in the sitemap enhances their discoverability.

    How: Add the 5 missing pages, including the cookie policy and privacy policy, into the sitemap.

    Checks: sitemap-coverage

  6. 6

    Address Thin Content

    Why: Improving thin content can enhance user engagement and SEO.

    How: Expand the content of the page at https://ascentech.ru/cookie-policy to exceed 200 words.

    Checks: thin-content

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

The security review identifies issues with the Content Security Policy allowing unsafe scripts and a sensitive path disclosed in robots.txt. These issues could expose the site to script injection risks and unnecessary probing.

  • 0 high
  • 1 medium
  • 0 low
  • 1 info
  1. 1

    Weak Content Security PolicyMedium

    Why it matters: The site’s Content Security Policy (CSP) allows 'unsafe-inline' scripts, reducing its effectiveness against script injection attacks.

    Fix: Update the CSP header to prohibit 'unsafe-inline' and 'unsafe-eval'. An example header: `Content-Security-Policy: default-src 'self'; script-src 'self' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net;`

    Evidence: Content Security Policy

  2. 2

    Sensitive Paths in robots.txtInfo

    Why it matters: The robots.txt file discloses a private path (/config/) that may lead to potential probing or unauthorized access attempts.

    Fix: Consider restricting access to sensitive paths through proper authentication and authorization instead of relying solely on robots.txt.

    Evidence: Sensitive paths in robots.txt

What the checks found

  • NoteContent Security Policy

    A Content-Security-Policy is set, but it allows inline or eval scripts ('unsafe-inline' / 'unsafe-eval'), which removes most of its protection against injected scripts.

    • https://ascentech.ru/ → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/works → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/services → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/blog → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/niches → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/privacy-policy → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/personal-data-consent → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/cookie-policy → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/data-processing-requests → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/user-agreement → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/works/catalog-theme → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
    • https://ascentech.ru/works/eltiko → default-src 'self'; script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net; font-src 'self'; connect-src 'self' https://mc.yandex.ru http
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /config/
12 checks passed, 2 not applicable
  • OKHTTPS

    All 113 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 113 HTML pages.

  • OKClickjacking protection

    x-frame-options is set on all 113 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 113 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 113 HTML pages.

  • OKPermissions policy

    permissions-policy is set on all 113 HTML pages.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    35 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKThird-party scripts

    The sampled pages load no scripts from other domains.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Earlier scans of ascentech.ru

No other scans of this site yet.

Sites scoring near ascentech.ru

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling ascentech.ru from its pages as published, the way a search engine does. It shows summary figures only.

Own ascentech.ru?