eelevenlabs.io

A broader rule of the same type already covers these paths.

Consequence. These lines change nothing. They are harmless, but they add length to a file that has a size limit, and they make the real policy harder to read.

If that is not intended. Remove the redundant rules, or narrow the broader rule if it is catching more than intended.

• allow: /share/L3Already covered by "allow: /" on line 2
• allow: /embed/L4Already covered by "allow: /" on line 2
• allow: /app/sign-inL5Already covered by "allow: /" on line 2
• allow: /app/sign-upL6Already covered by "allow: /" on line 2
• allow: /docs/api/fern-docs/ogL7Already covered by "allow: /" on line 2
• allow: /app/flowsL23Already covered by "allow: /" on line 2
• allow: /share/L33Already covered by "allow: /" on line 32
• allow: /embed/L34Already covered by "allow: /" on line 32
• allow: /app/sign-inL35Already covered by "allow: /" on line 32
• allow: /app/sign-upL36Already covered by "allow: /" on line 32

All 6 checked search engines are allowed at the site root.

All 4 checked AI answer engines are allowed at the site root.

All 3 checked user-triggered AI fetches are allowed at the site root.

All 5 checked social link previews are allowed at the site root.

All 6 checked AI training crawlers are allowed at the site root.

The page sends no robots meta tag and no X-Robots-Tag header.

These sitemaps were not seen: each was blocked for our bot, left out by a limit, or did not answer in time. Each line says which.

Consequence. Nothing is known about whether they work. They are not counted against the file.

• https://showcase.elevenlabs.io/sitemap.xmlL150Not fetched: it is on another origin, whose robots.txt could not be read

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.