Price testing for no-code sites: test prices on Webflow, Framer and Carrd with checkout links

Price testing for no-code sites: test prices on Webflow, Framer or Carrd with one hosted checkout link per price, and know the one limit before you start.

Short answer

Create one hosted checkout link per test price in Stripe, Polar, Lemon Squeezy or Dodo Payments, paste them into Leverprice and point your Buy button at the Leverprice link. Each visitor who clicks gets one price and lands on its checkout. The limit: your page can't show the tested price, so buyers see it at checkout.

  • No code and no script on your site: the Buy button points to a Leverprice link that picks a price and redirects to its checkout.
  • Your page can't display the tested price, so take the number off the page while the test runs.
  • Visitors join the test when they click Buy, so the test compares prices among people who reached checkout.
  • Crawlers and link previews that follow the Buy link always get your standard price's checkout.

If your product page runs on Webflow, Framer, Carrd or a static host, the price is a number typed into the page and the Buy button links to a hosted checkout. To change it, you make a new checkout link and compare this month's sales with last month's, which mixes the price with everything else that changed in between.

Leverprice's no-code mode turns that into a real split test, with no code and no script added to your site.

How does price testing work without a backend?

Through a link. You create one hosted checkout link per test price in your payment provider, paste them into Leverprice and point your Buy button at your Leverprice link. Then:

  1. A visitor clicks Buy and lands on the Leverprice link.
  2. Leverprice assigns them one of your prices and remembers it with a signed first-party cookie on its own domain, so clicking again gives the same price.
  3. It redirects them to that price's checkout link with signed attribution attached.
  4. When they pay, your provider's signed webhook tells Leverprice which price made the sale.

The links can be Stripe Payment Links or hosted checkout links from Polar, Lemon Squeezy or Dodo Payments. Your site builder only needs a URL field on the button.

What can't a no-code price test do?

It can't show the tested price on your page. The price is picked when the visitor clicks Buy, so the page doesn't know it; the visitor sees it on the provider's checkout page. That has two consequences.

Take the hard-coded price off the page while the test runs. If the page says $19 and checkout says $29, buyers bounce, and the test ends up measuring their reaction to the mismatch. Describe what's included and label the button "Get it" or "Buy now".

Visitors join the test when they click Buy. Revenue per visitor here means revenue per click on Buy, so the result tells you which price earns the most from people who reached checkout. It can't count people who would have left your landing page over a price, because the page shows none.

What should a no-code site price test first?

A one-time product behind a single Buy button. It's the simplest setup, and all four providers confirm one-time sales through signed webhooks.

1. A template or plugin

Example: a Framer template or a Figma plugin license at $19, $29 or $39, using three Stripe Payment Links behind one Leverprice link.

2. A lifetime license for an app

Example: a Mac app or browser extension sold from a Carrd page for $29, $49 or $69, paid once. If you're weighing a lifetime offer against a subscription, lifetime deal pricing covers the trade-offs.

3. A pre-order before you build

Example: pre-orders at $49, $79 or $99 for a product you haven't built yet. You learn what people pay, which tells you more than what they say in a survey. If you later refund some pre-orders, the refunds come off the price that sold them.

Which providers and site builders work?

Any site builder that lets you set a button's URL: Webflow, Framer, Carrd, or plain HTML on a static host. On the payment side, Stripe, Polar, Lemon Squeezy and Dodo Payments. You connect each with its webhook signing secret, which confirms purchases but cannot move money, and Leverprice never sees API keys or card data.

The Stripe and Polar integration pages cover setup. Lemon Squeezy closed to new stores on November 16, 2026 and stops processing payments on March 31, 2027 (announcement), so start a new site on one of the other three.

An AI assistant connected to Leverprice's MCP server at https://app.leverprice.com/mcp can create the product, start the test, read results and lock in the winner for you.

When you add a backend, move to the server SDKs for TypeScript, Python, PHP, Ruby or Go. Your server can then show the tested price on the page itself and serve regional prices per country, which checkout links can't do: they're made for standard prices only. Server-side price testing explains the setup.

How do you set up a no-code price test?

  1. Create a free project and add your product with its standard price.
  2. In your provider, create one hosted checkout link per price you want to test, for example Stripe Payment Links at $19, $29 and $39.
  3. Paste each link into Leverprice next to its price and copy your Leverprice link.
  4. In Webflow, Framer or Carrd, set the Buy button's URL to the Leverprice link and take the price off the page.
  5. In Payments, add the webhook URL Leverprice gives you to your provider, paste back the signing secret and start the test.

Which Leverprice plan fits a no-code site?

Free covers most single-product sites: a manual A/B split on one product and one experiment, up to $500 a month in tested revenue, with all four providers. Pro adds automatic optimization and unlimited tested revenue for $29 a month or $199 a year (about $17 a month), and covers up to 20 sites. Lifetime is $299 once for everything in Pro, with 50 spots. The pricing page has the details.

Frequently asked questions

Why can't my page show the tested price?

Because the price is chosen when the visitor clicks Buy, on Leverprice's link, and there's no Leverprice script on your page to fetch it. The visitor sees the price on your provider's checkout page.

Does a returning visitor see the same price?

In the same browser, yes: a signed cookie on Leverprice's link domain keeps their price. No-code mode has no user id, so the same person on another device can be assigned again, possibly to a different price.

No. Crawlers and link previewers that follow your Buy link get your standard price's checkout and are never enrolled, and prefetches of the link aren't counted. Does A/B testing prices hurt SEO? covers the search side.

Can I test a subscription price from a no-code site?

Yes on Polar, which verifies a subscription's first payment through its signed webhook. Stripe verification covers one-time Checkout Sessions only and Dodo Payments verifies one-time payments only, and a no-code site has no server to report a sale with trackPurchase(), so sell one-time products through those two.