Operated by LINER
The web crawler for LINER, an AI workspace and highlighter tool used to index content for user recommendations.
The web crawler for LINER, an AI workspace and highlighter tool used to index content for user recommendations.
LINER Bot is an AI data-collection crawler operated by LINER. It harvests web content to build or expand training datasets for large language models (LLMs). Unlike search crawlers, LINER Bot does NOT influence your page ranking in any search engine. The user-agent string LINER Bot can be safely blocked via robots.txt, meta tags (noai), or the emerging llms.txt standard without any SEO penalty. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.
User-agent: LINER Bot / Disallow: / without any SEO penalty. This is the recommended approach if you want to opt out of LINER's LLM training datasets.<code>User-agent: LINER Bot</code> — Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
LINER Bot is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).Understanding LINER Bot's purpose helps you decide whether to allow or block it.
LINER Bot. This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from LINER Bot by performing a reverse-DNS lookup on the source IP — legitimate bots resolve back to their operator's domain.LINER Bot is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).User-agent: LINER Bot / Disallow: / without any SEO penalty. This is the recommended approach if you want to opt out of LINER's LLM training datasets./robots.txt file:
User-agent: LINER Bot Disallow: /This instructs LINER Bot not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g.,
Disallow: /blog/). Note: robots.txt is publicly readable — any bot or human can inspect it at yourdomain.com/robots.txt.LINER Bot (case-insensitive grep: grep -i "LINER Bot" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For LINER Bot specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).User-agent: LINER Bot Crawl-delay: 10(10 second delay between requests).
Disallow: / you can restrict LINER Bot to specific paths:
User-agent: LINER Bot Disallow: /private/ Disallow: /staging/ Allow: /This allows LINER Bot everywhere except the listed paths. Path matching in robots.txt uses prefix matching —
Disallow: /private/ blocks /private/page.html but NOT /public/private/.<meta name="LINER Bot" content="noai, noimageai, noindex"> to your pages.
2. Add a llms.txt file at your domain root (emerging standard).
3. Use Cloudflare WAF or Nginx to return 403 for this user-agent.
4. Consider IP blocklists for LINER's known crawler IP ranges.<meta name="LINER Bot" content="noindex">
• **X-Robots-Tag HTTP header**: X-Robots-Tag: noai, noimageai
• **llms.txt**: Add a /llms.txt file (similar to robots.txt but for LLMs)
• **Server block**: Return 403 or 429 for this user-agent via WAF or Nginx
Using multiple layers provides the strongest protection.