How it works
You share your website with your agent. It submits the details through GitHub. Maintainers review and merge the change, and your site appears in the directory once the update is published.
- Agent preparesReads the rules and gathers details
- Opens a GitHub PRProposes a change for review
- Checks and reviewAutomated checks and maintainer review
- Merge and deployPublishes the approved entry
- Listed on the siteThe full directory and RSS feed update
How does the agent submit my website?
Send your agent this site and your website address, and authorize it to submit the information publicly. Starting with llms.txt, it reads the contribution guide, entry format, and PR template, then checks whether your site is already listed. It puts the name, URL, and description you approve into sites/<slug>.json. A feed, tags, and selected work can be added if you wish.
The agent then forks the project on GitHub, adds the entry on a separate branch, runs the checks, and pushes the change. It opens a pull request (PR) against web20next/web20next—a proposal to merge the change into the project. Once the PR is created, it should give you the real link so you can follow its progress.
View the submission repositoryWho decides whether a site is listed?
Once a PR is submitted, automated checks validate the entry format, look for duplicate URLs, run tests, and build the site. Maintainers review whether the website is accessible, the description is accurate, and the owner has authorized the listing. Passing the checks does not mean the site is listed; a maintainer must review and merge the PR.
If changes are needed, your agent can update the same PR in response to feedback. If checks fail or the review is still pending, the entry stays out of the public directory.
When will my website appear in the directory?
Merging the PR adds the entry to the project repository. The next site build reads the records in sites/ to generate the full directory, the homepage preview, the RSS feed, and directory data for agents. Visitors see the update once that version is successfully deployed to Cloudflare.
“PR submitted,” “merged,” and “published” are three different states. The homepage shows only a selection of sites; the full directory includes every listing. If deployment fails or has not happened yet, the live directory stays unchanged.
You might also want to know
Can any agent do this?
Your agent needs to browse websites, work with GitHub, and run the project checks. It also needs your permission to use the relevant GitHub account. If tools, sign-in, or permissions are missing, it should keep a draft and explain what it needs. Preparing a file does not mean the submission succeeded.
What happens to my website?
Your website stays at its own address. You control its content and how you publish. This directory lists the public introduction and links you approve, so others can find you.
How do I update or remove my entry?
Send your agent this site and your website address again, and explain what to change or remove. It edits or deletes the existing entry through a new PR, with the same checks and review. The directory and RSS feed update after the change is merged and successfully deployed.