Public example · AI Web Check
AI Web Check example report
This is a permanent example of AI Web Check checking itself. It shows the real report structure and does not run a new scan when the page is opened.
- Snapshot
- Data
- Fixed AI Web Check example; opening this page does not run a new scan
- Privacy
- No user reports or raw HTML
This demonstrates a result, not a prediction. Scores do not guarantee ranking, citation or selection by an AI system. View the example with problems · How the methodology works.
Example result
Checked address: https://ai.novikey.com
The evaluated primary signals are ready
All evaluated stable criteria are available in the expected form.
AI Readiness
100of 100
High AI Readiness
Assessment of technical accessibility, discoverability and machine readability for AI systems; Delivery Reliability is shown as a separate index and does not change AI Readiness. The score does not guarantee ranking, citation or selection by any AI system.
Website technical profile
The first four axes form AI Readiness. Delivery Reliability is the fifth axis and does not affect the primary score.
- Machine-readable semantics100 / 100
- Discovery and crawler rules100 / 100
- Metadata and indexing controls100 / 100
- Technical accessibility100 / 100
- Delivery ReliabilitySeparate index; it is not part of AI Readiness.100 / 100
- 33Pass
- 0Warning
- 0Fix
- 0Not evaluated
- 2Optional
Priorities
Recommendations
Confirmed errors and material improvements only, sorted by priority.
No confirmed problems were found in the primary assessment.
Details
All checks
Choose an area and open a check to see the conclusion, what was found, why it matters and what to do next.
PassStructured dataDetails
Summary
Structured data was observed in the expected form.
What was found
JSON-LD: 1 valid out of 1; Microdata: none; RDFa: none.
Why it matters
Structured data exposes entity types, properties and relationships explicitly instead of leaving them to inference from prose.
Recommendation
Keep structured data aligned with the visible page and avoid contradictory representations of the same entity.
Signal type
Machine-readable semantics
PassSchema.org JSON-LDDetails
Summary
Schema.org JSON-LD was observed in the expected form.
What was found
Blocks: 1; valid: 1; types: Organization, WebApplication.
Why it matters
JSON-LD is a common way to publish structured entities separately from the surrounding HTML markup.
Recommendation
Revalidate JSON-LD types and properties whenever templates or content models change.
Signal type
Machine-readable semantics
OptionalSchema.org MicrodataDetails
Summary
Schema.org Microdata is optional and does not reduce AI Readiness when absent.
What was found
itemscope: 0; types: not detected.
Why it matters
Microdata is a valid structured-data format, but it does not need to duplicate an already correct JSON-LD or RDFa representation.
Recommendation
Do not add Microdata solely for duplication; keep it accurate if the site already uses it.
Signal type
Machine-readable semantics
OptionalSchema.org RDFaDetails
Summary
Schema.org RDFa is optional and does not reduce AI Readiness when absent.
What was found
Types: not detected.
Why it matters
RDFa is another valid structured-data format and should be evaluated as an alternative, not as a mandatory companion to JSON-LD.
Recommendation
Do not add RDFa solely for duplication; keep it accurate if the site already uses it.
Signal type
Machine-readable semantics
PassSearch/discovery crawler accessDetails
Summary
Search/discovery crawler access was observed in the expected form.
What was found
Search / discovery — OAI-SearchBot: root: not explicitly disallowed; Claude-SearchBot: root: not disallowed via *; Googlebot: root: not disallowed via *; YandexBot: root: not disallowed via *; PerplexityBot: root: not disallowed via * | AI answer use / grounding — YandexAdditional: root: not disallowed via *; YandexAdditionalBot: root: not disallowed via * | User-requested retrieval — Claude-User: root: not disallowed via *; Perplexity-User: user-requested fetch; robots.txt is generally not applied | Training / model-use — GPTBot: root: not disallowed via *; ClaudeBot: root: not explicitly disallowed; Google-Extended: root: not explicitly disallowed | Scoring contract Methodology 4.2 — OAI-SearchBot: root not explicitly disallowed; Claude-SearchBot: корень не запрещён через *; Googlebot: корень не запрещён через *; YandexBot: корень не запрещён через *; PerplexityBot: корень не запрещён через *. Registry updated: 2026-08-11.
Why it matters
Search/discovery controls affect whether automated search systems can crawl public content, while training or model-use policy is a separate publisher choice and should not reduce this score.
Recommendation
Review search/discovery access independently from AI-answer-use, user-retrieval and training/model-use controls, and keep each policy aligned with its vendor documentation.
Signal type
Discovery and crawler rules
PassSitemap discovery in robots.txtDetails
Summary
Sitemap discovery in robots.txt was observed in the expected form.
What was found
Sitemap directives: 2; https://ai.novikey.com/sitemap.xml, https://ai.novikey.com/sitemap-en-foundational.xml.
Why it matters
A Sitemap directive gives automated systems a standard discovery path to the site’s published URL inventory.
Recommendation
Keep Sitemap directives current and point them to the canonical sitemap or sitemap index.
Signal type
Discovery and crawler rules
PassHomepage responseDetails
Summary
Homepage response was observed in the expected form.
What was found
HTTP 200; redirects: 0; HTML: yes.
Why it matters
A failed or non-HTML homepage does not provide a defensible base document for the rest of the technical assessment.
Recommendation
Keep the public homepage on a stable 2xx HTML response and avoid maintenance or error templates on the canonical URL.
Signal type
Technical foundation
Passrobots.txtDetails
Summary
robots.txt was observed in the expected form.
What was found
HTTP 200; expected format: yes.
Why it matters
robots.txt is the standard publication point for crawl rules and Sitemap discovery.
Recommendation
Keep robots.txt readable, publicly accessible and aligned with the intended crawler policy.
Signal type
Technical foundation
Passsitemap.xmlDetails
Summary
sitemap.xml was observed in the expected form.
What was found
HTTP 200; expected format: yes.
Why it matters
A sitemap helps automated systems discover public URLs without implying that those URLs will be indexed or ranked.
Recommendation
Publish a valid sitemap.xml or sitemap index and keep its URLs current.
Signal type
Technical foundation
PassDocument HTTP headersDetails
Summary
Document HTTP headers was observed in the expected form.
What was found
Content-Type: text/html; charset=utf-8; Content-Language: not specified.
Why it matters
Incorrect response metadata can prevent reliable automated interpretation even when HTML is present.
Recommendation
Return a correct HTML Content-Type, charset and language metadata where known.
Signal type
Technical foundation
PassContent without mandatory JavaScriptDetails
Summary
Content without mandatory JavaScript was observed in the expected form.
What was found
Text after removing code: about 3360 bytes; external scripts: 1.
Why it matters
Not every automated consumer executes client-side JavaScript before reading a page.
Recommendation
Keep essential content and page meaning available in the initial HTML response.
Signal type
Technical foundation
PassRedirect chainDetails
Summary
Redirect chain was observed in the expected form.
What was found
Requested origin: https://ai.novikey.com; hops: 0; final URL: https://ai.novikey.com/.
Why it matters
Redirects determine the actual document URL and can cross trust or transport boundaries before content is reached.
Recommendation
Keep redirect chains short, deterministic and HTTPS-only.
Signal type
Delivery security
PassHTTPS on the final URLDetails
Summary
HTTPS on the final URL was observed in the expected form.
What was found
Final URL: https://ai.novikey.com/.
Why it matters
HTTPS protects response integrity and confidentiality between the site and the client.
Recommendation
Keep all canonical public URLs and redirects on HTTPS.
Signal type
Delivery security
PassHSTSDetails
Summary
HSTS was observed in the expected form.
What was found
HSTS: max-age=31536000; includeSubDomains.
Why it matters
HSTS tells supporting browsers to use HTTPS for subsequent requests and reduces downgrade exposure.
Recommendation
Maintain an HSTS policy appropriate for the site and its subdomains.
Signal type
Delivery security
PassContent-Security-PolicyDetails
Summary
Content-Security-Policy was observed in the expected form.
What was found
Content-Security-Policy: default-src 'self'; frame-ancestors 'none'; object-src 'none'; base-uri 'none'; form-action 'self'.
Why it matters
CSP constrains allowed resource and execution sources and can reduce the impact of content-injection attacks.
Recommendation
Maintain a restrictive CSP that matches the resources the site actually needs.
Signal type
Delivery security
PassFraming protectionDetails
Summary
Framing protection was observed in the expected form.
What was found
Framing protection: default-src 'self'; frame-ancestors 'none'; object-src 'none'; base-uri 'none'; form-action 'self'.
Why it matters
frame-ancestors or X-Frame-Options can reduce clickjacking and unwanted framing of the interface.
Recommendation
Keep framing restrictions explicit unless third-party embedding is intentionally required.
Signal type
Delivery security
PassX-Content-Type-OptionsDetails
Summary
X-Content-Type-Options was observed in the expected form.
What was found
X-Content-Type-Options: nosniff.
Why it matters
nosniff tells browsers not to reinterpret resources as a different content type from the declared Content-Type.
Recommendation
Keep X-Content-Type-Options: nosniff on public responses where appropriate.
Signal type
Delivery security
PassReferrer-PolicyDetails
Summary
Referrer-Policy was observed in the expected form.
What was found
Referrer-Policy: no-referrer.
Why it matters
Referrer-Policy limits unintended disclosure of source URLs and their parameters to external recipients.
Recommendation
Choose and maintain a Referrer-Policy that matches the site’s privacy and integration requirements.
Signal type
Delivery security
PassPermissions-PolicyDetails
Summary
Permissions-Policy was observed in the expected form.
What was found
Permissions-Policy: camera=(), microphone=(), geolocation=().
Why it matters
Permissions-Policy can reduce unnecessary access to browser features, although it is diagnostic and does not affect AI Readiness.
Recommendation
Disable browser capabilities the site does not need and keep the policy synchronized with application behavior.
Signal type
Delivery security
PassMixed content in HTMLDetails
Summary
Mixed content in HTML was observed in the expected form.
What was found
Static HTML: no explicit mixed content.
Why it matters
Insecure subresources can be blocked by browsers and weaken the integrity of an otherwise HTTPS page.
Recommendation
Serve embedded resources over HTTPS and remove explicit HTTP resource URLs.
Signal type
Delivery security
PassForm action safetyDetails
Summary
Form action safety was observed in the expected form.
What was found
Static HTML: no insecure action detected.
Why it matters
Submitting form data over HTTP can expose or alter user input in transit.
Recommendation
Submit forms only to HTTPS endpoints and avoid protocol downgrades.
Signal type
Delivery security
PassWebMCP readinessDetails
Summary
WebMCP readiness was observed in the expected form.
What was found
Declarative forms: 1; tools: prepare_website_check — Подготавливает проверку публичного сайта: заполняет URL или домен в форме. Пользователь проверяет значение и запускает сканирование обычной кнопкой «Check a website».; parameters with toolparamdescription: 1; toolautosubmit: none.
Why it matters
WebMCP can expose structured page-level tools to browser agents, but it remains an emerging capability and is not required for AI Readiness.
Recommendation
Use WebMCP only for well-bounded agent actions with explicit schemas and separate security review.
Signal type
Experimental
Passllms.txtDetails
Summary
llms.txt was observed in the expected form.
What was found
HTTP 200; expected format: yes.
Why it matters
llms.txt can provide additional machine-readable navigation context, but its presence does not guarantee discovery, indexing or citation.
Recommendation
If used, keep llms.txt concise, public, current and consistent with the canonical site content.
Signal type
Experimental
Passllms-full.txtDetails
Summary
llms-full.txt was observed in the expected form.
What was found
HTTP 200; expected format: yes.
Why it matters
llms-full.txt can expose more machine-readable context, but it remains optional and does not guarantee use by an AI system.
Recommendation
If used, keep llms-full.txt current, non-sensitive and consistent with public documentation.
Signal type
Experimental
PassAgent interaction semanticsDetails
Summary
Agent interaction semantics was observed in the expected form.
What was found
Interactive controls: 9; with confirmed name: 9; coverage: 100%; native: 9; custom role: 0; ARIA state/control attributes: 0.
Why it matters
Browser agents can use accessible names, roles and states to interpret actions, but this diagnostic is not a ranking factor and does not replace a browser accessibility audit.
Recommendation
Prefer native HTML controls and keep labels, accessible names and ARIA states accurate where they are needed.
Signal type
Technical foundation
PassInternal pages: accessibilityDetails
Summary
Internal pages: accessibility was observed in the expected form.
What was found
Pages checked: 2; unavailable/non-HTML: 0; static-content concerns: 0.
Why it matters
A successful homepage does not prove that internal site pages are equally reachable to automated systems.
Recommendation
Keep important internal pages on stable HTML responses and expose their primary meaning in the initial document.
Signal type
Technical foundation
There are no checks in the selected category.
Diagnostics
Technical data
Details about the checked address, scan time, redirects and methodology version.
- Checked address
- https://ai.novikey.com
- Final URL
- https://ai.novikey.com/
- Redirects
- 0
- Methodology
- Version 4.2
- Check time
- 2026-08-14T00:00:00Z
- Result source
- New check
- Page used for assessment
- Homepage is suitable for the check
- AI-commerce
- Commerce context was not confirmed or is technically unavailable.
Redirect chain
No redirect chain was observed.