Can AI crawlers read Modrinth and CurseForge project pages?
Modrinth's yes; CurseForge's we could not read. Checked 2026-11-14: modrinth.com's robots.txt has a single Disallow: /_internal/ and names no AI crawler; all three sample project pages return 200 with the description text directly in the HTML. www.curseforge.com returned a 403 challenge page to all our plain requests (robots.txt, sitemap, project page), so what it says to AI crawlers and what its project pages contain can only be written as unverified; we did not bypass it.
| Check | modrinth.com | www.curseforge.com |
|---|---|---|
| robots.txt | 200, 35 bytes: User-agent * plus Disallow: /_internal/; no AI crawler is named | Unverified: 403, Cloudflare challenge page |
| sitemap | /sitemap.xml returns 404 and robots.txt has no Sitemap line; we found no public sitemap | Unverified: /sitemap.xml returns 403 |
| Project detail page | Three samples (a mod, a plugin, a resource pack) all return 200, about 460 KB, with the text in the HTML | Unverified: the sample project page returns 403 |
| A project that does not exist | Returns 200, title "Project not found", robots meta noindex | Not verified |
| Project count | Official public API: 169,151 projects, 1,571,443 versions, 72,788 authors | Not verified |
Modrinth has no sitemap, so crawlers have to find your project by following links. Give the project page external links: your GitHub README, your website and your video descriptions should all carry the Modrinth URL.
Where does each field appear on a Modrinth project page?
Title and summary matter most: in our sample the <title> is "project name - Minecraft type", the meta description is the summary plus a fixed suffix, and og:description is only the summary. The description body is under the Description tab, written directly in the HTML.
| Field | Where it appears on the public page (2026-11-14, sample Sodium) | How to write it |
|---|---|---|
| title (project name) | <title> is "Sodium - Minecraft Mod"; it is also the large heading on the page | Only the project name; no "mod", version number or loader name |
| summary | The first half of the meta description (followed by the fixed text "- Download the Minecraft Mod Sodium on Modrinth"); og:description; the line under the page title | One sentence saying what it does; plain text; do not repeat the project name |
| Description body | The Description tab, with the text directly in the HTML (matches the start of body in the API) | Restate the summary in the first two sentences, then write install, features, compatibility, configuration |
| Categories | Tags on the page (for example "Optimization") | Pick ones that really fit; do not pad |
| Environment, loaders, Minecraft versions | Compatibility, Platforms and Supported environments on the page | Fill them in accurately for every version, consistent with the description |
| License and links | Licensed, Report issues, View source and Visit wiki on the page | Fill all of them, pointing to public, relevant pages |
| Gallery | We did not check whether the gallery is in the HTML: unverified | Use in-game screenshots; the images must match the text |
Whether AI really uses the text in these places to answer questions, we have no evidence, so it is unverified. What we can confirm: for a crawler that does not run scripts, all of this text is already in the HTML; the reason is in Do AI crawlers render JavaScript?.
What does Modrinth officially require for descriptions?
The official content rules (the page says last modified 2026-08-13) ask the description to cover three things: what the project specifically does or adds; why someone should download it; and any critical information the user must know before downloading. We read the original on 2026-11-14; the summary is below.
| Rule | What the official text says (paraphrased) | Why it matters for AI search |
|---|---|---|
| 2.1 General expectations | From the description, users should be able to understand what the project does and how to use it | This is exactly the sentence AI needs when answering "which mod does X" |
| 2.2 Accessibility | Descriptions must have a plain-text version (images and video may take priority); headers must not be used for body text; there must be an English translation unless it is meant for a specific language (such as translation packs) | A description that is only images cannot be read by a crawler; an English version is required |
| 5 Metadata | License, environment, tags and so on must be filled in correctly and consistent with information elsewhere; the title is only the name; the summary is a small unformatted overview that does not repeat the title | Fields and body agree, so what AI reads says the same thing |
| 5 External links and gallery | External links must lead to public, relevant resources; gallery images must be relevant and not misleading | — |
| 6 Generative AI | Use must be disclosed honestly; images on the page such as the gallery, icon and description cannot be created or derived from generative AI and may be removed | Use real in-game screenshots |
The rules set no character limit for the summary or description; those numbers are unverified. On review the docs say: they aim for 24 to 48 hours, but it now fluctuates widely, averaging two to four weeks and sometimes longer; modpacks 72 to 96 hours. So write the first submission completely.
What does CurseForge officially require for projects?
CurseForge's help center (support.curseforge.com, which we could read) sets out submission requirements, read in the original on 2026-11-14: the name, summary and description each have requirements, and an unclear description is rejected. We cannot read the project page itself (403), so what follows is what the platform officially asks of authors, not where things actually appear on the page.
| Field | What the official text requires (paraphrased) | Which article |
|---|---|---|
| Project name | Unique; no version number, class name (mod, modpack, addon) or overlong name; names must be in English | Project Submission Guide and Tips; Moderation Policies |
| Summary | One line saying what the project does, not who made it or who it is for; preferably no more than a sentence; do not copy the description | Project Submission Guide and Tips; Moderation Policies |
| Description | Say what the project adds or changes; generic phrases like "Changes the core/vanilla game" or "adds items to the game" are not enough; bad grammar or an insufficient description is rejected; other languages may be added, but English comes first | Creating and Submitting a Project; Moderation Policies |
| Categories | One main category and up to 4 additional ones; padding with unrelated categories gets it sent back | Project Submission Guide and Tips; Creating and Submitting a Project |
| Logo | At least 400x400 px .png, not a solid-colour square, original | Project Submission Guide and Tips |
| Images | In-game screenshots with the mod enabled are recommended; resource packs need a sample image | Project Submission Guide and Tips; Moderation Policies |
| Updates and links | File updates need a changelog; external download links are not allowed; no updates with no real change just to gain visibility | Moderation Policies |
| AI showcase images | A showcase image altered by AI that could mislead must say so on the image or in the description | Moderation Policies |
The official articles do not say how long project review takes; that number is unverified.
What should I do after publishing a mod?
1. Make the title, summary and first two sentences of the description say the same thing
Say "what it does, for which loader and Minecraft version" in all three places. The official requirements of both platforms agree here: the summary does not copy the description, and the description opens by saying what it does.
Title: Sodium (the name only: no "mod", no version, no loader) Summary: A rendering engine replacement for Minecraft that raises frame rates and reduces stutter. (what it does; plain text; no title repeated) Description: 1. What it does (two sentences, same meaning as the summary) 2. Install: which loader, which Minecraft versions, which folder 3. Features: a list, one real feature per line 4. Compatibility and known conflicts: a table 5. Configuration: where the options are 6. Credits and links: source, issues, wiki Categories: one that really fits; extra ones only if true Gallery: in-game screenshots that match the page text2. Use real in-game screenshots
Modrinth does not allow generative-AI images, and CurseForge requires AI-altered showcase images to be disclosed. Screenshots must match the text.
3. Fill in the loader, versions and environment accurately for each version
These fields show on the page and must agree with what the description says.
4. Build external links to your project page
Modrinth has no sitemap; write the project page URL in your GitHub README, website and video descriptions so crawlers have a path to it. How to write the README is in Will AI search cite my GitHub README?.
5. If the source is on GitHub, make both pages say the same thing
Make the GitHub About, README and the Modrinth summary and description say the same thing; the other places an open-source project can write are in How do open source projects get recommended by AI search? Six places beyond the README.
6. Check the public page with curl
Replace the slug with your project; check that the title and meta description are the sentences you wrote, and that one sentence from the description can be found with grep.
# What does the public project page say in raw HTML? curl -sL -A "Mozilla/5.0" "https://modrinth.com/mod/YOUR-SLUG" | grep -io '<title>[^<]*</title>' curl -sL -A "Mozilla/5.0" "https://modrinth.com/mod/YOUR-SLUG" | grep -io '<meta name="description"[^>]*>' curl -sL -A "Mozilla/5.0" "https://modrinth.com/mod/YOUR-SLUG" | grep -c "a sentence from your description" # The same project through Modrinth's public API (set your own User-Agent) curl -s -A "your-name/check" "https://api.modrinth.com/v2/project/YOUR-SLUG" | head -c 600
7. Ask with web search on, three times
In ChatGPT and Perplexity ask "which Minecraft mod does X", and note which mods are recommended and which URLs are cited. Whether AI cites Modrinth or CurseForge pages, we have no evidence, so it is unverified; you have to test it yourself.
If you have your own website, its structure and how to write robots.txt are in How do you write robots.txt for AI crawlers?.
How is this different from game pages like Steam and itch.io?
| Modrinth | CurseForge | Steam, itch.io | |
|---|---|---|---|
| robots.txt | Only disallows /_internal/; no AI crawler named | Unverified (403) | Neither Steam nor itch.io disallows detail pages; see the indie games guide |
| sitemap | Not found | Not verified | itch.io has one; Steam's robots.txt does not list one |
| Detail page text in the HTML | Yes (sample page) | Not verified | Steam yes; itch.io unverified |
| What you can edit | title, summary, description, categories, gallery, license | Name, summary, description, categories, images | Store description, tags, screenshots |
If you make a game rather than a mod, Steam and itch.io are covered in How do indie games get recommended by AI?.
FAQ
Does Modrinth's robots.txt block AI crawlers?
The modrinth.com/robots.txt we read on 2026-11-14 has only "User-agent: *" and "Disallow: /_internal/", names no AI crawler, and project pages are not under Disallow. This is read from the text, not verified with a real crawler.
Does Modrinth have a sitemap?
We did not find one. /sitemap.xml and two other common paths return 404, and robots.txt has no Sitemap line, so how many project pages it includes is unverified.
Can AI read CurseForge project pages?
Unverified. On 2026-11-14 we requested robots.txt, the sitemap and a project page on www.curseforge.com and got a Cloudflare challenge page each time (HTTP 403); we read no content and did not bypass it.
Where does a Modrinth summary appear?
On the sample pages the summary is the first half of the meta description (followed by a fixed download line) and also og:description. The official rules ask the summary to be an unformatted overview that does not repeat the project name.
What are CurseForge's hard requirements for descriptions?
The official text says: titles and descriptions must be in English (other languages may be added, English first), the description must say what the project adds or changes, and bad grammar or an insufficient description is rejected. No character limit is given; that is unverified.
Can I use AI-generated images in my project gallery?
Modrinth's content rules say images on the page such as the gallery, icon and description cannot be created or derived from generative AI and may be removed. CurseForge requires AI showcase images that could mislead to be disclosed. Real in-game screenshots are the safe choice.
Will ChatGPT or Perplexity cite Modrinth pages?
We found no official statement and no evidence of actual citations, so it is unverified. What we can confirm: on 2026-11-14 the sample page returned 200 to a normal request, with the description text in the HTML.
Sources
- Modrinth · robots.txt (Fetched 2026-11-14)
- Modrinth · Sample project page (used to check what the HTML contains) (Fetched 2026-11-14)
- Modrinth · API:statistics (Fetched 2026-11-14)
- Modrinth · Content Rules (Read in full 2026-11-14)
- Modrinth · Project review times (Read in full 2026-11-14)
- CurseForge · Project Submission Guide and Tips (Read in full 2026-11-14)
- CurseForge · Creating and Submitting a Project (Read in full 2026-11-14)
- CurseForge · Moderation Policies (Read in full 2026-11-14)
- kagentx evaluations: the data on the case study pages; each example gives its date.