Browser extension website content checklist

A browser extension site has to show what the extension does in ten seconds and say plainly what it can see in the browser. Most delays come from store listing details, permission explanations and screenshots that match the current version.

8 pages39 requests24 requiredAnswered by the developer or product owner

Where to start

  1. Permissions and privacy. It needs the manifest and a privacy policy, which take the developer time, and it shapes how every other page is worded.
  2. Install and store listings. Store approval has its own waiting time, and the install links are needed before any button can be wired.
  3. Features. Fresh screenshots and the demo clip drive the layout of the home page and the features page.
  4. Pricing. The pricing model decides whether the site needs a checkout, a licence flow or only a download button.
  5. Support and docs. The known issues list is quick to write once the developer reads the last month of reviews.

The checklist

Home

Visitors arrive from a search or a store link and want to know what the extension does, so the page needs one clear demonstration and an install button that matches their browser.

  • Extension name and one-line description Short text, requiredThe name exactly as it appears in the store, then a line saying what it does for whom. For example: 'Tab Tamer closes duplicate tabs and saves your sessions.'
  • Browsers supported Multiple choice, requiredTick every browser with a published version today, not the ones planned. The install button changes to match the visitor's browser.ChromeEdgeFirefoxSafariBraveOpera
  • Demo clip File upload, requiredA screen recording of the main use in under 15 seconds. MP4 or WebM under 8 MB loads fast, and a clean recording with no personal tabs open is essential.
  • Main button Single choice, requiredWhat the first button does. If the extension is in several stores, the designer can detect the browser and swap the label.Add to ChromeAdd to FirefoxDownloadJoin the waitlistInstall from the store
  • User count and store rating Short textThe install count and star rating shown in the store today, with the date you checked. Only publish numbers that match the live store page.

Features

People compare extensions quickly, so this page needs the three or four things yours does better, shown with real screens rather than icons.

  • Main features Long text, requiredList three to six features, each with a name and one sentence on what the user gets. Put the one people install it for first.
  • Product screenshots Image upload, requiredThree to five captures of the extension in use, at 1280 by 800 pixels if you have them. Capture the popup, the options page and the extension working on a real page.
  • Websites it works on Long text, requiredName the sites or kinds of site where the extension is active, and any where it is known to break. Visitors search this before they install.
  • Keyboard shortcuts Long textDefault shortcuts for Windows and Mac, and whether users can change them. Power users scan for this on the page.
  • Languages supported Multiple choiceTick the interface languages that ship in the current version. The site lists them so visitors know if it will read in their language.EnglishSpanishFrenchGermanPortugueseJapaneseChineseOther

Install and store listings

The store page is usually the real front door, so the site has to link to it correctly and explain the install steps that people get wrong.

  • Chrome Web Store link LinkThe public listing address, which contains the extension ID. Paste the live link, because draft or dashboard links will not open for visitors.
  • Firefox Add-ons link LinkThe addons.mozilla.org listing address. Leave empty if there is no Firefox version yet.
  • Edge Add-ons or other store links LinkAny other store where the extension is published, such as Edge, Opera or the Mac App Store for Safari. One link per line, with the store name.
  • Install steps Long text, requiredThe clicks from the store page to a working extension, including pinning it to the toolbar. Most support emails come from people who installed it and cannot find it.
  • Minimum browser version Short textThe oldest version the extension supports, such as 'Chrome 114 or newer'. It prevents refund requests from people on old browsers.
  • Store icon and promo tiles File uploadThe original icon (128 by 128 pixels) and promotional tiles you submitted to the stores. The designer reuses them so the site and store match.

Permissions and privacy

Visitors are wary of extensions that can read every page, so this page earns trust by explaining each permission, and it fails when it hides behind a generic privacy statement.

  • Permissions and why each is needed Long text, requiredTake every permission in the manifest and explain it in one plain sentence. For example: 'tabs, to list your open tabs. We never send tab titles anywhere.'
  • Data the extension collects Long text, requiredState what is collected, what stays on the device and what is sent to a server. If the answer is 'nothing leaves the browser', say that in those words.
  • Data sent to your servers Yes or no, requiredAnswer yes if any page content, history or account data goes to a server you run or a third party. The privacy copy differs sharply between yes and no.
  • Analytics or crash reporting used Single choice, requiredChoose what is running in the shipped version. If it is on, the privacy page has to name the tool.NoneAnonymous usage analyticsCrash reports onlyBoth analytics and crash reports
  • Privacy policy link or file File upload, requiredThe policy the stores already link to. If it was written for the store listing only, name the person who will review it for the website.

Pricing

Extensions are judged on price in seconds, and this page needs to say what is free, what costs money and how the paid version is activated.

  • Pricing model Single choice, requiredChoose how the extension earns money. The pricing page layout changes completely between free and paid.FreeFree with paid upgradeOne-time purchaseSubscriptionFree, supported by donations
  • Plan details and limits Long textWhat each plan includes, with prices and any usage caps. Spell out what a free user cannot do, so there are no surprises after install.
  • How paid features are activated Single choiceSay how a customer proves they paid. It sets the wording on the buy button and the support page.Account loginLicence keyStore paymentEmail address match
  • Refund policy Long textHow many days a buyer has to ask, how to ask and who decides. Match it to what your payment provider allows.

Support and docs

Extensions break whenever a browser or a target site changes, so users arrive annoyed, and this page decides whether they email you or leave a one-star review.

  • Support email Short text, requiredThe address that reaches the developer. Add a line on how long replies take, so people do not post a review while waiting.
  • Known issues and fixes Long text, requiredThe five problems users report most, each with the fix. Look at the last month of store reviews and support emails for the list.
  • Documentation link LinkThe address of a docs site, wiki or README with setup guides. The site will link to it rather than copy it.
  • Bug reports and feature requests Single choice, requiredPick where users should send them. The site's contact page points to this channel.GitHub issuesEmailFeedback formDiscord or community chat

Changelog

A visible release history shows the extension is maintained, and users check it before they trust an update.

  • Current version number Short text, requiredThe version live in the stores today, in the format shown in the manifest, such as 2.4.1. The site shows it on the download area.
  • Release notes for the last three versions Long text, requiredA short list of changes per version, with dates. Write them for users, so say 'fixed duplicate tabs on YouTube' rather than 'refactored matcher'.
  • Changelog source LinkA link to where releases are listed, such as GitHub Releases or a markdown file. If one exists, the designer can pull entries from it.
  • Roadmap shown publicly Yes or no, requiredSay whether planned features can be listed. If yes, send only items you are confident about, since people hold you to them.

Brand and legal

Extensions often use other companies' names and logos in screenshots and copy, so this page covers whose names the site may show, as well as the developer's own.

  • Logo and icon files File upload, requiredThe SVG or PNG source of the extension icon, at least 512 by 512 pixels, and any wordmark. Stores resize icons badly, so use the source.
  • Brand colours ColourThe accent colour of the icon and popup as a hex code. The site's buttons and highlights will match it.
  • Brand fonts FontThe typeface used in the popup or on the store tiles. If it is the system font, say so.
  • Developer or company name as shown in stores Short text, requiredThe publisher name exactly as the stores display it. The footer and legal pages use the same name so visitors can match them.
  • Permission to show third-party names and logos Yes or no, requiredConfirm who approved using the names or logos of sites the extension works with. Many companies have brand rules, so check where the client operates.
  • Terms of service approved Yes or no, requiredSay whether terms exist for the paid version or accounts. If not, say who will supply them before launch.

What clients get stuck on

Screenshots from an old version

Store screenshots lag the product by months. Ask for fresh captures from the current build at the same window size, and check them against the live popup before they go on the page.

A permission list nobody can explain

Developers add permissions during testing and forget them. Ask for the manifest and walk each entry with the developer, because a permission you cannot justify becomes the top review complaint.

Store links before approval

Stores take days to approve a listing or update. Ask for the review status early, and build the install button so the link can be swapped without a redesign.

Release notes in developer language

Commit messages make poor changelog entries. Ask the developer for plain-language lines per release, or offer to rewrite them and send them back for a check.

Logos of sites the extension touches

Screenshots often show other brands. Ask whether the extension is affiliated with them and whether their logos can appear, and crop or blur the captures if the answer is unclear.

Copy the checklist

Plain Markdown you can paste into a doc or an email.

# Browser extension website content checklist

## Home
- [ ] Extension name and one-line description (Short text, required)
- [ ] Browsers supported (Multiple choice, required)
- [ ] Demo clip (File upload, required)
- [ ] Main button (Single choice, required)
- [ ] User count and store rating (Short text)

## Features
- [ ] Main features (Long text, required)
- [ ] Product screenshots (Image upload, required)
- [ ] Websites it works on (Long text, required)
- [ ] Keyboard shortcuts (Long text)
- [ ] Languages supported (Multiple choice)

## Install and store listings
- [ ] Chrome Web Store link (Link)
- [ ] Firefox Add-ons link (Link)
- [ ] Edge Add-ons or other store links (Link)
- [ ] Install steps (Long text, required)
- [ ] Minimum browser version (Short text)
- [ ] Store icon and promo tiles (File upload)

## Permissions and privacy
- [ ] Permissions and why each is needed (Long text, required)
- [ ] Data the extension collects (Long text, required)
- [ ] Data sent to your servers (Yes or no, required)
- [ ] Analytics or crash reporting used (Single choice, required)
- [ ] Privacy policy link or file (File upload, required)

## Pricing
- [ ] Pricing model (Single choice, required)
- [ ] Plan details and limits (Long text)
- [ ] How paid features are activated (Single choice)
- [ ] Refund policy (Long text)

## Support and docs
- [ ] Support email (Short text, required)
- [ ] Known issues and fixes (Long text, required)
- [ ] Documentation link (Link)
- [ ] Bug reports and feature requests (Single choice, required)

## Changelog
- [ ] Current version number (Short text, required)
- [ ] Release notes for the last three versions (Long text, required)
- [ ] Changelog source (Link)
- [ ] Roadmap shown publicly (Yes or no, required)

## Brand and legal
- [ ] Logo and icon files (File upload, required)
- [ ] Brand colours (Colour)
- [ ] Brand fonts (Font)
- [ ] Developer or company name as shown in stores (Short text, required)
- [ ] Permission to show third-party names and logos (Yes or no, required)
- [ ] Terms of service approved (Yes or no, required)

Questions about this checklist

Does a browser extension need its own website if it is already in the store?

Yes, for most. The store page cannot hold a privacy explanation, pricing detail or docs well, and many users search the name before installing. A short site also gives you a place to link from the store.

How should the site handle people on a browser the extension does not support?

Detect the browser and show a plain message naming the browsers that work, with a waitlist or email option. Hiding the install button leaves people confused, and a disabled button without a reason looks broken.

Should the site repeat the store description word for word?

No. Store descriptions are cut to fit limits and keywords. Write the site copy for a human reading in full, and keep the store text aligned in claims, so the two never disagree on features or price.