What This Checklist Does
This checklist is the first ground-level guide under Prepare Website Inputs.
Its job is simple: define the website type and the minimum input pack before anyone starts choosing tools, arranging sections, or writing code.
The goal is to reduce guessing. A builder or AI coding agent should know what kind of website is needed, who it is for, what it should make the visitor do, and what is still unknown.
Steps
Guide
Choose The Website Type
A website type is not a design preference. It is the job description for the site.
Start with the closest type:
- landing page
- product site
- portfolio
- campaign page
- SEO blog
- subdomain page
- something more specific
The type does not need to be perfect forever. It needs to be clear enough that the first version can be built without guessing.
Write The Main Goal
Write one short sentence that explains what the website must do.
Good examples are direct:
- explain one service and collect demo requests
- sell one product
- collect leads for one campaign
- publish search-led articles
- show a career timeline
- support a separate sub-brand
If the sentence contains three different jobs, split them. The first version should serve the most important job first.
Define The Audience And Next Action
The website should be clear about who it is for and what should happen next.
Answer these questions:
- Who is the primary visitor?
- What problem or need brought them to the website?
- What should they do next?
- What should they not be distracted by in the first version?
This step protects the website from becoming a generic collection of sections.
Collect The Content Inputs
Collect only the content needed for the first useful version.
Use this short list:
- key message
- page names
- existing copy
- proof points
- FAQs
- calls to action
- important source links
If content is missing, mark it as unknown. Do not ask the builder or AI coding agent to invent business claims, pricing, testimonials, legal wording, or product details.
Collect The Asset Inputs
Assets help the website feel specific instead of generic.
Collect what already exists:
- logo
- colors
- fonts
- images
- icons
- screenshots
- UI references
- examples of websites you like
If assets are missing, write what is missing. Missing assets are normal at this stage.
Set The First Scope
This is where most website projects become too big too early.
Keep the first version small:
- Which pages are required?
- Which forms are required?
- Which integrations are required?
- Which features can wait?
- Which decisions are blocked?
The smaller the scope, the easier it is to produce a clean first result.
Check The Build Path Fit
Choose the build path after the website type is clear.
A small landing page can use a no-code builder, static HTML, or a simple React/Next.js build. A content-heavy site needs reusable article structures, metadata, internal links, and a publishing workflow. A commerce site needs checkout, payments, inventory, and order logic from the start.
Before the type is clear, tool comparison is mostly guessing.
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
- known assets
- unknowns
- preferred build path if known
Example:
This is an SEO blog for business operators researching practical AI workflows. The main action is to read related guides and discover AI-Nikita. Content will be updated weekly. Unknowns: final keyword list and two banner images. 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 technology choice.
If content changes often, plan a reusable content structure. If content is fixed, keep the build lighter.
The brief looks complete but hides unknowns.
Add an unknowns list. Missing business, legal, content, asset, and technical decisions should stay visible.
Return to the Main Guide?
Main guide
Prepare Website Inputs
Website Input Checklist
Handoff checklist
Use this checklist before building the website.
#### Website Type
* Type:
* Example: landing page / product site / portfolio / campaign page / SEO blog / subdomain page
* Reason for this type:
* Example: one offer, repeated publishing, separate sub-brand, product explanation
#### Goal
* Main goal:
* Example: explain the service and collect demo requests
* Primary audience:
* Example: startup founders, HR managers, local customers, business operators
* Next visitor action:
* Example: book a call, submit a form, read a guide, download a file
#### Content
* Key message:
* Example: we help companies automate reporting with AI
* Required pages:
* Example: Home, Services, Cases, Blog, Contact
* Existing source content:
* Example: old website copy, Google Docs, Notion notes, pitch deck
* Missing content:
* Example: testimonials, pricing explanation, FAQ answers, product details
#### Assets
* Logo:
* Example: SVG logo or PNG logo
* Colors:
* Example: black, white, orange accent
* Images:
* Example: founder photo, product screenshots, generated thumbnails
* UI references:
* Example: websites with section or layout ideas you like
#### Scope
* Must-have for MVP:
* Example: homepage, contact form, basic metadata, mobile layout
* Can wait:
* Example: login, payments, dashboard, advanced animations
* Blocked or unknown:
* Example: legal copy missing, final keywords unknown, assets not approved
#### Handoff Sentence
* Final sentence:
* Example: This is a [website type] for [audience]. The goal is [goal]. The visitor should [next action]. The first version must include [must-have scope]. Unknowns are [unknowns].
If an answer is missing, mark it as unknown. The website builder or AI coding agent should not invent critical business, legal, content, asset, or technical decisions.