CONTENT STANDARDS
What we publish, what we index, and how we maintain it
Mine Mod AI is a working Minecraft creation tool first. Public pages exist to explain the product, document supported formats and show reproducible examples — not to manufacture search pages around every possible keyword variation.
Last editorial review: October 14, 2026
1. Flagship maker pages are written and maintained as product documentation
Our searchable maker hub contains the hand-written flagship set: pages for concrete creation workflows such as datapacks, Bedrock add-ons, custom items and supported minigame maps. A flagship page needs a specific explanation of what the generator does, real example prompts, installation steps, limitations, FAQs and current generated-pack evidence.
We may generate additional long-tail product routes for experimentation or direct navigation, but those variations are not automatically promoted into the sitemap or the crawlable maker hub.
2. Standalone mod examples use a smaller reviewed showcase
The interactive gallery can contain many examples because it is a product-browsing surface. Search-facing detail pages use a much smaller selection. To qualify for that reviewed set, an example must have a clear description, a real prompt, a current cover or visual context, and generated evidence showing an actual supported pack with an inspectable file inventory.
Removing an example from the reviewed set does not delete the product example; it simply stops treating that route as a standalone search landing page until it deserves that treatment again.
3. Generated evidence is not the same as claiming every pack was played manually
We distinguish structural validation from runtime gameplay testing. Build-time evidence checks that a supported prompt still routes to an engine and produces the expected pack format and files. Representative runtime tests cover supported categories, but we do not claim that every possible generated pack has been manually played on every Minecraft version or device.
The current validation approach and its limits are documented on the validation methodology page.
4. Guides must answer a real user task
Guides are kept when they help a reader understand pack formats, installation, compatibility, safe testing or a concrete creation workflow. We do not publish filler articles whose only purpose is to repeat a search phrase. Guide update dates are stored with the guide content and are included in the sitemap when available.
5. Maintenance means shrinking the site when quality falls
A growing URL count is not a quality metric. If a page becomes stale, loses working evidence, duplicates a stronger page or no longer represents the product accurately, it should be noindexed, removed from the crawlable hubs, or removed from the sitemap until it is repaired.