We could not read this site's robots.txt, its public rules file for bots (HTTP 403). A refusal like this usually comes from anti-bot software, not from the site's written rules, so on its own it does not count as a block. The homepage also turned our bot, which says who it is, away with a refusal page sent with HTTP 200 instead of an error code.
Blocking these keeps the site out of future AI training. It does not stop AI from reading the site to answer questions.
Bots for AI search Unknown
Unknown
Blocking these usually means the site stops showing up as a source in AI answers.
AI assistants Unknown
Unknown
5 of these 7 companies say their assistants may ignore robots.txt.
Bot by bot
We could not read the rules file, so we can't say which bots are allowed.
The rules file (robots.txt)
We could not read robots.txt (HTTP 403).
Everything else we checked
Front door
Turned awayThe homepage turned our bot, which says who it is, away with a refusal page sent with HTTP 200 instead of an error code.GET https://lowes.com/ as WalledWebBot, from a residential connection in the United States
llms.txt
Skipped: robots.txt request was refused
ai.txt
Skipped: robots.txt request was refused
TDMRep
Skipped: robots.txt request was refused/.well-known/tdmrep.json (W3C Community Group report)
Anti-bot software
Served through Akamai.From response headers and cookie names only. A cookie shows the product is there, not how it is set up.
Readable by AI
No schema.org structured data on the homepage. Readable text is present in the HTML.Homepage only. Useful for site owners; not part of the result.
Terms of Service
No Terms of Service page found.
Not found
No Content-Signal or Content-Usage lines, licensing signals (RSL License, HTTP 402) or robots meta tags.
History
39 versions on record since 1 Jan 2023
One square per month, from Internet Archive copies and our own daily checks. Dark: blocked. Gray: some blocked. Light: allowed. Striped: no copy that month.
No AI-relevant changes in 39 recorded versions since 1 Jan 2023.