Budget, timeline, search visibility, and upkeep tend to arrive all at once when a site is being planned. This FAQ gathers fifty recurring client questions by theme so you can understand the choices before you commit.
The notes below are split into seven sections. Whether this is a first build or an update to an existing site, you can match each planning question to an answer and avoid a few wrong turns.
Budget and Cost (Q1–Q8)
Money is almost always the first question. These eight notes explain how quotes are built and how a yearly budget can be framed.
Q1: What does a website usually cost?
Price swings widely with scope. A corporate brochure site often falls between 80,000 and 300,000, while an online shop or a heavily custom system can pass 500,000. Page count, feature depth, design finish, and whether you need an editable admin area all move the quote.
A practical start is to write down what must actually be done before talking numbers. If page count and membership are still open, any figure is only a guess. For a breakdown, see how website costs are split.
Q2: Why do quotes vary so widely?
The gap usually comes from scope, technical depth, and design quality. Lower quotes often rely on ready-made templates, may skip basic search setup, and limit revisions. Mid and higher quotes more often include custom layout, feature development, and support after launch. Team experience, company size, and aftercare promises also show up in the price. Compare more than the total: look at long-term value.
Q3: Template versus custom pricing
Template projects often land between 30,000 and 100,000. A custom project can also start near 30,000, but the gap widens as features grow. Templates suit a tight budget and simple needs. Custom work fits a brand and real workflows better and leaves more room to expand. If you are still deciding, see template versus custom sites.
Q4: Which extra costs are easy to miss?
Items often left off the first quote include hosting, domain renewal, SSL, extra page design, stock-asset licenses, and maintenance after launch.
An “all-inclusive” offer looks attractive until language versions, certificates, or a homepage visual are billed separately, and the total can exceed a higher quote you declined. Before signing, ask for a written list of possible add-ons. For ways to avoid that trap, see how to control build costs.
Q5: What yearly fees continue after launch?
Yearly costs usually fall into three groups: hosting (about 3,000 to 15,000), domain renewal (about 500 to 2,000), and maintenance as defined in the contract. If you use a content system, core software and plugins still need regular updates to stay secure. Some teams bundle support, content changes, and security monitoring into an annual plan.
Q6: What first-year budget fits a small firm?
A small business can start with 80,000 to 200,000 for the first year. That range usually covers visual design, about 5 to 10 content pages, basic search setup, and a simple admin area. If funds are limited, finish the essential pages first and add features in stages. Spend where the site can actually create business. More on allocation is in how to plan the budget.
Q7: Can design fees be paid in stages?
Most teams accept installments. A common split is three parts: about 40% at signing, 30% when design is approved, and 30% at launch acceptance. Four-part or monthly plans also exist. Staging eases early cash pressure, but check for fees or interest, and write payment points and acceptance rules into the contract.
Q8: How to build well on a tight budget?
The key is to lock a short list of goals. Name the 3 to 5 outcomes the site must deliver, and postpone features you do not need yet. A mature content system can lower build cost. A solid template with selective adjustments is another compromise. Preparing copy and images yourself also cuts labor. A good site is not defined by spending the most; it needs a clear strategy.
Process and Timeline (Q9–Q15)
Knowing the sequence and where time is spent makes the partnership smoother. This is also a very common part of a build FAQ.
Q9: How does a typical project proceed?
A usual path has six steps: discovery, planning, visual design, front-end build, back-end integration, then testing and launch. Each step is normally confirmed before the next begins. From kickoff to launch, expect about 6 to 12 weeks. Step details are in the build process guide.
Q10: How long does a website take?
A simple brochure site takes about 4 to 6 weeks. A mid-size site with a blog or member area takes about 8 to 12 weeks. A complex shop or custom system may need 3 to 6 months.
What actually stretches the calendar is feature depth, revision rounds, how fast you reply, and whether assets are ready. Delays often come from missing materials or a changing decision maker, not only from the production team. Timeline is also the point most people want clarified first.
Q11: What materials should you prepare?
This step is often underestimated. Prepare a company profile and brand story, product or service descriptions, a vector logo file, high-resolution images, competitor sites worth referencing, a description of the audience, and the concrete outcomes you want. Copy written early shortens the schedule a lot. If assets do not exist yet, the team can often help with writing or photography, at extra cost.
Q12: How many design revisions are included?
The count belongs in the contract. Visual design commonly includes 2 to 3 larger direction changes. Collect feedback in one pass so scattered notes do not drag the schedule. Work beyond the agreed rounds is usually billed by time. Stating preferences and limits early reduces later back-and-forth.
Q13: What should be tested before launch?
Before launch, check at least: browsers (Chrome, Safari, Firefox, Edge), screen sizes (phone, tablet, desktop), key functions (forms, checkout, search), performance (load time and image compression), search basics (meta tags, sitemap, robots.txt), and security (SSL and firewall settings). These checks confirm the site works across environments.
Q14: Redesign or rebuild from scratch?
It depends on the old stack and how much must change. If the structure is outdated, not adaptable to screens, hard to maintain, or both features and visuals must shift sharply, a rebuild is usually cleaner. A visual refresh or small feature tweak is cheaper as a redesign. Redesign cost is often about 40% to 70% of a rebuild.
Unless the old site still has a separate content system, sensible URLs, and accumulated search value, forcing a redesign can cost more to maintain than starting over. See what to watch in a redesign.
Q15: How soon can a finished site go live?
After tests pass and content is confirmed, technical launch often takes 1 to 3 business days, including DNS, hosting deployment, and a final check. The real date often waits on your last review. Leave at least a week for small fixes. The first two weeks after launch are a watch period, and the team usually monitors how the site behaves.
Design and Features (Q16–Q25)
This section has the most questions, from responsive layout to the admin area.
Q16: What is responsive web design?
Responsive design lets the layout reflow with screen width so phones, tablets, and desktops all remain readable. It is not merely shrinking the page. Type size, image ratio, menus, and interactions are rearranged. Search engines already index the mobile version first, so responsive layout is a baseline, not a bonus. See an introduction to responsive design.
Q17: Is a mobile experience optional?
The answer is no. Most web browsing now happens on mobile devices. A site that is hard to read or use on a phone loses visitors and can also lose search rank. Current builds assume mobile first, and the phone experience should not trail the desktop.
Q18: Which features should a business site include?
A basic set usually includes an about page, product or service display, a contact form, a map, social links, and an editable admin area. Depending on the industry, you may also need booking, case studies, an FAQ, articles, or news. For a company site, a careers page is worth planning too.
Q19: Can you update content yourself?
Yes, and many people ask this first. It depends on having a content management system. Most modern sites run on platforms such as WordPress or Laravel, so you can add posts, swap images, and edit copy through a visual screen without writing code. Handover usually includes an admin walkthrough. Structural layout changes or new features should still go to an experienced team.
Q20: What is a CMS?
A content management system lets non-engineers edit text, images, and product data. Think of it as the site’s control panel. Common options include WordPress, Joomla, and a back office built for the project. Choose for ease of use, room to extend, and whether security upkeep is realistic. See building with WordPress.
Q21: Should pages use video or images?
Use both. Video explains a process and can hold attention; images load faster and are easier to scan. A homepage can use a 15- to 30-second clip for impact, while product pages should rely on strong stills. Do not autoplay sound, and provide an image fallback so a slow connection does not leave a blank page.
Q22: What must the homepage communicate first?
The homepage should say who you are and what you offer within a few seconds. It needs a clear headline, a button that points to the next step, and proof such as cases, coverage, or partners. Do not put everything on the homepage; send people to the right inner page.
Q23: What color rules should a site follow?
A useful split is 60-30-10: about 60% primary color (often the background), 30% supporting color, and 10% accent. Brand color should run through the site, and action buttons should contrast clearly with the background. Text-to-background contrast should meet the common accessibility mark of at least 4.5:1 so content stays readable.
Q24: Do you need live chat?
If the offer needs real-time answers, such as advisory work or business sales, live chat can raise conversion. Common options connect a messaging app, a social inbox, or a dedicated support system. If nobody can reply promptly, a widget that is always offline does more harm than good. A complete form and an FAQ page are the better fit.
Q25: How should multilingual sites be structured?
Two common paths are a multilingual feature inside the content system, or separate subdomains and subdirectories. For search, a subdirectory plus hreflang tells the engine how language versions correspond. Translation quality matters too. Have someone who knows the language review the text so machine translation does not drift from the meaning.
SEO and Marketing (Q26–Q33)
This section explains how layout, code, search, and promotion affect one another.
Q26: How does design affect SEO?
Code structure, load speed, mobile friendliness, URLs, and meta settings all shape how a search engine judges the site. A polished look with a weak technical base can be nearly invisible in results. Search work belongs in planning, not as a patch after launch. See building in a search-friendly way.
Q27: When will Google index a new site?
A new site is often crawled for the first time within 1 to 4 weeks, but a stronger rank usually needs 3 to 6 months of steady work. Submit a sitemap in Search Console, earn links from other sites, and publish original content on a regular cadence. A low early rank is normal. What matters is continuing to publish useful material.
Q28: Is SEO still needed after launch?
Yes, it is worth doing. Without a search foundation, the site is like a shop on a street nobody walks. Even a refined design wastes exposure if people cannot find it. Basics include keywords, meta tags, a content plan, and a technical check. Over time, unpaid search traffic usually costs less than ongoing ads. Start with factors that affect rank.
Q29: Does a blog help search rankings?
It helps a great deal. Publishing substantial articles on a steady rhythm is an effective content approach. Each piece can become an indexed page, raise the chance of being found, build topical credibility, attract citations, and give social channels something to share. Consider at least one article a week, roughly 800 words or more.
Q30: What are meta title and description?
The meta title is the blue headline in search results. The meta description is the gray summary under it. They do not directly set rank, but they strongly affect whether someone clicks. Keep the title around 30 to 60 characters and include the target term. Keep the summary around 70 to 155 characters and describe the page clearly. Every page should have its own title and summary.
Q31: Does speed affect search ranking?
Yes, and the weight is real. Core Web Vitals are ranking factors, covering load, interaction response, and visual stability. Past 3 seconds, more than half of mobile visitors may leave. Improvements include compressing images, browser caching, a CDN, and leaner code. Details are in the performance guide.
Q32: Do social links help a website?
Social links usually do not raise search rank directly, but the indirect effect is strong. Sharing increases exposure and direct visits. Content that spreads widely is also more likely to be cited by other sites. Put share buttons on the site and repost content on social channels. Platforms companies often use include Facebook, Instagram, LINE, and LinkedIn.
Q33: Why keep a Google Business Profile?
A Google Business Profile is a free tool that can place company details in search and on maps. For a business with a physical location, it is a key local-search tool. Fill in hours, address, phone, photos, and reviews, then keep the record current and reply to reviews to improve local visibility.
Technical Care (Q34–Q41)
Care after launch decides whether the site stays reliable. These are the questions asked most often in that area.
Q34: Is an SSL certificate required?
Yes. SSL moves a site from HTTP to HTTPS and encrypts traffic between the visitor and the server. Without a certificate, a browser may mark the site as not secure, and search engines treat HTTPS as a ranking factor. Cost ranges from free Let's Encrypt to several thousand a year. Many hosting plans already include a free certificate.
Q35: What if the site is compromised?
Once an incident is confirmed, take the site offline so damage does not spread, tell the host, preserve the current state for review, remove malicious content, and replace passwords and access keys. Then find and close the weakness and strengthen protection, such as a firewall and regular updates. If a maintenance contract exists, the production team should help with this kind of emergency.
Q36: How often should you back up?
Back up at least weekly. If content changes daily or the site takes orders, switch to an automatic daily backup. Include files and the database, and store copies somewhere other than the host, such as cloud storage. Keep at least 30 days of versions so you can restore a known-good state. Automatic backup is a basic item in any care plan.
Q37: How do you choose hosting?
Hosting is the server that stores the site so others can open it by URL. Compare data-center location (choose a region close to your visitors), bandwidth and storage, stability and speed, support quality, and price. A company site is better on cloud or managed hosting. Very cheap shared hosting often hurts speed and uptime.
Q38: How should you pick a domain?
A memorable domain is usually short, easy to say, and tied to the brand. Prefer .com or a common commercial suffix in your market. Avoid hyphens, numbers, and words that are easy to misspell. If the ideal .com is taken, add a place or industry word. Once a domain is in use, avoid changing it. A switch can hurt accumulated search value and what people remember.
Q39: Can a redesign hurt SEO?
Poor handling can cause a clear drop. The usual problem is a URL change that turns many old pages into missing pages. Keep existing URLs when you can. If they must change, point each old address to the new one with a 301 redirect. Export URLs and rank data before the change, then watch indexing and rank in Search Console afterward.
Q40: Is WordPress right for a company site?
Often yes, depending on the need. It is a widely used content system with many plugins and themes, and it fits content sites and small to mid-size company sites. The admin is approachable, resources are plentiful, and it can be search-friendly. Too many plugins can slow the site, updates are ongoing, and highly specific business logic may not fit. If the workflow is complex, a custom build may be the better path.
Q41: How can a slow site be improved?
Common steps include compressing images (WebP can cut size by more than 30%), enabling browser cache, using a CDN, trimming CSS and JavaScript, moving to faster hosting, and removing plugins you do not need. PageSpeed Insights can show a score and concrete suggestions. Aim to keep the first load within about 2.5 seconds.
Choosing a Partner (Q42–Q47)
The right partner is half of a successful project. These notes help with that choice.
Q42: How do you evaluate a design team?
Look at five points: work quality (cases in a similar industry or scale), technical fit, communication (speed and understanding in the first talks), care after launch, and stability (years in business and team size).
Stability is the point most often skipped. A very cheap freelancer may close after a few years, leaving nobody to maintain the site, even when a certificate expires. Do not compare price alone. More criteria are in how to choose a build partner.
Q43: Freelancer or agency?
Each option has tradeoffs. A freelancer is often cheaper and more direct, which suits a small project, but continuity, technical range, and aftercare can be limited. An agency usually has design, front-end, back-end, and project management, so capability is broader and a longer relationship is more secure, at a higher fee and with more communication layers. For a mid-size or larger company site, a full team is the safer choice for quality and later care.
Q44: Which contract terms must be clear?
The contract should state: scope and deliverables (page count and feature list), schedule and milestones, payment terms, revision limits, copyright and usage rights, warranty and maintenance, termination terms, and how source files are handed over. Rights need to be explicit, including design and code copyright, the client’s permanent right to use the work, and who owns the content.
Q45: What if the vendor shuts down?
To reduce that risk, you should hold, at handover: domain ownership (registered in your own account), hosting access, a source backup, file-transfer credentials, and database credentials. If those sit with you, another team can take over even if the original vendor closes. The contract should also state that design and code copyright may remain with the maker, the client keeps a permanent right to use them, and content copyright stays with the client.
Q46: Should you review live portfolio sites?
Yes, and you should ask. A reliable team shows sites you can open, not only screenshots. Notice whether the style varies, whether phones work well, whether pages load smoothly, and whether any case is close to your industry. Ask for work from the last six months to see current design and technical level. More ways to compare are in how to compare partners.
Q47: What does aftercare usually cover?
Solid aftercare often includes a warranty period (bug fixes for 1 to 3 months after launch), technical support, security updates, regular backups, and limited content edits. A higher plan may add performance monitoring, search reports, traffic analysis, and advice on new features. Confirm the warranty scope and how maintenance is billed before you sign.
Industry-Specific Notes (Q48–Q50)
Different industries need different care. These notes cover a few specific questions.
Q48: How do shops differ from brochure sites?
The main difference is whether a transaction can be completed. A shop needs a catalog, cart and checkout, payments, shipping, an order admin, inventory, members, and returns. That complexity and cost sit well above a brochure site. Planning notes are in how to plan a shop, and related options are in shop platform approaches.
Q49: Do regulated industries need extra care?
Yes, and it matters. Health-related content must follow advertising and disclosure rules, must not overstate results, and must protect personal health data. Legal-service sites must respect professional rules on advertising and client testimonials. Have someone who knows the industry review public copy, and include any required disclaimer.
Q50: How do B2B and B2C sites differ?
The core difference is who decides and how long that takes. Business buyers have a long cycle, so the site needs specifications, technical documents, case studies, and a way to request a quote. Consumer visitors decide faster, so visual appeal, reviews, offers, and a smooth purchase path matter more. In tone, the first aims at professional trust; the second aims at feeling and ease of use.
Closing: Make the site a steady business asset
After these fifty notes, budget, process, and upkeep should be clearer. Each choice affects the result. Remember: a good site is an investment, not merely money spent.
The more common regret is not spending more, but saving in the wrong place: skimping on assets so products look poor, or skipping maintenance until an expired certificate gets the site marked unsafe. For a structured look at setup options, see how to choose a setup path.
Choose the right partner, do the early planning properly, and keep improving content and technology. The site can then keep reaching potential customers while you are away.
Note: These fifty questions can be published as FAQ structured data, which may appear as a common-questions block in search results and improve visibility and clicks.
