A meta robots tag or X-Robots-Tag header instructs crawlers not to index this URL.
Consequence. The page will be dropped from search results. That is the correct mechanism for removing a page — worth confirming it is intended for this URL.
If that is not intended. If the page should rank, remove the noindex directive. Keep the URL crawlable either way, since a crawler must fetch the page to see the change.
<meta name="robots" content="max-image-preview:large">Page HTML
X-Robots-Tag: noindex, followRobots.txt response
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: /wp-content/uploads/wc-logs/L2"logs" below the first level
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: 10L9
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.
Not checked
1 declared sitemap was not checked
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://typescale.com/sitemap_index.xmlL15Not fetched: it is on another origin, whose robots.txt could not be read
Pass
No syntax problems
Every line parses as a directive crawlers understand.
Pass
File size is 456 bytes
Comfortably within the 500 KB that crawlers will read.
