SaaS website design that carries a buyer from search to signup

On a software company’s site, a visitor can read the pricing page, check that you connect with a tool they already use and start a trial before anyone on your team hears from them. SaaS website design plans that path page by page, from the first search to the signup. Below is how we would plan, write, build and run a site for a software company, what California’s renewal law changes on the pricing page, plus what US agency price pages and guides show a build costs.

Who is SaaS website design for?

The work fits three stages of a software company:

• Before or just after launch: a small site that says what the product does, who it is for and how to try it, built to grow a page at a time.
• Growing: feature, integration and comparison pages, docs, customer stories cleared by the customers in them, and a pricing page that keeps up with the plans.
• Replacing an older site: years of posts, docs and links moved to a new build without losing what the old addresses earned.

Web design for startups follows the method behind all our Web Design work; this page is about what changes when the thing you sell is software. The renewal rules quoted below are California’s, and a company that sells into other states checks their rules with its counsel.

What does a SaaS website need beyond a home page?

Each page type does one job for a buyer comparing tools:

SaaS web design decides which of these exist at launch and which wait until the product and the search data call for them. A page with nothing true to say yet stays off the plan.

How should the pricing page show renewal and trial terms?

California’s Automatic Renewal Law, as the Attorney General summarizes it, requires a business to get a consumer’s express affirmative consent to auto-renewal or continuous-service terms before charging, and lets anyone who signed up online cancel online at will. It covers consumer plans that renew or run until cancelled, and free trials that become paid plans unless the consumer cancels in time. The alert adds that amendments effective July 1, 2025 made the law stronger.

On the page, we would put those terms where the buyer decides:

• Beside the button that starts a plan: the price, how often it is charged and how long each renewal period runs.
• On a trial: how long it lasts, what it turns into and when the first charge falls.
• On cancelling: a route that matches how people sign up, so an online signup has an online way out.

Whether a plan sold only to businesses falls under the law is for your counsel to say. The pricing, signup and cancellation pages carry the wording you or your counsel supply, and building them doesn’t by itself settle whether your plans meet the law. Our SaaS industry page sets out the notice windows the Attorney General’s summary lists.

Can the marketing site and the app share one domain?

Yes. The marketing site can sit at the main domain with the app and the docs on subdomains, or the docs can sit in a folder of the main site. Search Console sees all of it either way: a Domain property covers a domain with every subdomain and both http and https, and verifying one takes a DNS record.

Pages meant only for signed-in users get a noindex rule, and so does the login page. Google drops a page carrying that rule from Search even when other sites link to it. The rule only works where Google can crawl the page and read it, so robots.txt has to leave those pages open.

Why does the marketing site render before it reaches the browser?

When JavaScript builds a page’s words in the browser, a crawler has to run that code before it can read them. Google’s JavaScript SEO guide still calls server-side or pre-rendering a great idea: it makes a site faster for users and crawlers, and not all bots can run JavaScript.

So the marketing site we build sends every page to the browser already rendered. Your app stays as it is, on its own code and its own release schedule. If the current site runs on WordPress, Webflow or a site builder, the new build replaces it and the old addresses are redirected, as set out below.

Who writes the words on a SaaS site?

We do, working from the search research and from product facts your team checks. Software facts move as the product ships: a plan is renamed, a limit changes, an integration is retired. So each page lists the facts it depends on, and your product lead checks them on the preview before launch.

Some claims need more than a check:

• Numbers about customers or usage: only with a dated source you can show us.
• Customer logos and quotes: only with each customer’s permission, and quotes in their own words.
• Security and uptime statements: only the practices and figures you document.

How is a SaaS site planned from search data?

The page plan starts from what buyers type: the problem they want solved, the category name they use, the tools they want you to work with and the rivals they’re weighing. For each search worth a page, we look at what Google shows for it today, which pages rank and what they leave out, then give one page that job.

Startup web design has less to go on, because a new product has little search history and its category may still be settling on a name. Startup website design therefore begins with a smaller plan built on the problem and the category, and it grows as Search Console shows which searches bring people in. Our SaaS SEO page covers that work after launch.

What structured data does a software site carry?

Structured data is markup that tells search engines what a page describes. We would add organization markup across the site and SoftwareApplication markup on the product page. Google’s guide gives that markup’s purpose as to better display your app details in Google Search results, and it lists three required properties: the app’s name, its price in an offer (0 where the app is free to use) and a rating or review. It recommends the application category, such as BusinessApplication, and the operating system.

We would mark up a rating only from reviews your customers have actually left. Until there are some, the product page carries the organization markup and waits on the software markup.

How do signups reach your CRM and analytics?

Each signup and demo request should carry the page where the visitor began, which tells you the pages that bring in trials. That is why both are counted as events in your analytics from the first day.

Where your CRM accepts records from outside, each request goes to it with its page attached. Where it doesn’t, the request reaches your inbox behind spam protection. Getting the app’s own events into the CRM, such as a trial turning into a paid plan, is software work, and our Custom Software page covers it.

What happens to your current site and its addresses?

Google’s guide to moving a site to new URLs sets out the order: prepare the new site and test it, prepare a URL mapping from the current addresses to the new ones, then configure the server to redirect from old to new. It says 301 and other permanent redirects don’t cause a loss in PageRank and that submitting a sitemap can help Google discover the new addresses sooner, and for a small or medium site it recommends moving all the URLs at once rather than one section at a time. For a medium-sized site, it adds, Google can take a few weeks or more to start showing the new URLs in place of the old.

A software company’s map covers more than the marketing pages: blog posts, docs, changelog entries and old pricing pages can all have links pointing at them. We map each one before launch and redirect it. The domain stays registered where it is, and we change only the records that point it at the new site. The full sequence is on our website migration page.

Can AI search tools read a SaaS site?

Google says there are no additional requirements to appear in AI Overviews or AI Mode: to be shown as a supporting link, a page must be indexed and eligible to be shown in Google Search with a snippet, which the build above aims for. A site owner can also opt out. Search Console’s Search generative AI control, which Google says it had rolled out to every website worldwide by August 31, 2026, is set to Include by default; set to Exclude, it keeps the site’s links and content out of AI Overviews, AI Mode and Discover’s generative AI features. Google says the control isn’t used as a ranking or inclusion signal affecting other parts of Search.

With every page rendered, marked up and open to AI crawlers, a software site is easier for AI answers to find, read and cite. Still, the AI tool decides whether an answer names your product, and no one can promise that it will. There’s more on that work on our GEO page.

What live site shows how we build?

We rebuilt the Alvy Logistics website in our own system: 70 pages on Astro, which we still run. Alvy is owned by our co-founder Noah Alvarez, and DSI is an Alvy company. Because it sells freight services, its site shows how we build and run a website in general; the pages we would build for a software company are the ones this page sets out.

What does a SaaS site need after launch?

The site keeps changing with the product: features ship, plans are renamed, prices move and integrations retire. The pricing page has to say what the billing system charges, so a change to a plan is a change to the site as well.

For what moves a build’s price at each level, see our website design cost page. Midnite Systems was formed in 2023, and today we work remotely with businesses across the US, out of our office in Valencia, California. When you’re ready, book a 15-minute call with Nicolas Perez or Noah Alvarez, our co-founders.