Website Type First
Before building a website, define what kind of website you are making.
A website type is not a design style. It is the job description for the site. A landing page, product site, portfolio, campaign page, SEO blog, and subdomain page all need different content, pages, forms, integrations, and build logic.
The type does not need to be perfect forever. It needs to be clear enough that the first version can be built without guessing.
Landing Page
A landing page is built for one clear action.
It usually has one page, one message, and one main CTA. The goal is to explain the value quickly and move the visitor to the next step: book a call, join a waitlist, download something, or start signup.
Expected inputs:
- main offer
- target audience
- primary CTA
- proof points
- form fields if needed
- analytics or ad tracking tools
Usually needed: GA4, Microsoft Clarity, CRM, email notification, or ad pixel.
Usually not needed at first: blog, login, dashboard, complex navigation, or many secondary pages.
Product Site
A product site explains and sells a product.
It needs more structure than a landing page because visitors may need to understand features, pricing, use cases, screenshots, FAQs, and trust signals before acting.
Expected inputs:
- product description
- target customer
- core features
- pricing logic
- signup, checkout, or demo flow
- FAQs
- legal pages if needed
Usually needed: analytics, CRM, payment tool, calendar booking, product screenshots, and conversion tracking.
Usually not needed at first: advanced comparisons, resource center, public roadmap, or community features.
Portfolio
A portfolio proves capability.
It is used by freelancers, agencies, studios, consultants, and professionals who need to show work and create trust.
Expected inputs:
- selected projects
- short case studies
- services or skills
- about section
- testimonials
- contact method
Usually needed: contact form, email link, calendar link, analytics, and image assets.
Usually not needed at first: blog, login, newsletter, complex filters, or large CMS.
Campaign Page
A campaign page supports one temporary push.
It can be used for a launch, event, offer, waitlist, recruitment campaign, or awareness campaign.
Expected inputs:
- campaign goal
- campaign message
- target audience
- deadline if relevant
- CTA
- form or registration flow
- follow-up process
Usually needed: analytics, ad tracking, email marketing, CRM, payment, or event integration.
Usually not needed at first: full website rebuild, blog, large navigation, or evergreen content system.
SEO Blog
An SEO blog is built for repeated publishing.
It needs reusable article templates, categories, metadata, internal links, fast pages, and a structure search engines can understand.
Expected inputs:
- content categories
- article template
- publishing frequency
- author details
- metadata rules
- internal linking logic
- lead capture method if needed
Usually needed: CMS or markdown workflow, GA4, Google Search Console, sitemap, schema, and newsletter or CRM integration.
Usually not needed at first: comments, accounts, gated content, advanced personalization, or complex search.
Subdomain Page
A subdomain page gives one function its own space.
Examples: app.company.com, docs.company.com, help.company.com, careers.company.com, or partners.company.com.
Expected inputs:
- subdomain purpose
- required pages
- connection to main website
- ownership
- tracking setup
- login or access rules if needed
- technical routing
Usually needed: analytics, authentication, CMS, help desk, ATS, documentation tool, or product backend.
Usually not needed at first: duplicate main website content, broad navigation, or unrelated marketing pages.
Something More Specific
Some websites are closer to systems than pages.
Examples: directory, marketplace, dashboard, client portal, e-commerce store, learning platform, booking platform, or internal tool.
Expected inputs:
- user roles
- core actions
- required screens
- forms
- data structure
- integrations
- permissions
- admin needs
Usually needed: database, authentication, payments, search, storage, CRM, email, analytics, or third-party APIs.
Usually not needed at first: advanced automation, complex reporting, recommendation engines, or non-essential settings.
Write The Handoff Sentence
Finish with one compact sentence that a website builder or AI coding agent can use.
Use this structure:
- website type
- primary audience
- main action
- content update frequency
- must-have pages
Example:
This is an SEO blog for business operators researching practical AI workflows. The main action is to read related guides and discover in-house solutions. Content will be updated weekly. Build path should support reusable article templates, metadata, internal links, desktop and mobile banners, and fast static pages.Be Aware
The project starts with a tool name instead of a website type.
Pause the build and write the website job first. Tool choice should support the job.
The site tries to be a landing page, blog, product site, and portfolio at the same time.
Choose the first-release type. Put later site expansions into a separate backlog.
The content plan does not match the website type.
If content changes often, plan a reusable content structure. If the site is campaign-led or one-page, keep the build lighter.
Return to the Main Guide?
Main guide
Prepare Website Inputs
Website Type Handoff
Copy / paste
Define the website type before building.
Use this structure:
- Website type:
- Primary audience:
- Main visitor action:
- Content update frequency:
- Must-have pages or screens:
- Usually needed integrations:
- Usually not needed in the first version:
Write one compact handoff sentence for a website builder or AI coding agent.
Rules:
- Do not mix several website types into one first version.
- If the type is unclear, ask me to choose between landing page, product site, portfolio, campaign page, SEO blog, subdomain page, or a more specific system.
- Do not invent business, legal, content, asset, or technical decisions.