How to Plan a Website Before You Build It

The Work That Happens Before Anyone Opens a Design Tool

Here's a pattern that plays out constantly in web projects. A business decides they need a new website. They hire a designer or agency. The designer starts creating mockups. Two weeks in, someone realizes the site structure doesn't match how the business actually sells. The homepage hero is optimized for cold traffic but 80% of their traffic is warm referrals. A key service category got buried three levels deep. The redesign costs more than the original build.

The root cause: no planning. Or rather, planning that jumped directly to "what should it look like?" without first answering "what should it do, for whom, and how?"

Planning is the least glamorous phase of a website project and the one most frequently skimped on. It's also the phase where the highest-value decisions get made — decisions that are cheap to change when they're still ideas and enormously expensive to change once design and development have started.

This guide walks through every meaningful planning activity for a website — from clarifying goals to mapping user journeys to documenting a content strategy. Do this work before anyone opens Figma or writes a line of code, and the build phase becomes genuinely straightforward.

Start with the Business Goals, Not the Website

The first question isn't "what pages should we have?" It's: what is this website supposed to accomplish for the business?

This sounds obvious but is consistently skipped. Business owners start thinking about website features and pages before they've articulated what success looks like. Without a clear definition of success, there's no way to evaluate whether design decisions, content choices, or structural decisions are the right ones.

Work through these questions explicitly:

What is the primary business goal of this website? Generate leads for a sales team? Drive direct online purchases? Build brand awareness and credibility? Acquire email subscribers? Drive foot traffic to physical locations? Book appointments? Educate prospects so sales calls are shorter? Most websites have one primary goal and several secondary ones — identify and prioritize them.

What does a successful website visitor do? Define the conversion action: fills out a contact form, calls the phone number, purchases a product, books a consultation, subscribes to a newsletter, downloads a resource. This is your conversion event, and everything on the site should be oriented toward making it happen.

What is the value of a conversion? Knowing that a lead from your website is worth $500 in expected revenue changes how much you should invest in the website and in optimization. A site that generates 5 leads per month at a $500 LTV delivers $2,500/month in value — worth considerably more investment than a site that's purely a brochure with no measurable conversion.

What does failure look like? A site that confuses visitors about what the business does. A site that ranks poorly and generates no organic traffic. A site that loads slowly on mobile and drives away 40% of visitors before they see anything. Defining failure scenarios helps prevent them.

Define Your Audience with Real Specificity

The second planning step: who are you building this for?

"Our customers" is not an audience definition. "Small business owners in service industries who are frustrated with their current website not generating leads and are considering building or rebuilding" is an audience definition. The specificity of your audience definition directly determines the specificity of your content, messaging, and design decisions.

Build one or two audience personas — composite representations of your actual target visitors. For each persona, document:

Demographics and context: Business type, industry, role, company size, technical sophistication. Not to stereotype, but to understand what knowledge and vocabulary they bring to the interaction.

Goals and motivations: What are they trying to accomplish? What problem are they trying to solve? What does success look like to them?

Pain points and frustrations: What's currently not working? What have they tried? What has failed them? What are they afraid of getting wrong?

Objections and hesitations: Why might they choose not to work with you? Price concerns, trust concerns, skepticism about whether you can solve their specific problem, uncertainty about the process.

Information journey: Where do they first encounter you? What do they know when they arrive at your website? What questions do they need answered before they'll take action?

This persona documentation becomes the filter through which every content and design decision gets evaluated. "Would this resonate with [persona]?" "Does this address [persona]'s main objection?" "Is this language that [persona] actually uses?"

Audit What Already Exists

If you have an existing website (even one you're fully replacing), audit it before planning the new one. Don't repeat mistakes you're already making, and don't abandon things that are working.

Analytics review: Which pages drive the most traffic? Which have the highest engagement? Which have the highest exit rate and where in the user journey do people drop off? If your blog is generating significant organic traffic, that's an asset to protect in the redesign. If your pricing page has a 90% exit rate, that's a conversion problem to solve.

Search Console review: What queries is Google showing you for? Which pages are ranking? Are there relevant queries you're not ranking for that represent opportunity? The keyword data in Search Console is your map of organic search opportunity.

Content inventory: List every piece of content on the current site. Categorize each: keep (valuable, current, worth preserving), update (good bones, outdated information), merge (overlapping with other content, consolidate), or delete (thin, outdated, no traffic, no value). This inventory informs which content carries forward and what needs to be created.

User feedback: If you have customer-facing team members, ask what questions they hear constantly. What do prospects always ask during sales calls? What do customers wish was clearer before they purchased? These are content gaps your new site should fill.

Map the Site Architecture

Site architecture — the structure of pages and how they relate to each other — is the planning deliverable most directly connected to both user experience and SEO.

A site architecture document (often called a sitemap, though it serves a different purpose than the XML sitemap you submit to Google) is a hierarchical map of every planned page on the site. For a simple business site:

Home
├── Services
│   ├── Web Design
│   ├── SEO Services
│   └── Website Maintenance
├── Portfolio / Case Studies
├── About
├── Blog
└── Contact

Building this map forces clarity about what content the site needs and how visitors will navigate to it. The questions this process surfaces:

Are related pages grouped logically? Services a visitor is likely to consider together should be navigable together. A visitor comparing pricing models shouldn't have to navigate to three different unrelated sections.

What's the maximum depth? Any page a visitor might need should ideally be reachable in three clicks from the homepage. Pages buried four or five levels deep are effectively invisible to most visitors.

What pages are missing? Planning the architecture often reveals content gaps — important questions visitors would have that no planned page addresses, key services that don't have their own page, comparison or FAQ content that would help conversion.

What's the navigation structure? The top-level navigation should map to the top level of the site architecture. Planning them together ensures consistency.

Define Each Page's Purpose

For each page in the architecture, define two things before anything gets designed or written: the goal and the primary audience.

A page brief for each page documents:

Page goal: What should a visitor do after seeing this page? What action should they take? What understanding should they leave with?

Primary audience: Which persona visits this page? What do they know when they arrive? What are they looking for?

Key messages: The 3–5 most important things this page needs to communicate. Not the headlines, but the underlying ideas the copy needs to convey.

Call to action: What's the primary CTA for this page? What's the secondary CTA for visitors who aren't ready for the primary one?

Success metrics: How will you know if this page is working? Time on page, click-through to the next step, form completion, specific conversion event.

This brief becomes the brief for both the writer (who needs to know what to write and what job the copy needs to do) and the designer (who needs to know what the page is trying to accomplish before making layout decisions).

Map the User Journey

A user journey map traces the path a visitor takes from their first touchpoint with your brand to the conversion event you're optimizing for. This is different from the site architecture — it's not a map of pages, it's a map of the visitor's experience over time.

A basic user journey for a service business might look like:

Awareness: Visitor discovers the business through Google search, a referral, or social media. What's their mental state? What problem are they trying to solve? What words would they use to describe it?

First contact: Visitor lands on the site — likely the homepage or a blog post. What do they see? What question are they trying to answer? What would make them stay vs. leave?

Evaluation: Visitor explores to evaluate whether this business is right for them. They check the services pages, the about page, the portfolio. What are they looking for? What would make them feel confident enough to take the next step?

Conversion intention: Visitor decides to reach out. They look for the contact form or booking option. What friction do they encounter? What might make them hesitate at this final step?

Conversion: Visitor submits the form, books the call, makes the purchase. What confirmation do they receive? What expectations are set about next steps?

Mapping this journey reveals gaps in the current experience and prioritizes where design and content investment has the highest impact. If most visitors drop off between the services page and contact, that handoff is the thing to fix — not the hero image.

Plan Your Content Strategy

Content planning is typically the most underinvested part of website planning — and the most consequential for SEO and conversion.

Core pages content: Every key page needs a content plan before the build. Who's writing it? By when? Has the copy been reviewed by someone with editorial judgment before it goes live? Waiting until the site is built to think about content leads to placeholder text that sits for months and launch delays while copy is written under pressure.

Blog and content marketing strategy: If you're investing in content marketing and SEO, plan the content strategy during the website planning phase — not after launch. Which topics are you targeting? What's the publishing cadence? What mix of content types (how-to guides, comparison posts, industry explainers)?

SEO keyword strategy: What terms do you want to rank for? Map target keywords to specific pages. Which pages are targeting which search intents? This mapping ensures that every important page is optimized for a specific search opportunity rather than trying to rank for everything generally.

Existing content decisions: Based on the content audit, which existing pieces are being migrated? Do migrated pages keep their URLs (ideal for SEO) or do they get new URLs (requiring 301 redirects from old to new)? These are decisions that need to be made before build, not discovered mid-launch.

Technical Planning: The Non-Glamorous But Critical Decisions

Several technical decisions belong in the planning phase because they affect architecture, cost, and timeline:

Platform selection: If you haven't already decided — WordPress, Webflow, Shopify, custom — this decision should be made during planning, not mid-design. The platform constrains design possibilities, determines developer requirements, and affects hosting and maintenance costs.

Integrations needed: CRM integration, email marketing, payment processing, booking systems, analytics, live chat — every third-party integration needs to be identified in planning. Some integrations affect platform selection (certain tools only integrate cleanly with certain platforms). Discovering an integration requirement mid-build causes delays and potentially requires architectural changes.

Performance requirements: Are there specific performance thresholds to hit? Target Core Web Vitals scores? Load time requirements? These goals affect decisions about image approach, JavaScript usage, and hosting choice.

Migration and redirect plan: If the site has existing content and search equity, which URLs change? Every URL that changes needs a 301 redirect mapped from old to new. Building this redirect map during planning allows it to be built into the launch rather than retrofitted as an emergency after organic traffic drops.

Define Success Metrics and Measurement

Before the site launches, decide how you'll measure whether it's working. This sounds like a post-launch concern but belongs in planning because it determines what analytics need to be set up at launch.

For each business goal identified in the first planning step, define a measurable metric:

"Generate leads" → leads generated per month (contact form submissions, tracked in Google Analytics as a conversion event)

"Build credibility" → time on site, pages per session, direct traffic growth (proxy metrics for trust)

"Improve SEO" → organic traffic growth, keyword rankings, impressions in Search Console

"Increase sales" → revenue attributed to the website, e-commerce conversion rate

These metrics should be configured in Google Analytics and Search Console before launch. A site that launches without configured conversion tracking is generating business value that it can't measure — and can't optimize because there's no data to learn from.

The Planning Deliverables Checklist

A complete website planning process produces these documents:

• Business goals statement (primary and secondary conversion goals, success metrics)
• Audience personas (1–2 detailed descriptions of target visitors)
• Content audit (if rebuilding an existing site)
• Site architecture / sitemap (hierarchy of all planned pages)
• Page briefs (goal, audience, key messages, CTA for each key page)
• User journey map (visitor experience from awareness to conversion)
• Content plan (who writes what, by when, keyword targets per page)
• Technical integration list (all third-party tools that need to connect)
• URL migration and redirect map (if rebuilding existing site)
• Analytics setup plan (what events and conversions to track at launch)

This sounds like a lot. For a simple brochure site, many of these are brief — a page goal can be one sentence, a persona can be one paragraph. For a complex site or a business with significant existing search equity, each deserves proportionally more attention.

The Bottom Line

Website planning is the work that makes everything else faster, cheaper, and more successful. It catches misalignments before they're built in. It ensures everyone working on the project shares the same understanding of goals, audience, and success. It prevents the expensive mid-project pivots that come from discovering that the site structure doesn't match the business's needs after the design is already done.

Spend 20% of your total project time on planning. It returns 3–5x that investment in reduced rework, clearer briefs, faster execution, and a site that actually achieves its business goals from day one.

At Scalify, discovery and planning are built into our process — we ask the right questions upfront so the site we build is the site your business actually needs.