Most companies planning a new website think of "requirements" as something the developer hands them: a scope document, a quote, a timeline. Fewer plan for the requirements that run the other way — what the developer needs from the company before a single page can go live. That gap is the single most common reason a quoted six-week build quietly becomes a four-month one, and it has nothing to do with code.
Why "we're waiting on content" is the real delay, not the build itself
Industry write-ups on why web projects run late consistently point to the same root cause, and it isn't technical. As one project-delivery breakdown puts it plainly: most website projects don't get delayed because of technical problems — they get delayed because of slow client communication. Specifically, "it's the waiting. Waiting for the right images. Waiting for the approved copy. Waiting for someone to confirm which phone number goes in the header." A development team can usually design, build and launch quickly once it has everything it needs; the bottleneck almost always sits upstream of the build, in the handover. This checklist covers what to hand over — for the habits that keep the back-and-forth itself from eating the timeline, see the #1 reason website launches get delayed, and how to avoid it.
The core pre-build checklist
- Written content, page by page — final copy is ideal, but a rough bullet-point brain-dump per page is enough to start; a development team can shape it into finished copy.
- Images — feature and product/service photography — a strong hero shot per key page, plus supporting photography; stock imagery can fill genuine gaps, but real photography always reads as more credible.
- Logo and brand assets — vector logo files (SVG), a favicon-ready square version, and brand colours/fonts if they already exist.
- Confirmation of usage rights — for every image, testimonial, or piece of copy supplied, who actually owns it and can confirm it's clear to publish.
- Certifications, registrations and awards — anything the business holds that's relevant to display, with proof available if a visitor (or Google) ever needs to verify it.
- Existing trust signals — Google Business Profile reviews, client testimonials, case studies, and social proof already earned, ready to carry into the new site rather than start over.
Images and copyrights: who actually owns what's on the page
A website is built from material that came from somewhere — a client's own photography, a licensed stock library, a designer's original artwork, a logo commissioned years ago from a different agency. Ownership of each of those pieces doesn't transfer automatically just because it ends up on a new site. Whoever supplies an image, a piece of copy, or a certification logo to a development team is the party responsible for confirming the right to use and publish it — the agency building the site isn't in a position to independently verify third-party ownership on the client's behalf. Getting this sorted before build, not after launch, avoids the far more expensive version of this conversation: a takedown request or a licensing dispute on a page that's already live and already ranking.
| Field | What to include | Why it matters |
|---|---|---|
| File name | Short, descriptive, lowercase with hyphens | Descriptive filenames are themselves a minor on-page SEO signal, and prevent mix-ups during handover. |
| Page / section | Which page and sub-section the image belongs to | Removes back-and-forth guessing where each asset should be placed. |
| Rights confirmation | Owned, licensed stock, or third-party with permission | Protects both sides if a usage question ever comes up after launch. |
| Format | JPG/PNG for photos; SVG or PNG for logos and diagrams | Keeps file sizes and quality consistent across the finished site. |
Certifications and trust badges: proof, not decoration
ISO registrations, industry-body memberships, safety or quality certifications, and awards all function as visual shortcuts to credibility — a visitor doesn't have to read a paragraph to understand "this business has been independently checked by someone." That only works if what's displayed is current and genuine. A certification logo left up after it's expired, or a badge for a body the business never actually joined, does more damage than skipping it entirely once a visitor — or a competitor — notices.
GMB reviews and client testimonials — different playbooks for old and new companies
This is the one part of the pre-build checklist that genuinely splits into two different approaches, depending on whether the company is already established or just getting started. Around 95% of consumers check reviews before choosing a business, and 53% trust them as much as a personal recommendation — which makes existing trust content one of the highest-value things an established company can hand over, and one of the hardest things a brand-new company can fake convincingly.
If the company already exists
Pull the strongest Google Business Profile reviews, real client testimonials (with names, and photos if permission is given), before/after results or case studies, and any press or client logos already earned. This is existing proof — the job is presenting it well, not creating it from nothing.
If the company is new
Lean on what's genuinely true instead: the founder's real background and experience, transparency about process and pricing, clear guarantees, and honest "why us" content. Real reviews will come — until they do, overclaiming trust that hasn't been earned yet usually reads as less credible, not more.
How incomplete pre-build content becomes an SEO problem
This isn't only a scheduling issue. Thin, generic, or placeholder content at launch is exactly what weak E-E-A-T — Experience, Expertise, Authoritativeness, Trustworthiness — looks like to Google. Current guidance on demonstrating E-E-A-T points to concrete, checkable signals: real testimonials and reviews, clear contact information, a genuine About page, transparency about who created the content, and a published privacy policy — the same items on the checklist above, not a separate SEO task bolted on afterward. The gaps that make a stranger distrust a business — no reviews, stock-only photography with no real proof behind it, no verifiable contact details — are the same gaps that make a page less likely to be cited accurately in an AI-generated answer, since Generative Engine Optimization depends on exactly this kind of self-contained, verifiable content to cite in the first place. A complete pre-build handover is the first SEO decision a company makes on a new site, before a single keyword is targeted.
Where Apensia fits into this
Apensia is a Chandigarh-based web development, SEO and digital marketing company, founded in 2015 by Kuldeep Chandel, who has worked in IT since 1995. Every project here starts with exactly this kind of structured pre-build request — a page-by-page content and image checklist, a clear note on what can simply be referenced from an existing site rather than rewritten, and a defined format for how images should be submitted — so the build itself starts on schedule instead of on guesswork.
FAQ
What does a web development company need from a client before starting?
Page-by-page written content (or at least rough notes to work from), photography or approved stock images for each page, logo and brand files, any certifications or compliance badges the business wants displayed, and confirmation of who holds the rights to use everything supplied. For an existing company, its Google Business Profile reviews and client testimonials matter too, since these get carried into the new site as trust signals.
Why do website projects get delayed so often?
Far more often by slow client communication than by technical problems — specifically, waiting on approved copy, final images, and small confirmations like which phone number or address goes on the site. A web development company can usually build and launch quickly once it has everything it needs; the bottleneck is almost always the handover of content, not the build itself.
Do I need to provide certifications and trust badges for my website?
If the business holds relevant certifications, ISO registrations, industry memberships, or awards, yes — these are concrete trust signals that Google's own quality-rater guidance associates with trustworthiness, and they matter to human visitors deciding whether to do business with an unfamiliar company. Any certification displayed should be current and something the business can actually produce proof of if asked.
How do GMB reviews and testimonials affect a new website?
For an already-established company, existing Google Business Profile reviews and client testimonials are some of the strongest trust content a new site can carry over, and around 95% of consumers check reviews before choosing a business. A brand-new company without a review history yet needs a different approach — founder background, process transparency, and clear guarantees, until real reviews accumulate.
Who owns the copyright to images and content on a website?
Whoever holds the rights to the original material — the client, if it's their own photography or writing, or a licensed stock provider if it's purchased stock. A client supplying images or copy to a web development company is responsible for confirming it has the right to use and publish that material; the agency building the site is not in a position to verify third-party ownership on the client's behalf.
How does missing pre-build content affect SEO?
Directly. Thin, generic, or placeholder content at launch is exactly what weak E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) signals look like to Google, and the same gaps that hurt a human visitor's trust — no reviews, no real photography, no verifiable contact details — are the same gaps that make a page less likely to be cited in an AI-generated answer. A complete pre-build handover isn't just a timeline issue; it's the first SEO decision a company makes on a new site.
None of this is about perfection before launch — a rough draft of every item above beats a polished version of half of them, since a development team can shape rough content into something finished far faster than it can invent facts, photography or reviews that don't exist yet. The companies that launch on schedule are usually the ones that treated this list as their first deliverable, not their last.
Media contact: apensiapr@gmail.com · +91 81468 55589
Sources: REM Web Solutions — The #1 Reason Website Launches Get Delayed · Search Engine Journal — Google E-E-A-T: What Is It & How To Demonstrate It · DemandSage — Online Review Statistics 2026 (citing BrightLocal consumer survey data, as already used on this site's own trust & review listings post). Accessed September 26, 2026; guidance and figures change as sources update them.