Search visibility · Experimental

Create a proposal-v2 resource map for your site's key pages.

Build a small Markdown file that some agents and services may choose to read. It is optional, does not control access, and Google Search ignores it for rankings and visibility.

  • Runs in your browser
  • Proposal v2 core format
  • No page fetching
  • No ranking claim

Build your file

Curate the useful paths.

Required. This becomes the file's single H1 heading.

Optional. Rendered as one concise Markdown blockquote.

Additional context

Paragraphs and lists are allowed here. Put headings in the resource sections below.

Resource sections

Group only the pages that make a useful, compact map.

1 of 12 sections
Documentation
Getting started

“Optional” is only a proposal convention for secondary links—not an instruction that software must honor.

Live llms.txt preview

Review the file as plain text.

Experimental
Ready to export

1 section · 1 resource · 303 UTF-8 bytes

Proposal v2 core formatProposal v2 checked August 26, 2026
# Example Studio

> Practical resources for understanding and using Example Studio.

Use the introductory guide first. The reference pages contain more detailed implementation notes.

## Documentation

- [Getting started](https://example.com/docs/getting-started): The best introduction to the project.

Copying and downloading happen locally in this browser.

File review

  • URLs are not fetched

    The tool checks URL syntax locally; it does not confirm that a page exists or is publicly reachable.

What this tool cannot verify

It does not fetch links, publish the file, test agent support, grant reuse permission, or predict discovery, citation, indexing, rankings, or AI visibility.

Use it with context

A voluntary resource map—not a search control.

llms.txt is an emerging community proposal rather than an IETF or W3C web standard. Support varies by service and can change. Google says it ignores llms.txt for Search, including generative Search features, so the file neither helps nor harms rankings or visibility.

What it can contain

A project name, short summary, additional context, and curated link sections.

What still matters

Useful HTML, accessible navigation, metadata, canonicals, sitemaps, and ordinary SEO.

What it cannot control

Crawling, indexing, model training, reuse, citation, ranking, or inclusion in an answer.

What protects private content

Authentication and authorization—not llms.txt, robots.txt, or a hidden-looking URL.

Treat the published file as public.

Never include secrets, tokens, personal data, private URLs, or unpublished paths. Listing a link does not grant a service permission to reuse its content.

After download

Publish deliberately.

  1. Review every public link

    Confirm each destination exists, is meant to be public, and is worth highlighting.

  2. Place the file at the intended path

    Use /llms.txt for a site-wide file, or a subpath file for that section of a site.

  3. Consider the optional v2 discovery links

    Proposal v2 recommends rel="alternate" type="text/markdown" for a page's Markdown version and rel="describedby" for the applicable llms.txt file, supplied through HTML or an HTTP Link header. This generator does not configure those integrations.

  4. Serve and maintain it as plain text

    Serve the file as UTF-8 plain text. Do not render generated content as trusted HTML, and update or remove links when pages move or access changes.

Sources and limits

Read the proposal—and the counterweight.

Checked August 26, 2026. The generator follows the proposal v2 core file order while adding bounded local validation. It does not configure Markdown alternates, HTTP headers, crawling, access, or permissions.