Index of every page on this site: llms.txt
All skills
rshankras avatar

/web-presence

@f958982
Run it yourself

The discovery surfaces outside the App Store app — your apps.apple.com product page ranking on Google, an owned landing page with a Smart App Banner, and the deal-site ecosystem that auto-amplifies price drops. Use when building a landing page, improving Google visibility for an app, planning a price-drop promotion, or auditing off-store discovery.

Use this Skill: https://skilld.dev/gh/rshankras/claude-code-apple-skills/web-presence

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈92 tokens for metadata: the name and description. ≈1.1k when used: this file.

Description uses 4.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈365 characters, or 4.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Web Presence

Every app has a public web page at apps.apple.com that ranks in Google — most developers never work that surface. Pair it with an owned landing page and the deal-site ecosystem and the open web becomes a free acquisition channel that compounds with everything on-store.

When This Skill Activates

  • "Make my app findable on Google" / no results for the app's own name
  • Building or reviewing a product landing page
  • Planning a temporary price drop or sale
  • The store-growth audit flags P6.6 (web presence) or P7.5 (deal sites)

Surface 1: The apps.apple.com page is a Google citizen

The store page's Google snippet draws from your app name, subtitle, and description opening — one more reason the first description paragraph must be benefit-led plain language (see app-store/app-description-writer).

  • ✅ Search your app's name + category terms on Google periodically; if the store page doesn't rank for your own brand, something is wrong (usually a generic name — see product/app-namer).
  • ✅ Ratings, price, and In-App Purchase labels appear in the snippet — per-storefront ratings mechanics apply (app-store/ratings-mechanics).
  • ❌ Treating the store URL as un-shareable internal plumbing. It's often your best-ranking page; link to it from everywhere (with ?pt= provider token for attribution where you need source data).

Surface 2: An owned landing page + Smart App Banner

One page, one job: convert a web visitor into a store visitor.

  • Structure: name + one-line promise → 2–3 screenshots or a short capture → social proof → a prominent Download on the App Store badge (Apple's official artwork, linked with your attribution token).

  • Smart App Banner — one meta tag; Safari renders a native install/open banner:

    <meta name="apple-itunes-app" content="app-id=YOUR_APP_ID, app-argument=https://yourapp.com/from-web">

    ✅ The banner shows Open for installed users — deep-linking into the app, down to specific in-app content via app-argument — and View for everyone else, opening the App Store in one tap. ❌ Custom "download our app" interstitials — the native banner already does this for free.

  • App Store Marketing Tools (tools.applemediaservices.com) — use for referral links, QR codes, and localized badge assets instead of hand-rolling them.

  • The landing page is also where pre-launch waitlists live (TestFlight public link — see product/beta-testing) and where press/link-in-bio traffic should land, because you can measure it before it enters the store funnel.

  • App Clips can front the landing page with an instant experience (generators/app-clip).

Surface 3: The deal-site ecosystem

Deal aggregators scrape App Store price drops automatically — no submission needed, just drop the price.

Price drop → aggregator listing → download spike → chart climb → organic downloads that outlive the sale. Velocity is the product; the discounted revenue is the cost of the campaign.

  • ✅ Drop meaningfully (50%+ or free-for-a-day reads as a deal; 10% doesn't scrape well).
  • ✅ Time drops to compound: with an in-app event, a seasonal moment, or the announced On-Sale badge surface (see generators/in-app-events), and have the next release ready so climbers land on a fresh listing.
  • ✅ Prompt for ratings during the spike window — sale users rate too, and the count sticks after prices recover.
  • ❌ Permanent-discount theater (always "90% off") — scrapers and users both learn to ignore it, and review teams notice manipulated anchor pricing.
  • ❌ Dropping the price of a subscription app's download — use offer codes instead (generators/offer-codes-setup).

Output Format

Audit report:

Google: brand query rank · store-page snippet quality (name/subtitle/desc opener)
Landing page: live? banner tag? attribution token? waitlist path?
Deal readiness: pricing model compatible? last drop + result? next planned window?

Each gap routed: copy fixes → app-store/app-description-writer; page build → this skill; price-drop plan → this skill + monetization pricing.

References

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    This skill provides guidelines and strategies for enhancing the web presence and App Store discovery of mobile applications. It contains no executable code, remote dependencies, or malicious patterns.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at f958982. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 months ago
What it can do
Reads files Edits files
last_verified
2026-07-16
review_by
2027-06-22
All 5 allowed tools
ReadWriteEditGlobGrep

README badge

README badge for rshankras/claude-code-apple-skills/web-presence