Question

How to submit llms.txt to Google Search Console

Updated July 2, 2026

You do not submit llms.txt as a separate Search Console feature. Treat it as a normal crawlable URL on your site, then use Search Console to verify the pages that matter: the homepage, sitemap, and the source pages listed inside the file.

The practical mistake is spending all the time on the file and none on the linked pages. Google can crawl a clean /llms.txt file and still decide not to index weak source pages.

Practical workflow

1. Publish the file at https://yourdomain.com/llms.txt.
2. Verify domain ownership in Google Search Console.
3. Submit your sitemap URL and keep it up to date.
4. Check URL Inspection for key source pages listed in your file.

What to inspect in Search Console

• Live URL test for /llms.txt: confirms Google can fetch the file.
• Sitemap report: confirms Google has discovered your current URL set.
• Page indexing report: shows whether source pages are indexed, crawled but not indexed, or blocked.
• Performance report: shows whether impressions are moving from homepage-only queries into intent pages.

URLs worth submitting first

If your site is new, do not submit every URL manually. Start with the pages that explain the site and have the strongest chance of becoming search results:

1. Homepage.
2. Main /llms.txt guide or generator page.
3. Examples page.
4. Top comparison page, such as llms.txt vs sitemap.xml.
5. Two or three high-value source pages that are linked from /llms.txt.

Example submission batch

For a new llms.txt or GEO site, a sensible first batch is narrow: submit the homepage, the main guide, the generator or validator tool, the sitemap URL, and five source pages that already answer specific search intent. Do not submit every tag page or thin template variation; that usually wastes the daily manual inspection quota.

For example, submit pages like /questions/where-to-put-llms-txt/, /questions/how-to-test-llms-txt/, and one comparison page before submitting lower-value archive pages. After 48-72 hours, check whether the status moved from discovered to crawled or indexed before requesting another batch.

What actually helps indexing

Google relies on crawlability, useful content, internal links, and sitemap discovery. Keep llms.txt aligned with those source pages, but do not treat it as a replacement for sitemap or indexing checks.

What GSC statuses usually mean

• Indexed: Google selected the page for the index. Ranking still depends on relevance and quality.
• Crawled, currently not indexed: Google fetched the page but has not chosen to store it. For thin or repetitive pages, improve the page before requesting indexing again.
• Discovered, currently not indexed: Google knows the URL but has not crawled it yet. Internal links and sitemap freshness can help discovery, but patience is still required.

Command checks before requesting indexing

curl -I https://yourdomain.com/llms.txt
curl -I https://yourdomain.com/sitemap.xml
curl -I https://yourdomain.com/
curl -s https://yourdomain.com/llms.txt | sed -n '1,80p'

If the file returns 200 and the linked source pages are useful, request indexing for the source pages, not just the text file. Google's own guidance is clear that a sitemap helps discovery but does not guarantee indexing.

When not to request indexing again

If Search Console says a page was crawled but not indexed, do not immediately click request indexing again without changing the page. First add missing examples, reduce overlap with nearby pages, strengthen internal links, and confirm the page has one clear query intent. Re-requesting the same unchanged page rarely fixes a quality or duplication decision.

Related: generate a clean draft, copy examples, and understand the SEO limits.

Validate your llms.txt