The proposal looks polished. The price fits your budget. The designer says your new site can launch quickly and bring in more customers. Then you notice that the proposal never says who will own the domain, how many pages are included, or what happens after launch.
Those missing details can cost more than an ugly homepage. A business can end up paying surprise fees, losing access to its own accounts, rebuilding work that was never finished, or waiting months for a contact form that still does not send messages.
Web designer red flags are not always proof that someone is dishonest or unqualified. A new freelancer may have a small portfolio, and an agency may need discovery before giving a firm price. Both can be reasonable when the person explains the limits clearly.
The warning comes from a pattern of vague answers, missing documentation, and promises that cannot be verified. Here are seven signs that deserve a closer look before you sign or pay a deposit.
1. The Scope Is Vague or Nothing Is in Writing
A website project needs more than a total price and a target launch month. The written scope should describe what the designer will produce, what you must provide, and how both sides will decide that the work is complete.
At minimum, look for:
- The number and purpose of pages
- Whether design, development, writing, and image work are included
- Forms, scheduling tools, payments, maps, or other integrations
- The number of revision rounds
- Project milestones and payment dates
- What happens when either side misses a deadline
- What counts as additional work and how it is priced
- Ownership, cancellation, and post-launch terms
“Five-page website” can mean five finished pages with original copy and tested forms. It can also mean five empty templates that you must finish yourself. The contract should remove that uncertainty.
A good answer sounds like this: “The proposal includes five named pages, one quote form, mobile testing, two revision rounds, and thirty days of bug fixes after launch. New pages or features require a written change order.”
Be cautious when a designer refuses to define the work, says a contract is unnecessary, or treats reasonable questions as a lack of trust. Clear terms protect the designer as well as the client.
2. You Will Not Control the Domain and Business Accounts
Your domain should generally live in an account your business can access with an email address you control. A designer can receive the technical permissions needed to connect hosting, update records, or launch the site without becoming the only person who can renew or transfer the domain.
Use the same approach for hosting, analytics, Google Search Console, form services, payment tools, and business listings. Your company should know where each account lives, who pays for it, and how access can be recovered.
Ask these questions before work starts:
- In whose name will the domain be registered?
- Which email address receives renewal and security notices?
- Will I have administrator access to every business account?
- Who owns the website files, copy, images, and custom code after payment?
- Can another developer manage or move the site later?
- What must be exported if our working relationship ends?
Account control also affects security. CISA recommends multifactor authentication for business systems and advises starting with administrative accounts. Its multifactor authentication guidance explains why a password alone is not enough protection for sensitive access.
Do not send a reusable password in a long email thread when the service offers invitations, roles, or temporary access. A responsible designer should be comfortable working inside accounts your company owns.
For a fuller breakdown, read who owns your website after it is built.
3. The Designer Guarantees a Number-One Google Ranking
A web designer can build a strong search foundation. That work may include clear page structure, descriptive titles, useful content, fast pages, crawlable links, local business information, structured data, and Google Search Console setup.
No designer controls Google’s results. Google states in its guide to hiring an SEO that no one can guarantee a number-one ranking. The same guide warns about providers who claim a special relationship with Google or refuse to explain what they plan to do.
Promises such as “first page in thirty days” leave out the search phrase, location, competition, starting condition of the site, and methods being used. Ranking first for an obscure phrase that no customer searches does not help a business. Aggressive tactics can also create problems that the next provider must clean up.
Ask what the designer can control and how progress will be measured. A credible answer may cover technical setup, content, local search signals, qualified traffic, calls, forms, and Search Console data. It should also acknowledge that results depend on the market and continued work.
SEO is a process with evidence, priorities, and tradeoffs. It is not a guaranteed line item stamped onto a proposal.
4. You Receive a Firm Solution Before the Designer Understands the Business
A designer does not need weeks of meetings to plan a small service website. The person does need enough information to understand the job.
Expect questions about:
- The customers you want to reach
- The services or products that matter most
- The towns or counties you genuinely serve
- What visitors should do next
- How leads arrive and who answers them
- Problems with the current website
- Existing brand materials, photographs, and written content
- Scheduling, payment, email, or customer-management tools already in use
A contractor serving Grayson and Hardin counties may need service pages, project photographs, financing details, and a quote form that works well on a phone. A Louisville restaurant may need menus, hours, directions, reservations, and accessibility information. Giving both businesses the same package without asking questions is fast, but it is not thoughtful planning.
A fixed-price starter package can still be a good fit. The designer should explain its boundaries and confirm that your needs fit inside them. If every answer is an upsell or every business receives the same structure, the low price may lead to a second build later.
Our guide to cheap website design explains how to separate a focused, affordable scope from a price that hides missing work.
5. The Portfolio Cannot Be Verified
Screenshots can show visual style, but they do not prove that a website works. Open the live sites in a designer’s portfolio whenever possible. Check them on a phone. Follow the navigation. Try the main action without submitting a real inquiry. Look for broken pages, unreadable text, obvious template leftovers, and confusing forms.
Ask what the designer handled on each project. One person may have created the visual design while another wrote the copy and a third developed the site. That is normal in team projects. The problem is claiming responsibility for work the person did not do.
Also account for age and client changes. A business owner may replace a well-built site or stop operating. One broken portfolio link does not settle the question. Several unverifiable projects, copied case studies, stock mockups presented as live clients, or evasive answers should slow the decision.
References can help with larger projects, but ask useful questions. Did the provider communicate clearly? Did the final invoice match the approved scope? Were delays explained? Did the forms and accounts work at handoff? How did support work after launch?
You are checking whether the person can finish the kind of project being sold to you, not whether every portfolio image matches your taste.
6. Testing, Accessibility, Performance, and Security Are Missing
A homepage mockup is not a finished website. Someone needs to test the real pages in browsers and on phones, confirm that links work, and make sure each form reaches the correct recipient once. A form that looks good but sends ten duplicate emails is still broken.
Ask what happens before launch. A reasonable quality check should cover:
- Common phone and desktop sizes
- Navigation, links, buttons, and downloads
- Form submission, confirmation, spam handling, and notifications
- Page titles, search descriptions, and crawl settings
- Image sizes and page-loading behavior
- Keyboard navigation, labels, headings, contrast, and alternative text
- Secure connections, account permissions, updates, and backups where applicable
- Analytics and Search Console access
The Department of Justice’s web accessibility guidance lists barriers such as poor contrast, missing text cues, weak heading structure, and keyboard problems. It also notes that automated checkers can help but do not prove a site is accessible. Manual review still has a place.
Performance should be measured too. Google’s Web Vitals guidance focuses on loading, responsiveness, and visual stability. A designer does not need to promise a perfect score on every test. The person should be able to explain what was tested, what affects the result, and which problems were fixed.
Be wary of “fully secure,” “100 percent accessible,” or “perfect PageSpeed” claims with no method behind them. A better provider describes the standard, test, limits, and maintenance plan.
7. Nobody Can Explain What Happens After Launch
Launch changes the work, but it does not erase future responsibilities. Domain renewals, hosting, software updates, backups, form delivery, content changes, and account access still need owners.
Some designers include maintenance. Others charge when changes are requested. Both models can work. You need the terms before launch, including:
- Monthly or annual fees and what they cover
- Response times for support requests
- Rates for work outside the original scope
- Who handles software and security updates
- Backup frequency and restoration responsibility
- Whether the site stays online if a service plan ends
- How files, data, and accounts are transferred
- How long bug fixes are included after launch
“Call me if you need anything” is friendly but incomplete. Ask how requests are submitted, when they are billed, and what happens if the original designer becomes unavailable.
A useful handoff includes account details, renewal dates, source files or export instructions, and a short explanation of the systems the site uses. Keep that information somewhere your business can reach without relying on one person’s inbox.
How to Compare Web Designers Without Overreacting
One unusual answer is not always a reason to walk away. A new freelancer may have limited client work but excellent technical skill and a careful process. A designer may keep hosting under a managed account while still giving you clear ownership and an exit path. A proposal may use a range instead of a fixed total because the project contains unknowns.
Look for clarity across the whole conversation. Can the provider explain choices in plain language? Are limitations stated before payment? Do the contract, proposal, and spoken answers agree? Can you verify the work and access terms?
Compare proposals line by line rather than comparing only the totals. Freelancers and agencies have different costs and staffing models, but size does not guarantee a better process. The right provider understands the work, documents it, and gives you a practical way to leave.
Before signing, use the detailed questions to ask a web designer and write down any answer that affects price, ownership, schedule, or support. If the answer matters later, it belongs in the agreement.
Choose Clarity Before Confidence
The strongest sales pitch is less useful than a clear scope, verifiable work, secure account access, realistic search expectations, and a tested handoff. A capable designer should welcome specific questions because good answers prevent conflict after the project starts.
If you are comparing web designers or trying to replace a website that left you locked out, Twin Lakes Web Co. can help you define the scope, ownership, testing, and support terms before another dollar is spent. Request a website quote and tell me what your business needs, what you already control, and what went wrong with the last setup.