pproducthunt.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://www.producthunt.com/sitemaps_v3/root_sitemap.xml.gzL34Responded HTTP 403
• https://www.producthunt.com/sitemaps_v3/stories_sitemap.xml.gzL35Responded HTTP 403
• https://www.producthunt.com/sitemaps_v3/topics_sitemap.xml.gzL36Responded HTTP 403
• https://www.producthunt.com/sitemaps_v3/newsletters_sitemap.xml.gzL37Responded HTTP 403
• https://www.producthunt.com/sitemaps_v3/forums_sitemap.xml.gzL38Responded HTTP 403
• https://www.producthunt.com/sitemaps_v3/discussions_sitemap.xml.gzL39Responded HTTP 403
• https://www.producthunt.com/sitemaps_v3/product_about_sitemap.xml.gzL40Responded HTTP 403
• https://www.producthunt.com/sitemaps_v3/product_alternatives_sitemap.xml.gzL41Responded HTTP 403
• https://www.producthunt.com/sitemaps_v3/product_reviews_sitemap.xml.gzL42Responded HTTP 403
• https://www.producthunt.com/sitemaps_v3/products_categories_sitemap.xml.gzL43Responded HTTP 403

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: 1L46
• Crawl-delay: 1L49

The same directive and path appear repeatedly within one group.

Consequence. Duplicates have no effect on crawling, but they inflate the file toward the 500 KB limit and usually signal that the file is generated without dedup.

If that is not intended. Remove the repeats.

• disallow: /search*L32Already declared on line 7 for *

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.

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.