Website conversion rate: from the visit to the signup

Conversion rate is signups divided by visits. Use real numbers from your site.

Conversion rate = (Number of conversions) / (Number of visits)

Decide what counts as a conversion on each page. Then calculate by page and by source. Sitewide averages hide the work.

Worked example: /pricing had 1200 visits in 28 days. If about one in ten signed up, the conversion rate would be roughly ten percent. That example is typical, not your measured data. Track this by device too. Mobile and desktop behave differently on pricing pages as of 2026.

Choose one primary conversion per page. You can track secondary actions, but do not promote them on the page if they distract from the primary goal.

If revenue matters on first touch, add Purchase as a conversion on the checkout path. Keep signup and purchase as separate events. You will need both rates later.

People arrive with different intent. A search for "kanban software" will convert on /pricing if your offer fits. A search for "what is kanban" will not. That search needs an educational page with a soft CTA. Expect a lower rate there and judge it on assisted conversions over time, not last click only as of 2026.

Source changes the baseline. Paid brand will convert higher than cold social. Direct on /pricing means someone already decided. Do not compare that to traffic from an educational post. Segment by landing page and source before you judge the rate. Use the same 28 day window when you compare pages to avoid seasonality noise on a small site.

Before you rewrite a page, check the query and the referrer. You must match the promise they saw before the click. This is where most leaks happen on small sites.

1. 1

   Check the landing page queries

   Open your Search Console Performance report. Filter by Page for the landing page, then view Queries. Note the top terms and their intent. If you see "what is" queries on /pricing, you have an intent mismatch.

2. 2

   Open the referring page

   If traffic comes from your own page, read the copy and CTA there. If it comes from a partner or a directory, click through the live link. Write down the exact promise they saw, like "Free kanban boards, no card limits".

3. 3

   Compare promise to fold

   Load your landing page in a clean browser. The above the fold area must restate the same promise in the same words. If not, rewrite the headline and subhead.

4. 4

   Trace user flow

   Use your analytics to see Next page from the landing page. If most users bounce to /features, your pricing page is doing feature work. Move that proof into /pricing.

Do the simple work first. Make the fold carry the promise, proof and one action. This lifts conversion on most small product pages without design sprints as of 2026.

• Headline: repeat the searcher’s words. If the query was "kanban software", use "Kanban software for small teams" on /pricing.
• Subhead: name the job and the outcome in one sentence. Example: "Plan sprints, limit WIP, ship on time."
• Primary CTA: one button. The text says the action, not fluff. "Start trial" beats "Get started" most of the time.
• Proof: place one tight row, like "Trusted by 1200 teams" plus three small logos. No carousel.
• Friction cuts: show SSO if you have it, show "No credit card" only if true, say trial length.
• Speed: keep Largest Contentful Paint under 2.5 seconds. Defer analytics tags that are not needed before click.

Before: "Welcome to yourproduct.com, the leading platform for agile excellence" and two CTAs. After: "Kanban software for small teams" with one Start trial button and plan highlights. Expect a cleaner path and fewer stray clicks to the nav bar. Your fold should look boring to you and clear to a visitor in three seconds.

One page, one job. Your menu still exists, but the body gives one path. Remove ghost CTAs that skim intent away from the primary action. You will not lose users who want a demo or docs, they will find them in the nav or the footer.

• On /pricing keep only Start trial as a primary button. Move Contact sales to a text link under Enterprise.
• On blog posts use one CTA block that matches the topic. Do not stack "Download eBook", "Subscribe", and "Start trial" in one screen.
• On integration pages let Connect or Start trial be the only coloured button. Docs go in a calm link near it.
• On /guides/getting-started offer "Use this guide in-app" if the product is needed to finish the guide. That click should go straight to signup.

Write for the search that brings the visit. Use the query in the title, h1 and the first paragraph. Mirror the user’s language in the CTA. Then remove the steps that slow them down.

1. 1

   Map search intent to page sections

   For "kanban software" on /pricing, put plans, key features, and comparisons above testimonials. For "what is kanban" on /blog, define, show a simple board, then a light product pitch.

2. 2

   Answer objections inline

   Add a short FAQ block near the CTA with three real objections. Example: "Can I import Trello boards? Yes, upload JSON in Settings."

3. 3

   Show the path after signup

   Add a three step strip: "Create account, Create your first board, Invite your team". This makes the action feel smaller and raises clicks on Start trial.

4. 4

   Tighten the form

   Remove fields you do not need to start value. Keep email and password only if possible. Offer SSO if you have it. Make the button say "Create account".

Instrument at page and event level. You want visits, primary conversion, and the steps in between. Use the same names on all pages so reports stay clear. Do not rely on screenshots or memory later.

• Define events: view_pricing, click_pricing_cta, start_signup, signup_complete. Use consistent casing.
• Attach page context: page=/pricing, source=search, medium=organic, campaign if it is paid.
• Mark the primary conversion with a distinct event like signup_complete. Do not infer it from a pageview of /welcome if that page can be reached in other ways.
• Track form abandon: form_start and form_error with field names redacted. You want counts by field, not values.
• Log speed for the landing page: LCP, CLS, INP. Slow speed lowers conversion on mobile. Fix regressions before you A B test copy.
• Record device, viewport width and country. Segment rates by these before you compare copies.

Build a funnel report per landing page. Example: Pageview /pricing to click_pricing_cta to start_signup to signup_complete. If the biggest drop is to click_pricing_cta, change the fold. If the drop is in the form, fix the form. Tie wins back to the query mix in Search Console to avoid learning the wrong lesson from a traffic shift.

Change one big thing at a time on small sites. You do not have the traffic to test ten tiny tweaks in a week. Work in weekly cycles and read 28 day windows. Keep a change log in your repo and correlate with your rate chart before you celebrate or panic.

1. 1

   Set a baseline by page

   Pick your top five landing pages by signups. Record their last 28 days: visits, conversions, conversion rate, speed, top queries, top sources.

2. 2

   Ship the biggest fix first

   Lead with the fold rewrite on /pricing or the removal of extra CTAs. Do not mix with a pricing change. Price changes create noise that drowns copy tests.

3. 3

   Monitor for two cycles

   Wait two full 28 day windows unless you see a clear uplift with the same traffic mix. Seasonality and small numbers swing daily rates. Use cumulative charts.

4. 4

   Roll forward or revert

   If the rate holds up with a similar query and source mix, keep it and ship to similar pages. If not, revert and test the next biggest idea.

• Intent mismatch: ranking a how to article that lands on /pricing. Fix with a proper landing page that matches the query.
• Split attention: three CTAs on /pricing. Fix by picking one primary action and demoting the rest.
• Slow fold: a hero video that kills LCP. Replace with a static image and a short loop below the fold.
• Hidden fees: taxes or add ons only shown at checkout. Add a Pricing notes link near plans to set expectations.
• Form pain: required company size, phone, or team count. Remove or move to after signup when you ask to set up the workspace.
• Trust gap: no social proof above the fold. Add one proof line and three relevant logos only.
• Mobile pain: sticky chat widget over the CTA. Hide on small viewports or move it below the fold.