Rich Links App Store Listing in Simplified Chinese — LPLinkMetadata Link Preview Cards, Messages / Mail / Notes Paste URL Rich Link Cards, 丰富链接 / 链接预览 / 富链接 zh-Hans Copy

Who this is for

Western indie iOS developers — US, UK, EU, Canada, Australia — who:

• Ship an app whose en-US listing markets Rich Links, link preview, rich link cards, or LPLinkMetadata paste URL previews — title, image, and domain cards when a URL is pasted into Messages, Mail, Notes, or in-app compose surfaces
• Show gallery frames with "Rich Links", "Link preview", "Rich link card", "Paste URL preview", or 丰富链接 / 链接预览 / 富链接 overlay lines on the US product page
• Finished link preview or LPLinkMetadata integration in the binary — not looking for LPMetadataProvider engineering or Open Graph scraping help here
• Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on rich-link preview gallery frames
• Need paste-ready Connect text — not an engineer for URL unfurling, not a designer to re-export every link-preview screenshot from scratch

If your lead feature is Underline Links always-underlined hyperlinks — not link preview cards — see our Underline Links listing guide. If you market Link Tracking Protection Safari parameter stripping, see our Link Tracking Protection listing guide. If your hero is the full Messages chat experience — not Rich Links preview cards alone — see our Messages listing guide. If the entire China page is still English on every field, start with China App Store still shows English or the AppLocale product page.

Rich Links on the device vs zh-Hans listing copy — two different jobs

US/EU indie teams conflate link preview engineering with storefront language. iOS frameworks and App Store Connect actually separate them:

• Rich Links and LPLinkMetadata on the device — when users paste a URL, the system or your app can fetch metadata and render a rich link card with title, image, and domain using LPLinkMetadata and LPMetadataProvider. In-app link preview behavior — outside AppLocale scope.
• Link preview and URL unfurling engineering — code that implements LPLinkMetadata, custom link preview UI, Open Graph or oEmbed fetching, and paste-detection in compose views. Engineering inside the binary — not listing rewrite.
• Rich Links marketing on the product page — description paragraphs, subtitle positioning, keywords, promotional text, and screenshot overlays that tell buyers your app shows link preview cards, Rich Links, or paste URL rich link cards. Connect text fields — this page.
• Pricing and Availability → China — makes the app downloadable on the China storefront. Separate from language rows.
• App Store tab → Chinese (Simplified) localization — independent row for title, subtitle, keywords, description, promotional text, and screenshot caption lines. Empty or English here means China buyers see English fallback regardless of how strongly your US listing markets Rich Links.

An app that renders link preview cards and a localized China listing are both valuable — neither replaces the other. AppLocale covers how you describe Rich Links and LPLinkMetadata preview cards on the store page, not whether link unfurling works inside the app binary.

Rich Links listing copy vs Underline Links, Link Tracking Protection, and adjacent guides

Several shop guides cover adjacent Apple link and messaging features. This page covers Rich Links and LPLinkMetadata link preview card marketing on listing metadata — not engineering, not unrelated category copy:

• Rich Links and link preview cards (this page) — description, subtitle, keywords, promotional text, and screenshot overlays like "Rich Links", "Link preview", "Rich link card", "Paste URL preview", "LPLinkMetadata", and Messages / Mail / Notes compose frames showing title+image+domain cards. zh-Hans terms: 丰富链接, 链接预览, 富链接, 链接卡片.
• Underline Links (contrast only — LIVE) — Settings → Accessibility → Display & Text Size → Underline Links, always underlined hyperlinks — 给链接加下划线, 链接下划线. See Underline Links listing guide when hyperlink underline affordance is your lead claim — not paste URL preview cards.
• Link Tracking Protection (contrast only — LIVE) — Safari strips tracking parameters from copied and shared URLs — 链接跟踪保护, 移除链接跟踪参数. See Link Tracking Protection listing guide when URL parameter privacy is your lead claim — not LPLinkMetadata preview cards.
• Auto-Play Video Previews (contrast only — LIVE) — App Store product page video preview autoplay marketing. See Auto-Play Video Previews listing guide — not in-app paste URL link preview cards.
• App Preview video captions (contrast only — LIVE) — zh-Hans caption lines on App Store marketing video previews. See App Preview captions listing guide — not Rich Links LPLinkMetadata cards in Messages or Mail.
• Messages hub (contrast only — LIVE) — general iMessage, chat threads, and messaging UX marketing. See Messages listing guide when the entire chat experience is your lead story — not Rich Links preview cards alone unless that is what your gallery shows.
• Safari browser hub (contrast only — LIVE) — in-app browsing, tabs, Reader, extensions. See Safari listing guide when browser UX is your lead story — not Rich Links paste preview cards unless your gallery shows them.
• Share sheet (different scope) — Share, Copy Link, Save Image export UI. See Share Sheet listing guide when export actions are your lead claim — not link preview cards unless your English gallery explicitly shows both on the same frame.

You can localize the title and still leave every Rich Links screenshot overlay English-only. Buyers then see a Chinese name with English "Link preview" badges — a mismatch that reads like half-finished localization. See also China App Store still shows English when entire rows fall back.

No twin slug pages — link-previews and link-metadata belong here

AppLocale does not maintain separate twin pages for these slugs when Rich Links dominates your lead gallery:

• link-previews — link preview and paste URL preview search intent folds here — not as a duplicate SKU
• messages-rich-links — Messages Rich Links marketing belongs here when preview cards dominate — not as a separate twin slug page
• rich-link — singular rich-link search intent folds onto this Rich Links-as-lead page
• rich-link-previews — rich link preview vocabulary belongs here — not as duplicate slug files
• lp-link-metadata — LPLinkMetadata developer search intent folds here when listing marketing dominates
• link-metadata — link metadata and unfurl marketing belongs on this page — AppLocale does not publish duplicate pages

If your en-US product page leads with Rich Links badges, link preview cards, and LPLinkMetadata paste URL demos on gallery frames, order AppLocale copy scoped to this Rich Links page — not Underline Links copy, not Link Tracking Protection copy, and not duplicate slug files AppLocale does not publish.

Where English Rich Links copy shows on the China product page

Link-preview-conscious purchasers browsing the China App Store evaluate rich link card claims in the first scroll. Common surfaces where English marketing text still appears:

• Screenshot overlay badges — "Rich Links", "Link preview", "Rich link card", "Paste URL preview", "LPLinkMetadata" on gallery frames showing Messages, Mail, or Notes compose UIs with title+image+domain cards
• Description paragraphs — English link-preview value props ("See rich link cards when you paste a URL", "Beautiful link previews in Messages") that China readers skim past
• Subtitle and keywords — English-only rows miss China Search intent for 丰富链接, 链接预览, or 富链接 when buyers filter for link-preview-friendly apps
• Promotional text — 170-character field still pitching Rich Links in English above the description
• Mixed page — Chinese description pasted once but Rich Links screenshot captions and subtitle still English — reads unfinished next to localized competitors
• Formal machine translation — stiff 翻译腔 that uses wrong vocabulary (给链接加下划线 for Underline Links instead of 链接预览 for link preview cards) or conflates Rich Links with Link Tracking Protection parameter stripping or Share sheet export UI when your English source only claimed paste URL preview cards

Better zh-Hans listing copy helps Rich Links-conscious buyers understand your link preview story before install. It does not replace LPLinkMetadata engineering in the binary or Apple's review decisions.

What AppLocale delivers for Rich Links apps on zh-Hans

This SKU is a listing rewrite scoped to Rich Links and LPLinkMetadata link preview card marketing — paste-ready fields you copy into App Store Connect:

• Name (title) — zh-Hans app name within Connect character limits when your English title does not signal Rich Links or link preview awareness to China searchers
• Subtitle — concise benefit line that can reference link preview cards or Rich Links without stuffing raw English badge text
• Keywords — zh-Hans search terms buyers use for link preview workflows, rich link cards, and paste URL preview claims in your category
• Description — long listing body with clear zh-Hans paragraphs on Rich Links and link preview features you already claim — without English-only link-preview jargon
• Promotional text — when you include the 170-character promo field in scope
• Screenshot overlay / caption lines — short zh-Hans text on gallery images that show link preview cards ("丰富链接预览", "粘贴链接显示卡片", "链接预览带标题和图片")
• English alignment — matching en-US field notes when both storefronts must stay consistent on Rich Links and link preview promises

We map deliverables to the fields you actually use. Send every English overlay line and description paragraph that mentions Rich Links, link preview, rich link cards, or LPLinkMetadata — we deliver counted strings that fit Connect limits. We rewrite what you already claim on the US page; we do not invent Rich Links integration your app does not describe.

Rich Links-specific listing vocabulary — what translates differently

Link preview marketing on App Store pages uses vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese buyers describe Rich Links and paste URL preview cards — not a literal paste of US marketing:

Rich Links and link preview phrasing

US pages use "Rich Links", "Link preview", "Rich link card", "Paste URL preview", and "LPLinkMetadata." Chinese App Store and messaging vocabulary often uses 丰富链接 for Rich Links feature marketing, 链接预览 for link preview cards, 富链接 for rich link card shorthand, 链接卡片 for title+image+domain cards, and 粘贴链接 for paste URL workflows. Listing copy should mirror that vocabulary — not 给链接加下划线 Underline Links terms or 链接跟踪保护 Link Tracking Protection terms that belong on those pages.

Rich Links vs Underline Links — do not conflate

Underline Links always underlines hyperlinks under Accessibility settings — 给链接加下划线. Rich Links shows LPLinkMetadata preview cards when a URL is pasted — 丰富链接, 链接预览. If your English gallery shows an Underline Links toggle, do not upgrade zh-Hans copy to link preview card claims unless that frame shows Rich Links. See the Underline Links listing guide only if hyperlink underline marketing is your lead claim.

Rich Links vs Link Tracking Protection — do not conflate

Link Tracking Protection strips tracking parameters from copied Safari URLs — 链接跟踪保护. Rich Links renders title+image+domain preview cards on paste — 链接预览. If your English gallery shows Safari Advanced settings toggles, do not upgrade zh-Hans copy to Rich Links claims unless that frame shows link preview cards. See the Link Tracking Protection listing guide only if parameter stripping is your lead marketing claim.

Rich Links vs App Preview captions or Auto-Play Video Previews — do not conflate

App Preview captions are zh-Hans text on App Store marketing video previews. Auto-Play Video Previews is product-page video autoplay marketing. Rich Links is in-app or system paste URL link preview cards — 丰富链接. Do not reuse App Preview caption vocabulary on Messages compose frames showing LPLinkMetadata cards.

Subtitle and keyword packing

The 30-character subtitle and 100-character keyword field need Rich Links search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 丰富链接, 链接预览, and 富链接 each signal different intent from 给链接加下划线 Underline Links terms or 链接跟踪保护 Link Tracking Protection terms.

Caption lines vs burned-in badges

Marketing screenshot overlays you control — "Rich Links" headlines on gallery frames showing Messages paste URL preview cards — are separate caption fields or burned-in PNG text. See Screenshot captions in Simplified Chinese for caption-field mechanics when overlays are editable in Connect.

Why English-only Rich Links copy hurts China storefront conversion

Link-preview-conscious purchasers browsing the China App Store evaluate rich link card claims in the first scroll. Common failure modes when only en-US is filled:

• Trust gap — Chinese social posts recommend a "rich link preview app"; buyer taps through and sees English "Link preview" with no zh-Hans context
• Localized listing, English badges — description promises Chinese messaging polish; screenshot overlays still "Rich link card" at the worst moment
• Search intent miss — buyers search 丰富链接 or 链接预览; English-only keywords miss intent even when your app renders LPLinkMetadata cards in the binary
• Underline Links vocabulary bleed — machine-translated 给链接加下划线 when English source showed link preview cards, not Underline Links toggles
• Link Tracking Protection vocabulary bleed — machine-translated 链接跟踪保护 when English source meant paste URL preview cards, not Safari parameter stripping
• Messages hub vocabulary bleed — generic 信息 or iMessage chat copy on dedicated Rich Links preview frames when buyers expected 链接预览 language
• Competitor contrast — rivals with native zh-Hans Rich Links and link preview copy look more serious about China buyers who care about polished paste URL cards

Clearer zh-Hans Rich Links marketing reduces confusion on the product page. It does not replace LPLinkMetadata engineering in the binary or in-app link unfurling work.

Why machine-translated Rich Links copy fails

• Literal "Rich Links" → awkward 丰富链接直译 instead of commerce-idiomatic 链接预览 or 丰富链接预览 card vocabulary
• Underline Links vocabulary bleed — 给链接加下划线 when English source showed LPLinkMetadata preview cards, not Accessibility hyperlink underlines
• Link Tracking Protection vocabulary bleed — 链接跟踪保护 when English source showed paste URL rich link cards, not Safari Advanced toggles
• Share sheet vocabulary bleed — 共享 or 拷贝链接 when English source meant link preview cards after paste, not export action rows
• App Preview caption bleed — 预览视频字幕 when English source meant in-app link preview cards, not App Store marketing video captions
• English badge headlines preserved on zh-Hans screenshots — "Link preview" with no Chinese benefit line beside it
• Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention Rich Links

Machine translation is fine for internal drafts. Finished Rich Links strings need idiomatic zh-Hans that states what link preview scope you claim — while keeping accurate separation from Underline Links, Link Tracking Protection, Messages hub, and Safari hub copy. AppLocale rewrites by hand; we do not deliver raw Google Translate or LLM output as finished copy.

What good zh-Hans Rich Links listing copy looks like

Link preview copy appears on screenshot galleries and in description skims. Strong Chinese strings lead with the benefit and state scope plainly:

• Overlay: "粘贴链接，显示丰富链接预览卡片" — paste workflow + preview card benefit in one line
• Description paragraph: plain zh-Hans list of how your app shows Rich Links or LPLinkMetadata preview cards — title, image, domain on paste — matching what you actually describe on the US page
• Subtitle: "链接预览带标题图片" or "丰富链接卡片" within the ~30-character cap
• Keywords: include 丰富链接 / 链接预览 / 富链接 only when accurate — do not keyword-stuff Underline Links, Link Tracking Protection, or generic Messages terms if you only market Rich Links preview cards
• Honest scope — do not claim "full Messages Rich Links for every URL type" in Chinese if your app only previews links for part of your compose flow

zh-Hans and en-US strings can differ in length and structure when the underlying Rich Links story is the same — avoid mirroring English comma-heavy promo lines character-for-character.

What you send

• Your live App Store listing URL
• Current English listing copy — name, subtitle, keywords, description, promotional text if used
• Screenshot overlay text that mentions Rich Links or link preview cards ("Rich Links", "Link preview", "Rich link card", "LPLinkMetadata", "Paste URL preview")
• Brief note on how your app references Rich Links or link preview cards today — so zh-Hans copy stays accurate to your marketing scope
• Target locales (e.g. zh-Hans for China storefront)
• Your deadline if aligning with a messaging launch or App Store gallery update
• Reply from the email address on your Stripe receipt after checkout

What you get

• Simplified Chinese (zh-Hans) — listing fields and screenshot overlay lines scoped to Rich Links and link preview card marketing, paste-ready for Connect
• English (en-US) — aligned listing strings when both locales need the same promise in native phrasing
• Character-count notes — which strings fit Connect limits and what to trim
• Paste-ready delivery — formatted copy mapped to each field you sent
• 24-hour turnaround — delivered to the email on your Stripe receipt

What we do not promise

• No guarantee that every pasted URL unfurls on a buyer's device — listing rewrite describes what you already claim
• No LPLinkMetadata, LPMetadataProvider, Open Graph scraping, or link preview UI engineering
• No Underline Links, Link Tracking Protection, Auto-Play Video Previews, or App Preview caption listing copy as the hero — see those guides only if that is your marketing scope
• No generic Messages hub or Safari browser hub listing copy as the hero — see those guides only if that is your marketing scope
• No Share sheet export UI listing copy unless that is your lead claim on the English page
• No screenshot set production, link-preview PNG re-export, or gallery design
• No guaranteed App Store ranking, keyword position, download growth, or link-preview adoption outcomes
• No fabricated social proof, review quotes, ratings, or traffic numbers
• No binary localization, in-app string translation, or Connect configuration on your behalf
• No Apple Search Ads or review-reply retainers
• Not QuantRadar · not investment advice · not legal review

AppLocale FAQ

Are Rich Links the same as Underline Links?

No. Rich Links shows LPLinkMetadata preview cards with title, image, and domain when a URL is pasted — 丰富链接, 链接预览. Underline Links always underlines hyperlinks under Accessibility settings — 给链接加下划线. See our Underline Links listing guide for hyperlink underline marketing copy.

Are Rich Links the same as Link Tracking Protection?

No. Link Tracking Protection strips tracking parameters from copied Safari URLs — 链接跟踪保护. Rich Links renders paste URL preview cards — 链接预览, 富链接. See our Link Tracking Protection listing guide for Safari link-privacy marketing copy.

Are Rich Links the same as Auto-Play Video Previews or App Preview captions?

No. Auto-Play Video Previews and App Preview captions cover App Store marketing video behavior and caption lines. Rich Links covers in-app or system paste URL link preview cards. See our Auto-Play Video Previews guide and App Preview captions guide for those buyer stories.

Are Rich Links the same as the Messages hub or Safari hub?

No. The Messages hub covers general chat and iMessage marketing. The Safari hub covers browser UX marketing. Rich Links covers link preview cards when URLs are pasted — often on Messages, Mail, or Notes frames — as the lead claim. See our Messages listing guide and Safari listing guide only if those broader stories are your lead marketing scope.

What listing fields does AppLocale rewrite for Rich Links apps?

Paste-ready Simplified Chinese (zh-Hans) copy for App Store Connect listing fields you specify: title, subtitle, keywords, description, promotional text when included, and screenshot overlay or caption lines that mention Rich Links, link preview, rich link cards, or LPLinkMetadata — rewritten from your English originals.

Does AppLocale implement LPLinkMetadata in my app?

No. We deliver listing metadata copy only. LPLinkMetadata, LPMetadataProvider, URL unfurling, and in-app link preview rendering are outside AppLocale scope. We rewrite how you describe existing Rich Links claims on the store page.

Does AppLocale maintain twin pages for link-previews or link-metadata?

No. link-previews, messages-rich-links, rich-link, rich-link-previews, lp-link-metadata, and link-metadata search intents fold onto this Rich Links-as-lead page. AppLocale does not publish separate twin slug pages for those variants.

What do I send after payment?

Your live App Store listing URL, current English listing copy (name, subtitle, keywords, description, promo if used), screenshot overlay lines mentioning Rich Links or link preview cards, target locales (e.g. zh-Hans), and deadline. Reply from the email address on your Stripe receipt.

Is this machine translation?

No. We rewrite Rich Links and link preview listing copy by hand. We do not paste Google Translate or ChatGPT output into deliverables.

How fast is delivery?

Within 24 hours after your Stripe receipt. Send your App Store URL, English listing and overlay copy, target locales, and deadline from the email on your receipt.

Do you guarantee conversion lift or App Store rankings?

No. We improve clarity from your existing copy. We do not promise keyword position, search rank, or download growth.

How much does AppLocale cost?

$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.

What is AppLocale not?

Not LPLinkMetadata engineering, not Underline Links or Link Tracking Protection listing copy as the hero, not Auto-Play Video Previews or App Preview caption listing copy as the hero, not Messages or Safari hub listing copy as the hero, not screenshot set production, not binary localization, not Connect configuration, not ranking guarantees, not review-reply retainers, not QuantRadar, and not investment advice. We do not invent reviews, ratings, or traffic numbers.

AppLocale — Rich Links & LPLinkMetadata link preview card listing copy in Simplified Chinese

$79 one-time

Buy on Stripe

After checkout, reply from your Stripe receipt email with your App Store URL, English listing and Rich Links overlay copy, target locales, and deadline. Delivery within 24 hours.
No ranking guarantees. AppLocale does not implement LPLinkMetadata in your app. Sold by Fortune Insight, LLC.