eelevenlabs.io

The URL is declared in robots.txt but does not return a successful response.

Consequence. Crawlers find nothing at the address they were pointed to, so no URLs are submitted. This is worse than declaring no sitemap, because the declaration suggests discovery is covered when it is not.

If that is not intended. Publish the sitemap at the declared URL, or correct the URL to where it lives.

• https://showcase.elevenlabs.io/sitemap.xmlL150Responded HTTP 429

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 '*/page-template-preview/' should start with '/'L21invalid_path
• Path '*/abtest/' should start with '/'L46invalid_path
• Path '*/p/' should start with '/'L47invalid_path
• Path '*/ab/' should start with '/'L48invalid_path
• Path '*/page-template-preview/' should start with '/'L51invalid_path
• Path '*/abtest/' should start with '/'L76invalid_path
• Path '*/p/' should start with '/'L77invalid_path
• Path '*/ab/' should start with '/'L78invalid_path
• Path '*/page-template-preview/' should start with '/'L81invalid_path
• Path '*/abtest/' should start with '/'L106invalid_path
• Path '*/p/' should start with '/'L107invalid_path
• Path '*/ab/' should start with '/'L108invalid_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/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.

Comfortably within the 500 KB that crawlers will read.