← MWM AICONTENT HISTORY

Update to MWM AI

Snapshot Nov 16, 2026 · 18:15 UTC · version 0.32.2

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save MWM AI and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Pages for one audience, search intent or campaign: App Store custom product pages, Google Play custom store listings, and the app's landing page on the web. Use when the person says things like \"make pages for my keywords\", \"a page for my TikTok campaign\", \"I need a website for my app\", \"a download page for a QR code\" or \"which custom pages should I make?\". Not for the main listing's text (store-copy) or its screenshots (store-visuals).",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 403
    }
  ],
  "name": "acquisition-pages",
  "skill_md_contents": "---\nname: acquisition-pages\ndescription: \"Pages for one audience, search intent or campaign: App Store custom product pages, Google Play custom store listings, and the app's landing page on the web. Use when the person says things like \\\"make pages for my keywords\\\", \\\"a page for my TikTok campaign\\\", \\\"I need a website for my app\\\", \\\"a download page for a QR code\\\" or \\\"which custom pages should I make?\\\". Not for the main listing's text (store-copy) or its screenshots (store-visuals).\"\n---\n\n# Acquisition pages\n\n## When this applies\n\nGiving one audience, search intent or campaign its own page: a custom product page on the App Store, a custom store listing on Google Play, or the app's landing page for traffic that starts outside the stores. The main listing's words belong to store-copy and its images to store-visuals.\n\n## The job and what good looks like\n\nEach page answers what its visitor came for in its first screen and first headline: someone who searched for a bass tuner lands on a bass. A page has its own concept, a subject, a scene or a palette, staged around the app's real interface, with headlines in the words of the query. A landing page tells in one screen what the app is, why it is good and where to get it, with facts from the store listing. A few pages that someone measures beat many that nobody looks at, since each one costs review and upkeep.\n\n## How a pro decides\n\n- **Store page or landing page.** When the traffic arrives in the store, from search or a store ad, make a store page. When it comes from the web, social networks, a QR code or an email, make a landing page.\n- **Group by intent, not by word.** Words that express one need make one page. Rank the groups by the traffic they bring and the demand behind them, and prefer words the app already ranks for.\n- **What changes and what stays.** Say what each page changes, such as the subject, the scene or the season, and what it keeps: the app's real interface, its brand type and its layout.\n- **Which screen leads.** Reorder so the screen answering the query comes first; design a new one when no existing screen shows the feature.\n- **Keep or retire.** Compare each page with the default page over time; rework or retire one that converts worse.\n\n## Do\n\n- Start each page in the app's primary language and add languages once it works.\n- Give the person the campaign link of each page they will use in an ad.\n- Write a landing page natively in each language, from the store description.\n- Show every page of a batch, not only the last one.\n\n## Don't\n\n- Don't stage a feature the app does not have: it costs a rejection and a bad review.\n- Don't reuse iPhone or iPad renders on Google Play.\n- Don't put one shared sentence on every screen of every page.\n- Don't make pages nobody will measure.\n- Don't invent a rating, a review, a download count, an award or a link.\n- Don't set the landing page as the listing's marketing link unless the person asks.\n\n## Pitfalls\n\n- A keyword the app does not rank for never brings anyone to its page.\n- A word another page already holds needs a decision to move it, not a duplicate.\n- A page created halfway exists: fix it rather than making a second one.\n- Taking a landing page offline breaks every ad, QR code and listing that points at it.\n\n## Store facts\n\nTool results carry the store rules and limits they depend on, each with its source and the date it was checked. `get_publishing_knowledge` answers questions on this skill's topics the same way (topics: `app-store/custom-product-pages`, `google-play/custom-store-listings`, `mwm/landing-pages`, `aso/custom-page-strategy`). When you use one of these facts, give its source and date.\n"
}

SHA-256 of public snapshot: 0480a7d3586e49a77fafe530abfe80b4222fea5f4cddea9c0d2991fad2a82e25