Уровень 2

Сайту нужны исправления

Сайт находится в поиске, но не пройдено проверок: 9. Это мешает AI-агентам понять и использовать сайт. Ниже — что сделать в первую очередь.

Перейти к плану исправлений

https://aitextwatermarkremover.com/

92
Видимость для AI
4/5 проверок
43
Доступность контента
1/4 проверок
57
Правила для AI-ботов
1/3 проверок
0
Технические протоколы
0/6 проверок
0
Электронная коммерция
0/3 проверок

Сообщить о неверном результате

Укажите проверку, которую стоит пересмотреть. Это не изменит отчёт или его оценку.

Результат проверкиЧто неверно?

Комментарий (необязательно)0/500

Не указывайте пароли, токены доступа, персональные данные или другие секреты.

Видимость для AI

4 пройдено · 1 частично · 0 ошибок

СреднеЧастично

Discovery Link headers

Add `Link` headers at the web server or application response layer; use absolute URLs and correct `rel`/`type` parameters.

Детали аудита

Discovery Link headers

Метаданные

Категория: Обнаруживаемость
Remediation key: link_headers_incomplete
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

The main response includes machine-readable `Link` headers with rel values for canonical, sitemap, `api-catalog`, `linkset`, `service-desc`, or other registered discovery resources.

Как исправить

Add `Link` headers at the web server or application response layer; use absolute URLs and correct `rel`/`type` parameters.

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for Discovery Link headers (link_headers).
Current check result:

{"evidence":{"discovered_links":[],"discovery_counts":{"machine_readable":0,"navigational":0},"final_url":"https://aitextwatermarkremover.com/","headers":{"content-type":"text/html; charset=utf-8","link":"</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"malformed_entries":[],"redirects":[],"rel_missing_entries":[],"requested_url":"https://aitextwatermarkremover.com/","status_code":200,"well_known_api_catalog":{"content_type":"text/html; charset=utf-8","final_url":"https://aitextwatermarkremover.com/.well-known/api-catalog","found":false,"requested_url":"https://aitextwatermarkremover.com/.well-known/api-catalog","status":"fetched","status_code":404}},"outputs":{"discovery_link_count":0,"link_count":2,"machine_readable_link_count":0},"remediation_key":"link_headers_incomplete","scanner_message":"Link headers exist but do not expose recognized machine-readable discovery links.","status"...

Expected result: The main response includes machine-readable `Link` headers with rel values for canonical, sitemap, `api-catalog`, `linkset`, `service-desc`, or other registered discovery resources.
Fix guidance: Add `Link` headers at the web server or application response layer; use absolute URLs and correct `rel`/`type` parameters.
Stack templates:
- Generic web server: serve HTTP `Link` headers from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for HTTP `Link` headers; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for HTTP `Link` headers; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for HTTP `Link` headers; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for HTTP `Link` headers; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for HTTP `Link` headers; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for HTTP `Link` headers; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement HTTP `Link` headers via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add HTTP `Link` headers via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add HTTP `Link` headers as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate HTTP `Link` headers in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "headers": {
    "link": "</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"",
    "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
    "content-type": "text/html; charset=utf-8"
  },
  "final_url": "https://aitextwatermarkremover.com/",
  "redirects": [],
  "status_code": 200,
  "requested_url": "https://aitextwatermarkremover.com/",
  "discovered_links": [],
  "discovery_counts": {
    "navigational": 0,
    "machine_readable": 0
  },
  "malformed_entries": [],
  "rel_missing_entries": [],
  "well_known_api_catalog": {
    "found": false,
    "status": "fetched",
    "final_url": "https://aitextwatermarkremover.com/.well-known/api-catalog",
    "status_code": 404,
    "content_type": "text/html; charset=utf-8",
    "requested_url": "https://aitextwatermarkremover.com/.well-known/api-catalog"
  }
}

{
  "link_count": 2,
  "discovery_link_count": 0,
  "machine_readable_link_count": 0
}

```
"link_headers_incomplete"
```
```
"Link headers exist but do not expose recognized machine-readable discovery links."
```
```
"partial"
```

Доступность контента

1 пройдено · 1 частично · 2 ошибок

СреднеОшибка

llms-full.txt

Publish the full public content as one Markdown file: an H1 title, a blockquote summary right after it, then `##`/`###` sections of complete text (overview, important pages, usage limits) and no private data. Serve it with an explicit `Content-Type: text/markdown` (or `text/plain`) and `Vary: Accept`, and keep a companion `/llms.txt` index next to it. Do not trim the file just for size — a large valid document passes the check.

Детали аудита

llms-full.txt

Метаданные

Категория: Доступность контента
Remediation key: llms_full_txt_missing
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

`/llms-full.txt` returns HTTP 200 as an explicit `text/markdown` (or `text/plain`) document: it starts with an H1 title and a short blockquote summary, then groups the full content under `##`/`###` sections (not just links). This is a de-facto convention, not part of the official llms.txt spec; a large file is normal, so size is not penalized as long as the body stays within the scanner's fetch limit.

Как исправить

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for llms-full.txt (llms_full_txt).
Current check result:

{"evidence":{"body_size_bytes":86050,"final_url":"https://aitextwatermarkremover.com/llms-full.txt","has_explicit_markdown_or_plain_text":false,"headers":{"content-type":"text/html; charset=utf-8","link":"</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/chunks/007gw7jkz3mh2.css>; rel=preload; as=\"style\"","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"is_markdown_or_plain_text":false,"redirects":[],"requested_url":"https://aitextwatermarkremover.com/llms-full.txt","status_code":404},"outputs":{"http_status":404},"remediation_key":"llms_full_txt_missing","scanner_message":"llms-full.txt is not available with HTTP 200.","status":"fail"}

Expected result: `/llms-full.txt` returns HTTP 200 as an explicit `text/markdown` (or `text/plain`) document: it starts with an H1 title and a short blockquote summary, then groups the full content under `##`/`###` sections (not just links). This is a de-facto convention, not part of the official llms.txt spec; a large file is normal, so size is not penalized as long as the body stays within the scanner's fetch limit.
Fix guidance: Publish the full public content as one Markdown file: an H1 title, a blockquote summary right after it, then `##`/`###` sections of complete text (overview, important pages, usage limits) and no private data. Serve it with an explicit `Content-Type: text/markdown` (or `text/plain`) and `Vary: Accept`, and keep a companion `/llms.txt` index next to it. Do not trim the file just for size — a large valid document passes the check.
Stack templates:
- Generic web server: serve `/llms-full.txt` from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for `/llms-full.txt`; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for `/llms-full.txt`; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for `/llms-full.txt`; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for `/llms-full.txt`; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for `/llms-full.txt`; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for `/llms-full.txt`; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement `/llms-full.txt` via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add `/llms-full.txt` via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add `/llms-full.txt` as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate `/llms-full.txt` in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "headers": {
    "link": "</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/chunks/007gw7jkz3mh2.css>; rel=preload; as=\"style\"",
    "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
    "content-type": "text/html; charset=utf-8"
  },
  "final_url": "https://aitextwatermarkremover.com/llms-full.txt",
  "redirects": [],
  "status_code": 404,
  "requested_url": "https://aitextwatermarkremover.com/llms-full.txt",
  "body_size_bytes": 86050,
  "is_markdown_or_plain_text": false,
  "has_explicit_markdown_or_plain_text": false
}

```
{
  "http_status": 404
}
```
```
"llms_full_txt_missing"
```
```
"llms-full.txt is not available with HTTP 200."
```
```
"fail"
```

ВажноЧастично

llms.txt

Create a short agent-facing index: a single H1 title, a one-line blockquote summary right after it, `##` sections that list key URLs as `[name](url): note`, prefer Markdown (`.md`) link targets, and serve the file with an explicit `Content-Type: text/markdown` or `text/plain`.

Детали аудита

llms.txt

Метаданные

Категория: Доступность контента
Remediation key: llms_txt_incomplete
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

`/llms.txt` returns HTTP 200 with an explicit `Content-Type: text/markdown` (or `text/plain`), starts with one H1 followed by a short blockquote summary, and groups links with per-link descriptions (`[name](url): note`) under `##` sections; language hints for `uk`, `ru`, or `en` are a bonus.

Как исправить

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for llms.txt (llms_txt).
Current check result:

{"evidence":{"body_size_bytes":4499,"discovered_links":[{"notes":"Detect, clean, and Pro-rewrite AI text watermarks","target_is_markdown":false,"title":"Home","url":"https://aitextwatermarkremover.com/"},{"notes":"Free local tools plus Pro credit packs and subscriptions","target_is_markdown":false,"title":"Pricing","url":"https://aitextwatermarkremover.com/pricing"},{"notes":"Directory of free local cleaners and Pro rewrite landings","target_is_markdown":false,"title":"Tools","url":"https://aitextwatermarkremover.com/tools"},{"notes":"Free in-browser cleaner for hidden Unicode and paste artifacts","target_is_markdown":false,"title":"Invisible Character Remover","url":"https://aitextwatermarkremover.com/invisible-character-remover"},{"notes":"Inspect hidden Unicode and formatting residue; not an AI-probability detector","target_is_markdown":false,"title":"AI Text Watermark Detector","url":"https://aitextwatermarkremover.com/ai-text-watermark-detector"},{"notes":"Pro rewrite that changes tone and rhythm; not a detector-bypass tool","target_is_markdown":false,"title":"AI Humanizer","url":"https://aitextwatermarkremover.com/ai-humanizer"},{"notes":"Pro AI Humanizer for scholarly dra...

Expected result: `/llms.txt` returns HTTP 200 with an explicit `Content-Type: text/markdown` (or `text/plain`), starts with one H1 followed by a short blockquote summary, and groups links with per-link descriptions (`[name](url): note`) under `##` sections; language hints for `uk`, `ru`, or `en` are a bonus.
Fix guidance: Create a short agent-facing index: a single H1 title, a one-line blockquote summary right after it, `##` sections that list key URLs as `[name](url): note`, prefer Markdown (`.md`) link targets, and serve the file with an explicit `Content-Type: text/markdown` or `text/plain`.
Stack templates:
- Generic web server: serve `/llms.txt` from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for `/llms.txt`; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for `/llms.txt`; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for `/llms.txt`; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for `/llms.txt`; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for `/llms.txt`; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for `/llms.txt`; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement `/llms.txt` via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add `/llms.txt` via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add `/llms.txt` as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate `/llms.txt` in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "headers": {
    "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
    "content-type": "text/markdown; charset=utf-8"
  },
  "snippet": "# AI Text Watermark Remover > Detect and clean hidden characters and Markdown formatting, or remove embedded AI text watermarks by regenerating wording. Works with Claude, ChatGPT, Gemini and more. AI Text Watermark Remover is a web app for detecting and cleaning AI-generated text watermarks. Free t",
  "final_url": "https://aitextwatermarkremover.com/llms.txt",
  "redirects": [],
  "structure": {
    "h1_count": 1,
    "h2_count": 2,
    "link_count": 25,
    "has_summary": true,
    "starts_with_h1": true,
    "blockquote_count": 1,
    "has_useful_links": true,
    "links_with_notes": 25,
    "optional_section": true,
    "has_described_links": true,
    "has_required_structure": true,
    "markdown_link_target_count": 0,
    "markdown_link_target_share": 0
  },
  "status_code": 200,
  "requested_url": "https://aitextwatermarkremover.com/llms.txt",
  "language_hints": [
    "en"
  ],
  "body_size_bytes": 4499,
  "discovered_links": [
    {
      "url": "https://aitextwatermarkremover.com/",
      "notes": "Detect, clean, and Pro-rewrite AI text watermarks",
      "title": "Home",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/pricing",
      "notes": "Free local tools plus Pro credit packs and subscriptions",
      "title": "Pricing",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/tools",
      "notes": "Directory of free local cleaners and Pro rewrite landings",
      "title": "Tools",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/invisible-character-remover",
      "notes": "Free in-browser cleaner for hidden Unicode and paste artifacts",
      "title": "Invisible Character Remover",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/ai-text-watermark-detector",
      "notes": "Inspect hidden Unicode and formatting residue; not an AI-probability detector",
      "title": "AI Text Watermark Detector",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/ai-humanizer",
      "notes": "Pro rewrite that changes tone and rhythm; not a detector-bypass tool",
      "title": "AI Humanizer",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/academic-humanizer",
      "notes": "Pro AI Humanizer for scholarly drafts; does not guarantee detector or review pass",
      "title": "Academic Humanizer",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/markdown-cleaner",
      "notes": "Free in-browser strip of markdown markers from AI pastes",
      "title": "Markdown Cleaner",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/text-watermark-remover",
      "notes": "Pro meaning-preserving reconstruction for wording-level watermarks",
      "title": "Text Watermark Remover",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/remove-ai-watermark-from-text",
      "notes": "Two-layer cleanup: hidden Unicode residue vs statistical wording watermarks",
      "title": "Remove AI Watermark from Text",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/ai-text-cleaner",
      "notes": "Free paste hygiene for invisible Unicode and markdown in LLM output",
      "title": "AI Text Cleaner",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/chatgpt-cleaner",
      "notes": "Clean ChatGPT paste residue such as U+202F, markdown, and hidden characters",
      "title": "ChatGPT Cleaner",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/zero-width-space-remover",
      "notes": "Remove U+200B and related zero-width characters in the browser",
      "title": "Zero-Width Space Remover",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/claude-watermark-remover",
      "notes": "Guide and tool for Claude text watermarks",
      "title": "Claude Watermark Remover",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/chatgpt-watermark-remover",
      "notes": "Guide and tool for ChatGPT text watermarks",
      "title": "ChatGPT Watermark Remover",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/gemini-watermark-remover",
      "notes": "Guide and tool for Gemini text watermarks",
      "title": "Gemini Watermark Remover",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/about",
      "notes": "What AI Text Watermark Remover is",
      "title": "About",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/blog",
      "notes": "Guides on AI text watermarks and reconstruction",
      "title": "Blog",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/blog/claude-official-text-watermark",
      "notes": "How Claude’s statistical text watermark works and how reconstruction removes it",
      "title": "Claude official text watermark",
      "target_is_markdown": false
    },
    {
      "url": "https://aitextwatermarkremover.com/blog/chatgpt-paste-hidden-characters",
      "notes": "ChatGPT paste residue such as U+202F versus Claude’s official statistical watermark",
      "title": "ChatGPT paste hidden characters",
      "target_is_markdown": false
    }
  ],
  "malformed_link_lines": [
    36
  ],
  "is_markdown_content_type": true,
  "is_markdown_or_plain_text": true,
  "has_explicit_markdown_or_plain_text": true
}

{
  "has_links": true,
  "link_count": 25,
  "has_summary": true,
  "language_hints": [
    "en"
  ],
  "links_with_notes": 25,
  "has_language_hints": true,
  "has_described_links": true,
  "has_required_structure": true,
  "is_markdown_content_type": true,
  "is_markdown_or_plain_text": true,
  "markdown_link_target_share": 0,
  "has_explicit_markdown_or_plain_text": true
}

```
"llms_txt_incomplete"
```
```
"llms.txt is present but its structure, links, or media type are incomplete."
```
```
"partial"
```

ВажноОшибка

Markdown content negotiation

The simplest path is publishing a Markdown twin of every page at the same URL with `.md` appended (`index.html.md` for directories), as llms.txt/Mintlify/ReadMe do, and announcing it with `Link: <…/page.md>; rel="alternate"; type="text/markdown"`. If you negotiate on a single URL in the route or middleware instead, render clean page text for Markdown requests, serve the canonical `Content-Type: text/markdown` (replace the deprecated `text/x-markdown`), and always add `Vary: Accept`.

Детали аудита

Markdown content negotiation

Метаданные

Категория: Доступность контента
Remediation key: markdown_negotiation_missing
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

The page serves Markdown one of two ways: negotiation on the same URL (a request with `Accept: text/markdown` returns the canonical `Content-Type: text/markdown` — not the deprecated `text/x-markdown` — together with `Vary: Accept` so caches never hand Markdown to browsers), or a Markdown twin at the same URL with `.md` appended (`index.html.md` for directory paths) — a dedicated `.md` URL does not need `Vary: Accept`. Announcing the alternate via `Link: rel="alternate"; type="text/markdown"` also counts as a signal.

Как исправить

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for Markdown content negotiation (markdown_negotiation).
Current check result:

{"evidence":{"body_size_bytes":175903,"final_url":"https://aitextwatermarkremover.com/","has_canonical_markdown_content_type":false,"has_legacy_markdown_content_type":false,"has_markdown_content_type":false,"has_vary_accept":false,"headers":{"content-type":"text/html; charset=utf-8","link":"</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"markdown":{"has_code_fence":true,"has_heading":false,"has_link":true,"has_list":true,"html_tag_count":1476,"looks_like_markdown":false,"non_empty_line_count":7,"signal_count":3,"variant":null},"md_fallback":{"body_size_bytes":86050,"final_url":"https://aitextwatermarkremover.com/index.html.md","headers":{"content-type":"text/html; charset=utf-8","link":"</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=pre...

Expected result: The page serves Markdown one of two ways: negotiation on the same URL (a request with `Accept: text/markdown` returns the canonical `Content-Type: text/markdown` — not the deprecated `text/x-markdown` — together with `Vary: Accept` so caches never hand Markdown to browsers), or a Markdown twin at the same URL with `.md` appended (`index.html.md` for directory paths) — a dedicated `.md` URL does not need `Vary: Accept`. Announcing the alternate via `Link: rel="alternate"; type="text/markdown"` also counts as a signal.
Fix guidance: The simplest path is publishing a Markdown twin of every page at the same URL with `.md` appended (`index.html.md` for directories), as llms.txt/Mintlify/ReadMe do, and announcing it with `Link: <…/page.md>; rel="alternate"; type="text/markdown"`. If you negotiate on a single URL in the route or middleware instead, render clean page text for Markdown requests, serve the canonical `Content-Type: text/markdown` (replace the deprecated `text/x-markdown`), and always add `Vary: Accept`.
Stack templates:
- Generic web server: serve `Accept: text/markdown` negotiation from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for `Accept: text/markdown` negotiation; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for `Accept: text/markdown` negotiation; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for `Accept: text/markdown` negotiation; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for `Accept: text/markdown` negotiation; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for `Accept: text/markdown` negotiation; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for `Accept: text/markdown` negotiation; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement `Accept: text/markdown` negotiation via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add `Accept: text/markdown` negotiation via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add `Accept: text/markdown` negotiation as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate `Accept: text/markdown` negotiation in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "headers": {
    "link": "</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"",
    "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
    "content-type": "text/html; charset=utf-8"
  },
  "snippet": "<!DOCTYPE html><html lang=\"en\" class=\"inter_c6e48ee1-module__JRO3KW__variable plus_jakarta_sans_73e8db66-module__y9VS4a__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/007gw7jkz3mh2.css\" da",
  "markdown": {
    "variant": null,
    "has_link": true,
    "has_list": true,
    "has_heading": false,
    "signal_count": 3,
    "has_code_fence": true,
    "html_tag_count": 1476,
    "looks_like_markdown": false,
    "non_empty_line_count": 7
  },
  "final_url": "https://aitextwatermarkremover.com/",
  "redirects": [],
  "md_fallback": {
    "headers": {
      "link": "</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/chunks/007gw7jkz3mh2.css>; rel=preload; as=\"style\"",
      "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
      "content-type": "text/html; charset=utf-8"
    },
    "final_url": "https://aitextwatermarkremover.com/index.html.md",
    "redirects": [],
    "status_code": 404,
    "requested_url": "https://aitextwatermarkremover.com/index.html.md",
    "body_size_bytes": 86050
  },
  "status_code": 200,
  "requested_url": "https://aitextwatermarkremover.com/",
  "body_size_bytes": 175903,
  "has_vary_accept": false,
  "has_markdown_content_type": false,
  "has_legacy_markdown_content_type": false,
  "has_canonical_markdown_content_type": false
}

{
  "md_suffix_url": "https://aitextwatermarkremover.com/index.html.md",
  "body_size_bytes": 175903,
  "has_vary_accept": false,
  "markdown_signal_count": 3,
  "has_markdown_content_type": false,
  "has_markdown_via_md_suffix": false,
  "has_markdown_link_alternate": false,
  "has_legacy_markdown_content_type": false,
  "has_canonical_markdown_content_type": false
}

```
"markdown_negotiation_missing"
```
```
"Target page does not expose a Markdown representation."
```
```
"fail"
```

Правила для AI-ботов

1 пройдено · 0 частично · 2 ошибок

СреднеОшибка

Content usage policy signals

Publish at least one explicit machine-readable signal: serve `/.well-known/tdmrep.json` (a JSON array with `location`, `tdm-reservation: 1|0`, and an optional `tdm-policy` URL), add a robots.txt `Content-Signal` with explicit `yes`/`no` values for `search`/`ai-input`/`ai-train` or an RSL `License: <url>` directive, or send `noai`/`noimageai`/`tdm-reservation` headers or meta tags. Make the direction explicit — values without a recognized polarity stay weak; do not encode legal guarantees in code.

Детали аудита

Content usage policy signals

Метаданные

Категория: Правила для ботов
Remediation key: content_usage_policy_missing
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

The site publishes machine-readable AI/TDM content-usage signals through at least one canonical mechanism: `/.well-known/tdmrep.json` with `tdm-reservation` `1` (rights reserved) or `0` (not reserved), a `Content-Signal: search=yes, ai-train=no` or RSL `License:` directive in robots.txt, an RSL link (`rel="license" type="application/rsl+xml"`), or `noai`/`noimageai`/dedicated policy headers and meta tags. Signals with a recognized polarity are reported as `reserved`/`permitted`; a plain license link without the RSL type is only a weak signal.

Как исправить

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for Content usage policy signals (content_usage_policy).
Current check result:

{"evidence":{"final_url":"https://aitextwatermarkremover.com/","headers":{"content-type":"text/html; charset=utf-8","link":"</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"items":[],"malformed_fields":[],"redirects":[],"requested_url":"https://aitextwatermarkremover.com/","robots_txt":{"content_policy_directive_count":0,"fetched":true,"requested_url":"https://aitextwatermarkremover.com/robots.txt","status_code":200},"snippet":"<!DOCTYPE html><html lang=\"en\" class=\"inter_c6e48ee1-module__JRO3KW__variable plus_jakarta_sans_73e8db66-module__y9VS4a__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/007gw7jkz3mh2.css\" da","status_code":200,"tdmrep_well_known":{"fetched":true,"requested_url":"https://aitextwatermarkremover.com/.well-known/tdmrep.json","status_code":404}...

Expected result: The site publishes machine-readable AI/TDM content-usage signals through at least one canonical mechanism: `/.well-known/tdmrep.json` with `tdm-reservation` `1` (rights reserved) or `0` (not reserved), a `Content-Signal: search=yes, ai-train=no` or RSL `License:` directive in robots.txt, an RSL link (`rel="license" type="application/rsl+xml"`), or `noai`/`noimageai`/dedicated policy headers and meta tags. Signals with a recognized polarity are reported as `reserved`/`permitted`; a plain license link without the RSL type is only a weak signal.
Fix guidance: Publish at least one explicit machine-readable signal: serve `/.well-known/tdmrep.json` (a JSON array with `location`, `tdm-reservation: 1|0`, and an optional `tdm-policy` URL), add a robots.txt `Content-Signal` with explicit `yes`/`no` values for `search`/`ai-input`/`ai-train` or an RSL `License: <url>` directive, or send `noai`/`noimageai`/`tdm-reservation` headers or meta tags. Make the direction explicit — values without a recognized polarity stay weak; do not encode legal guarantees in code.
Stack templates:
- Generic web server: serve content usage policy signals from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for content usage policy signals; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for content usage policy signals; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for content usage policy signals; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for content usage policy signals; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for content usage policy signals; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for content usage policy signals; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement content usage policy signals via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add content usage policy signals via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add content usage policy signals as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate content usage policy signals in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "items": [],
  "headers": {
    "link": "</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"",
    "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
    "content-type": "text/html; charset=utf-8"
  },
  "snippet": "<!DOCTYPE html><html lang=\"en\" class=\"inter_c6e48ee1-module__JRO3KW__variable plus_jakarta_sans_73e8db66-module__y9VS4a__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/007gw7jkz3mh2.css\" da",
  "final_url": "https://aitextwatermarkremover.com/",
  "redirects": [],
  "robots_txt": {
    "fetched": true,
    "status_code": 200,
    "requested_url": "https://aitextwatermarkremover.com/robots.txt",
    "content_policy_directive_count": 0
  },
  "status_code": 200,
  "requested_url": "https://aitextwatermarkremover.com/",
  "malformed_fields": [],
  "tdmrep_well_known": {
    "fetched": true,
    "status_code": 404,
    "requested_url": "https://aitextwatermarkremover.com/.well-known/tdmrep.json"
  }
}

{
  "disposition": "unknown",
  "signal_count": 0,
  "header_signal_count": 0,
  "robots_signal_count": 0,
  "strong_signal_count": 0,
  "malformed_field_count": 0,
  "metadata_signal_count": 0,
  "reserved_signal_count": 0,
  "permitted_signal_count": 0,
  "wellknown_signal_count": 0
}

```
"content_usage_policy_missing"
```
```
"No supported content usage policy headers or metadata were found."
```
```
"fail"
```

Можно отложитьОшибка

Rate-limit hints

Serve standard `RateLimit` and `RateLimit-Policy` (RFC 9651 structured fields: a quoted policy name plus `r`/`t` and `q`/`w`) and a valid `Retry-After` on `429`/`503`. Upgrade legacy `X-RateLimit-*` to the modern format and make sure the values parse, not merely that the headers are present.

Детали аудита

Rate-limit hints

Метаданные

Категория: Правила для ботов
Remediation key: rate_limit_hints_missing
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

Responses include modern `RateLimit`/`RateLimit-Policy` structured-field headers (for example `RateLimit: "default";r=50;t=30`) or a valid `Retry-After` (a non-negative number of seconds or a valid HTTP-date). Legacy `X-RateLimit-*`, vendor bot-policy headers, or a `429` without a valid `Retry-After` are only a partial signal.

Как исправить

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for Rate-limit hints (rate_limit_hints).
Current check result:

{"evidence":{"final_url":"https://aitextwatermarkremover.com/","headers":{},"observed_from":"initial_fetch","parsed":{"ratelimit":[],"ratelimit_policy":[]},"requested_url":"https://aitextwatermarkremover.com/","safe_probe":{"request_count":0,"strategy":"passive_initial_fetch"},"status_code":200},"outputs":{"bot_policy_hint_count":0,"has_429":false,"has_retry_after":false,"hint_count":0,"legacy_rate_limit_header_count":0,"modern_standard_rate_limit_header_count":0,"ratelimit_field_parsed":false,"ratelimit_policy_count":0},"remediation_key":"rate_limit_hints_missing","scanner_message":"No valid Retry-After, RateLimit, 429, or bot-specific throttling hints were observed.","status":"fail"}

Expected result: Responses include modern `RateLimit`/`RateLimit-Policy` structured-field headers (for example `RateLimit: "default";r=50;t=30`) or a valid `Retry-After` (a non-negative number of seconds or a valid HTTP-date). Legacy `X-RateLimit-*`, vendor bot-policy headers, or a `429` without a valid `Retry-After` are only a partial signal.
Fix guidance: Serve standard `RateLimit` and `RateLimit-Policy` (RFC 9651 structured fields: a quoted policy name plus `r`/`t` and `q`/`w`) and a valid `Retry-After` on `429`/`503`. Upgrade legacy `X-RateLimit-*` to the modern format and make sure the values parse, not merely that the headers are present.
Stack templates:
- Generic web server: serve RateLimit/Retry-After hints from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for RateLimit/Retry-After hints; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for RateLimit/Retry-After hints; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for RateLimit/Retry-After hints; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for RateLimit/Retry-After hints; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for RateLimit/Retry-After hints; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for RateLimit/Retry-After hints; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement RateLimit/Retry-After hints via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add RateLimit/Retry-After hints via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add RateLimit/Retry-After hints as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate RateLimit/Retry-After hints in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "parsed": {
    "ratelimit": [],
    "ratelimit_policy": []
  },
  "headers": {},
  "final_url": "https://aitextwatermarkremover.com/",
  "safe_probe": {
    "strategy": "passive_initial_fetch",
    "request_count": 0
  },
  "status_code": 200,
  "observed_from": "initial_fetch",
  "requested_url": "https://aitextwatermarkremover.com/"
}

{
  "has_429": false,
  "hint_count": 0,
  "has_retry_after": false,
  "bot_policy_hint_count": 0,
  "ratelimit_field_parsed": false,
  "ratelimit_policy_count": 0,
  "legacy_rate_limit_header_count": 0,
  "modern_standard_rate_limit_header_count": 0
}

```
"rate_limit_hints_missing"
```
```
"No valid Retry-After, RateLimit, 429, or bot-specific throttling hints were observed."
```
```
"fail"
```

Технические протоколы

0 пройдено · 0 частично · 4 ошибок

СреднеОшибка

A2A Agent Card

Publish the Agent Card at the canonical `/.well-known/agent-card.json` (the legacy `/.well-known/agent.json` keeps working as a fallback) and fill in every required A2A field; restrict `preferredTransport` and `additionalInterfaces[].transport` to `JSONRPC`, `GRPC`, or `HTTP+JSON` and keep the primary `url` on https. Serve the card with `Content-Type: application/a2a+json` or `application/json`, and describe only skills and endpoints that truly exist. WebMCP has no static discovery file — do not publish a `webmcp.json`.

Детали аудита

A2A Agent Card

Метаданные

Категория: Protocol/API
Remediation key: a2a_webmcp_readiness_missing
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

`/.well-known/agent-card.json` returns an A2A Agent Card with every field the specification requires: `protocolVersion`, `name`, `description`, an https `url`, `preferredTransport`, `version`, `capabilities`, `defaultInputModes`/`defaultOutputModes`, and a non-empty `skills` list.

Как исправить

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for A2A Agent Card (a2a_webmcp_readiness).
Current check result:

{"evidence":{"candidates":[{"final_url":"https://aitextwatermarkremover.com/.well-known/agent-card.json","headers":{"cache-control":"private, no-cache, no-store, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"source":"well_known","status":"http_error","status_code":404,"url":"https://aitextwatermarkremover.com/.well-known/agent-card.json"},{"final_url":"https://aitextwatermarkremover.com/.well-known/agent.json","headers":{"cache-control":"private, no-cache, no-store, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"source":"well_known","status":"http_error","status_code":404,"url":"https://aitextwatermarkremover.com/.well-known/agent.json"}],"final_url":"https://aitextwatermarkremover.com/.well-known/agent-card.json","headers":{"cache-control":"private, no-cache, no-store, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"requested_url":"https://ai...

Expected result: `/.well-known/agent-card.json` returns an A2A Agent Card with every field the specification requires: `protocolVersion`, `name`, `description`, an https `url`, `preferredTransport`, `version`, `capabilities`, `defaultInputModes`/`defaultOutputModes`, and a non-empty `skills` list.
Fix guidance: Publish the Agent Card at the canonical `/.well-known/agent-card.json` (the legacy `/.well-known/agent.json` keeps working as a fallback) and fill in every required A2A field; restrict `preferredTransport` and `additionalInterfaces[].transport` to `JSONRPC`, `GRPC`, or `HTTP+JSON` and keep the primary `url` on https. Serve the card with `Content-Type: application/a2a+json` or `application/json`, and describe only skills and endpoints that truly exist. WebMCP has no static discovery file — do not publish a `webmcp.json`.
Stack templates:
- Generic web server: serve A2A Agent Card from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for A2A Agent Card; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for A2A Agent Card; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for A2A Agent Card; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for A2A Agent Card; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for A2A Agent Card; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for A2A Agent Card; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement A2A Agent Card via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add A2A Agent Card via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add A2A Agent Card as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate A2A Agent Card in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "root": {
    "status": "fetched",
    "headers": {
      "link": "</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"",
      "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
      "content-type": "text/html; charset=utf-8",
      "cache-control": "public, max-age=0, must-revalidate"
    },
    "final_url": "https://aitextwatermarkremover.com/",
    "redirects": [],
    "status_code": 200,
    "requested_url": "https://aitextwatermarkremover.com/",
    "discovered_links": [],
    "malformed_entries": []
  },
  "headers": {
    "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
    "content-type": "text/html; charset=utf-8",
    "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
  },
  "final_url": "https://aitextwatermarkremover.com/.well-known/agent-card.json",
  "candidates": [
    {
      "url": "https://aitextwatermarkremover.com/.well-known/agent-card.json",
      "source": "well_known",
      "status": "http_error",
      "headers": {
        "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
        "content-type": "text/html; charset=utf-8",
        "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
      },
      "final_url": "https://aitextwatermarkremover.com/.well-known/agent-card.json",
      "status_code": 404
    },
    {
      "url": "https://aitextwatermarkremover.com/.well-known/agent.json",
      "source": "well_known",
      "status": "http_error",
      "headers": {
        "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
        "content-type": "text/html; charset=utf-8",
        "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
      },
      "final_url": "https://aitextwatermarkremover.com/.well-known/agent.json",
      "status_code": 404
    }
  ],
  "status_code": 404,
  "requested_url": "https://aitextwatermarkremover.com/.well-known/agent-card.json"
}

{
  "protocols": [],
  "transports": [],
  "completeness": null,
  "endpoint_count": 0,
  "metadata_found": false,
  "webmcp_statically_undetectable": true
}

```
"a2a_webmcp_readiness_missing"
```
```
"No A2A Agent Card was discovered at well-known locations."
```
```
"fail"
```

СреднеОшибка

Agent Skills index

Publish the index with `$schema` `https://schemas.agentskills.io/discovery/0.2.0/schema.json`. Give every skill a lowercase hyphenated `name` (1-64 chars, no `_`/uppercase), a `type` of `skill-md` or `archive`, a non-empty `description` (≤1024), a stable http(s) `url`, and a `digest` in `sha256:<64 hex>` form. Serve the index with `Content-Type: application/json`.

Детали аудита

Agent Skills index

Метаданные

Категория: Protocol/API
Remediation key: agent_skills_missing
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

`/.well-known/agent-skills/index.json` returns an Agent Skills Discovery 0.2.0 index: a top-level `$schema` plus `skills[]` entries with `name`, `type`, `description`, `url`, and `digest`.

Как исправить

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for Agent Skills index (agent_skills).
Current check result:

{"evidence":{"candidates":[{"final_url":"https://aitextwatermarkremover.com/.well-known/agent-skills/index.json","headers":{"cache-control":"private, no-cache, no-store, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"source":"well_known","status":"http_error","status_code":404,"url":"https://aitextwatermarkremover.com/.well-known/agent-skills/index.json"}],"final_url":"https://aitextwatermarkremover.com/.well-known/agent-skills/index.json","headers":{"cache-control":"private, no-cache, no-store, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"requested_url":"https://aitextwatermarkremover.com/.well-known/agent-skills/index.json","status_code":404},"outputs":{"skill_count":0,"skills_found":false,"valid_skill_count":0},"remediation_key":"agent_skills_missing","scanner_message":"No Agent Skills index was discovered.","status":"fail"}

Expected result: `/.well-known/agent-skills/index.json` returns an Agent Skills Discovery 0.2.0 index: a top-level `$schema` plus `skills[]` entries with `name`, `type`, `description`, `url`, and `digest`.
Fix guidance: Publish the index with `$schema` `https://schemas.agentskills.io/discovery/0.2.0/schema.json`. Give every skill a lowercase hyphenated `name` (1-64 chars, no `_`/uppercase), a `type` of `skill-md` or `archive`, a non-empty `description` (≤1024), a stable http(s) `url`, and a `digest` in `sha256:<64 hex>` form. Serve the index with `Content-Type: application/json`.
Stack templates:
- Generic web server: serve Agent Skills index from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for Agent Skills index; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for Agent Skills index; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for Agent Skills index; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for Agent Skills index; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for Agent Skills index; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for Agent Skills index; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement Agent Skills index via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add Agent Skills index via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add Agent Skills index as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate Agent Skills index in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "headers": {
    "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
    "content-type": "text/html; charset=utf-8",
    "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
  },
  "final_url": "https://aitextwatermarkremover.com/.well-known/agent-skills/index.json",
  "candidates": [
    {
      "url": "https://aitextwatermarkremover.com/.well-known/agent-skills/index.json",
      "source": "well_known",
      "status": "http_error",
      "headers": {
        "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
        "content-type": "text/html; charset=utf-8",
        "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
      },
      "final_url": "https://aitextwatermarkremover.com/.well-known/agent-skills/index.json",
      "status_code": 404
    }
  ],
  "status_code": 404,
  "requested_url": "https://aitextwatermarkremover.com/.well-known/agent-skills/index.json"
}

{
  "skill_count": 0,
  "skills_found": false,
  "valid_skill_count": 0
}

```
"agent_skills_missing"
```
```
"No Agent Skills index was discovered."
```
```
"fail"
```

СреднеОшибка

API Catalog discovery

Serve the catalog as `application/linkset+json` (RFC 9264) with a top-level `linkset` array: list member APIs under `item` and link the machine-readable description with `service-desc`; add the `profile="https://www.rfc-editor.org/info/rfc9727"` parameter, advertise it with a `Link` header, never return an HTML single-page-app shell at the catalog path, and do not include private or internal endpoints.

Детали аудита

API Catalog discovery

Метаданные

Категория: Protocol/API
Remediation key: api_catalog_missing
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

`/.well-known/api-catalog` (or `Link rel="api-catalog"`) returns an RFC 9727 `application/linkset+json` linkset whose `item` links point at API endpoints and whose `service-desc` link resolves to a valid OpenAPI or JSON Schema document.

Как исправить

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for API Catalog discovery (api_catalog).
Current check result:

{"evidence":{"candidates":[{"final_url":"https://aitextwatermarkremover.com/.well-known/api-catalog","headers":{"cache-control":"private, no-cache, no-store, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"source":"well_known","status":"http_error","status_code":404,"url":"https://aitextwatermarkremover.com/.well-known/api-catalog"}],"final_url":"https://aitextwatermarkremover.com/.well-known/api-catalog","headers":{"cache-control":"private, no-cache, no-store, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"requested_url":"https://aitextwatermarkremover.com/.well-known/api-catalog","root":{"discovered_links":[],"final_url":"https://aitextwatermarkremover.com/","headers":{"cache-control":"public, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","link":"</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.wo...

Expected result: `/.well-known/api-catalog` (or `Link rel="api-catalog"`) returns an RFC 9727 `application/linkset+json` linkset whose `item` links point at API endpoints and whose `service-desc` link resolves to a valid OpenAPI or JSON Schema document.
Fix guidance: Serve the catalog as `application/linkset+json` (RFC 9264) with a top-level `linkset` array: list member APIs under `item` and link the machine-readable description with `service-desc`; add the `profile="https://www.rfc-editor.org/info/rfc9727"` parameter, advertise it with a `Link` header, never return an HTML single-page-app shell at the catalog path, and do not include private or internal endpoints.
Stack templates:
- Generic web server: serve `/.well-known/api-catalog` from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for `/.well-known/api-catalog`; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for `/.well-known/api-catalog`; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for `/.well-known/api-catalog`; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for `/.well-known/api-catalog`; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for `/.well-known/api-catalog`; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for `/.well-known/api-catalog`; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement `/.well-known/api-catalog` via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add `/.well-known/api-catalog` via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add `/.well-known/api-catalog` as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate `/.well-known/api-catalog` in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "root": {
    "status": "fetched",
    "headers": {
      "link": "</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"",
      "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
      "content-type": "text/html; charset=utf-8",
      "cache-control": "public, max-age=0, must-revalidate"
    },
    "final_url": "https://aitextwatermarkremover.com/",
    "redirects": [],
    "status_code": 200,
    "requested_url": "https://aitextwatermarkremover.com/",
    "discovered_links": [],
    "malformed_entries": []
  },
  "headers": {
    "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
    "content-type": "text/html; charset=utf-8",
    "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
  },
  "final_url": "https://aitextwatermarkremover.com/.well-known/api-catalog",
  "candidates": [
    {
      "url": "https://aitextwatermarkremover.com/.well-known/api-catalog",
      "source": "well_known",
      "status": "http_error",
      "headers": {
        "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
        "content-type": "text/html; charset=utf-8",
        "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
      },
      "final_url": "https://aitextwatermarkremover.com/.well-known/api-catalog",
      "status_code": 404
    }
  ],
  "status_code": 404,
  "requested_url": "https://aitextwatermarkremover.com/.well-known/api-catalog"
}

{
  "catalog_found": false,
  "api_link_count": 0,
  "linkset_media_type": false,
  "rfc9727_conformant": false,
  "endpoint_link_count": 0,
  "link_relation_found": false,
  "description_link_count": 0,
  "api_description_document_count": 0,
  "api_description_document_types": [],
  "valid_api_description_document_count": 0,
  "api_description_document_fanout_limit": 5
}

```
"api_catalog_missing"
```
```
"No API catalog was found at /.well-known/api-catalog or through Link headers."
```
```
"fail"
```

СреднеОшибка

MCP Server Card

Publish MCP discovery JSON at `/.well-known/mcp` or an MCP Server Card path; when using another URL, add a root `Link` header with `rel="mcp-server-card"`. State the protocol version as a `YYYY-MM-DD` date (not `1.0`), serve `Content-Type: application/json`, and use the canonical `streamable-http`/`sse` transports instead of the legacy `http+sse`. When the MCP server sits behind authorization, publish RFC 9728 metadata at `/.well-known/oauth-protected-resource` in addition to the card. List only public endpoints and do not expose private tools.

Детали аудита

MCP Server Card

Метаданные

Категория: Protocol/API
Remediation key: mcp_server_card_missing
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

`/.well-known/mcp`, an MCP Server Card path, or a `Link` relation returns valid JSON in any recognized form: a SEP-2127 registry-style card (reverse-DNS `name`, `description`, optional `remotes[]` with `type`/`url`), a SEP-1960 manifest (`mcp_version` plus an `endpoints` object with `streamable_http`/`sse` URLs), or a legacy SEP-1649 card (`serverInfo`, `protocolVersion`, transport endpoint). The protocol version is a `YYYY-MM-DD` revision date (e.g. `2025-11-25`), the response is served with `Content-Type: application/json`, and the transport is a canonical `streamable-http` or `sse`.

Как исправить

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for MCP Server Card (mcp_server_card).
Current check result:

{"evidence":{"candidates":[{"final_url":"https://aitextwatermarkremover.com/.well-known/mcp","headers":{"cache-control":"private, no-cache, no-store, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"source":"well_known","status":"http_error","status_code":404,"url":"https://aitextwatermarkremover.com/.well-known/mcp"},{"final_url":"https://aitextwatermarkremover.com/.well-known/mcp/server-card.json","headers":{"cache-control":"private, no-cache, no-store, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"source":"well_known","status":"http_error","status_code":404,"url":"https://aitextwatermarkremover.com/.well-known/mcp/server-card.json"},{"final_url":"https://aitextwatermarkremover.com/.well-known/mcp.json","headers":{"cache-control":"private, no-cache, no-store, max-age=0, must-revalidate","content-type":"text/html; charset=utf-8","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"source":"well_known","status":"http_e...

Expected result: `/.well-known/mcp`, an MCP Server Card path, or a `Link` relation returns valid JSON in any recognized form: a SEP-2127 registry-style card (reverse-DNS `name`, `description`, optional `remotes[]` with `type`/`url`), a SEP-1960 manifest (`mcp_version` plus an `endpoints` object with `streamable_http`/`sse` URLs), or a legacy SEP-1649 card (`serverInfo`, `protocolVersion`, transport endpoint). The protocol version is a `YYYY-MM-DD` revision date (e.g. `2025-11-25`), the response is served with `Content-Type: application/json`, and the transport is a canonical `streamable-http` or `sse`.
Fix guidance: Publish MCP discovery JSON at `/.well-known/mcp` or an MCP Server Card path; when using another URL, add a root `Link` header with `rel="mcp-server-card"`. State the protocol version as a `YYYY-MM-DD` date (not `1.0`), serve `Content-Type: application/json`, and use the canonical `streamable-http`/`sse` transports instead of the legacy `http+sse`. When the MCP server sits behind authorization, publish RFC 9728 metadata at `/.well-known/oauth-protected-resource` in addition to the card. List only public endpoints and do not expose private tools.
Stack templates:
- Generic web server: serve MCP Server Card from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for MCP Server Card; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for MCP Server Card; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for MCP Server Card; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for MCP Server Card; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for MCP Server Card; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for MCP Server Card; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement MCP Server Card via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add MCP Server Card via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add MCP Server Card as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate MCP Server Card in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "root": {
    "status": "fetched",
    "headers": {
      "link": "</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"",
      "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
      "content-type": "text/html; charset=utf-8",
      "cache-control": "public, max-age=0, must-revalidate"
    },
    "final_url": "https://aitextwatermarkremover.com/",
    "redirects": [],
    "status_code": 200,
    "requested_url": "https://aitextwatermarkremover.com/",
    "discovered_links": [],
    "malformed_entries": []
  },
  "headers": {
    "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
    "content-type": "text/html; charset=utf-8",
    "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
  },
  "final_url": "https://aitextwatermarkremover.com/.well-known/mcp",
  "candidates": [
    {
      "url": "https://aitextwatermarkremover.com/.well-known/mcp",
      "source": "well_known",
      "status": "http_error",
      "headers": {
        "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
        "content-type": "text/html; charset=utf-8",
        "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
      },
      "final_url": "https://aitextwatermarkremover.com/.well-known/mcp",
      "status_code": 404
    },
    {
      "url": "https://aitextwatermarkremover.com/.well-known/mcp/server-card.json",
      "source": "well_known",
      "status": "http_error",
      "headers": {
        "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
        "content-type": "text/html; charset=utf-8",
        "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
      },
      "final_url": "https://aitextwatermarkremover.com/.well-known/mcp/server-card.json",
      "status_code": 404
    },
    {
      "url": "https://aitextwatermarkremover.com/.well-known/mcp.json",
      "source": "well_known",
      "status": "http_error",
      "headers": {
        "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
        "content-type": "text/html; charset=utf-8",
        "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
      },
      "final_url": "https://aitextwatermarkremover.com/.well-known/mcp.json",
      "status_code": 404
    },
    {
      "url": "https://aitextwatermarkremover.com/.well-known/mcp-server.json",
      "source": "well_known",
      "status": "http_error",
      "headers": {
        "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
        "content-type": "text/html; charset=utf-8",
        "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
      },
      "final_url": "https://aitextwatermarkremover.com/.well-known/mcp-server.json",
      "status_code": 404
    },
    {
      "url": "https://aitextwatermarkremover.com/.well-known/mcp/server.json",
      "source": "well_known",
      "status": "http_error",
      "headers": {
        "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
        "content-type": "text/html; charset=utf-8",
        "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
      },
      "final_url": "https://aitextwatermarkremover.com/.well-known/mcp/server.json",
      "status_code": 404
    }
  ],
  "status_code": 404,
  "requested_url": "https://aitextwatermarkremover.com/.well-known/mcp",
  "related_candidates": {
    "oauth_protected_resource": [
      {
        "url": "https://aitextwatermarkremover.com/.well-known/oauth-protected-resource",
        "source": "oauth_protected_resource",
        "status": "http_error",
        "headers": {
          "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
          "content-type": "text/html; charset=utf-8",
          "cache-control": "private, no-cache, no-store, max-age=0, must-revalidate"
        },
        "final_url": "https://aitextwatermarkremover.com/.well-known/oauth-protected-resource",
        "status_code": 404
      }
    ]
  }
}

{
  "capabilities": [],
  "endpoint_count": 0,
  "transport_types": [],
  "protocol_versions": [],
  "server_card_found": false,
  "tools_signal_found": false,
  "link_relation_found": false,
  "prompts_signal_found": false,
  "resources_signal_found": false,
  "oauth_protected_resource_found": false
}

```
"mcp_server_card_missing"
```
```
"No MCP Server Card was discovered at configured .well-known locations."
```
```
"fail"
```

Электронная коммерция

0 пройдено · 0 частично · 1 ошибок

Можно отложитьОшибка

Product feed hints

Publish a UCP discovery document at `/.well-known/ucp` (JSON) and the agentic sitemap (`sitemap_agentic_discovery.xml`) as the primary public discovery path; add the product feed URL to a `Link` header or server-rendered `<link>`/`meta` with an absolute URL, and avoid exposing private price/order endpoints.

Детали аудита

Product feed hints

Метаданные

Категория: Коммерция
Remediation key: product_feed_hints_missing
URL: https://aitextwatermarkremover.com/

Ожидаемый результат

The site publishes agentic catalog discovery — UCP `/.well-known/ucp` (valid JSON) or the agentic sitemap — or at least an explicit product feed hint through HTTP/HTML `Link`, a meta tag, or a merchant/catalog feed URL. A public hint is not an ACP feed: ACP is push-based and not publicly discoverable.

Как исправить

Промпт для AI-агента

You are a senior web developer. Improve aitextwatermarkremover.com for AI agents.
Task: add or repair support for Product feed hints (product_feed_hints).
Current check result:

{"evidence":{"discovered_links":[],"feed_hints":[],"final_url":"https://aitextwatermarkremover.com/","headers":{"content-type":"text/html; charset=utf-8","link":"</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"","vary":"rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch"},"malformed_entries":[],"redirects":[],"requested_url":"https://aitextwatermarkremover.com/","snippet":"<!DOCTYPE html><html lang=\"en\" class=\"inter_c6e48ee1-module__JRO3KW__variable plus_jakarta_sans_73e8db66-module__y9VS4a__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/007gw7jkz3mh2.css\" da","status_code":200,"ucp_probe":{"outcome":"http_error","status_code":404,"url":"https://aitextwatermarkremover.com/.well-known/ucp"}},"outputs":{"discovery_hint_count":0,"feed_hint_count":0,"generic_feed_hint_count":0,"product_feed_hint_count":0},"remediation_key":"pro...

Expected result: The site publishes agentic catalog discovery — UCP `/.well-known/ucp` (valid JSON) or the agentic sitemap — or at least an explicit product feed hint through HTTP/HTML `Link`, a meta tag, or a merchant/catalog feed URL. A public hint is not an ACP feed: ACP is push-based and not publicly discoverable.
Fix guidance: Publish a UCP discovery document at `/.well-known/ucp` (JSON) and the agentic sitemap (`sitemap_agentic_discovery.xml`) as the primary public discovery path; add the product feed URL to a `Link` header or server-rendered `<link>`/`meta` with an absolute URL, and avoid exposing private price/order endpoints.
Stack templates:
- Generic web server: serve product feed discovery metadata from the public web root or a route, with the correct status, `Content-Type`, and cache policy.
- Nginx: add a `location`/`add_header` for product feed discovery metadata; verify `try_files`, redirects, and that private upstreams are not exposed.
- Apache: configure `Alias`, `Header set`, or a rewrite rule for product feed discovery metadata; check `.htaccess` and virtual host precedence.
- Next.js: use `public/`, route handlers, Metadata API, or middleware for product feed discovery metadata; do not disable SSR/SSG for public content.
- Nuxt: use `public/`, server routes, `useHead`/Nitro middleware for product feed discovery metadata; verify prerender/SSR output.
- Laravel: add a route/controller, Blade metadata, or middleware headers for product feed discovery metadata; do not bypass auth/authorization for private routes.
- Django: add a `urls.py` route/view, template metadata, or middleware headers for product feed discovery metadata; verify `ALLOWED_HOSTS` and cache behavior.
- WordPress: implement product feed discovery metadata via theme/plugin hooks, SEO plugin settings, or a static file; do not edit core files.
- Bitrix: add product feed discovery metadata via the site template, component, or web server config; verify composite cache and multi-site rules.
- Static hosting: add product feed discovery metadata as a static asset or platform headers file (`_headers`, `vercel.json`, `netlify.toml`).
- Headless CMS: generate product feed discovery metadata in the delivery layer/edge app from published content; do not expose draft or admin APIs.
Constraints: do not break SEO; do not expose private endpoints; preserve SSRF/redirect safety; do not add remote JS execution to the scanner; add tests.
Return a patch/diff and a short explanation.

Evidence JSON

{
  "headers": {
    "link": "</_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\", </_next/static/media/fba5a26ea33df6a3-s.p.18rizl4rsrl42.woff2>; rel=preload; as=\"font\"; crossorigin=\"\"; type=\"font/woff2\"",
    "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch",
    "content-type": "text/html; charset=utf-8"
  },
  "snippet": "<!DOCTYPE html><html lang=\"en\" class=\"inter_c6e48ee1-module__JRO3KW__variable plus_jakarta_sans_73e8db66-module__y9VS4a__variable\"><head><meta charSet=\"utf-8\"/><meta name=\"viewport\" content=\"width=device-width, initial-scale=1\"/><link rel=\"stylesheet\" href=\"/_next/static/chunks/007gw7jkz3mh2.css\" da",
  "final_url": "https://aitextwatermarkremover.com/",
  "redirects": [],
  "ucp_probe": {
    "url": "https://aitextwatermarkremover.com/.well-known/ucp",
    "outcome": "http_error",
    "status_code": 404
  },
  "feed_hints": [],
  "status_code": 200,
  "requested_url": "https://aitextwatermarkremover.com/",
  "discovered_links": [],
  "malformed_entries": []
}

{
  "feed_hint_count": 0,
  "discovery_hint_count": 0,
  "generic_feed_hint_count": 0,
  "product_feed_hint_count": 0
}

```
"product_feed_hints_missing"
```
```
"No public product feed hints were found in headers or metadata."
```
```
"fail"
```

Сайту нужны исправления

Зоны сайта

Сообщить о неверном результате

Видимость для AI

Discovery Link headers

Доступность контента

llms-full.txt

llms.txt

Markdown content negotiation

Правила для AI-ботов

Content usage policy signals

Rate-limit hints

Технические протоколы

A2A Agent Card

Agent Skills index

API Catalog discovery

MCP Server Card

Электронная коммерция

Product feed hints