ccoalitiontechnologies.com

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://coalitiontechnologies.com/sitemap_index.xmlL26Responded HTTP 403

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

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.

• Unknown directive 'entitymap' — crawlers will ignore this lineL29unknown_directive

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 403 with a bot challenge instead of its content, 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.

Comfortably within the 500 KB that crawlers will read.