A Chrome extension landing page that earns the install
The install button lives in the browser's store, so your own page has a narrower job: explain what the extension does, show it working, and answer the question that stops most installs, which is "why does this need to read my data on every site?". Pair that with a privacy policy at a stable address and a clear link to the store.
What the page has to do
People reach a browser extension website from a search, a post or a link in the extension's own store listing. They want to know three things before they click through: what it does in one sentence, whether it works with the sites and browsers they use, and whether it's safe to give it the access the store's warning dialog will mention. A store listing has limited room for the third; a Chrome extension landing page on your own site doesn't.
Sections that do the work
- One sentence and a store button. "Hides prices on shopping sites until you've waited 24 hours." Name the browser on the button: "Add to Chrome", "Get it for Firefox".
- Three screenshots showing the extension in a real page, before and after.
- Permissions, explained (below).
- Works with: browsers, versions and any sites it targets or skips.
- Pricing, if there's a paid tier, with a buy button pointing at your payment link.
- FAQ, support and the privacy policy, linked in the footer as well.
Explain every permission in plain words
The install dialog shows broad warnings such as "read and change all your data on all websites", which sound alarming out of context. List each permission your extension requests and say, in a sentence, why it needs it and what it never does with it. Be exact; vague reassurance reads like the thing it's denying.
| What the browser says | What your page should say |
|---|---|
| Read and change your data on all websites | We need to see product pages to hide their prices. Nothing on the page is sent anywhere; it's processed in your browser. |
| Read your browsing history | We check whether you've visited a shop before to apply your waiting period. History never leaves your device. |
| Manage your downloads | Only to save the export you ask for. We don't see other downloads. |
| Communicate with cooperating websites | To sync your settings with your account on our site. You can turn this off. |
If any data does leave the browser, say exactly what, where it goes and how long it's kept. That paragraph should match your privacy policy word for word in substance, and match what the code does.
The privacy policy
Browser stores' developer policies generally ask extensions that handle user data to link a privacy policy, and reviewers check that it matches the extension's behaviour. Check the current policy of each store you publish to. The policy needs to describe the extension, which is software only you know the internals of.
Screenshots and demo
Show the extension on a real, recognisable kind of page with real-looking content, cropped tight enough that the extension's own interface is readable on a phone. Upload them to the build; the model sees photos and places them with the copy. Give each image alt text that describes what the extension is doing in it. Video can't play on published design-engine pages, embedded or uploaded, so put a short screen recording on YouTube or Vimeo and link to it.
Building it with Anticode
Describe the extension: "an extension landing page for a Chrome and Firefox extension that delays online shopping, with permissions explained, screenshots, a free and a paid tier and a privacy policy page". The Architect asks up to three questions where the answer changes the build and shows a plan. The Technical design system suits developer tools; Playful or Organic suits consumer ones. Pages from the design engine ship with no scripts at all, which makes for a fast page and, for an extension that asks for trust, a small point in your favour you can mention. A paid plan lets you publish on your own domain.
Limits
- No install button that works on the page. Installs happen in the store; your buttons link there.
- No licence keys or account system for paid tiers. Use your payment provider's checkout link and handle licensing in the extension or your own backend.
- No video or store badges loaded from the store. Upload your own badge images and link out to any demo video.
- The generated legal pages describe the site, not the extension.
Questions people ask
Does a Chrome extension need a website at all?
Not to be listed, but a site gives you a stable address for the privacy policy, support and a page that can rank for the problem the extension solves.
Can I collect feedback or bug reports on the site?
Yes, through the contact form, or a custom form with fields such as browser version. Forms don't accept screenshots as attachments.
Can I see how many people click through to the store?
The dashboard shows page views per day by source. Click-throughs to the store are best measured in the store's own statistics.