This report is outdated. It was fetched on , and a newer version from is available.

View the latest version

robots.txt report

builtinnyc.com

https://www.builtinnyc.com/

C

63/100

Complexity 69/100

How scoring works
User Agents
5
Rules
138
Sitemaps
0
Warning
3
File Size
3.9 KB

3 things to look at

2 warning · 1 notice · 7 pass

5 crawlers named · 1 unrecognised

Who this file lets in

  • AI Search Crawler all 2 allowed
  • Every other crawler all 1 allowed
  • AI Data Scraper all 1 allowed
  • AI Assistant all 1 allowed

Path Access Checker

Detailed Analysis

Warning

No sitemap is declared

The file contains no "Sitemap:" line.

Consequence. Crawlers have to discover every URL by following links. Pages that are deep, newly published, or poorly linked internally take longer to be found, and some may never be. A sitemap is the most direct way to hand a crawler the full list.

If that is not intended. Publish an XML sitemap and declare it with an absolute URL, e.g. "Sitemap: https://example.com/sitemap.xml". The line is global — it belongs outside any User-agent group and applies to every crawler.

Warning

7 lines will be ignored by crawlers

Lines that do not parse as a known directive: invalid_path.

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.

  • Path '*?page=' should start with '/'L107invalid_path
  • Path '*?region_id=' should start with '/'L108invalid_path
  • Path '*sitemap.xml?page=' should start with '/'L109invalid_path
  • Path '*?event_src=' should start with '/'L116invalid_path
  • Path '*?elementor_library' should start with '/'L117invalid_path
  • Path '*?state=' should start with '/'L118invalid_path
  • Path '*challenge-platform' should start with '/'L120invalid_path
Notice

3 rules can never take effect

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: /search/L64Already covered by "disallow: /search" on line 65
  • disallow: /form/claim-company?*L89Already covered by "disallow: /form/" on line 112
  • disallow: /onboarding*L95Already covered by "disallow: /onboarding" on line 122
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

AI training crawlers can reach the site

All 6 checked AI training crawlers are allowed at the site root.

Pass

No indexing directives on the requested page

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

Pass

File size is 3.9 KB

Comfortably within the 500 KB that crawlers will read.