Report Junk App Store Listing in Simplified Chinese — Messages/Mail Report Junk / Mark as Junk / 举报垃圾 / 标记垃圾 zh-Hans Copy
Your iOS or iPadOS app already markets Report Junk, report junk message, mark as junk, Mail report junk, or Messages report spam — gallery frames show the Messages swipe action, Report Junk confirmation sheet, Mail Mark as Junk button, or junk-reporting wizard — and buyers understand the benefit in English.
Open the same app on the China storefront and the product page still shows English name, subtitle, keywords, description, and screenshot captions that repeat untranslated junk-report jargon — "Report Junk", "Mark as Junk", "Report spam", or "Flag unwanted messages" in Latin script.
Shipping junk-reporting guidance or companion UX in the binary does not auto-fill a Simplified Chinese (zh-Hans) localization row.
AppLocale writes paste-ready zh-Hans listing copy for those Connect fields — aligned with what your Report Junk or mark-as-junk feature actually delivers, without claiming universal spam blocking or Messages.app replacement.
Report Junk is reporting or marking a message or email as junk/spam — not filtering unknown senders into a separate inbox, not muting one thread with Hide Alerts, not silencing unknown phone callers, not tapback reactions, not general Messages hub marketing.
Operator guidance only — no ranking promise, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie iOS and iPadOS developers — US, UK, EU, Canada, Australia — who:
Already ship or are launching an app that markets Report Junk, mark as junk, report spam message, or Mail report junk on the en-US product page
Show the Messages Report Junk swipe menu, Mark as Junk Mail toolbar action, junk-reporting confirmation sheet, spam-flag dashboards, or report-junk setup wizards in screenshot galleries and App Previews
Help users enable or complement Apple's Report Junk Messages action or Mark as Junk Mail flow — not looking for MessageUI, MailKit, or general group-chat marketing help here
Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on junk-reporting gallery frames
Need paste-ready Connect text — not an engineer to wire spam-filter extensions, not a designer to re-export every screenshot from scratch
Messages/Mail junk reporting vs zh-Hans listing copy — two different jobs
Teams assume junk-reporting capability in the binary or a companion guide covers storefront language. Xcode, Messages/Mail system actions, and Connect actually separate Report Junk behavior from product-page copy:
Report Junk (Messages conversation swipe / long-press) — system action that flags an unwanted SMS, MMS, or iMessage as junk to Apple and your carrier. Does not generate Chinese listing text.
Mark as Junk (Mail message toolbar) — system action that moves an unwanted email to Junk and trains Mail's junk filter. Separate from the zh-Hans description paragraph that explains junk-reporting value to buyers.
In-app junk-report UI — setup wizards, reported-spam lists, junk-flag dashboards, and confirmation explainers. Your listing may mention Report Junk; implementing IdentityLookup extensions or carrier spam APIs is engineering work, not listing copy.
Pricing and Availability → China — makes the app downloadable on the China App Store. Separate from language rows.
App Store tab → Chinese (Simplified) — independent row for title, subtitle, keywords, description, promotional text, screenshots, and caption lines. Empty or English here means China buyers see English fallback regardless of junk-report flags in the binary.
Working Report Junk guidance in the app or system Messages/Mail and a localized China listing are both required when you sell on the China storefront — neither replaces the other.
Report Junk listing copy is not Filter Unknown Senders, Hide Alerts, Silence Unknown Callers, general Messages, or Tapbacks
Communication and productivity apps blur several surfaces indie teams conflate. AppLocale covers listing metadata only — layer 1.
1 — App Store listing metadata (zh-Hans row)
Name, subtitle, keywords, description, plus screenshot overlay captions and App Preview text on the Simplified Chinese localization in App Store Connect. This is what buyers see before install. AppLocale's $79 deliverable is paste-ready copy for these fields — including caption lines on frames that show Report Junk menus, Mark as Junk buttons, or junk-reporting marketing art.
2 — In-app junk-report UI (not included)
Text inside setup wizards — toggle labels, reported-spam lists, junk-flag stats — comes from your app binary, String Catalog, or runtime data. Translating that requires Xcode localization, not a listing rewrite. We do not edit Messages swipe menus or Mail junk-filter code.
Filter Unknown Senders (过滤未知发件人) routes texts from people not in Contacts into a separate Unknown Senders inbox list — inbox separation, not reporting one message as junk. See Filter Unknown Senders listing guide — stranger-message filtering, not Report Junk confirmation sheets.
4 — Hide Alerts (different Messages action)
Hide Alerts (隐藏提醒) mutes notification alerts for one conversation thread — per-thread mute, not junk reporting. See Hide Alerts listing guide — quiet-thread badges, not Report Junk swipe actions.
Silence Unknown Callers (静音未知来电) is a Phone setting that sends calls from numbers not in Contacts straight to voicemail without ringing. Report Junk is a Messages or Mail action that flags unwanted texts or emails — different app, different buyer story. See Silence Unknown Callers listing guide, not here.
6 — General Messages, Tapbacks, Edit Message & Mail unsubscribe (different listing guides)
General Messages / iMessage / group chat / tapbacks / RCS marketing covers conversation threads and chat utilities — see Messages listing guide. Tapback covers long-press emoji reactions on iMessage bubbles — see Tapback listing guide. Edit Message covers edit-after-send within the edit window — see Edit Message listing guide. Mail Unsubscribe Suggestions covers one-tap unsubscribe links in Apple Mail — see Unsubscribe Suggestions listing guide. Report Junk is flagging unwanted content as junk — not group chat hero frames, not tapback reaction bubbles, not edit-after-send overlays, not unsubscribe-link marketing.
No twin slug pages — report-spam, mark-as-junk, and junk-mail belong here
AppLocale does not maintain separate twin pages for these slugs when Report Junk dominates your lead gallery:
report-spam — report-spam and report spam message search intents fold onto this page
mark-as-junk — mark-as-junk and mark junk mail marketing belongs here
junk-mail — junk-mail and Mail mark-as-junk intents fold here
spam-filter — spam-filter marketing folds here when junk reporting is the lead story — not as a separate Filter Unknown Senders twin page
report-spam-message — report-spam-message search intent belongs on this page
junk-folder — junk-folder and spam-folder marketing folds here when Report Junk or Mark as Junk dominates your gallery
Twin slugs: AppLocale does not maintain separate pages for report-spam, mark-as-junk, junk-mail, spam-filter, report-spam-message, or junk-folder URL slug variants. Only app-store-report-junk-chinese.html covers Report Junk listing copy when message or mail junk-reporting dominates your gallery.
What China buyers still see when the zh-Hans row is incomplete
When Simplified Chinese metadata is missing or falls back to English, the China storefront product page mirrors your US Report Junk marketing gaps:
English app name or subtitle — Search results and the product header show Latin script while competitors read native
Untranslated keyword field — wasted 100-character cap; China Search indexes Simplified Chinese characters like 举报垃圾 and 标记垃圾, not English "Report Junk" alone
English description — long body text that never mentions 举报垃圾邮件, 标记垃圾, or how junk reporting works before install
Report Junk screenshot captions still in English — overlay lines like "Report Junk", "Mark as Junk", "Report spam", or "Flag unwanted messages" on gallery frames targeting China buyers
Universal spam blocking overclaimed — description promises carrier-wide spam-database enforcement when your app only guides users to enable Report Junk on one message
Conflated with Filter Unknown Senders — zh-Hans copy mentions 过滤未知发件人 inbox separation when the product actually markets per-message junk reporting — confusing buyers who expect a different Messages setting
Conflated with Hide Alerts — description written for per-thread mute with one sentence mentioning Report Junk instead of naming junk-flag workflows per screenshot frame
Conflated with general Messages or tapback copy — description written for group chat or tapbacks with one sentence mentioning Report Junk instead of naming junk-report confirmation sheets per frame
App Preview voiceover or burned-in English — Connect preview text fields can be zh-Hans even when video assets still carry English; redesigning burned-in video text is outside AppLocale scope
Better zh-Hans listing copy reduces product-page bounce for users who already search in Chinese — it does not auto-enable Report Junk in Messages or translate in-app junk-report labels after install.
Common mistakes on Report Junk zh-Hans listings
Leaving "Report Junk" untranslated — Apple markets 举报垃圾 and 标记垃圾 in zh-Hans regions; English-only overlay lines on otherwise Chinese copy looks unfinished
Machine-translated "Mark as Junk" as 标记为垃圾 — awkward phrasing; align with buyer-facing terms like 举报垃圾, 标记垃圾, or 举报垃圾邮件 depending on your UX and whether Messages or Mail leads
Conflating Report Junk with Filter Unknown Senders — 举报垃圾 (flag one message as junk) is not 过滤未知发件人 (route strangers to a separate inbox) — different buyer stories per frame
Conflating with Hide Alerts — 隐藏提醒 (per-thread mute) is not 举报垃圾 (junk reporting) — different Messages actions per screenshot
Conflating with Silence Unknown Callers — Phone call filtering is not Messages or Mail junk reporting — different apps, different screenshot stories
Conflating with general Messages or tapback copy — reusing 群聊, 消息回应, or tapback vocabulary from sibling guides instead of 举报垃圾 and 标记垃圾 phrasing
Claiming universal spam blocking — metadata must match delivery; do not promise carrier-wide spam-database coverage unless your app actually ships that enforcement
Claiming Messages or Mail.app replacement — companion apps and setup guides should not imply they replace Apple's Messages or Mail apps or carrier SMS routing for all users
English-only What's New after a Report Junk launch — version notes are a separate field; base $79 focuses on evergreen listing fields unless you bundle What's New in intake
Assuming spam-filter APIs localize the store page — engineering and App Store metadata are independent workstreams
What good zh-Hans Report Junk listing copy looks like
Align tone with your en-US listing and name the junk-report surfaces buyers actually see:
Name & subtitle (30 chars each) — lead with the outcome (举报垃圾, 标记垃圾) not SDK jargon alone
Keywords (100 chars) — Simplified Chinese queries for junk reporting, Report Junk, mark as junk — weave 举报垃圾, 标记垃圾, 举报垃圾邮件, and report spam naturally; not English API names stuffed into the hidden field
Description — one clear paragraph on where Report Junk appears (Messages swipe menu, Mail Mark as Junk button, in-app junk-report wizard) and what the buyer gets — flag unwanted texts or emails, reduce spam noise
Screenshot captions — one line per frame naming the on-screen state: "滑动举报垃圾信息，减少骚扰短信" not "Report Junk" alone
Honest scope — if junk reporting requires specific OS versions, carrier support, or supported regions, say so in plain zh-Hans without Messages-replacement or universal-spam-blocking language
Report Junk screenshot captions Chinese buyers expect
Productivity, security, and business-messaging apps often dedicate one or two gallery frames to the junk-reporting story — Messages Report Junk swipe menus, Mail Mark as Junk buttons, junk-flag confirmation sheets, or spam-report dashboards. Overlay lines on those frames should name the feature in plain zh-Hans:
Messages swipe / Report Junk frame — describe the system action: "滑动选择举报垃圾，标记骚扰信息" instead of "Report Junk" alone
Mail Mark as Junk frame — name the outcome honestly: "一键标记垃圾邮件，减少收件箱骚扰" vs vague "Stay safe" when mark-as-junk is the actual deliverable
Setup wizard frame — explain the guided benefit: "几步学会举报垃圾短信与邮件" — not English-only "Report spam"
Reported-spam dashboard frame — state the peace-of-mind benefit only when shipped: "已标记的垃圾信息不再打扰主收件箱" when art shows junk-flag history
Match caption to capture — if the screenshot shows a Mail junk toolbar, the overlay should describe 标记垃圾邮件 not Messages thread UI unless art shows that context
AppLocale includes Report Junk-related overlay lines in the screenshot caption deliverable when your gallery uses them. We do not redesign or re-export PNG assets — you paste overlay text into Connect or your design tool.
Connect checklist before you order Report Junk listing copy
Open App Store → Chinese (Simplified) — confirm the zh-Hans localization row exists; adding China under Pricing and Availability alone does not fill it
Audit five text fields — name, subtitle, keywords, description, promotional text (if used) saved in zh-Hans, not placeholder English
List screenshot frames that show Report Junk UI — note which gallery images show Messages swipe menus, Mail Mark as Junk buttons, junk-report wizards, or spam-flag art so caption lines match frame order
Export current English captions — overlay text from Connect or your design spreadsheet, including any "Report Junk", "Mark as Junk", "Report spam", or "Flag unwanted messages" boilerplate
Confirm feature scope honestly — note Messages Report Junk vs Mail Mark as Junk vs in-app junk-dashboard vs spam-filter extension companion so zh-Hans copy does not overclaim universal blocking; confirm you are marketing Report Junk — not Filter Unknown Senders, not Hide Alerts, not general group chat or tapbacks
Confirm in-app UI language separately — plan Xcode string localization if junk-report labels are still English after install
Skip engineering tasks here — IdentityLookup extensions, carrier spam APIs, and Report Junk QA stay with your dev team
Paste-ready Simplified Chinese listing metadata rewritten from your English App Store copy, with Report Junk-aware phrasing:
App name — up to 30 characters on the zh-Hans row
Subtitle — up to 30 characters; visible under the name in Search
Keywords — up to 100 characters in the hidden keyword field
Description — long listing body explaining Report Junk and mark-as-junk value for China buyers
Screenshot caption lines — overlay text for frames showcasing Report Junk menus, Mark as Junk buttons, setup wizards, or junk-reporting marketing art (send frame count and current English lines)
Listing alignment — voice consistent with your en-US page; we note both sides when English also needs tightening on junk-report or spam-flag claims
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite — not a machine translation dump. Character counts verified before delivery.
What AppLocale does not do
Does not implement MessageUI, MailKit, Messages.framework, IdentityLookup, or carrier spam-reporting APIs
Does not configure Report Junk system toggles or claim Messages or Mail.app replacement in engineering work
Does not write Filter Unknown Senders or Unknown Senders inbox listing copy as lead
Does not write Hide Alerts or per-thread mute listing copy as lead
Does not write Silence Unknown Callers (Phone) listing copy — a different app setting with a different buyer story
Does not write general Messages / iMessage / group chat / tapbacks listing copy as lead — see the Messages hub guide
Does not write Edit Message, Undo Send, or Auto-Play Message Effects listing copy as lead
Does not write Mail Unsubscribe Suggestions or Mail Categories listing copy as lead
Does not localize in-app junk-report labels, setup wizard strings, or runtime spam-filter strings
Does not design or re-export screenshots — only Connect caption text you paste or hand to a designer
Does not edit App Preview video files or burn new subtitles into video assets
Does not manage Apple Search Ads, Custom Product Pages, or ad campaigns
Does not write App Review replies or ongoing ASO retainers
Does not guarantee App Store ranking, junk-report accuracy, or download growth in China or elsewhere
Does not maintain separate twin pages for report-spam, mark-as-junk, junk-mail, spam-filter, report-spam-message, or junk-folder slug variants
Is not QuantRadar, not paid ads management, and not investment or legal advice
Does not invent reviews, ratings, or traffic numbers
How it works
Confirm scope — zh-Hans listing fields plus Report Junk screenshot captions; spam-filter engineering stays on your side
Send intake — reply from the email on your Stripe receipt with your App Store listing URL, current English name/subtitle/keywords/description, screenshot caption lines (note which frames show Report Junk or Mark as Junk UI), feature scope (Messages guide vs Mail guide vs in-app junk dashboard), and target locale (zh-Hans)
Receive files — within 24 hours, paste-ready zh-Hans fields arrive at your Stripe receipt email
Paste in Connect — App Store → Chinese (Simplified) → save → submit with your next version if needed
Does localizing my listing enable Report Junk inside Messages or Mail?
No. AppLocale rewrites App Store Connect metadata — name, subtitle, keywords, description, and screenshot caption lines on your zh-Hans product page. The Report Junk swipe action in Messages, Mark as Junk in Mail, carrier spam reporting, in-app junk-flag flows, and system junk-folder routing are runtime or binary work outside AppLocale scope.
How is Report Junk listing copy different from Filter Unknown Senders, Hide Alerts, or general Messages guides?
Report Junk listing copy markets reporting or marking a specific message or email as junk or spam — the Messages swipe action or Mail Mark as Junk flow. Filter Unknown Senders routes stranger texts into a separate Unknown Senders inbox — inbox separation, not per-message junk reporting. Hide Alerts mutes notification alerts for one conversation thread. The Messages hub guide covers general chat, iMessage, group chats, tapbacks, and RCS — not Report Junk confirmation sheets as the hero. Screenshot captions should name 举报垃圾 or 标记垃圾 benefits rather than 过滤未知发件人 inbox separation, 隐藏提醒 per-thread mute, or 群聊 group chat overlays.
What character limits apply to zh-Hans Report Junk listing fields?
App name and subtitle are each up to 30 characters on the zh-Hans row. The keyword field allows up to 100 characters. Description and screenshot caption lines have longer limits but should stay concise — especially subtitle and overlay lines that must fit on-device mockups showing Messages Report Junk menus or Mail Mark as Junk buttons.
Should I claim my app replaces Messages, Mail, or blocks every spam message?
No. Listing copy should describe the junk-reporting, mark-as-junk guidance, or spam-flag workflows your app actually ships — without promising universal spam blocking, carrier-wide enforcement, or that you are the system Messages or Mail app. AppLocale rewrites from your English source claims; we do not invent junk-filtering coverage your binary does not support.
What do I send after AppLocale payment?
Your live App Store listing URL, current English (or partial zh-Hans) name, subtitle, keywords, description, screenshot overlay lines with frame order noted, which frames show Report Junk or Mark as Junk UI, and feature scope (Messages guide vs Mail guide vs in-app junk dashboard). Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.
Does AppLocale implement MessageUI, MailKit, or spam-filtering APIs?
No. We rewrite Connect listing copy only. MessageUI compose sheets, Messages.framework, MailKit, IdentityLookup message-filter extensions, carrier spam reporting, and Report Junk system-action behavior are engineering tasks we do not perform.
Does AppLocale sell separate report-spam, mark-as-junk, or junk-mail twin listing pages?
No. AppLocale does not maintain separate twin listing pages for report-spam, mark-as-junk, junk-mail, spam-filter, report-spam-message, or junk-folder slug variants. Those search intents fold onto this Report Junk page when message or mail junk-reporting dominates your gallery.
Will zh-Hans copy mentioning Report Junk improve China rankings?
We do not guarantee ranking, browse placement, or download lift. Complete zh-Hans metadata helps users who already find your page understand junk-reporting value in their language — it is not a placement hack.
How much does AppLocale cost?
$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.
What is AppLocale not?
Not Filter Unknown Senders or Unknown Senders inbox listing copy, not Silence Unknown Callers or Phone call-filter listing copy, not Hide Alerts or per-thread mute listing copy, not general Messages / iMessage / group chat / tapbacks listing copy as lead, not Edit Message or Auto-Play Message Effects listing copy, not Mail Unsubscribe Suggestions listing copy as lead, not MessageUI, MailKit, or Messages.framework engineering, not screenshot image design, not in-app string localization, not Apple Search Ads management, not ranking guarantees, not QuantRadar, and not investment or legal advice. We do not invent reviews, ratings, or traffic numbers.
Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL and English listing copy. No ranking guarantees. Sold by Fortune Insight, LLC.