Publishing
Listing Best Practices
Write accurate app and workflow descriptions with useful screenshots, requirements and support details.
Updated · Guide version 1.0
Read as MarkdownA useful listing helps a visitor decide whether the product fits their task. Describe available functionality and show the actual application. The suggestions here are editorial recommendations, not mandatory upload rules or measured conversion claims.
Lead with a direct answer
Begin with what the product does and who it is for. For example: “Example Planner organizes tasks for individual freelancers on Windows. It needs an account with the developer's service.” This is an illustrative description, not an actual Theaimart listing.
Explain requirements and limitations
| Visitor question | Information to supply |
|---|---|
| What problem does it solve? | A concrete task and expected result |
| Where can I run it? | Tested operating systems or workflow platform and version |
| What must I configure? | Accounts, credentials, dependencies and required permissions |
| What is included? | Available features and any paid restrictions |
| What does it cost? | The listing price and separate external service costs, when applicable |
| What can it not do? | Known limits, supported input formats and failure cases |
| Where do I get help? | Support contact and the developer's privacy policy |
Do not claim Theaimart guarantees safety or results. Do not describe a roadmap item as a shipped feature. Attribute performance claims to a dated, reproducible test with the environment, inputs and comparison method.
Use clear names and descriptions
Use the actual product name, followed by a concise description of its function if helpful. Avoid repeated keywords, invented popularity, competitor endorsements and unsupported ratings. Choose the category that best matches the product. There is no documented keyword-density rule or guaranteed position in the catalog.
Show the product honestly
Use a legible icon and screenshots of the current interface. Recommendations such as square icons or several screenshots help presentation, but this guide does not invent minimum screenshot requirements. Remove API keys, private customer data and notification contents. If you include an illustrative mockup, label it clearly.
For a workflow, include an import example and configuration instructions. Use synthetic inputs and explain the expected output. Keep downloads and launch URLs current.
Check the visitor's next step
- •Test the download, launch URL or workflow import.
- •Confirm the stated platform and version match what you tested.
- •Make pricing and prerequisites easy to find.
- •Open support and privacy links in a signed-out browser.
- •Preview your listing on a mobile screen.
Related guides
Start with Getting Started, then read the appropriate guide for native apps, web apps or agent workflows. Contact support when the live form differs from these guides.