zzapier.com

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 'agentmap' — crawlers will ignore this lineL42unknown_directive

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: /shared/L3Already covered by "allow: /" on line 2
• allow: /app/loginL4Already covered by "allow: /" on line 2
• disallow: /engine/hydrate/L6Already covered by "disallow: /engine/" on line 13

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://zapier.com/automations/sitemap-automations.xmlL40Not fetched: only the first few sitemaps are fetched, within a time limit and the site's Crawl-delay

Comfortably within the 500 KB that crawlers will read.