report link
Link directly to these audit results.
https://app.nyman.media/site/crpt.ruChecks that the page returns HTTP 200 when fetched. If crawlers cannot reliably fetch the URL, citations and visibility signals break.
HTTP 200
The audited URL returns a successful HTTP 200 response with usable page content.
LLMs and their web crawlers (GPTBot, ClaudeBot, etc.) discard URLs that return non-200 status codes. A page that cannot be fetched simply cannot appear in AI-generated responses or citations.
A 200 response is the baseline requirement for indexing; Googlebot drops non-200 URLs from its queue, so the page earns zero organic traffic regardless of its content quality.
100% of Technology sites pass this check. This site is pass; 100% of the benchmark has the same status.
Evaluates page served over HTTPS against its documented passing condition. The exact target appears under Expected behavior.
HTTPS
The canonical page is served securely over HTTPS, with HTTP requests redirected to it.
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
99.3% of Technology sites pass this check. This site is pass; 99.3% of the benchmark has the same status.
Evaluates redirect chain ≤ 1 hop against its documented passing condition. The exact target appears under Expected behavior.
0 redirect(s)
Requests reach the final page in no more than one redirect hop.
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
81.6% of Technology sites pass this check. This site is pass; 81.6% of the benchmark has the same status.
Evaluates response time < 3 s against its documented passing condition. The exact target appears under Expected behavior.
1492 ms
The initial HTML response completes in 1,500 ms or less, reducing crawler timeouts and shortening the wait before rendering begins.
Slow pages increase the likelihood that a crawl times out or is abandoned mid-response; fast pages are more likely to be fully fetched and included in AI knowledge bases.
Core Web Vitals (particularly Time to First Byte) directly influence Google's page experience signals, and slow pages are systematically demoted in competitive SERPs.
86% of Technology sites pass this check. This site is pass; 86% of the benchmark has the same status.
Evaluates HTML size reasonable (< 512 KB) against its documented passing condition. The exact target appears under Expected behavior.
43 KB
The uncompressed HTML response remains at or below 512 KB so crawlers can parse it without excessive transfer or memory cost.
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
75.4% of Technology sites pass this check. This site is pass; 75.4% of the benchmark has the same status.
Evaluates main content is present without running JavaScript against its documented passing condition. The exact target appears under Expected behavior.
4886 characters of text present in the served HTML
The primary page content is present in the served HTML without requiring client-side JavaScript execution.
Reliable, directly parseable responses make it more likely that AI crawlers can retrieve, attribute, and cite the intended URL.
Response integrity, canonicalization, and crawl performance affect whether search engines can index the preferred page consistently.
93% of Technology sites pass this check. This site is pass; 93% of the benchmark has the same status.
Evaluates AI crawlers not blocked against its documented passing condition. The exact target appears under Expected behavior.
robots.txt missing
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates sitemap declared in robots.txt against its documented passing condition. The exact target appears under Expected behavior.
robots.txt missing
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates sitemap available against its documented passing condition. The exact target appears under Expected behavior.
Not found (404)
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates llms.txt available and well-formed against its documented passing condition. The exact target appears under Expected behavior.
Missing
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates ai.txt available and well-formed against its documented passing condition. The exact target appears under Expected behavior.
Missing (404)
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates robots.txt available against its documented passing condition. The exact target appears under Expected behavior.
Missing (not required for crawlability)
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates robots.txt does not blanket-block all crawlers against its documented passing condition. The exact target appears under Expected behavior.
robots.txt missing
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates meta robots is not noindex against its documented passing condition. The exact target appears under Expected behavior.
Missing
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates meta robots does not block AI against its documented passing condition. The exact target appears under Expected behavior.
Missing
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates X-Robots-Tag is not noindex against its documented passing condition. The exact target appears under Expected behavior.
Missing
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates X-Robots-Tag does not block AI against its documented passing condition. The exact target appears under Expected behavior.
Missing
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates sitemap looks like XML (not HTML) against its documented passing condition. The exact target appears under Expected behavior.
Sitemap missing (scored by the availability check)
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates current page found in sitemap against its documented passing condition. The exact target appears under Expected behavior.
Sitemap unavailable
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates AI crawlers can fetch the page against its documented passing condition. The exact target appears under Expected behavior.
Reachable for GPTBot, ClaudeBot, PerplexityBot
Crawler directives and server behavior consistently allow the discovery policy intended for this page.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates meta description present against its documented passing condition. The exact target appears under Expected behavior.
Missing
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates exactly one H1 against its documented passing condition. The exact target appears under Expected behavior.
0
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates canonical URL present against its documented passing condition. The exact target appears under Expected behavior.
Missing
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Checks whether OpenGraph title, description, and image tags are present so shared links render with rich previews.
title=false, desc=false, image=false
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates title length reasonable against its documented passing condition. The exact target appears under Expected behavior.
7 chars
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates title and H1 aligned against its documented passing condition. The exact target appears under Expected behavior.
Missing H1 text
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates meta description length reasonable against its documented passing condition. The exact target appears under Expected behavior.
Missing (scored by the presence check)
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates canonical URL matches site origin against its documented passing condition. The exact target appears under Expected behavior.
Missing canonical (scored by the presence check)
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates canonical URL matches the current page URL against its documented passing condition. The exact target appears under Expected behavior.
No canonical URL set
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates title tag present against its documented passing condition. The exact target appears under Expected behavior.
Главная
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates HTML lang attribute present against its documented passing condition. The exact target appears under Expected behavior.
ru
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates viewport meta present against its documented passing condition. The exact target appears under Expected behavior.
Present
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates favicon link present against its documented passing condition. The exact target appears under Expected behavior.
Present
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates text-to-HTML ratio reasonable against its documented passing condition. The exact target appears under Expected behavior.
11%
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates sufficient on-page text against its documented passing condition. The exact target appears under Expected behavior.
4886 chars
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates images have alt text against its documented passing condition. The exact target appears under Expected behavior.
No images found
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates viewport configured for mobile devices against its documented passing condition. The exact target appears under Expected behavior.
Viewport meta tag present. Page configured for mobile rendering
The served HTML exposes the page topic and main content through valid, machine-readable markup.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
JSON-LD is structured data that helps machines understand this page and its entities (organization, website, products, etc.).
Missing
The page includes parseable JSON-LD that describes the page or the entity behind it.
JSON-LD is the format AI systems most reliably parse when extracting structured facts about an entity; its absence forces LLMs to rely on heuristic text extraction, which is less accurate and less authoritative.
JSON-LD is Google's preferred structured data format; correctly implemented, it unlocks rich result types (sitelinks, FAQs, product panels) that significantly improve click-through rates.
46.4% of Technology sites pass this check. This site is fail; 53.6% of the benchmark has the same status.
Checks whether Organization schema is present in your JSON-LD. This helps systems identify the entity behind the page (name, logo, contact points, etc.).
Missing (JSON-LD missing)
The page includes valid Organization structured data when that type accurately represents the visible content.
Organization schema gives LLMs a canonical, machine-readable definition of the entity (name, logo, sameAs links), reducing the chance of misattribution or confusion with similarly named entities.
Organisation structured data feeds the Google Knowledge Panel and entity-recognition algorithms, improving brand appearance in branded search queries and knowledge graphs.
28.8% of Technology sites pass this check. This site is fail; 71.2% of the benchmark has the same status.
Checks whether WebSite schema is present in your JSON-LD. This helps systems understand the site as a whole and can support sitelinks/search actions.
Missing (JSON-LD missing)
The page includes valid WebSite structured data when that type accurately represents the visible content.
WebSite schema communicates the site's purpose and searchable structure to AI systems, enabling them to correctly classify the domain as a coherent entity rather than a random collection of pages.
WebSite schema enables the Sitelinks Searchbox feature in Google results and reinforces the association between a domain and its brand name in entity-based ranking systems.
27.3% of Technology sites pass this check. This site is fail; 72.7% of the benchmark has the same status.
Checks whether WebPage schema is present in your JSON-LD. This helps systems understand the page type and main entity being described.
Missing (JSON-LD missing)
The page includes valid WebPage structured data when that type accurately represents the visible content.
WebPage schema allows AI crawlers to understand the type, author, and primary topic of a page without needing to infer these from prose, improving the accuracy of AI-generated summaries.
Page-level schema enriches Google's understanding of content type and authorship, contributing to E-E-A-T signals and supporting rich results for review, article, and FAQ pages.
17.6% of Technology sites pass this check. This site is fail; 82.4% of the benchmark has the same status.
Checks whether BreadcrumbList schema is present in your JSON-LD. Breadcrumbs can improve understanding of site structure and context.
Missing (JSON-LD missing)
The page includes valid BreadcrumbList structured data when that type accurately represents the visible content.
BreadcrumbList schema tells AI systems where a page sits within the site hierarchy, which helps LLMs contextualise content and understand whether a page is a top-level resource or a deep sub-topic.
Breadcrumb markup enables the breadcrumb trail to appear in Google SERP snippets, improving visual clarity and typically increasing organic click-through rates.
9% of Technology sites pass this check. This site is fail; 91% of the benchmark has the same status.
Checks whether FAQPage schema is present in your JSON-LD. Useful when you have real FAQ content on the page.
Missing (JSON-LD missing)
The page includes valid FAQPage structured data when that type accurately represents the visible content.
FAQPage schema presents question–answer pairs in a format LLMs are optimised to consume directly; well-structured FAQ pages dramatically increase the probability of being used as an AI answer source.
FAQ rich results expand the SERP footprint significantly; pages with FAQ schema can occupy two to three times the normal result space, substantially boosting click-through rates.
3.6% of Technology sites pass this check. This site is fail; 96.4% of the benchmark has the same status.
Checks whether Article/NewsArticle/BlogPosting schema is present in your JSON-LD (if applicable). Helps machines understand content type and authorship.
Missing (JSON-LD missing)
The page includes valid Article structured data when that type accurately represents the visible content.
Article schema signals authorship, publication date, and content type to LLMs, making it easier for AI systems to assess freshness and credibility before citing or summarising the content.
Article schema can unlock Top Stories and news carousels in Google results, and the author/datePublished fields directly contribute to E-E-A-T signals.
0.7% of Technology sites pass this check. This site is fail; 99.3% of the benchmark has the same status.
Checks whether Person schema is present in your JSON-LD (if applicable). Useful for personal brands and author entities.
Missing (JSON-LD missing)
The page includes valid Person structured data when that type accurately represents the visible content.
Person schema is how AI knowledge bases build named-entity graphs; without it, LLMs must guess biographical details from unstructured text, leading to factual errors in AI-generated profiles.
Person structured data strengthens author entity recognition in Google's E-E-A-T framework, improving the ranking authority of content attributed to that individual.
0.4% of Technology sites pass this check. This site is fail; 99.6% of the benchmark has the same status.
Checks whether Product schema is present in your JSON-LD (if applicable). Useful for ecommerce/product pages and rich understanding.
Missing (JSON-LD missing)
The page includes valid Product structured data when that type accurately represents the visible content.
Product schema gives AI shopping and comparison agents the structured price, availability, and description data they need to reliably recommend or compare offerings.
Product markup unlocks Google's Product rich results and Merchant Center integrations, placing product details directly in search snippets and potentially in Shopping panels.
1.4% of Technology sites pass this check. This site is fail; 98.6% of the benchmark has the same status.
JSON-LD is structured data that helps machines understand this page and its entities (organization, website, products, etc.).
No JSON-LD scripts to validate
Every JSON-LD block parses as valid JSON and can be consumed by structured-data tools.
Syntactically invalid JSON-LD is silently discarded by parsers; even well-intentioned structured data provides zero benefit to AI systems if the underlying JSON cannot be parsed.
Google's Rich Results Test rejects invalid JSON-LD; syntax errors mean no rich results are eligible, negating the investment made in adding structured data.
46% of Technology sites pass this check. This site is warn; 0% of the benchmark has the same status.
JSON-LD is structured data that helps machines understand this page and its entities (organization, website, products, etc.).
No JSON-LD to validate
Detected schema types include the required properties for the entities they describe.
Valid structured data gives machines an explicit representation of the page and its entities, reducing ambiguity during extraction.
Accurate structured data supports entity understanding and eligibility for applicable search-result enhancements.
96% of Technology sites pass this check. This site is pass; 96% of the benchmark has the same status.
Evaluates organization or LocalBusiness schema present against its documented passing condition. The exact target appears under Expected behavior.
JSON-LD missing
Organization or LocalBusiness schema identifies the entity operating the site with consistent core properties.
Entity clarity is the degree to which AI systems can identify the brand, organisation, or person behind a site. A well-populated Organization schema with sameAs links, legalName, and logo gives models a canonical source of truth and reduces hallucinated profiles.
Organisation detail in structured data feeds the Knowledge Panel, reinforces branded query dominance, and provides Google with verified facts about the entity to surface in AI Overviews.
28.8% of Technology sites pass this check. This site is warn; 0% of the benchmark has the same status.
Evaluates brand/entity name appears in title against its documented passing condition. The exact target appears under Expected behavior.
Missing "crpt"
The page title names the audited brand or entity clearly enough to connect the page to it.
Including the entity or brand name in the title tag helps AI systems connect this URL to the correct real-world brand; without it, pages are harder to attribute correctly in entity-based reasoning.
Brand-inclusive titles improve branded search recall and help Google's entity graph link the page to the correct brand entity, supporting rich results and Knowledge Panel associations.
67.3% of Technology sites pass this check. This site is warn; 0% of the benchmark has the same status.
Evaluates brand/entity name appears in H1 against its documented passing condition. The exact target appears under Expected behavior.
Missing H1 text
The primary heading names the audited brand or entity where that identity is central to the page.
The H1 is the strongest in-document entity signal. Naming the brand or entity here tells LLMs that the page is an authoritative on-site resource for that organisation, product, or person.
Entity presence in H1 reinforces brand-to-page association in Google's NLP layer, improving dominance in branded SERP queries and supporting entity-based rich features.
12.2% of Technology sites pass this check. This site is warn; 0% of the benchmark has the same status.
Checks whether social media profile links are present in structured data.
None found
The site links to its authoritative external profiles using consistent entity identity.
sameAs links to social profiles help AI knowledge graphs verify that this web entity is the same brand, organisation, or person represented on other trusted platforms.
Linking to verified social profiles in structured data strengthens E-E-A-T by corroborating the entity's real-world presence and is used by Google to populate Knowledge Panel social links.
60.8% of Technology sites pass this check. This site is warn; 0% of the benchmark has the same status.
Evaluates privacy policy link present against its documented passing condition. The exact target appears under Expected behavior.
No
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates terms link present against its documented passing condition. The exact target appears under Expected behavior.
No
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates testimonials / case studies signals against its documented passing condition. The exact target appears under Expected behavior.
Not detected
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates press / featured-in signals against its documented passing condition. The exact target appears under Expected behavior.
Not detected
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates HTTP security headers present (HSTS, CSP, X-Content-Type, X-Frame, Referrer-Policy, Permissions-Policy) against its documented passing condition. The exact target appears under Expected behavior.
3/6 recommended headers present. Missing: Strict-Transport-Security, Referrer-Policy, Permissions-Policy
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates RSS or Atom feed discoverable against its documented passing condition. The exact target appears under Expected behavior.
No RSS/Atom feed link: LLMs rely on crawling only
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates cookies use Secure, HttpOnly, and SameSite flags against its documented passing condition. The exact target appears under Expected behavior.
Cookie attribute(s) missing: Secure
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates hreflang tags for multilingual targeting against its documented passing condition. The exact target appears under Expected behavior.
No hreflang tags (only relevant for multilingual sites)
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates speakable schema markup present against its documented passing condition. The exact target appears under Expected behavior.
No Speakable schema (optional for voice assistant targeting)
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates searchAction schema present (sitelinks search box) against its documented passing condition. The exact target appears under Expected behavior.
No SearchAction schema (optional for sitelinks)
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates about/Company link present against its documented passing condition. The exact target appears under Expected behavior.
Yes
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates contact link present against its documented passing condition. The exact target appears under Expected behavior.
Yes
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates internal link density supports entity graph crawling against its documented passing condition. The exact target appears under Expected behavior.
55 internal links: strong entity graph signal
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates no API keys or credentials exposed in client-side code against its documented passing condition. The exact target appears under Expected behavior.
No exposed credentials detected in HTML or first-party JavaScript
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates no sensitive files exposed at well-known paths against its documented passing condition. The exact target appears under Expected behavior.
No sensitive files reachable (10 common paths checked)
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates directory listing is disabled against its documented passing condition. The exact target appears under Expected behavior.
No open directory listings detected
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates no mixed (insecure) content on an HTTPS page against its documented passing condition. The exact target appears under Expected behavior.
All sub-resources loaded securely over HTTPS
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates forms submit over HTTPS against its documented passing condition. The exact target appears under Expected behavior.
No insecure form submissions detected
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates CORS policy is not dangerously permissive against its documented passing condition. The exact target appears under Expected behavior.
No wildcard CORS exposure
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates server software versions are not disclosed in headers against its documented passing condition. The exact target appears under Expected behavior.
No server version disclosure in response headers
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates production source maps are not publicly exposed against its documented passing condition. The exact target appears under Expected behavior.
No exposed source maps detected
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates internal paths are not openly accessible against its documented passing condition. The exact target appears under Expected behavior.
No openly accessible internal paths detected
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates third-party scripts use Subresource Integrity against its documented passing condition. The exact target appears under Expected behavior.
No third-party scripts or stylesheets to protect
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates error pages do not leak stack traces or debug output against its documented passing condition. The exact target appears under Expected behavior.
No framework debug output on a missing-page request
The reported trust or security condition is resolved without weakening the page response or user journey.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates headings use question phrasing (who, what, how…) against its documented passing condition. The exact target appears under Expected behavior.
0/3 headings use question phrasing: LLMs may not extract clear Q&A pairs
Where question-led content is appropriate, at least 30% of H2 and H3 headings map a clear question to its answer.
Headings phrased as questions mirror how users phrase prompts to LLMs; structuring content this way increases the probability that a passage will be returned as a direct answer in conversational AI interactions.
Question-formatted headings align with natural language queries and improve the chance of winning People Also Ask (PAA) boxes, which command high visibility and click share.
4.1% of Technology sites pass this check. This site is warn; 0% of the benchmark has the same status.
Evaluates content uses definition patterns ("X is…", "refers to…") against its documented passing condition. The exact target appears under Expected behavior.
No explicit definition patterns: consider adding "X is…" phrasing for key concepts
Key concepts include concise, explicit definitions that can stand alone when extracted.
Pages that define terms and concepts are natural targets for AI "what is X?" queries; clear definitional structures help LLMs extract and cache concept definitions for conversational use.
Definitional content frequently wins featured snippets for informational queries; the structured "X is…" format is exactly what Google extracts for position-zero answers.
100% of Technology sites pass this check. This site is pass; 100% of the benchmark has the same status.
Evaluates FAQ or expandable Q&A section on page against its documented passing condition. The exact target appears under Expected behavior.
No FAQ section: consider adding one for common questions about your offering
Common questions are paired with direct answers, with matching FAQPage schema when the visible content qualifies.
FAQ-style content provides a library of ready-to-use question–answer pairs that AI systems can directly surface when answering user queries, making the page a high-yield citation candidate.
FAQ content expands keyword surface area, targets long-tail question queries, and can earn PAA (People Also Ask) inclusions, all of which broaden organic visibility without additional page creation.
16.9% of Technology sites pass this check. This site is pass; 16.9% of the benchmark has the same status.
Evaluates content includes structured elements (lists, tables) against its documented passing condition. The exact target appears under Expected behavior.
5 list/table element(s) (7.7 per 1k words): excellent structured content
Long-form content uses lists or tables where structure makes facts easier to extract and compare.
Structured content (lists, tables, step-by-step instructions) is significantly easier for AI systems to parse and summarise than dense prose; high-density structured content is more frequently cited in AI responses.
Lists and tables improve content scannability, dwell time, and engagement metrics; they are also more likely to be extracted as featured snippets, earning prominent above-the-fold SERP placement.
70.5% of Technology sites pass this check. This site is pass; 70.5% of the benchmark has the same status.
Checks whether the page has sufficient content depth for AI systems to extract meaningful information.
Median section: ~651 words: thorough coverage
Content sections provide enough substance to answer their topic, with a median depth of at least 40 words.
Deep, comprehensive content gives AI systems more raw material to form accurate, nuanced responses; thin content is systematically down-ranked or excluded from AI answer pools.
Content depth correlates strongly with topical authority, Google's primary long-term ranking mechanism; comprehensive pages earn more backlinks and rank for more keyword variants.
87.6% of Technology sites pass this check. This site is pass; 87.6% of the benchmark has the same status.
Evaluates content includes unique data points (numbers, percentages, prices) against its documented passing condition. The exact target appears under Expected behavior.
44 data points found: LLMs prefer content with specific figures
The content supports claims with specific, attributable numbers, percentages, prices, or original data.
Original data, statistics, and research findings are among the most valuable signals for AI systems seeking authoritative sources; unique data dramatically increases citation likelihood and reduces the chance of being displaced by duplicate content.
Proprietary data and original research are top-tier link magnets; pages that cite unique numbers or findings earn disproportionate backlink profiles and high-authority placements.
48.6% of Technology sites pass this check. This site is pass; 48.6% of the benchmark has the same status.
Evaluates external mentions found against its documented passing condition. The exact target appears under Expected behavior.
17 brand-relevant result(s)
Independent sources identify the entity accurately with sufficient relevance, diversity, recency, and authority.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates unique source diversity against its documented passing condition. The exact target appears under Expected behavior.
16 source(s)
Independent sources identify the entity accurately with sufficient relevance, diversity, recency, and authority.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates high-authority source mentions against its documented passing condition. The exact target appears under Expected behavior.
Tier 1: 2, Tier 2: 0
Independent sources identify the entity accurately with sufficient relevance, diversity, recency, and authority.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates brand name accuracy in results against its documented passing condition. The exact target appears under Expected behavior.
85% brand-relevant
Independent sources identify the entity accurately with sufficient relevance, diversity, recency, and authority.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates recent mentions (last ~6 months) against its documented passing condition. The exact target appears under Expected behavior.
2 recent
Independent sources identify the entity accurately with sufficient relevance, diversity, recency, and authority.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
Evaluates no negative/controversy signals against its documented passing condition. The exact target appears under Expected behavior.
Clean
Independent sources identify the entity accurately with sufficient relevance, diversity, recency, and authority.
This check has no published direct effect on AI discovery. Any effect depends on whether the issue also changes crawler access, extractable content, or entity clarity.
This check has no published direct search impact. Any effect depends on whether the issue also changes crawlability, page understanding, or user access to the content.
One completed run · oldest to newest
This is the first scored run for this domain. Re-run the audit after making changes to start a comparison.
Run a fresh auditCompared with the latest scored run from 141 other Technology sites, the median score is 67.
crpt.ru scores above 27% of this same-version comparison set.
We auto-verify ownership from your email domain. If they match, your first year of Premium is 20% off. No extra step at checkout.
Run the same deterministic checks again to refresh this report and see a valid before-and-after comparison.
Link to the full results or add a verified score card to your site.
Link directly to these audit results.
https://app.nyman.media/site/crpt.ruShows the latest score, audit date, and Nyman Media verification.
<a href="https://app.nyman.media/site/crpt.ru"><img src="https://app.nyman.media/api/badge/site/crpt.ru.svg" alt="Website audit score for crpt.ru" width="420" height="112" /></a>An always-current card with score, audit date, and link to the findings.
<iframe src="https://app.nyman.media/embed/site/crpt.ru" width="460" height="210" frameborder="0" loading="lazy" title="Website audit results for crpt.ru"></iframe>The branded score summary shown when this page is shared.
<meta property="og:image" content="https://app.nyman.media/site/crpt.ru/opengraph-image" />