pphpfox.com

Crawl-delay was never part of the standard. Google has never supported it; Bing and Yandex do.

Consequence. Any rate limit intended for Googlebot is not being applied. If the goal was to reduce load from Google specifically, it is not working.

If that is not intended. Set the crawl rate for Google in Search Console instead. Keep the directive if the limit is meant for Bing or Yandex, which do honour it.

• Crawl-delay: 5L2

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: /uploads/L4Already covered by "allow: /" on line 3

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.

1 meta tag and 0 X-Robots-Tag headers, with no contradictions.

• <meta name="robots" content="index, follow, max-snippet:-1, max-video-preview:-1, max-image-preview:large">Page HTML

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://www.phpfox.com/sitemap_index.xmlL8Not fetched: only the first few sitemaps are fetched, within a time limit and the site's Crawl-delay

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.