Online marketplace website content checklist

A marketplace site has two audiences with different questions, so it needs a separate story for buyers and for sellers, plain fee rules and visible trust signals. Most delays come from seller terms, payout details and category lists nobody has finished.

8 pages43 requests32 requiredAnswered by the founder or product lead

Where to start

  1. Brand and legal. Terms and the company details need several people to approve them, so they take the longest to come back.
  2. Fees and payments. The fee structure shapes the seller page and the pricing layout, and it is the part founders delay deciding.
  3. Categories and listings. Real category and listing samples set the card sizes and the navigation for the whole site.
  4. Seller onboarding. Supply is the hard side to recruit, so this page needs the most thought and the most review rounds.
  5. How it works. It is easy to write once the fees and listing rules are settled, and it can be finished in an afternoon.

The checklist

Home

The home page has to explain what is traded and who it is for in a few seconds, and it usually fails by trying to speak to buyers and sellers with the same sentence.

  • Marketplace name and tagline Short text, requiredThe name as it appears in the app and on invoices, then a tagline of under 10 words. The designer sets both in the header, so settle spelling and capitals now.
  • What is bought and sold Short text, requiredOne sentence naming the goods or services and both sides. For example: 'Local makers sell handmade furniture to homeowners.' If it takes two sentences, the home page will read unclearly too.
  • Hero image Image upload, requiredA wide image of real people using the marketplace, or a collage of live listings. At least 2400 pixels wide. Stock photos of laptops and handshakes make a marketplace look empty.
  • Audience to lead with Single choice, requiredPick the side that is harder to recruit. The headline and first button speak to that side, and the other side gets its own strip lower on the page.BuyersSellersBoth equally
  • Primary button Single choice, requiredThe single action you want from a first-time visitor. It repeats in the header and again at the bottom of the home page.Browse listingsPost a listingCreate an accountRequest an invite
  • Live figures for the home page Long textListings, active sellers, orders completed or cities covered. Send only numbers you can confirm from an admin screen this week, and the date you checked. Leave blank if the marketplace is new.

How it works

Buyers and sellers each want to know what happens after they sign up, and this page goes wrong when the steps describe the software instead of the person.

  • Buyer steps Long text, requiredThree to five steps from first search to receiving the item or booking. Write what the buyer does at each step, in the order they see it on screen.
  • Seller steps Long text, requiredThree to five steps from creating an account to getting paid. Include any approval wait, because sellers ask about it before they ask about fees.
  • Transaction flow Single choice, requiredChoose how agreement and money move between the two sides. The answer decides the button on every listing and whether the site needs a checkout page at all.Buyer pays on the platformBuyer pays the seller directlyBuyer requests a quote firstMix of these, depending on category
  • Explainer video or walkthrough LinkA link to a screen recording or product video if one exists. A rough recording with a voiceover is more useful than a polished one that is a year out of date.

Categories and listings

Category pages and listing cards are the bulk of the site, and the designer cannot size them without real examples, which clients usually have to dig out of the admin area.

  • Category tree File upload, requiredA spreadsheet or document with top-level categories and sub-categories as they exist now. Mark any category that has no listings yet so the designer can decide whether to hide it.
  • Category images or icons Image uploadOne square image or icon per top-level category, at least 800 pixels. If none exist, say so and the designer will propose a simple icon set.
  • Three real listings File upload, requiredScreenshots or exports of one rich listing, one average listing and one thin listing. Thin listings expose layout problems that the polished example hides.
  • Fields shown on a listing Multiple choice, requiredTick every piece of information a buyer sees on a listing card or detail page. Anything not ticked will not get space in the layout.TitlePhotosPriceLocationConditionAvailability calendarSeller ratingDelivery optionsReviews
  • Listing approval method Single choice, requiredSay whether a new listing goes live at once or waits for a person. A review queue means sellers need a visible 'pending' message on the site.Goes live immediatelyStaff review before publishingReviewed after publishing
  • Search filters buyers rely on Long textThe filters people use most, such as price, distance, date, brand or size. Mark which are built today and which are planned.

Seller onboarding

A marketplace lives or dies on supply, so this page has to answer the questions a would-be seller asks before they hand over bank details.

  • Who can sell Long text, requiredThe rules for becoming a seller: individuals or businesses, countries, minimum stock, any categories that need approval. Write it as you would tell a seller over the phone.
  • Seller verification steps Long text, requiredWhat a seller has to submit and what you check, such as identity, business registration or bank account. Check the rules where the client operates before naming any specific document.
  • Seller agreement File upload, requiredThe current terms a seller accepts at sign-up. If the terms are still being drafted, send the latest draft and name the person who approves the final version.
  • Seller success story Long textOne real seller, a short paragraph about what they sell and what changed for them since joining. Get their written agreement to be quoted before it goes on the site.
  • Seller portrait Image uploadA photo of that seller at work or with their products, at least 1500 pixels on the short side. A phone picture in good light is fine.
  • Permission to name sellers Yes or no, requiredConfirm you may show seller names, shop names or logos on the marketing pages. If the answer varies by seller, say who keeps the list.

Fees and payments

Fees are the first thing a seller checks and the last thing a founder wants to publish, so this page tends to stall on a decision rather than on content.

  • Fee schedule Long text, requiredEvery charge in one list: commission, listing fee, payment processing, subscription. Give the rate or amount, who is charged and when.
  • Who pays the commission Single choice, requiredState which side the platform charges. The pricing page and the checkout summary both repeat this wording.SellerBuyerSplit between both
  • Payment provider Single choice, requiredThe service that holds and moves the money. Its logo and terms have to appear on the site in some cases, so confirm the choice is final.Stripe ConnectPayPalAdyenMangopayAnother providerNot decided yet
  • Payout timing Short text, requiredHow many days after a sale the seller is paid, and what can delay it. For example: 'Two business days after the buyer confirms delivery.'
  • Refund and dispute rules Long text, requiredWhat happens when an item does not arrive or is not as described: who decides, how long it takes and who bears the cost.
  • Countries and currencies supported Long textList where buyers can pay and where sellers can be paid out, if the two differ. The designer needs this for the currency selector and the footer.

Trust and safety

Strangers trade here, so visitors look for proof that bad actors are handled, and the page falls flat when it only repeats the word 'secure'.

  • Trust badges in use Multiple choice, requiredTick each check the platform actually performs today. The site only shows a badge if the process behind it exists.Email verifiedPhone verifiedID checkedBusiness registeredInsuredPayment protected
  • Review and rating policy Long textWho can leave a review, when, and what you remove. Include whether sellers can reply, since buyers read replies closely.
  • Prohibited listings Long text, requiredThe list of items or services that are not allowed. Your support team probably keeps one already, so ask them for the current version.
  • Abuse report contact Short text, requiredThe address or form that goes to a person who acts on reports. Name the role that reads it, and how fast they aim to reply.
  • Buyer protection promise Yes or no, requiredAnswer yes only if a written policy backs it up. If yes, send the policy, because the exact wording on the site has to match it.

Help and support

Marketplaces get repeat questions from two audiences, so the help page works best when it is built from real support tickets rather than guesses.

  • Support email Short text, requiredAn address a person reads on working days. If buyers and sellers go to different inboxes, list both and label them.
  • Support hours and reply time Short text, requiredThe days and hours someone answers, and the usual wait for a reply. A promise the team cannot keep will be quoted back to them.
  • Top ten questions with answers Long text, requiredPull the ten most common tickets from the last month and write the answer your team gives. Split them into buyer and seller questions.
  • Help centre address LinkThe link to any existing help centre, such as Zendesk or Intercom. The site will link to it instead of copying its articles.

Brand and legal

Terms and logo files hold up the final week of most marketplace builds, because several people have to approve them.

  • Logo files File upload, requiredVector files (SVG, EPS or PDF) in full colour, in one colour and in white for dark backgrounds. Include the app icon if it differs from the logo.
  • Brand colours ColourThe main colour and any accent as hex codes. If the product interface already uses a palette, send the colour values from its stylesheet.
  • Brand fonts FontThe typeface used in the product and any licence details. If the app uses a free web font, the name is enough.
  • Terms of use for buyers File upload, requiredThe current buyer terms as a document. Name the person who has authority to approve changes, because the designer will not edit legal text.
  • Privacy and cookie notice approved Yes or no, requiredSay whether a policy covering both buyer and seller data exists and has been reviewed. If not, say who will supply it before launch.
  • Operating company name and number Short text, requiredThe registered legal entity that runs the marketplace, with its registration number and country. It goes in the footer and on the terms page.

What clients get stuck on

Seller terms nobody has written

Founders often run on a verbal deal with early sellers. Ask for the written terms in week one, and if none exist, get a named person to draft them, because the seller page cannot be finished without them.

Fee rules that live in one head

Ask the person who set the commission to list every charge on one page. If the answer changes between two conversations, the pricing is not settled and the pricing page should wait.

Listings too thin to design with

A young marketplace has a few good listings and many bare ones. Request a sample of the worst three as well as the best three, so the card layout survives real content.

Two audiences, one approver

Buyer copy and seller copy often have different owners, such as marketing and operations. Find out who signs off each side at the start, or the home page will be rewritten twice.

Payout and tax wording

The payment provider has rules for what the site must say about payouts and identity checks. Ask the client to confirm the wording with the provider, and keep their reply on file.

Copy the checklist

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

# Online marketplace website content checklist

## Home
- [ ] Marketplace name and tagline (Short text, required)
- [ ] What is bought and sold (Short text, required)
- [ ] Hero image (Image upload, required)
- [ ] Audience to lead with (Single choice, required)
- [ ] Primary button (Single choice, required)
- [ ] Live figures for the home page (Long text)

## How it works
- [ ] Buyer steps (Long text, required)
- [ ] Seller steps (Long text, required)
- [ ] Transaction flow (Single choice, required)
- [ ] Explainer video or walkthrough (Link)

## Categories and listings
- [ ] Category tree (File upload, required)
- [ ] Category images or icons (Image upload)
- [ ] Three real listings (File upload, required)
- [ ] Fields shown on a listing (Multiple choice, required)
- [ ] Listing approval method (Single choice, required)
- [ ] Search filters buyers rely on (Long text)

## Seller onboarding
- [ ] Who can sell (Long text, required)
- [ ] Seller verification steps (Long text, required)
- [ ] Seller agreement (File upload, required)
- [ ] Seller success story (Long text)
- [ ] Seller portrait (Image upload)
- [ ] Permission to name sellers (Yes or no, required)

## Fees and payments
- [ ] Fee schedule (Long text, required)
- [ ] Who pays the commission (Single choice, required)
- [ ] Payment provider (Single choice, required)
- [ ] Payout timing (Short text, required)
- [ ] Refund and dispute rules (Long text, required)
- [ ] Countries and currencies supported (Long text)

## Trust and safety
- [ ] Trust badges in use (Multiple choice, required)
- [ ] Review and rating policy (Long text)
- [ ] Prohibited listings (Long text, required)
- [ ] Abuse report contact (Short text, required)
- [ ] Buyer protection promise (Yes or no, required)

## Help and support
- [ ] Support email (Short text, required)
- [ ] Support hours and reply time (Short text, required)
- [ ] Top ten questions with answers (Long text, required)
- [ ] Help centre address (Link)

## Brand and legal
- [ ] Logo files (File upload, required)
- [ ] Brand colours (Colour)
- [ ] Brand fonts (Font)
- [ ] Terms of use for buyers (File upload, required)
- [ ] Privacy and cookie notice approved (Yes or no, required)
- [ ] Operating company name and number (Short text, required)

Questions about this checklist

Should a marketplace marketing site show real listings or sample content at launch?

Show real listings if there are enough to fill a page without gaps. If the marketplace is new, use a small honest set with a note that it is growing, and avoid invented sellers and fake reviews.

How do you write one home page for buyers and sellers?

Lead with whichever side is harder to recruit and give the other side a clearly labelled section lower down. A split hero with two equal pitches usually weakens both, and the first button should serve only one of them.

Does the marketing site need to match the app design?

It should share the logo, colours and type so visitors recognise the product after signing up. It does not need to copy app screens, and a separate marketing build is easier to change than the product.