Public crawl path
Allow public SEO pages, visibility pages, tools, answers, use cases, comparisons, and resources.
Visibility architecture
robots.txt for TypeToSell should allow public pages, sitemap.xml, llms.txt, and AI search crawlers while blocking private app, auth, admin, and checkout surfaces. Training-only crawlers can be handled separately from citation and search crawlers so public pages remain discoverable.
Last updated: 2026-07-12. This page is written for SEO, ASO, GEO, AEO, and internal-link citation.
Signals
Allow public SEO pages, visibility pages, tools, answers, use cases, comparisons, and resources.
Disallow API, auth confirmation, admin, and private trial surfaces from public crawling.
Allow citation and search crawlers such as GPTBot, OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, Googlebot, and Bingbot.
Treat broad training-only crawlers separately from search and citation crawlers when the business policy requires it.
Implementation
Keep robots.txt pointing to the canonical sitemap URL.
Make sure dotted files such as llms.txt and llms-full.txt do not redirect to language parameters.
Keep /api/, /auth/confirm, /admin/, and /start out of crawler paths.
Verify robots.txt, sitemap.xml, llms.txt, and llms-full.txt from a clean browser profile before off-page submissions.
Related internal links
FAQ
Not if the goal is AI citation visibility. Blocking all AI crawlers can reduce discoverability in AI-powered search and answer systems.
Private app, API, admin, auth, checkout, and trial surfaces should stay blocked or noindexed because they are not public SEO landing pages.
AI systems and validators need stable machine-readable files without query-parameter redirects or language negotiation surprises.
Try the product surface
Use the free generator or Chrome extension workflow to see the same manual-first promise that the SEO, ASO, and GEO pages describe.