Why a Client’s Website Gets No Traffic After Launch (And It’s Not the Design)

The short answer

When a well-designed website produces no traffic or inquiries after launch, the cause is usually one of five setup problems, not the design:

1. The site isn’t indexed. It was never submitted to Google Search Console, so key pages don’t appear in search.
2. The site is slow on mobile. Third-party scripts, font files, and video backgrounds, not images, are the usual cause.
3. Cookie consent is misconfigured. The client either collects data without permission or loses the analytics data that would show what’s happening.
4. The site isn’t accessible. Low contrast, missing alt text, and broken heading structure exclude visitors and weaken search signals.
5. The business doesn’t look legitimate. Missing contact details, broken forms, and template leftovers stop visitors from inquiring.

Each problem can be diagnosed in under an hour with free tools: Google Search Console, PageSpeed Insights, WAVE, and the browser’s network tab. Most of the fixes belong in the first week of a project, not in launch week.

Who this guide is for

Prefer video? The full walkthrough is in How To Fix Your Website Reach in 2026.

The benchmarks this guide uses

Each check below is measured against a published standard, so the result is pass or fail rather than opinion.

The order to check them in

Check the five causes in order. Each step is faster than the next, and an earlier failure can hide a later one. A site that isn’t indexed gets no traffic no matter how fast it is, and broken consent can make healthy traffic look like none.

1. Is the site indexed by Google?

Diagnosis: If a site launched weeks ago and gets no search traffic, check indexing first. Many client sites are never submitted to Google Search Console.

Google usually discovers new sites on its own, but discovery can take weeks. When it does crawl an unsubmitted site, it can miss pages or index the wrong ones.

How to fix it

1. Set up Google Search Console and verify the domain. It’s free and takes about ten minutes.
2. Submit the sitemap. Squarespace, Showit, Webflow, and WordPress (with an SEO plugin) generate one automatically, usually at /sitemap.xml.
3. Request indexing for the key pages: home, services, contact, and portfolio.
4. Read the Pages report. It lists which pages aren’t indexed and why. The most common cause is a noindex tag left over from the staging site.

2. Why is the site slow on mobile?

Diagnosis: On a client site, images are rarely the main cause of slowness. Third-party scripts, font files, video backgrounds, and unused platform code usually are.

What slows sites down

• Third-party scripts. Analytics, chat widgets, booking tools, social embeds, and ad pixels each send a request to a server you don’t control.
• Fonts. Each font weight is a separate file. Loading six weights when the design uses two adds four unnecessary requests. Without a fallback strategy, text can shift or disappear while fonts load.
• Video backgrounds. A hero video is often larger than every other asset on the page combined.
• Platform bloat. Page builders and plugins load code for features the site doesn’t use.

How to check

1. Run the site through PageSpeed Insights and read the mobile score. Mobile is where most visitors are, and it’s almost always the lower score.
2. Open the browser’s network tab and sort by size and load time. The problem is usually two or three specific files, not the whole site.
3. Compare the results with the Core Web Vitals thresholds in the benchmarks table above.

3. Is cookie consent set up correctly?

Diagnosis: A typical client site runs analytics, a chat widget, embedded video, an ad pixel, and third-party fonts. Each can set cookies or collect personal data. When consent is added in launch week, it usually fails in one of three ways.

Why it matters

1. It’s the brand’s first impression. The consent banner often appears before the hero section finishes loading. An unstyled grey box is the first thing visitors see.
2. It creates legal exposure for the client. A rushed setup often lets tracking scripts fire before a visitor clicks accept, or shows a banner that doesn’t control anything. Either way, the client collects data without permission under laws like GDPR and a growing number of US state privacy laws.
3. It corrupts the client’s data. If consent isn’t connected to analytics and ad tools, visitors who decline can vanish from reports. Without Google Consent Mode v2, Google Ads and Analytics lose the signals they need. The result is a client who says “nothing’s happening” when nobody can actually see what’s happening.

How to fix it

1. During scoping, list every third-party tool the site will run: analytics, pixels, embeds, chat, and fonts.
2. Use a consent management platform (CMP) that blocks scripts until a visitor consents. A banner alone isn’t enough. See the comparison below.
3. Design the banner like any other component: brand fonts, brand colors, plain-language copy, and “accept” and “decline” buttons that are equally easy to find.
4. Test it. Open the site in a private window, decline all cookies, and confirm in the network tab that no trackers loaded.

4. Is the site accessible?

Diagnosis: An inaccessible site excludes screen reader users, keyboard users, and anyone with low vision. It also weakens search performance, because the same structure that helps assistive technology helps search engines understand the page.

Accessibility is also a legal risk for clients. The European Accessibility Act has applied to many businesses selling to EU customers since June 2025, and accessibility lawsuits are common in the US.

What usually goes wrong

• Low contrast. Soft, tonal palettes often fall below the 4.5:1 ratio WCAG requires for body text.
• Missing or useless alt text. Images labeled “IMG_4821” or not labeled at all.
• Headings chosen for size. An H3 used because it looked right, not because it’s the right level in the page structure.
• No visible focus states. Keyboard users can’t tell where they are on the page.
• Unlabeled form fields. Placeholder text used instead of a label disappears as soon as someone starts typing.
• Text inside images. Headlines and service lists exported as graphics can’t be read by screen readers or search engines.

How to check

1. Run the site through WAVE or the accessibility audit in Lighthouse.
2. Test the color palette in a contrast checker before you hand off the brand, not after the build.
3. Put the mouse away and tab through the whole site, including the menu and contact form.
4. Make accessibility part of the design phase. Choosing an accessible palette in week one costs far less than fixing one in week six.

5. Does the business look legitimate?

Diagnosis: Visitors decide within seconds whether a business is real and trustworthy, and Google evaluates similar signals. A site can be well designed and still fail this test because of missing content or setup.

Trust signals that get missed

• Real contact details. An email address on the client’s own domain instead of Gmail, plus a phone number, location, or service area where relevant.
• A working contact form. Test it after launch. Forms sometimes send to an old inbox, or nowhere, for months.
• Real people and proof. A photo of the person behind the business, testimonials with names, and portfolio work that’s genuinely theirs.
• A Google Business Profile. Essential for any client serving a local area, and linked to the site.
• Legal basics. A privacy policy, terms where needed, and an SSL certificate so browsers don’t label the site “not secure.”
• No leftovers. Lorem ipsum, template stock photos, broken social icons, dead links, a missing favicon, or an outdated copyright year.

How to check

Open the site on your phone as a stranger would and ask: if I’d never heard of this business, would I pay them? Then click every link, submit every form, and confirm every claim on the page is backed up somewhere.

Which consent management platform should you use?

The right platform depends on how many sites you manage, how much banner styling the brand needs, and the client’s budget. Every option below must block trackers, such as Google Analytics, Meta Pixel, Adobe Analytics, and embedded video, until a visitor consents.

Verdict

• For designers and studios who need a branded banner across several client sites: Usercentrics or Cookiebot.
• For a single low-budget site: CookieYes is often enough.
• For clients who also need a privacy policy written: Termly.
• For enterprise clients with an in-house legal team: OneTrust.

Whichever you choose, run the private-window test from cause 3. A consent tool only protects the client if it actually blocks scripts.

Frequently asked questions

How long does Google take to index a new website? Without a sitemap submission, discovery can take several weeks. Submitting the sitemap and requesting indexing in Google Search Console usually speeds this up to days, though Google doesn’t guarantee a timeline.

Do US websites need a cookie consent banner? It depends on where visitors are and what the site collects. Sites with EU or UK visitors fall under GDPR-style consent rules. More than a dozen US states now have comprehensive privacy laws, most built on opt-out rights. A consent platform that adapts to the visitor’s region covers both.

Does accessibility affect SEO? Indirectly, yes. Descriptive alt text, a logical heading structure, and real text instead of text in images help search engines understand a page, as well as screen readers.

What is a good mobile PageSpeed score? The score itself matters less than the Core Web Vitals behind it. Aim for Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 ms, and Cumulative Layout Shift under 0.1.

Who is responsible for post-launch setup, the designer or the client? Define it in the contract. If the designer owns indexing, consent, and accessibility setup, list them as deliverables. If the client owns them, give the client this checklist at handoff.

The post-launch checklist

Run this before launch and again three months after.

• Search Console verified, sitemap submitted, key pages indexed
• No noindex tags left from staging
• Mobile Core Web Vitals checked; largest scripts, fonts, and videos trimmed
• Every third-party tool listed, with a branded consent banner that blocks trackers until consent
• Declined consent tested in a private window
• Contrast, alt text, heading levels, focus states, and form labels checked against WCAG 2.2 AA
• Domain email, working forms, real photos, named testimonials, privacy policy, and SSL in place

If a client’s site is “doing nothing,” start at the top of this list. The answer is usually here, not in the design.

Sources

• Google Search Central: Build and submit a sitemap
• web.dev: Web Vitals
• W3C: Web Content Accessibility Guidelines (WCAG) 2.2
• Google: Consent mode overview
• WebAIM: WAVE accessibility evaluation tool