Website Refresh

Most sites do not fail all at once. They erode. A page gets added for a product launch, then another for a partnership, then a landing page for a paid campaign that outlived the campaign. Two years in, the navigation no longer matches how buyers actually shop, the mobile experience was patched instead of designed, and the analytics tell you people are landing and leaving. A refresh is the reset that puts the site back in step with the business.

This page walks through what AdsTalent delivers in a website refresh, who tends to buy one, how we run the work, and what to expect on timeline and process.

What a website refresh actually delivers

A refresh is a full replacement of the public site, not a redesign of the homepage with the rest left untouched. At the end of the engagement you own a working site plus the documentation and source files that let any competent developer maintain it after us.

The concrete artifacts you receive:

• A written audit of the current site covering analytics behavior, a page-by-page content inventory, and a technical SEO baseline. This document names every URL that carries traffic or backlinks, flags thin or duplicate pages, and identifies the templates that need to change.
• A new sitemap and information architecture document. This is the shape of the site: top navigation, secondary navigation, footer, and how deep each content type lives. It is delivered as a diagram plus a spreadsheet mapping old URLs to new URLs.
• Wireframes for the top eight to twelve templates. Home, primary service or product page, secondary service or product page, category or listing, blog index, blog post, about, contact, and any specialty templates the business needs. Wireframes are structural, not visual, and they get sign-off before any design work starts.
• A visual design system tied to your brand. Type scale, color tokens, spacing tokens, button and form states, card patterns, imagery direction, and iconography. Delivered as a Figma file plus a short written system guide so the tokens are usable by future designers and developers.
• High fidelity designs for every template in the wireframe set, in desktop and mobile breakpoints.
• The built site, on either WordPress with a custom theme or a static Next.js stack. We choose the platform based on how often the content changes, who edits it, and any technical constraints from existing systems. WordPress when non technical staff need to publish frequently. Next.js when the site is more product marketing than publishing and speed and control matter more than in browser editing.
• Content migration handled together with your team. We move existing content that is worth keeping, rewrite what needs rewriting, and retire the rest with proper redirects.
• A launch checklist executed on go live day: 301 redirects from every old URL that had traffic or links, tracking verification for GA4 and any conversion pixels, updated XML sitemap submitted to Google Search Console and Bing Webmaster Tools, and a Core Web Vitals check on the top templates.
• Source files. The Figma file, the WordPress theme repository or the Next.js repository, and the design system documentation. You own all of it.

You finish the engagement with a site that reflects the business as it is today, and with the assets needed to keep it current without starting over.

Who this is for

A website refresh is a real investment of time and money, and it is not the right move for every company at every moment. The businesses that get the most out of it usually share a few conditions.

The visual identity is five or more years old and no longer matches how the company presents itself in the room. If your sales deck, your trade show booth, and your website look like three different companies, the site is usually the one holding back conversion.

You have been through a change of ownership, a merger, or an acquisition, and the current site still speaks in the voice of the previous owner. This is a common driver. The new owner often waits a year before touching the site, then realizes every downstream marketing effort is anchored to yesterday.

You expanded the product line or the service list and the current information architecture cannot absorb the new categories cleanly. You are stuffing new SKUs into a navigation designed for a smaller catalog and the analytics show buyers cannot find what they came for.

You are moving upmarket. The buyer profile changed, the price point changed, and the site still looks like it is selling to the old audience. This shows up in longer sales cycles and more discovery call time spent overcoming a first impression.

You have grown beyond the original DIY logo, the founder built site, or the template kit purchased in year one. There is nothing wrong with any of those starting points. They stop scaling at a predictable size.

You are launching a new product line or a new business unit and you need the site to hold it correctly rather than tacking on a page.

You are about to spend meaningful money on paid media, SEO, or outbound and every campaign will land on this site. The math on a refresh often looks reasonable when the alternative is buying traffic that lands on a page that does not convert.

If none of these describe you, a refresh is probably premature. A conversion rate optimization engagement or a targeted SEO project may return more per dollar on the existing site.

How AdsTalent runs a website refresh

The work runs in five phases. Each phase has defined deliverables, a defined sign off, and a defined ask of your team. We do not move to the next phase until the current one is closed.

Phase one: discovery and kickoff. Two to three weeks. We start with a kickoff call that includes the decision makers and anyone who will edit the site after launch. We collect access to analytics, Search Console, the current CMS, the domain registrar, and any existing brand assets. We interview two to four people inside the company and, when useful, two to four customers. We produce the audit document described above and a short strategy memo covering positioning, primary conversion goals, and any technical constraints we found. You sign off on the sitemap and information architecture before we move on. What we need from you: access, calendar time for interviews, and a single decision maker who can approve the IA.

Phase two: wireframes. Two weeks. We deliver low fidelity wireframes for every template in the agreed scope. These are structural documents that lock down what goes on each page and in what order. We review them together on a working call, revise, and get written sign off. This is the cheapest place to change your mind. Rearranging boxes in a wireframe is a morning of work. Rearranging them in a built page is a week. What we need from you: engaged review and a real decision on scope. If a template needs to be added it is easiest to add it here.

Phase three: visual design. Three to five weeks depending on template count. We present the design system first, applied to two anchor templates, usually the home and the primary product or service page. We take one round of consolidated feedback, revise, and get sign off on direction. Then we apply the approved system to the remaining templates and present them in batches. What we need from you: consolidated feedback rather than drip feedback, and imagery decisions. If we need new photography we flag it here so it can be shot in parallel.

Phase four: build. Four to six weeks depending on platform and template count. We build in an environment you can review. You get access to a staging URL and we cut a fresh build for review on a set cadence, usually twice a week. Content migration runs in parallel. We meet weekly for a build review. What we need from you: content decisions on any page where the old copy no longer applies, and reviewer availability so we are not blocked waiting for approval.

Phase five: launch. One week. We run through a written launch checklist: redirects, tracking, sitemap, forms, DNS, SSL, Core Web Vitals, cross browser and cross device checks, and a full click through of every template. We schedule the DNS cut for a low traffic window. We monitor the site for the first 72 hours after launch and address anything that surfaces. What we need from you: a decision on the launch window and availability for a go no go call the day of.

Communication runs on a fixed cadence. A weekly written status note, a weekly working call, and a shared project workspace where every file, comment, and decision is logged. You always know what phase we are in, what is blocking, and what the next deliverable is.

What success looks like

Category level examples, not real client names.

A regional professional services firm with a fifteen year old site typically comes out of a refresh with a coherent story across service pages, mobile pages that load in under two seconds instead of over five, a contact flow that captures qualified leads with enough context that the intake team can route them without a follow up email, and analytics that finally attribute traffic to real channels instead of a wall of direct and referral noise.

A regional coffee roaster with eight SKUs and a growing wholesale side typically comes out with a wholesale portal that is separate from the retail storefront, product pages that hold up when a buyer lands from a paid search ad on a phone, and a content structure that supports the origin and process storytelling the brand depends on.

A B2B manufacturer with a catalog of a few hundred parts typically comes out with faceted category pages that let engineers narrow to the right part in a few clicks, spec sheets that render cleanly and print cleanly, and a quote request flow that reaches the right regional sales rep automatically.

A software company moving from founder led sales to a repeatable sales motion typically comes out with a site that supports both self serve trial and enterprise demo request paths without one cannibalizing the other, and a resource library that gives the sales team something to send in a follow up.

The measurable outcomes tend to be lower bounce on the top landing pages, higher form completion rates, higher pages per session on the primary conversion paths, and a mobile experience that no longer loses buyers on the way to the goal. What a refresh does not do on its own is generate new demand. That work belongs to SEO and paid media. What it does is make sure the demand you already have and the demand you are about to buy lands somewhere that holds up.

Timeline

Twelve to sixteen weeks from kickoff to launch is the honest range for a full refresh with the scope described above. Simpler projects with fewer templates and clean existing content can close in ten. Larger projects with heavy content work, custom integrations, or a full ecommerce build run longer and are quoted separately.

Rough milestones:

• Weeks one to three: kickoff, audit, IA and sitemap sign off.
• Weeks four to five: wireframes and wireframe sign off.
• Weeks six to ten: visual design system, template designs, design sign off.
• Weeks ten to fifteen: build, content migration, staging review.
• Week sixteen: launch checklist, DNS cut, post launch monitoring.

Client turnaround is the single biggest variable. If reviews come back in three business days as agreed, the timeline holds. If reviews slip a week each phase, the project slips a month. We track review cycle time in the weekly status note so this is visible early rather than at the end.

We also plan around known blackout windows. If you have a trade show, a fiscal year end, or a product launch inside the window, we build the schedule around it rather than pretending it does not exist.

Website Refresh FAQ

Q: How long does a website refresh take?

Twelve to sixteen weeks for a project in the scope described on this page. Shorter for a small template set with clean content. Longer for heavy custom builds or ecommerce. We commit to a specific timeline in the written estimate after the discovery call.

Q: What does a website refresh cost?

Pricing is scoped per engagement based on template count, platform, content migration volume, and any custom functionality. We provide a written estimate after the discovery call. Payment terms are 50 percent at kickoff and the balance at launch, with milestone billing available on larger scopes.

Q: What if we want more design concept rounds than the scope includes?

The base scope includes one round of direction level revision on the design system and one round of revision on each template batch. Additional rounds are available and quoted as a change order before the work starts, so there are no surprise charges at the end.

Q: Do you work with our existing agency, developer, or internal marketing team?

Yes. Many refreshes run alongside an existing SEO agency, an existing paid media team, or an internal marketing function. We define handoffs in the kickoff so it is clear who owns what after launch. If your team will maintain the site, we include a training session and written documentation.

Q: Do we own the source files and the code?

Yes. The Figma file, the WordPress theme repository or Next.js repository, and the design system documentation are yours. If we part ways, another team can pick up the work without starting over.

Q: What if we do not like any of the initial design directions?

We do not present a single direction and defend it. The design system phase includes two anchor templates applied to the system, and we present with the reasoning behind each choice. If the direction is wrong we revise inside the included round. If it is fundamentally wrong we regroup on strategy before spending more design time. In practice this has not required scrapping a project, because the IA and wireframe sign offs upstream catch most disagreements early.

Q: Do you provide brand guidelines?

The design system document that comes with the refresh functions as a working brand system for the web. It covers type, color, spacing, components, and imagery direction. If you need a full brand guidelines document that also covers print, packaging, and non web applications, we scope that separately.

Q: Does the engagement include print production management or ongoing site maintenance?

No, not by default. Print production is a separate scope. Ongoing site maintenance, hosting management, content updates, and small feature additions are offered as a monthly retainer after launch if you want us to keep the site healthy. Many clients take the retainer for the first six months and reassess.

Related services

• Local SEO. If you sell to a defined geography, a refreshed site is the foundation the local SEO work sits on.
• National SEO. A refresh fixes the technical SEO baseline that a national program depends on to compound.
• Pay Per Click Management. Paid traffic gets expensive fast on a site that does not convert. Refresh first, then scale paid.
• Conversion Rate Optimization. Once the new site is live and collecting real data, CRO is the ongoing engine that keeps improving results.
• Web Development. For custom functionality, integrations, or ongoing engineering work beyond the refresh scope.