Is the Unity Asset Store open to crawlers?
Yes, with a very complete sitemap, and no AI crawlers are named. On 2026-11-14 we tested assetstore.unity.com with curl (User-Agent Mozilla/5.0):
| Check | Test result |
|---|---|
| robots.txt | 200, 336 bytes: the * group only disallows /users/, /health, /beta, /?q=*, /lists/, /cms/, /mega-bundles-preview/, /unseen-assets, /auth/; two Sitemap lines |
| sitemap.xml | 200, 3,341 bytes, an index with 20 child sitemaps (all with lastmod 2026-11-14); fetched in full they hold 145,339 URLs: 128,628 /packages/, 16,504 /publishers/, 207 others |
| unity3d-sitemap.xml | 200, 3,815,352 bytes, 20,000 URLs in the old site format (www.assetstore.unity3d.com/en/#!/content/<number>), all with lastmod 2020-04-08, and a header comment saying it was generated by Screaming Frog SEO Spider 12.6 |
So once your asset page is approved and live, it goes into the current sitemap; the second sitemap listed in robots.txt is an old file from 2020 and has nothing to do with your asset page. For the names and purposes of the AI crawlers see AI crawler user agents: a side-by-side table.
What is in the HTML of an asset page?
A title, a template meta description and structured data, but the publisher's long description is not in the visible markup. We fetched three asset pages; below are the results for the HD Development- Inventory System page (assetstore.unity.com/packages/templates/systems/hd-development-inventory-system-215370, 2026-11-14, curl, no scripts run):
| Check | Test result |
|---|---|
| HTTP status and size | 200, 425,188 bytes |
| title | “HD Development- Inventory System | Systems | Unity Asset Store” |
| meta description | A platform-generated template sentence: Use … from … to elevate your next project. Find this & more Systems and templates on the Unity Asset Store.; the other two pages have template sentences of the same kind with different wording |
| canonical and og tags | canonical present; og:title, og:description, og:image and og:type present |
| JSON-LD | Two blocks: Product (name, image, description, brand, reviews) and BreadcrumbList |
| Visible text (scripts removed) | 2,734 characters (2,051 and 2,276 on the other two pages): name, publisher, price, version, release date, file size, render pipeline compatibility table, keyword tags |
| The publisher's long description | Not in the visible markup; it is in the JSON data inside the page's script (we saw the original description text on the fx-simple-ice-pack1 page) |
This means a crawler that does not run scripts can reliably read your asset name, publisher, category and keyword tags, but cannot read the feature list and technical parameters in the long description. For whether crawlers run scripts see Do AI crawlers render JavaScript?; whether real search crawlers read the data inside the script is unverified. For how to write titles and descriptions see Do title and meta description matter for AI search?; for Product structured data see Should a SaaS add SoftwareApplication structured data?.
What does Unity officially specify for an asset's title, description and images?
The clauses of the official Submission Guidelines (assetstore.unity.com/publishing/submission-guidelines, page marked updated 2026-10-23, original text read 2026-11-14) that relate to the listing page:
| Clause | What the vendor says (summary) |
|---|---|
| 1.1.d Text quality | The title, description, keywords, folders, scripts and documentation must not contain an excessive amount of spelling or grammatical mistakes; the text must be readable and reasonably understandable |
| 3.1.a Description content | The description must accurately cover all important aspects or key features of the product, including dependencies, intended functionality and requirements for use; limitations that affect usability must be stated transparently |
| 3.1.b Art assets | List the number of unique assets or asset types and give technical details: audio sample rate, track length, bit depth, 3D model polygon count, texture or sprite dimensions, supported render pipelines, texture map types |
| 3.1.c Several editions | If there are several editions such as lite/pro, compare the features in the description, technical details or images as a list or summary |
| 1.5.c Third-party APIs | A package that uses third-party APIs must state the API terms of use and any additional costs at the very top of the listing description, and also in the documentation |
| 1.1.f Demos | 3D, 2D, VFX, Animation and Template categories need demo scenes; Tools that manipulate external assets need sample assets |
| 2.3.c Video | Video documentation or tutorials are not packaged; they may be hosted on online services such as YouTube or Vimeo |
| 1.6.a–d AI | If AI was used, disclose it plainly in the “AI description” field; do not use words that imply human effort such as “drawn” or “painted”; marketing material must truthfully reflect the package's main content; packages mass-produced with AI may be rejected |
| 4.1.a Publisher | Must have a working email and an actively maintained website showing relevant work |
| 1.1.e Size | A submission must not exceed 6GB; one distributed through UPM must not exceed 700MB |
This page does not specify character limits for the title and description, how many keywords are allowed, or pixel sizes for images and icons; these may be in the help documentation of the Publisher Portal, which we did not read: unverified. The vendor also does not say how these fields affect on-site search or AI citation, and we have no evidence.
How do you make a Unity asset easier to find, step by step?
1. Write the name as “what it is + what it does”
For example “Inventory System” or “Ice VFX Pack”, not just a brand name; the name goes into the URL and is the start of the title.
2. Write the description in the order of vendor clause 3.1
First one sentence on what it does, then the counts and technical details (polygon count, texture sizes, supported render pipelines, supported Unity versions), and a comparison table if there are several editions. Because the long description sits only in script data, this paragraph has to stand on its own.
3. Choose keywords that really apply
Use the words that show up as tags on the asset page, written the way users would search; run a spell check (vendor clause 1.1.d).
4. Disclose AI use truthfully
State the tools and content in the AI description field, and avoid words like “hand drawn” (vendor clauses 1.6.a and 1.6.c).
5. Write a full introduction page on your site
For crawlers that do not run scripts, the asset page has only the name, tags and the template snippet. On your site, spell out the features, supported Unity versions and render pipelines, and the changelog, and link to the Asset Store page; vendor clause 4.1.a also requires publishers to have an actively maintained website.
6. Test again after a few weeks with the same questions
Ask ChatGPT and Perplexity “is there a Unity asset that does such-and-such”, ask each question 3 times, and note whether you are mentioned and which URLs are cited.
If you make the game itself, see How do indie games get recommended by AI?; if you sell on platforms like Gumroad, see How do digital products sold on Gumroad and Lemon Squeezy get recommended by AI?. Comparable store guides: How do AI search tools find Figma plugins? The Community plugin page's robots.txt, sitemap and Figma's requirements, How do AI search tools find Atlassian Marketplace apps? App pages tested, plus the vendor's requirements.
FAQ
Does the Unity Asset Store robots.txt block AI crawlers?
No crawlers are named. The robots.txt tested on 2026-11-14 is 336 bytes: User-agent: * only disallows /users/, /lists/, /cms/, /auth/, /?q=* and a few others; it does not disallow /packages/, and names no AI crawler.
Does the Asset Store have a sitemap? How many asset pages?
Yes. /sitemap.xml is an index with 20 child sitemaps, all with lastmod 2026-11-14; fetched in full they hold 145,339 URLs, of which 128,628 are /packages/ asset pages and 16,504 are /publishers/ publisher pages.
Why does robots.txt also list unity3d-sitemap.xml?
It is an old file: 20,000 URLs, all in the old site format www.assetstore.unity3d.com/en/#!/content/<number>, with lastmod 2020-04-08. It does not affect your asset page, but it shows that the second sitemap in robots.txt is not current.
Is the asset page's meta description the description I wrote?
No. In our test, the meta descriptions of three asset pages were all template sentences the platform builds from the name, publisher and category, for example “Use … from … to elevate your next project. Find this & more Systems and templates on the Unity Asset Store.”. The long description you write is in the JSON data inside the page's script, not in the visible markup.
What can a crawler that does not run scripts read on an asset page?
It can read the title, the template meta description, canonical, og tags, the Product and BreadcrumbList JSON-LD, and about 2,000–2,700 visible characters with scripts removed: name, publisher, price, version, file size, the render pipeline compatibility table and keyword tags. The publisher's long description requires reading script data; whether real crawlers do so is unverified.
What does the vendor require of the description?
Submission Guidelines (updated 2026-10-23) 3.1.a: the description must accurately cover the key features, dependencies and requirements for use; 3.1.b: art assets must state counts and technical details such as polygon count, texture sizes and supported render pipelines; 3.1.c: several editions must be compared by feature; 1.5.c: packages using third-party APIs must put the terms and additional costs at the top of the description.
How do I write about content generated with AI?
Vendor clause 1.6.a requires stating, in plain words in the “AI description” field, which AI tools were used and what was generated; 1.6.c forbids words that imply human effort such as “drawn”, “hand drawn” and “painted”; 1.6.d says submissions mass-produced with AI and without clear differentiation may be rejected.
Are there rules for title length, number of keywords and image sizes?
Not on this page of the Submission Guidelines. It only says that spelling and grammar must not have an excessive number of mistakes (1.1.d). Specific character counts and pixel sizes may be in the help documentation of the Publisher Portal, which we did not read: unverified.
Sources
- Unity · assetstore.unity.com: robots.txt, sitemap index and child sitemaps, three asset pages (Read 2026-11-14)
- Unity · Asset Store Submission Guidelines (2026-11-14 original text read; the page is marked last updated 2026-10-23)
- kagentx evaluations: the data on the case study pages; each example gives its date.