A new website can look finished before it is ready to serve customers. The homepage may be polished, the photos may be sharp, and the designer may be asking for the final payment. But can a customer actually request an estimate? Does the business owner control the accounts? And what happens when something breaks after launch?

For a cleaning company, handyman, landscaping firm, or other small service business, the final review should be about whether the agreed work has been delivered and can be used, not whether every design choice is personally appealing. You do not need to become a developer to carry out a useful acceptance check.

First, read your agreement. A final-payment milestone may come before launch, after launch, or at another defined stage. This guide does not override your contract or tell you to withhold a payment that is legally due. It helps you document what is complete, what remains unresolved, and what you need to understand before signing off.

Start With the Deliverables, Not the Homepage

Put the original proposal, scope of work, or statement of work beside the delivered site. Look for the specific items you purchased: page count, copywriting, photo handling, mobile layout, contact forms, booking integration, basic SEO setup, analytics, training, or a post-launch support period.

An item is not automatically included because it sounds standard for web design. A designer hired to build five pages may not have agreed to write new service descriptions, configure a CRM, or maintain the site indefinitely. Equally, a deliverable explicitly included in the contract should not disappear behind the phrase “we can do that later.”

Create three simple statuses for every deliverable: accepted, needs correction, or not included in the agreement. This keeps genuine defects separate from new requests that may require a change order.

Try the Website as a Customer Would

Do the review on your own phone, not just on the designer’s presentation screen. Then repeat the most important steps on a laptop or desktop browser.

Imagine a customer with a clogged drain, an overgrown yard, or a cleaning request. Can they tell in a few moments whether you serve their area, do that particular job, and have a credible way to contact you?

Check the paths that matter to your business:

  • Open each core service page and confirm the service is accurately described.
  • Tap the phone number and check that your device offers to call the correct business number.
  • Follow every prominent “Get a Quote,” “Book,” or “Contact” button to its intended destination.
  • Submit a clearly labeled test inquiry from a private email address you control.
  • Confirm the inquiry reaches the correct inbox or system, not merely a confirmation screen.
  • Check the mobile navigation, footer, and any sticky contact button for dead ends.

A successful test is not simply “the form says thank you.” Check where the message arrives, whether it identifies the requested service, and who is expected to answer it. If the site sends an automated response, make sure the promised reply window matches how you actually operate.

Do not send real customer information through a test form. Use dummy data and remove the test record afterward where practical.

Verify Business Facts Before They Become Customer Problems

Incorrect details can cost a small service firm time even when the site itself works perfectly. Read every page for things only you can reliably confirm: services you truly perform, neighborhoods you serve, hours when calls are answered, whether emergency service is available, and any claims about licensing, insurance, guarantees, or response times.

Pay special attention to statements added during copywriting. “24/7 emergency dispatch” is not the same as “messages accepted after hours.” A service area on a map is not permission to promise appointments in every listed town. A customer testimonial should not appear under a name or photograph without appropriate permission.

If you spot an error, record the exact page and the corrected wording. A screenshot helps, but a clear written change request is even better: “On the drain-cleaning page, replace the weekday hours with Monday–Friday, 8 a.m.–5 p.m.”

Confirm You Control the Website Accounts

A website is not fully handed over just because you can see it on the internet. You should know which services make it run and which accounts you will need to manage it.

Ask for an account and access inventory covering whichever items are relevant to the project:

  • Domain registrar and renewal responsibility
  • Hosting or website-builder billing account
  • Content management system administrator access
  • Business email or form-delivery service
  • Google Analytics and Search Console access, if those were in scope
  • Booking, payment, or CRM integrations, if included
  • Any paid fonts, images, themes, plug-ins, or other licensed components

Confirm access by signing in yourself using an authorized account. Do not ask the designer to email passwords in plain text; use the platform’s user-invitation, account transfer, or secure credential-sharing process where possible.

Also establish who pays renewals and who receives expiration notices. You may have full editing access but still depend on another person for the domain or the hosting bill. Whether transferring an account is feasible depends on the platform and the contract, so document the actual arrangement rather than assuming ownership means every login can be moved instantly.

If Google Analytics is part of the project, Google documents role-based access management at account and property levels. That is a useful model: the owner should understand who can change the property, not simply receive a screenshot of a report.

Protect Existing Pages During a Redesign

If this is your first website, there may be no old pages to preserve. If it replaces an existing site, ask a different question: What happens to the old URLs?

Customers may have saved your service-page links, and search engines may have discovered those pages. A redesign that changes addresses without a plan can strand visitors at missing pages. Ask the designer for a list of important old URLs, their new destinations, and any redirects included in the agreed scope.

Google’s site-move documentation recommends mapping changed URLs to appropriate destinations, testing redirects, checking indexing-related settings, and monitoring the migration. That does not mean every redesign requires a site move; it means URL changes deserve an explicit plan.

Also confirm that any temporary development settings, such as a sitewide noindex instruction, have been handled appropriately before a public launch. A sitemap is helpful for discovery, but Google does not guarantee indexing simply because a page is listed in one.

Check the Parts That Are Easy to Miss

Some defects are invisible during a visual walk-through. They matter because they affect actual visitors or your future ability to maintain the site.

Forms and accessibility

Can you navigate to the form fields by keyboard? Are field purposes clear without relying entirely on placeholder text? Does an error message explain how to fix a missing entry? The W3C's form-label guidance explains why controls need accessible labels that identify their purpose. You are not conducting a full accessibility audit in a ten-minute test, but obvious failures are worth fixing before acceptance.

Mobile layout and readability

Read a long service description on a narrow screen. Look for text hidden behind a floating button, menus that cannot be closed, pricing notes pushed off-screen, or contact actions blocked by pop-ups. Check both portrait and landscape views if your audience is likely to use them.

Photos and legal permissions

Confirm the company has permission to use delivered photos, graphics, testimonials, and any stock assets under the arrangement you purchased. Ask whether recurring software subscriptions or photo licenses are needed to keep the design working. You do not need a blanket statement that you own everything; you need a clear list of what you may use, edit, and retain.

Basic measurement

If analytics setup was included, have the designer show you which account collects data and how to identify a test visit or test event where feasible. A tracking installation is not proof that every lead is attributed correctly. Agree on what was actually configured and what was not.

Ask for a Handoff You Can Use Six Months Later

The handoff should match the services and responsibilities in your agreement. For many small business sites, a short guide or recorded walkthrough can be more useful than an enormous technical manual.

At minimum, you should know how to change business hours, update a phone number, replace a photo, publish a basic notice, and contact support when something fails. Ask where backups are handled, who performs software updates if relevant, and which changes fall outside the initial design fee.

If ongoing maintenance was purchased, get the support terms in writing: what is covered, how requests are submitted, who responds, and whether fixes or content changes have limits. If maintenance was not purchased, decide who will take responsibility once the project ends.

Handle Unfinished Work Without Turning It Into a Fight

A useful final review ends with a short written punch list, not a vague argument about whether the site “feels done.” For each issue, include the page or feature, the expected behavior, the actual behavior, the responsible person, and the agreed next action.

Separate launch blockers from improvements that can be scheduled later. A broken contact form, incorrect phone number, or inaccessible owner account may block a practical handoff. Changing the spacing above a heading may be a reasonable refinement but not necessarily a reason to delay everything. The distinction depends on your agreement and the seriousness of the issue.

Before approving the final invoice, ask: Does the current milestone match what our contract requires? Which open items are already agreed corrections? What happens after approval? If there is a dispute over payment, follow the contract and obtain appropriate professional advice rather than relying on an online checklist as a legal rule.

A Final-Payment Review You Can Finish in One Sitting

You can make the process manageable with a final short pass:

  1. Match the agreed deliverables against the pages and features delivered.
  2. Complete a real customer journey on your phone, including a test call link and test inquiry.
  3. Approve the business facts and review every claim that could mislead a customer.
  4. Log into the accounts you are supposed to control and identify renewal responsibilities.
  5. Check the old-URL and redirect plan if an existing site was replaced.
  6. Receive usable update instructions and the agreed maintenance or support terms.
  7. Send one written acceptance note or punch list tied to the contract's payment milestone.

The point is not to make a small business owner perform a developer's quality-assurance job. It is to make sure the site can answer questions, receive customers, and remain manageable after the designer leaves. A finished website should be more than a finished design.

Sources and Further Reading