robots.txt report

impact.com

https://impact.com

B

81/100

Complexity 90/100

How scoring works
User Agents
9
Rules
13
Sitemaps
1
Warning
2
File Size
519 B
Cached result · Expires in 23 hours 31 minutes

2 things to look at

1 warning · 1 notice · 1 info · 8 pass

9 crawlers named · 3 unrecognised

What this file says about crawlers

Who this file lets in

  • SEO Crawler all 3 blocked
  • Uncategorized all 2 blocked
  • Unrecognised all 2 blocked
  • AI Data Scraper all 1 blocked
  • Every other crawler all 1 allowed

Path Access Checker

Detailed Analysis

Warning

1 rule names a location nobody would have guessed

Rules name a sensitive location made specific by a qualifier or by where it sits, or a spreadsheet by its full path.

Consequence. A bare "/backup" is in every scanner wordlist; "/backup-2023/" is in none. Listing it advertises the location to the readers least likely to honour the rule.

If that is not intended. Put these locations behind authentication or remove them; once they are protected, the line can stay or go. Responses behind authentication are not indexed, so they need no "noindex". Content that is public by design and only has to stay out of search wants a "noindex" without the Disallow: a crawler only sees a noindex on a page it may fetch.

  • Disallow: /search-internal/L21"internal" with a qualifier
Notice

Crawl-delay is declared 1 time and Google ignores it

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: 5L24
Info

1 of 6 AI training crawlers are blocked

Blocked: Bytespider.

  • BytespiderByteDanceL6

    ByteDance model training

    "Disallow: /" blocks Bytespider.

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.

Pass

Search engines can reach the site

All 6 checked search engines are allowed at the site root.

Pass

AI answer engines can reach the site

All 4 checked AI answer engines are allowed at the site root.

Pass

User-triggered AI fetches can reach the site

All 3 checked user-triggered AI fetches are allowed at the site root.

Pass

Social link previews can reach the site

All 5 checked social link previews are allowed at the site root.

Pass

Page indexing directives are consistent

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

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

1 sitemap declared

Every declared sitemap is an absolute URL and is crawlable.

  • https://impact.com/sitemap_index.xmlL26
Pass

No syntax problems

Every line parses as a directive crawlers understand.

Pass

File size is 519 bytes

Comfortably within the 500 KB that crawlers will read.