rremoteok.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: 1L132
• Crawl-delay: 1L212

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.

• disallow: /*?action=get_jobsL141Already covered by "disallow: /" on line 137
• disallow: /*?*action=get_jobsL142Already covered by "disallow: /" on line 137
• disallow: /*?*&action=get_jobsL143Already covered by "disallow: /" on line 137
• disallow: /*?*&action=get_jobs&*L144Already covered by "disallow: /" on line 137
• disallow: /*?url=L145Already covered by "disallow: /" on line 137
• disallow: /track-adL146Already covered by "disallow: /" on line 137
• disallow: /?tagsL147Already covered by "disallow: /" on line 137
• disallow: /?&actionL148Already covered by "disallow: /" on line 137
• disallow: /l/L189Already covered by "disallow: /" on line 186
• disallow: /*ou-tout-autre*L190Already covered by "disallow: /" on line 186

Blocked: Baiduspider.

• BaiduspiderBaiduL81

  Baidu

  "Disallow: /" blocks Baiduspider.

If that is the intention. If your intention is to keep the site out of the major search indexes, the current configuration achieves that for these crawlers — the rest of the group is still allowed.

Consequence. These search engines cannot crawl the site, so its pages will not appear in their results. Note that robots.txt does not remove URLs that are already indexed — it stops them being re-crawled.

If that is not intended. Remove the matching Disallow rule, or give these crawlers their own group with an Allow rule. Path matching is longest-wins, so a specific Allow overrides a broader Disallow.

Blocked: Bytespider, meta-externalagent, Amazonbot.

• BytespiderByteDanceL42

  ByteDance model training

  "Disallow: /" blocks Bytespider.

• meta-externalagentMetaL75

  Meta model training

  "Disallow: /" blocks meta-externalagent.

• AmazonbotAmazonL36

  Amazon model training and Alexa

  "Disallow: /" blocks Amazonbot.

If that is the intention. If your intention is to prevent this content being used as model training data, the current configuration achieves that for these crawlers — the rest of the group is still allowed.

Consequence. These crawlers cannot retrieve content from the site, so it will not be collected as training data. They send no traffic back, and blocking them does not affect search rankings.

If that is not intended. Remove the site-wide block, or replace it with narrower path restrictions.

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.

The page sends no robots meta tag and no X-Robots-Tag header.

Every declared sitemap is an absolute URL and is crawlable.

• https://remoteok.com/sitemap.xmlL134

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.