eelevenlabs.io

Lines that do not parse as a known directive: invalid_path.

Consequence. A crawler skips what it cannot parse, without reporting anything. A misspelled "Dissalow" leaves a path fully crawlable while the file appears to restrict it.

If that is not intended. Correct the spelling of each field name, and make sure every line follows "Field: value". Rules must also appear after a User-agent line to belong to a group.

• Path '*/abtest/' should start with '/'L16invalid_path
• Path '*/p/' should start with '/'L17invalid_path
• Path '*/ab/' should start with '/'L18invalid_path
• Path '*/abtest/' should start with '/'L47invalid_path
• Path '*/p/' should start with '/'L48invalid_path
• Path '*/ab/' should start with '/'L49invalid_path
• Path '*/abtest/' should start with '/'L78invalid_path
• Path '*/p/' should start with '/'L79invalid_path
• Path '*/ab/' should start with '/'L80invalid_path
• Path '*/abtest/' should start with '/'L109invalid_path
• Path '*/p/' should start with '/'L110invalid_path
• Path '*/ab/' should start with '/'L111invalid_path
• Path '*/abtest/' should start with '/'L141invalid_path
• Path '*/p/' should start with '/'L142invalid_path
• Path '*/ab/' should start with '/'L143invalid_path

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/flowsL24Already covered by "allow: /" on line 2
• allow: /share/L34Already covered by "allow: /" on line 33
• allow: /embed/L35Already covered by "allow: /" on line 33
• allow: /app/sign-inL36Already covered by "allow: /" on line 33
• allow: /app/sign-upL37Already covered by "allow: /" on line 33

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 answered HTTP , so its meta robots tags and X-Robots-Tag headers were not read.

Consequence. Nothing is known about whether this page asks to be kept out of search results. Its absence of directives here proves nothing either way.

If that is not intended. Analyse the page again once it answers normally to our bot.

Every declared sitemap is an absolute URL and is crawlable.

• https://elevenlabs.io/sitemap.xmlL152
• https://help.elevenlabs.io/hc/sitemap.xmlL153
• https://elevenlabs.io/docs/sitemap.xmlL154
• https://showcase.elevenlabs.io/sitemap.xmlL155

Comfortably within the 500 KB that crawlers will read.