Question

How to submit llms.txt to Google Search Console

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

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.

The exact order I would use

  1. Submit the sitemap first: use the Sitemaps report for https://yourdomain.com/sitemap.xml. This gives Google the canonical URL set and gives you a place to watch sitemap parsing errors.
  2. Inspect the homepage: confirm the live test returns the rendered page, not a firewall page, redirect loop, or origin error.
  3. Inspect the best source pages: pick pages that answer one narrow query, have internal links, and are linked from /llms.txt.
  4. Request indexing only after the live test passes: if the live test cannot fetch the page, fix access first. A manual request cannot compensate for a blocked or broken URL.
  5. Wait before repeating: if the page remains crawled but not indexed, improve the page before asking again.

Fast triage for "crawled, currently not indexed"

This status is normal for a new site, but it is also the status you get when a page is too similar to nearby pages. Before requesting indexing again, compare the page against the closest five pages on your own site. If the title, opening paragraph, examples, and internal links could be swapped without changing much, Google has little reason to keep a separate result.

How to choose the next 10 URLs

When you have more pages than manual inspection quota, do not pick randomly. Use pages that already have one signal of demand and one signal of quality. A simple batch rule works well for new GEO sites:

For example, a better batch is one tool page, two troubleshooting pages, two comparison or policy pages, and five high-intent industry/use-case pages. That mix gives Google a clearer picture of the site's topical coverage than ten similar template pages.

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

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.

Official references

Related: generate a clean draft, copy examples, understand the SEO limits, and separate crawl errors from origin 52x failures.

Validate your llms.txt