Control crawl access
Publish robots.txt with intentional exclusions only, and declare the sitemap location.
Technical SEO and AI Discoverability
Audit robots.txt, sitemap.xml, and llms.txt health, then connect post-release discovery workflows with sitemap URL extraction and IndexNow submission.
Cover configuration checks, URL inventory, and update notification at each release stage.
Check crawl directive syntax, conflicts, sitemap declarations, and file-size limits.
Run checkValidate XML structure, URL entries, robots declaration, encoding, and response performance.
Run checkCheck title, summary, and resource-list structure against the llmstxt.org proposal.
Run checkExport URL lists from sitemaps for batch audits, migration checks, and content inventory.
Extract URLsNotify compatible search engines after pages are added, updated, or deleted.
Submit URLsPublish robots.txt with intentional exclusions only, and declare the sitemap location.
Generate valid sitemaps containing canonical, accessible URLs you want discovered.
Use llms.txt to explain the site and curate high-value entry pages for models.
Recheck after releases; use IndexNow and search platforms when important URLs change.
Start by confirming that robots.txt and sitemap.xml are accessible and consistent, then provide llms.txt when appropriate. After publishing important pages, IndexNow may notify compatible search engines.
No. The checkers quickly identify configuration problems before release or during troubleshooting, while search platforms report actual crawling and indexing behavior.
A sitemap supports search discovery by listing important URLs; llms.txt supports model understanding through concise background and curated resource links.
No. The score highlights configuration risk and improvement opportunities; indexing also depends on page quality, links, and search-engine decisions.