Safari Web Extension App Store Listing in Simplified Chinese — zh-Hans Extension Product Page for China
You shipped a Safari Web Extension or Safari App Extension through the App Store, localized the companion iOS or Mac app in zh-Hans, and opened the extension product page on the China storefront — still English name, English subtitle, or toolbar and popup screenshots with Latin overlay lines.
Safari extensions on the App Store are a separate listing surface in App Store Connect. The companion app's zh-Hans row does not backfill extension metadata, screenshot captions, or promotional text.
AppLocale writes paste-ready Simplified Chinese extension listing copy aligned with your companion app voice — not extension engineering, not WebKit debugging, not in-popup UI localization.
Operator guidance only — no install guarantee, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie developers — US, UK, EU, Canada, Australia — who:
Distribute a Safari Web Extension or legacy Safari App Extension through the App Store alongside an iOS, iPad, or Mac companion app
Target the China App Store or zh-Hans device language for that extension listing
Already have a zh-Hans row on the companion app (or are finishing one) but left the extension product page in English or machine translation
Need paste-ready Connect metadata — not an engineer to rewrite content scripts, manifest permissions, or WebKit handlers
If your lead feature is a Safari Content Blocker — block-list rules under Settings → Safari → Content Blockers, 内容拦截器 / 广告拦截 — see Safari Content Blockers listing (zh-Hans) when Content Blocker API ad blocking is your hero — not general Safari Web Extension toolbar copy (this page may mention 广告拦截 as one keyword example but does not co-hero Content Blockers in title or H1). If your companion app product page is still English on the China storefront, start with China App Store still shows English or the AppLocale product page for default listing fields first. Extension listing copy sits alongside a localized companion app — it does not replace it.
Companion app listing ≠ Safari extension listing
Teams conflate two product pages when planning a China launch with a Safari extension. Each has its own Connect editor, localization dropdown, and screenshot gallery.
1 — Companion app (iOS, iPad, or Mac)
The full app users install to manage settings, sync data, or unlock premium features. Name, subtitle, keywords, description, promotional text, What's New, and screenshots on the zh-Hans localization row for that app target. AppLocale's core $79 deliverable covers these fields for one listing. See the AppLocale product page.
2 — Safari extension (App Store product page)
The extension users enable in Safari Settings after installing the companion app. App Store Connect stores a separate product page for the extension target: its own name, subtitle, keywords, description, promotional text, and screenshot sets — including frames that show the toolbar icon, popup panel, context menu, and permission prompts. Filling zh-Hans on the companion app row does not propagate here.
3 — In-extension UI (inside the popup and options pages)
Button labels, settings toggles, and error strings inside the extension popup or background UI are binary localization — Xcode string catalogs, localized HTML, or extension resource bundles. AppLocale does not rewrite those strings. This page covers the App Store product page only.
What China users see on an English extension listing
A buyer in China who searches for a Safari ad blocker, password helper, or productivity extension may land on a product page that still reads Latin script while your companion app page looks native. Common failure modes:
English extension name on a zh-Hans companion app — the full app says one thing in Search; the extension page says another when users browse extensions in Safari or the App Store
Generic English subtitle — "Enhance your browsing" instead of a concrete outcome in Simplified Chinese
Toolbar screenshot with English overlay — popup panel captioned "Block ads instantly" on every frame while title and subtitle are zh-Hans
Permission-flow frames left in English — screenshots showing Safari permission dialogs with English headline overlays explaining why the extension needs access
Machine-translated description — 翻译腔 paragraphs that do not match the tone of your companion app's zh-Hans listing
Mac-only extension screenshots untranslated — iPhone companion gallery done but Mac extension screenshot set still English when buyers browse on Mac hardware; see iPad, Mac & Watch screenshot captions
Keywords copied from the companion app — extension-specific search terms (广告拦截, 密码管理, 网页翻译) missing from the extension's hidden keyword row
Better zh-Hans extension listing copy reduces friction when users evaluate whether to install and enable your extension — it does not replace in-popup UI localization, Safari review decisions, or Apple's extension permission UX.
Extension screenshot captions are a separate craft
Safari extension listings lean heavily on toolbar and popup screenshots — small UI surfaces with tight caption budgets. Generic phone-app screenshot copy rarely fits a 390×844 frame showing a browser toolbar icon and a narrow popup panel.
Toolbar context — captions should name what the icon does in one line, not repeat the full app marketing tagline
Popup panel — outcome-first phrasing for the action visible in the capture (save page, translate selection, fill password)
Permission prompt frames — explain the user benefit in zh-Hans overlay text; the system dialog itself stays in the user's device language
Before/after browsing — comparison frames need parallel zh-Hans labels on both sides, not English "Before" / "After"
Mac vs iPhone extension sets — desktop Safari toolbar layouts differ; caption lines written for phone captures may need rephrasing for Mac frames
Apple Connect field limits (extension listing text)
Safari extension product pages use the same core listing field caps as other App Store apps on the zh-Hans row. CJK characters count toward the same limits as Latin letters — plan shorter Chinese phrasing than English drafts.
App name (title) — up to ~30 characters; should signal extension function, not only the companion app brand
Subtitle — up to ~30 characters; one fact the title does not repeat — what Safari users get after enabling
Keywords — up to ~100 characters; extension-specific search terms separate from companion app keywords
Description — long listing body explaining enable steps, Safari Settings path, and sync with the companion app
Promotional text — up to 170 characters; updatable without a new binary when you ship extension feature updates
Screenshot overlay captions — per-frame text on toolbar, popup, and permission-flow captures
Safari Web Extensions require users to enable the extension in Safari Settings after install — strong zh-Hans description copy should mention that flow in plain language without sounding like a support ticket.
What good zh-Hans Safari extension listing copy looks like
Extension product pages compete for attention in a niche category. Strong Chinese copy states browser context and outcome in plain language, aligned with your companion app listing:
Name (30 chars) — extension function visible in Safari: "网页广告拦截" not "欢迎使用我们的浏览器扩展"
Subtitle (30 chars) — one crisp outcome after enabling in Safari Settings
Keywords — extension-category terms your companion app title does not already carry; no duplicate stuffing across visible fields
Description opening — what the extension does in Safari, how to enable it, and how it connects to the companion app — before feature bullet dumps
Toolbar caption lines — short zh-Hans overlays matching the popup UI visible in each screenshot frame
Voice match — same 你/您 habits and punctuation as your companion app's zh-Hans listing
Connect checklist before you order copy
Open the extension target in Connect — not only the companion app → App Store tab → Chinese (Simplified) on the extension product page
Audit name, subtitle, keywords, description — saved in zh-Hans, not placeholder English copied from en-US
Review extension screenshot sets — toolbar, popup, and permission frames; note which overlay lines are still English
Check Mac extension gallery separately — if you distribute on macOS, Mac screenshot slots need their own zh-Hans captions
Confirm promotional text — empty or English while description is Chinese is a common half-done row
Compare voice to companion app — extension page should read like the same product family, not a machine-translated fork
Do not conflate with App Clips — App Clip card metadata is a different Connect surface; see App Clip card copy (zh-Hans) only if you also ship an App Clip
What AppLocale delivers
For one Safari extension App Store product page, paste-ready Simplified Chinese listing metadata rewritten from your English extension copy:
App name — up to ~30 characters for the extension listing title
Subtitle — up to ~30 characters for the secondary line
Keywords — comma-separated zh-Hans block with rationale notes; extension-specific terms separated from companion app duplicates
Description — long listing body rewritten for Chinese skim readers, including enable-in-Safari guidance where relevant
Promotional text — 170-character zh-Hans field updatable without a new binary
Screenshot overlay / caption lines — paste-ready zh-Hans text for toolbar, popup, and permission-flow frames you specify in intake
Companion app alignment — phrasing consistent with your existing zh-Hans companion listing (send both URLs with intake)
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite from your extension listing brief — not a machine translation dump. Character counts verified before delivery so fields fit Connect caps.
What AppLocale does not do
Does not build, compile, debug, or upload Safari Web Extensions or Safari App Extension binaries
Does not edit manifest.json, content scripts, background service workers, or WebKit entitlements
Does not localize in-extension popup HTML, options panel strings, or extension resource bundles
Does not configure Safari extension permissions, associated domains, or native messaging handlers
Does not design or re-export screenshot images — caption lines only
Does not rewrite companion app listing fields in the base extension-focused deliverable unless bundled in the same order
Does not manage Apple Search Ads, App Clips, tvOS, or visionOS listing surfaces
Does not guarantee extension installs, enable rates, Safari Settings discovery, or App Store ranking
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 — one Safari extension App Store product page, zh-Hans name through screenshot captions; companion app listing already localized or in progress
Send intake — reply from the email on your Stripe receipt with your extension App Store listing URL, companion app URL, current English extension copy (title, subtitle, description, keywords), screenshot frames needing caption lines, and target locale (zh-Hans)
Receive files — within 24 hours, paste-ready zh-Hans extension listing fields arrive at your Stripe receipt email
Paste in Connect — extension target → App Store → Chinese (Simplified) → save → submit with your app version
Does a localized zh-Hans companion app automatically localize my Safari extension listing?
No. Safari Web Extensions and Safari App Extensions distributed through the App Store have their own product page metadata in App Store Connect — name, subtitle, keywords, description, promotional text, and screenshot sets — under the extension target's localization rows. Filling Chinese (Simplified) on the companion iOS or Mac app row does not propagate to the Safari extension listing.
What Safari extension listing fields does AppLocale rewrite?
Paste-ready Simplified Chinese (zh-Hans) for the Safari extension App Store product page: app name, subtitle, keywords with rationale, description, promotional text, and screenshot overlay or caption lines for toolbar, popup, and permission-flow frames — rewritten from your English extension listing and aligned with your existing zh-Hans companion app voice. Delivered within 24 hours to the email on your Stripe receipt.
What do I send after AppLocale payment?
Your live Safari extension App Store listing URL, companion app listing URL, current English extension copy (title, subtitle, description, keywords if populated), which screenshot frames need zh-Hans overlay lines, and target locale (zh-Hans). Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.
Does AppLocale build or debug my Safari Web Extension?
No. manifest.json, content scripts, background pages, WebKit entitlements, Xcode Safari extension targets, and extension signing are engineering tasks. We rewrite Connect text fields only — you paste them and submit with your app version.
Will localized extension listing copy get more installs in China?
We do not guarantee installs, enable rates, or Search rank. Apple controls extension discovery and Safari Settings surfacing. Complete zh-Hans extension metadata helps users who browse your product page understand it 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 Safari extension engineering, not WebKit or content-script development, not App Clips or tvOS or visionOS listing work, not Apple Search Ads management, not screenshot image design, not in-extension UI string localization, not ranking or install guarantees, not QuantRadar, and not investment or legal advice. We do not invent reviews, ratings, or traffic numbers.
AppLocale — zh-Hans Safari extension listing copy aligned with your companion app
Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your extension App Store URL and English listing copy. No install or ranking guarantees. Sold by Fortune Insight, LLC.