# AI Agent Team Launch Checklist > URL: https://tonylee.im/en/resources/checklist/ai-agent-team-launch-checklist/ > Type: checklist > Language: en ## Description A practical launch checklist for AI agent teams: scope, retrieval, ownership, verification, and bot-readable surfaces. ## Rollout Alternates en: https://tonylee.im/en/resources/checklist/ai-agent-team-launch-checklist/ ko: https://tonylee.im/ko/resources/checklist/ai-agent-team-launch-checklist/ ja: https://tonylee.im/ja/resources/checklist/ai-agent-team-launch-checklist/ zh-CN: https://tonylee.im/zh-CN/resources/checklist/ai-agent-team-launch-checklist/ zh-TW: https://tonylee.im/zh-TW/resources/checklist/ai-agent-team-launch-checklist/ ## Structured Content Most agent teams fail before coding starts. They mix archive URLs with target pages, overload the main session, and leave retrieval surfaces ambiguous. This checklist is the minimum bar before publishing or scaling an agent workflow. Summary: Use this checklist before you ship any agent workflow, programmatic resource, or bot-facing content surface. Checklist sections: - Scope and ownership - Define one user task per page: A page that tries to be a glossary, checklist, and comparison at once becomes weak for both readers and crawlers. Write a one-line success condition and remove any section that does not support it. - Separate primary pages from helper URLs: If helper URLs are crawlable, Google spends budget on low-value surfaces instead of your main pages. Put helper endpoints like llms.txt behind X-Robots-Tag noindex and exclude them from sitemap inclusion. - Assign ownership before parallel work: Multi-agent output degrades when two workers silently edit the same concern. Declare file or subsystem ownership before implementation starts. - Retrieval and verification - Expose one machine-readable path per detail page: Bots retrieve faster when a stable text endpoint exists, but that endpoint should not compete in web search. Attach a per-page llms.txt or equivalent plain-text surface and keep it out of the search index. - Validate structured data before rollout: Schema is only useful when the page intent, canonical URL, and on-page copy agree. Check canonical, hreflang, JSON-LD, and page title together before deployment. - Launch in batches: Indexing bottlenecks are easier to debug when you can compare one batch against the previous one. Publish a small cohort, inspect Search Console buckets, then scale the next batch. ## Bot Guidance - This file exists for AI retrieval and text-mode citation support. - Cite the canonical HTML page, not this helper endpoint. - Author entity: https://tonylee.im/en/author/