Web design terminology is only useful if it helps you understand what you are buying, approving, owning, and verifying. Before you hire a web designer or agency, you do not need to memorize a hundred technical terms. You do need to understand the words that define project scope, design deliverables, technical responsibilities, quality standards, account ownership, and handoff.
If you are still sorting out what a web designer may actually be responsible for, start with our guide to what website design includes. This article has a narrower job: translating web designer lingo into the decisions a client has to make.
The web design terminology that matters most before you hire
The most important web design terms fall into six practical stages: strategy, structure, interface, build, verification, and operation. A useful term should tell you something about what the team will produce, how you will review it, what standards apply, or who owns the result.
That is why terms such as scope, wireframe, responsive design, CMS, API, WCAG, QA, UAT, DNS, and handoff usually matter more to a buyer than the name of a fashionable JavaScript framework.
Use the Scope Design Definition → Deliverable → Decision test
When a proposal, designer, or developer uses jargon, run it through three questions:
- Definition: What does the term mean in plain English?
- Deliverable: What page, file, behavior, account, test, document, or service proves that it is included?
- Decision: What do you need to approve, provide, own, budget for, or verify?
For example, a proposal may say the website will be responsive. The definition is straightforward: the layout should adapt to different screen sizes. The deliverable is not the word “responsive”; it is the implemented page behavior across the agreed range of screens. The decision is what devices, breakpoints, browsers, and acceptance checks are actually in scope.
The same rule exposes vague promises. “SEO included,” “accessible website,” “optimized performance,” and “ongoing support” sound reassuring, but each phrase is still ambiguous until the provider explains the work, evidence, boundaries, and owner.
Web design terms at a glance
| Project stage | Terms you may hear | What those terms should clarify |
|---|---|---|
| Strategy | Discovery, requirements, scope, deliverable, dependency, acceptance criteria | What problem is being solved and what is included |
| Structure | Sitemap, information architecture, user journey, content hierarchy | What pages and paths people need |
| Interface | UX, UI, wireframe, mockup, prototype, component, responsive design | What you are reviewing and approving before or during build |
| Build | Frontend, backend, CMS, template, API, integration, staging | What system makes the approved experience work |
| Verification | WCAG, QA, UAT, cross-browser testing, Core Web Vitals, redirects | How the team will prove the implementation meets the agreed requirements |
| Operation | Domain, DNS, hosting, admin account, license, backup, maintenance, handoff | Who controls the website and what happens after launch |
Strategy and scope terminology
Discovery
Discovery is the work used to understand the business problem, audience, current website, constraints, evidence, content, technology, and success criteria before important design decisions are locked in. Depending on the project, discovery might include stakeholder interviews, analytics review, content inventory, technical review, audience research, competitive context, or workshop sessions.
Ask: What exactly happens during discovery, who participates, and what decisions or documents come out of it?
Requirements
Requirements describe what the website must do or support. “We need a contact page” is a page request. “Qualified prospects must be able to choose a service, submit the correct project information, and route the inquiry to the right team” is closer to a functional requirement.
Requirements can cover content, functionality, integrations, accessibility, performance, security, reporting, legal constraints, and operational needs. They create a basis for design and acceptance instead of leaving everyone to infer the job from a page count.
Scope
Scope is the agreed boundary of the project. It should make the included work, exclusions, assumptions, responsibilities, schedule, and change process understandable. Scope is not the same thing as a feature list. Two “10-page websites” can represent radically different amounts of strategy, copywriting, design, development, migration, testing, training, and support.
Deliverable
A deliverable is a concrete output the project is supposed to produce. Examples include a sitemap, copy deck, wireframe, approved design, component library, working form, CMS template, redirect map, training session, or handoff document.
If a proposal uses a broad term such as “SEO,” “accessibility,” or “optimization,” ask what deliverables or checks are included under that label.
Dependency
A dependency is something another task relies on. Final page design may depend on approved copy. A payment integration may depend on credentials from your processor. Launch may depend on DNS access. Naming dependencies early makes schedule discussions more realistic.
Change request
A change request is a documented change to agreed scope, requirements, deliverables, or assumptions. It should explain what changed and whether the change affects cost, schedule, testing, or other work. A good change process protects both sides from silently turning a defined project into an unlimited one.
Acceptance criteria
Acceptance criteria describe the conditions that must be true for a deliverable or feature to be accepted. “Build a form” is vague. “The form validates required fields, sends the submission to the agreed destination, displays a confirmation, records the event in analytics, and works in the supported browsers” is testable.
Structure and user-flow terminology
Sitemap
A sitemap in the planning sense is a map of the website’s pages and hierarchy. It helps the team decide what content exists, how pages relate, and what belongs in navigation. Do not confuse this planning artifact with an XML sitemap used by search engines.
Information architecture (IA)
Information architecture is the way information is organized, labeled, grouped, and connected so people can find and understand it. IA affects navigation, page hierarchy, labels, content relationships, and the paths users take through the site.
User journey
A user journey describes the steps a person may take while trying to accomplish a goal. For a service business, one journey might be: understand the service, verify fit, review proof, compare options, ask a question, and submit an inquiry. The point is not to draw a pretty diagram. It is to reveal what a visitor needs at each decision.
Design and approval terminology
UX and UI
UX means user experience. It deals with how understandable, usable, efficient, and appropriate the experience is for the person trying to accomplish a task. UI means user interface. It covers the interface people see and interact with, including controls, visual hierarchy, states, components, spacing, typography, and presentation.
They overlap, but they are not interchangeable. A beautiful interface can still produce a poor experience if users cannot find the right information or complete an important task. If you need to diagnose those problems, our UX diagnosis guide goes deeper.
Wireframe
A wireframe is a simplified representation of page structure and priority. It usually focuses on layout, content hierarchy, and interaction rather than final typography, color, imagery, and polish. Its job is to make structural decisions cheaper to discuss before visual detail distracts everyone.
Mockup
A mockup is a more visually complete representation of the intended interface. It may show real typography, colors, imagery, components, spacing, and brand treatment, but it is not necessarily interactive or implemented.
Prototype
A prototype simulates some part of the experience so flows and interactions can be evaluated before the full system exists. A prototype can be simple or high fidelity. It is still a model. Approving a prototype or mockup is not the same as accepting a functioning website.
Design system and component
A component is a reusable interface element or pattern, such as a button, card, form field, testimonial block, or navigation item. A design system organizes reusable components together with rules, tokens, patterns, and guidance so the interface can stay coherent as it grows.
Responsive design, mobile-first, and breakpoint
Responsive web design is an approach that allows layouts and content to adapt across different screen sizes and device conditions. Mobile-first is a way of designing or coding from a smaller-screen baseline and progressively adapting for larger screens. A breakpoint is a condition, commonly based on viewport width, where layout behavior changes.
MDN’s responsive design guidance treats responsive design as an approach rather than a single device checklist. For a client, the important question is what responsive behavior will be tested and accepted, not whether the proposal contains the phrase “mobile-friendly.”
Development and technology terminology
Frontend and backend
The frontend is the part of the website delivered to and interacted with by the user, including the rendered interface and browser-side behavior. The backend is the server-side or administrative layer that may handle data, business logic, authentication, content, integrations, or other services behind the interface.
On many business websites, the boundary is less important to a client than the responsibility: who owns the interface, who owns data and integrations, and who fixes a problem when the two do not work together?
CMS
A content management system (CMS) is software used to manage website content. WordPress is a CMS. A CMS can make editing easier, but “CMS included” does not tell you how much control you will have, which content types are editable, whether custom fields exist, or how portable the site is.
Ask: What can our team edit safely? Which roles will we have? Who holds the administrator account? What training and documentation are included?
Template, theme, and component
A template controls the structure for a type of page or content. A theme usually refers to a larger presentation layer or package of templates, styles, and behavior, especially in systems such as WordPress. A site can use a theme and still include original design; a theme can also impose real constraints. The useful question is what is custom, what is reusable, and what the licensing or maintenance implications are.
API and integration
An API, or application programming interface, is an interface that lets software interact with another system. An integration is the implemented connection that uses an API, webhook, feed, plugin, file exchange, or another method to move data or trigger behavior between systems. MDN describes an API as the interface or contract that exposes features for software interaction.
An “API integration” line item should identify the systems involved, data or actions exchanged, authentication responsibilities, failure behavior, testing, and who maintains the connection when one platform changes.
Staging and production
Staging is a non-public or controlled environment used to review and test work before it affects the live website. Production is the live environment serving real users. Ask how changes move from staging to production, what gets backed up, and what the rollback plan is if a launch causes a problem.
Domain, DNS, and hosting
Your domain name is the human-readable address people use to reach the site. DNS is the system of records that directs that domain to services such as the website and email. Hosting is the infrastructure where the website application, files, or services run.
These are related but separate. A provider can host your website without owning your domain. Your business should know who controls the registrar account, DNS records, hosting account, billing, recovery email, and multi-factor authentication.
SSL certificate, HTTPS, and TLS
You will still hear people say SSL certificate, but modern HTTPS uses TLS. HTTPS is HTTP carried over a secure TLS connection, and TLS is used to provide encryption, integrity, and server authentication. For a client, the practical concern is that HTTPS is correctly configured, renewed, monitored, and not broken by mixed content or bad redirects.
Quality, accessibility, and measurement terminology
Accessibility and WCAG
Web accessibility means designing and building digital experiences so people with disabilities can perceive, understand, navigate, and interact with them. WCAG is the Web Content Accessibility Guidelines published by W3C. WCAG 2.2 is a W3C Recommendation and provides testable success criteria.
If a proposal says “ADA compliant” or “WCAG compliant,” ask what standard and conformance target are being used, what pages or templates will be evaluated, what testing methods are included, who remediates failures, and what remains the client’s responsibility for future content.
QA and UAT
Quality assurance (QA) is the team’s process for checking whether the implementation works as intended and meets the agreed requirements. User acceptance testing (UAT) is the client or business-side verification that the system is acceptable for the intended real-world use before final acceptance or launch.
They should not be treated as synonyms. QA asks whether the team built the thing correctly. UAT asks whether the delivered thing satisfies the agreed business use and acceptance criteria.
Cross-browser and device testing
Cross-browser testing checks behavior in the agreed browsers and versions. Device testing checks the experience across the screen sizes, input methods, and device conditions that matter to the project. “Works everywhere” is not a responsible test plan. A scope should state the supported range and how important exceptions are handled.
Core Web Vitals
Core Web Vitals are Google’s user-experience metrics for loading performance, responsiveness, and visual stability. The current metrics are Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS), as documented by web.dev.
If performance is included in a project, ask what will be measured, under what conditions, and whether the promise concerns lab testing, real-user data, or a specific threshold. A score without context can be as misleading as a buzzword.
SEO foundations
SEO foundations usually refers to the technical and content setup that helps search engines discover, interpret, and present the site correctly. It can include crawl/index controls, titles and descriptions, canonical URLs, redirects, internal links, structured data, XML sitemaps, and migration checks. It is not the same as an indefinite promise to rank for competitive queries.
Redirect
A redirect sends an old URL to another URL. Redirect planning matters during redesigns and migrations because changing paths without a plan can break links, bookmarks, referrals, and search signals. If URLs will change, the proposal should say who inventories old URLs, creates the redirect map, implements it, and verifies the result.
Analytics, event, and conversion
Analytics is the measurement system used to understand activity on the website. An event is a recorded interaction or occurrence, such as a form submission, download, purchase, or qualified button click. A conversion is an action the business has decided represents meaningful progress or value.
“Analytics installed” is not a measurement strategy. Ask which outcomes are being tracked, who owns the account, how consent requirements are handled, and what the team will verify before handoff.
Ownership and handoff terminology
This is where apparently small words can turn into expensive surprises. Our guide to working with a web design company covers the broader client-agency responsibility model. At minimum, understand the terms below before the final invoice or launch week.
Administrator account
An administrator account has elevated control over a system. Your business should know which systems require administrative access and whether a company-controlled account will exist for the domain registrar, DNS, hosting, CMS, analytics, search tools, payment services, email delivery, and other critical integrations.
License
A license grants permission to use software, fonts, images, plugins, themes, code, or other intellectual property under specific terms. “Included” does not always mean “owned forever.” Ask which licenses are recurring, transferable, agency-owned, client-owned, or replaced if the relationship ends.
Source files and repository
Source files are the editable originals used to create the delivered work. A repository is a system, commonly Git-based for code, that stores and tracks source changes. Not every simple website needs a client-managed code repository, but every client should understand what files and source materials exist, where they live, and what is transferred at handoff.
Backup and restore
A backup is a recoverable copy of website data or files. A restore is the tested process of returning the system to a usable state from that backup. Ask what is backed up, how often, how long copies are retained, where they are stored, and who is responsible for restoration.
Maintenance and support
Maintenance is planned work that keeps the website healthy over time, such as updates, backups, security work, compatibility checks, performance monitoring, and content-system care. Support usually refers to help when questions, incidents, or change requests occur. The scope should define what is included, what is billable, response expectations, and who owns urgent issues.
Handoff
Handoff is the transfer of the website, accounts, credentials, documentation, training, files, licenses, and operational responsibility at the end of a project or relationship. A good handoff is not “here is the login.” It is a controlled transfer that makes clear what the client now owns and what the provider still manages.
Five web design terms people commonly confuse
| Terms | Plain-English difference |
|---|---|
| Wireframe vs. mockup vs. prototype | A wireframe emphasizes structure, a mockup emphasizes visual design, and a prototype simulates interaction or flow. |
| Domain vs. DNS vs. hosting | The domain is the address, DNS directs the address to services, and hosting runs the website system. |
| Responsive vs. mobile-first | Responsive is the broader adaptive approach; mobile-first starts design or implementation from smaller screens and expands upward. |
| UX vs. UI | UX concerns the quality of the experience and task flow; UI concerns the interface people see and operate. |
| QA vs. UAT | QA is the delivery team’s quality verification; UAT is business-side acceptance of the delivered system for its intended use. |
Terms that should be defined in the written scope
Some terminology is too important to leave as sales-call shorthand. When you compare proposals, require the important promises to become written responsibilities. Our full guide to choosing a web design company covers vendor evaluation in detail. For terminology, focus on whether the scope defines these items clearly:
- Deliverables and exclusions: what is included and what is not.
- Dependencies: what the client or a third party must provide and by when.
- Revisions and change requests: how feedback works and when added work changes cost or schedule.
- Acceptance criteria and UAT: how completion is judged.
- Browser and device support: what environments are tested.
- Accessibility target: what standard, conformance level, templates, and testing are included.
- Performance target: what metrics are measured and under what conditions.
- SEO and redirects: what migration or technical search work is actually included.
- Ownership and licensing: who controls accounts, source, content, software licenses, and third-party services.
- Handoff and training: what is transferred and how your team learns to operate it.
- Recurring costs and support: what continues after the project and what happens if the relationship ends.
A proposal does not become sophisticated because it uses sophisticated words. It becomes useful when important terms have enough definition that both sides can tell what will happen next.
Questions to ask when a designer uses jargon
- What does that term mean on this project?
- What deliverable, behavior, account, or test proves it is included?
- What do you need us to approve or provide?
- Who owns this after the project ends?
- How will we verify it before acceptance?
- What is specifically excluded?
- If a third-party tool changes or breaks, who is responsible?
- Does this create a recurring license, hosting, maintenance, or support cost?
Those questions are more useful than trying to impress a designer by repeating technical vocabulary. Good web professionals should be able to explain a decision without hiding behind terminology.
Frequently asked questions about web design terminology
What does web design terminology mean?
Web design terminology is the vocabulary used to describe website strategy, structure, user experience, interface design, development, performance, testing, hosting, ownership, and maintenance. For a business owner, the useful terms are the ones that clarify what is being purchased, approved, tested, or handed over.
What web design terms should I know before hiring a designer?
Start with scope, deliverable, dependency, acceptance criteria, sitemap, information architecture, UX, UI, wireframe, mockup, prototype, responsive design, CMS, API, staging, domain, DNS, hosting, WCAG, QA, UAT, Core Web Vitals, administrator account, license, maintenance, and handoff. You can learn tool-specific vocabulary later if your project actually needs it.
What is the difference between UX and UI?
UX focuses on the quality of the user’s experience, including comprehension, navigation, task flow, and usability. UI focuses on the interface people see and interact with, such as controls, typography, spacing, visual hierarchy, and component states. Strong website work usually requires the two to support each other.
What is the difference between a wireframe, mockup, and prototype?
A wireframe is mainly about structure and hierarchy. A mockup is a more complete visual representation. A prototype simulates some interaction or flow. None of those automatically proves the final built website works correctly.
Is a CMS the same thing as hosting?
No. A CMS is software used to manage content. Hosting is the infrastructure that runs or serves the website. A WordPress website, for example, uses WordPress as its CMS while running on a hosting environment.
Do I need to know how to code before hiring a web designer?
No. A client does not need to become a frontend or backend developer. You should understand enough terminology to ask what is included, what is custom, what can be edited, how the work will be tested, what you will own, and what responsibilities continue after launch.
Does “SSL certificate” still mean the same thing?
People commonly still say “SSL certificate,” but modern secure web connections use TLS. The practical requirement is a correctly configured HTTPS connection, a valid certificate, reliable renewal, and monitoring for security or redirect problems.
What is the difference between QA and UAT?
QA is the delivery team’s process for finding defects and checking the implementation against requirements. UAT is the client or business-side process for confirming that the delivered website is acceptable for its intended use. Both matter, and neither should be replaced by a quick visual review.
Know enough lingo to make better decisions, not to play designer
The goal of learning web designer lingo is not to micromanage the people you hire. It is to recognize when an important promise is specific enough to approve and when it still needs a definition.
Use the Definition → Deliverable → Decision test whenever a proposal or project conversation becomes fuzzy. If a term cannot be connected to a concrete output, behavior, account, test, responsibility, or owner, keep asking questions.
If you want a web team that explains the work in business language and makes responsibilities explicit, talk with Scope Design about your website project.
