What to Do When Review Is Rejected: High-Frequency Rejection Reasons and Fixes
Search for "mini program review rejected," and you'll mostly find two paths: hiring an agency that "guarantees approval," or resubmitting as-is and hoping for luck. Both are wrong.
WeChat has written the scenarios that get rejected into official documents: "WeChat Mini Program Platform Common Rejection Scenarios" and "WeChat Mini Program Platform Operation Specifications" — almost every reason in a rejection notice can be matched to one of them. Once matched, you know what to change, how to change it, and how to resubmit after fixing it.
This is Lesson 5 of Route B (building a mini program), and also Route B's "first aid kit": B4 teaches you to self-check before submitting and avoid rejection as much as possible; this lesson deals with rejections that have already happened — reading the reasons, fixing them one by one, resubmitting, and when to appeal.
What You'll Be Able to Do After This Lesson
- Find the complete review reason returned by WeChat in the WorkBuddy sharing panel or in WeChat's "Service Notifications"
- Match the rejection reason to its category: six major categories of high-frequency rejection reasons, each with the cause and a fix
- Distinguish between "rejected for violation" and "procedural send-back" — mini programs that require a test account will always be sent back on the first submission
- After fixing, first release an experience version for real-device verification, then resubmit the official version — don't waste review attempts
- Understand the penalty ladder and the boundaries of appeals, and know why you must never fight the review process
⏳ First-pass triage: a 60-second quick check
After being rejected, don't rush to make changes — spend 60 seconds getting four things clear:
| # | Question | Answer and Action |
|---|---|---|
| 1 | Where can I see the complete reason? | The WorkBuddy sharing panel will show the complete review reason returned by WeChat, and WeChat's "Service Notifications" will also send review message reminders |
| 2 | Which category does it fall under? | Match it against the six categories below (basic info / category and features / content red lines / payment / completeness / privacy) to find the clause and the fix |
| 3 | Is it a procedural send-back? | When a mini program needs a test account to complete the review experience, the first review submission will be sent back, and only when submitting again does the entry for providing a test account open — this is not a violation; just add the test account and resubmit |
| 4 | Can I submit for review right after fixing? | No. First release an experience version and complete real-device verification; only after confirming the features and content are correct, resubmit the official version for review |
💡 Review attempts are a scarce resource
Under the WorkBuddy hosted path, each WeChat mini program can submit 3 official version reviews per week, and no new official version update can be submitted while a review is in progress (remaining attempts are as shown on the panel). The official public platform path has no such panel counter: only one version can be under review at a time, and once a review result comes back, you can resubmit directly and overwrite the version under review. What both paths have in common: the official reminder that "too many failed reviews may affect subsequent timing" — fix first, then submit; don't rely on luck.
🔧 Troubleshooting Common Issues
The reason categories below come from the official "WeChat Mini Program Platform Common Rejection Scenarios," and the fixes were compiled against the operation specifications and the WorkBuddy publishing documentation. The examples continue with B3's "Reading List."
Rejected over basic account information
"Name, description, or logo contains commercial language or terms banned by advertising law"
Reason: The official rules state that the name, description, logo, etc. must not contain commercial language (official examples: "free buffet," "women's clothing super cheap," "brand-name bags clearance"), must not contain terms banned by the new advertising law such as "national-level" or "top-level," must not pile up search hot words unrelated to the features, and must not use brands or trademarks that don't belong to you, or ride on the WeChat brand (e.g., "WeChat Assistant").
Fix:
- Log in to the WeChat public platform mini program admin console and change the name, description, and logo
- Make the name clearly state "what you do," and list the specific feature points in the description
- Also check the in-app copy for the same kind of words — AI-generated pages love to write "free" and "limited time"; for how to modify them in the app, see B3
"The mini program description must clearly introduce the mini program's feature points and must not use vague wording"
Reason: The official text specifically calls out expressions like "aimed at improving users' quality of life" as unacceptable; the name and description must be related and consistent with each other, and consistent with the features actually provided.
Fix: Write the core features into the description. For the Reading List, write "WeChat login, add books you're reading or have finished, record your book list in the cloud," not "elevate your reading taste."
"When the mini program avatar logo is not clear enough, it will not be approved"
Reason: It will not be approved when the text, objects, shapes, and other elements in the image cannot be clearly seen, distinguished, or identified; the logo should be consistent with the name and description, must not contain official brand marks of Tencent, WeChat, etc.; when using a white background, a colored border is required.
Fix: Replace it with a high-resolution logo whose content echoes the name; don't use WeChat official marks as the avatar.
Rejected over category and features
"The mini program's category must match the services it provides"
Reason: The core content of the category's corresponding page must match that category, and users must be able to use the service directly on that page; it must not be hidden and must not involve multiple redirects; a category link that won't open, loads illegal information, or shows malicious ads will also be rejected.
Fix:
- Check each page against the category you selected to confirm it really provides that service
- Don't use a "bait-and-switch" category to drive traffic — if you selected the "housekeeping" category, the corresponding page must be a housekeeping service
- Once the game category is selected, it cannot be changed to another category — think it through before choosing a category
"All service category features must be reflected on the mini program's home page"
Reason: The official requirement is that the home page must reach all submitted service category pages directly, or within 2 clicks. Features inconsistent with the description, or providing services the platform has not yet opened, will also be rejected.
Fix: Put the entry point for each category's feature on the home page or a second-level page, not buried behind three layers of redirects. AI-generated apps tend to pile features into a "More" page — click through each one before submitting for review to confirm.
"The mini program's features should have practical value and must not be overly simple"
Reason: Official examples: a Mini Program with only one page and one button will be rejected; being severely homogeneous with other Mini Programs is also not allowed.
Solution: Add real functionality to the Mini Program before resubmitting for review. A toy app like "tap to change background color" won't pass no matter how you rename it.
"Web pages embedded in the Mini Program must have completed filing procedures"
Reason: Per the operation specifications, web pages embedded in a Mini Program (web-view) must have completed filing procedures, and the services provided must be consistent with the selected category.
Solution: Complete the filing for embedded web pages before submitting for review; if the web page content doesn't match the selected category, either change the category or replace the web page content.
Rejected for content red lines
"Contains inducement behaviors, including but not limited to inducing shares, adds, follows, and downloads"
Reason: Requiring users to share, add, follow, or download before they can use a feature; pages containing text, images, buttons, floating layers, or pop-ups that explicitly or implicitly prompt sharing; or luring users to share with benefits or exaggerated language — all will be rejected. The operation specifications also explicitly state: for team-up or group-forming share campaigns, if the total number of participants per sharer is not limited to within 5 people, it is a violation.
Fix:
- Remove features and copy like "unlock after sharing" or "invite 3 friends to use"
- For team-up or group-forming share campaigns, limit the total number of participants to within 5 people
- For AI-generated pages, focus on checking pop-ups, floating layers, and button copy — inducement-style wording is a common leftover
"The page content of the Mini Program must not contain test-type content; examples: fortune-telling, drawing lots, horoscope readings"
Reason: The official examples explicitly name fortune-telling, drawing lots, and horoscope readings; the operation specifications also list "portrait scoring, AI fortune-telling" as clear violations, and require calling the content security detection API to check whether text and images contain sensitive content (UGC, test, and lottery features are key inspection targets).
Solution: Take down fortune-telling, lot-drawing, and horoscope pages; if there is user-generated content or a lottery feature, integrate the content security detection API.
"Primarily for marketing or advertising purposes (e.g., containing blank ad slots, merchant-recruitment ads, etc.)"
Reason: Floating or overlay ads, ad display proportion on feature pages exceeding 50%, ads covering features — all will be rejected.
Solution: Remove blank ad slots and floating ads, and don't let ads cover features. AI-generated pages often leave "ad slot for rent" placeholder blocks — delete them all before submitting for review.
Rejected for payment and virtual goods
"Virtual goods not integrated with Mini Program virtual payment, guiding users to complete payment in an App, Official Account, or H5 page"
Reason: Virtual goods within a Mini Program — virtual tokens, feature unlocks, subscription content, tips, etc. — must be integrated with Mini Program virtual payment. The operation specifications explicitly state "users must not be guided to complete payment in an app, Official Account, h5 page, personal account, or website"; violations on the iOS side will trigger escalating bans on iOS payment APIs, search, and opening.
Fix:
- For virtual tokens, unlocks, subscriptions, and tipping goods, integrate Mini Program virtual payment
- Remove guiding copy and buttons like "add me on WeChat to pay" or "jump to a web page to pay"
Rejected for completeness and test accounts
"The submitted Mini Program must be a finished product: it must open, run, and must not be a test version"
Reason: Not runnable, crashing, force-closing, unresponsive buttons, or incomplete text will all lead to rejection; a Mini Program that crashes the WeChat client or has severe bugs (cannot be added or opened, cannot go back or exit, severe lag) is likewise rejected.
Fix:
- Tap through every page before submitting for review: it opens, you can go back, buttons respond
- Don't leave "TODO", "in testing", or "coming soon" in the copy — common leftovers on AI-generated pages
- Walk through the entire core flow on a real device before submitting
"If the Mini Program has an account system, a test account must be provided"
Reason: The test account must include an account name and password, ensuring reviewers can experience all features; when there are paid or restricted features (visible only after topping up, members-only), the test account must be able to fully present and experience those features. Official mechanism: for Mini Programs that require a test account to complete the review experience, the first submission will be rejected, and the entrance for providing a test account will open on the second submission.
Fix:
- Prepare a test account: it can log in, experience all features, and restricted features must also be viewable
- Don't panic if the first submission is rejected — this is by design; fill the test account into the entrance on the second submission
- Configure feature pages in the submission form: categories and tags for important business pages, with no more than 5 groups
Rejected for privacy and data security
"Collecting and using user data without explicit notification and user consent"
Reason: Collecting and using any user data (geolocation, contacts, phone number, etc.) requires explicitly informing users of the purpose, obtaining their explicit consent and authorization, and using it reasonably within the authorized scope; relevant data should be deleted after the user deletes their account. You must not require users to enter personal information such as a phone number to use features; after a user refuses authorization, you must not stop all services, and developers are obligated to delete and stop using that user's WeChat avatar, nickname, and other data.
Fix:
- Sort out exactly what data the Mini Program collects, and state the purpose of each item clearly
- Cut the "no phone number authorization, no usage" design — provide basic features before asking for authorization
- After a user refuses authorization, basic services remain available as usual
"User privacy protection guide incompletely filled in"
Reason: Before the first official release, the Mini Program filing, the user privacy protection guide, and the UGC information security declaration must be completed; an incompletely filled privacy protection guide may cause the review to fail.
Solution: Go back to B4 step 2 and check the three settings — the privacy guide must cover the actual types of information processed, the purposes of collection, how changes are notified, and the developer's contact phone number and email.
⚠️ Penalty ladder, appeals, and hard red lines
For most rejections, fixing the issues and resubmitting is the end of it. But repeated violations, or touching a hard red line, means facing more than "one more fix":
Penalty ladder (each violation type has its corresponding clauses):
| Ladder | Penalty |
|---|---|
| 1 | Restrict capabilities such as pages and sharing |
| 2 | Restrict features |
| 3 | Take down |
| 4 | Ban the account |
Other red lines named in the operation specifications include: multi-level distribution, fake traffic, money-making schemes, and inducing app downloads — each corresponding to different penalty clauses. A concrete example: a first offense of paid voting requires rectification within 3 days; failure to rectify results in banning the "Mini Program payment" feature.
Appeal: The official wording — violations may be based on mistakes, negligence, or other faults; after a Mini Program is penalized, Tencent may provide an appeal channel, and you can rectify the Mini Program and resubmit it to Tencent for release review through the appeal channel. However, if it still does not meet the requirements after multiple rounds of rectification, Tencent has the right to temporarily or permanently close your Mini Program's appeal channel depending on the circumstances.@@I18N_KEEP_000008@@
Hard red line: opposing the review. The official rule states: the version of the Mini Program submitted for review should be identical to the version actually released and operated online. Showing different content to different users, forging qualifications, or hiding test content to bypass review all count as "circumventing, evading, or opposing platform review" — if adversarial behavior by Mini Programs under the same entity and related entities exceeds 1 time (≥2), penalties accumulate on the same ladder, up to permanent takedown and refusal of further service; if the same entity or its related entities violate the rules repeatedly, Tencent has the right to no longer provide an appeal channel.
In one sentence: review issues can be rectified, but never cheated. Keeping the submitted version identical to the online version is the only correct approach.
💡 Still not working?
- Can't understand the reason: Send the original rejection reason text from the notice, along with the corresponding clause on this page, directly to your AI tool (WorkBuddy chat or Claude Code), and have it locate the corresponding pages and copy to fix — handling review reasons follows the same loop as handling errors; see the error loop
- Still failing after multiple rounds of fixes: First confirm you haven't crossed any red lines (a mismatch between the submitted version and the live version is the most hidden one); then go through "Common Rejection Scenarios on the WeChat Mini Program Platform" item by item for a full self-check, focusing on the clauses not covered in detail on this page
- Disagreeing with a penalty: Use the appeal channel (see the previous section); note that the appeal channel itself may also be closed, so don't treat appeals as a routine way to resubmit
Next Lesson Preview
Route B ends here: from choosing a mini program, registering an account, generating with WorkBuddy, submitting for review, to fixing rejections, you can now independently take a mini program from idea to launch. The next lesson starts Route C (browser extensions): C1 What Is a Browser Extension: If You Can Build Web Pages, You Can Build Extensions, where you will learn:
- What browser extensions can do: Actions, Side Panels, intercepting requests, injecting scripts
- Why knowing web development (HTML/CSS/JS) means you can build extensions
- How to follow the official Chrome tutorial with AI
- Three compliance prerequisites for publishing to the app store
Want to preview another review system first? The Chrome Web Store's review and publishing strategy is covered in C7 Store Review and Publishing Strategy. For the route overview, go back to 4.0 Hands-On Scenarios.