72% of clients report that their website did not meet their expectations after launch, according to Clutch’s web design satisfaction survey. The gap between expectation and outcome almost always traces to deliverables that weren’t defined upfront — or weren’t included at all. Here is a specific, itemized list of what a professional WordPress build should include. Use it to evaluate any quote you receive.
Discovery and Strategy Deliverables
The discovery phase defines what the site needs to accomplish before any design starts. Skipping it produces sites that look good in a mockup and miss the mark at launch.
Project Brief and Scope Document
A written document that defines: number of pages, functionality requirements, content ownership (who writes it, who sources images), timeline, revision rounds, and success criteria. If you’ve received a quote without a written scope, you don’t have a project — you have a handshake. Scope documents prevent the most common cause of project disputes: disagreement about what was included.
Sitemap: Page Architecture
A sitemap is a hierarchical diagram of every page the site will include, showing navigation structure and content relationships. It answers: how many pages, what are they called, how do they link to each other? A sitemap is not a deliverable you create after design starts — it’s what makes design decisions possible. If a designer shows you mockups without a sitemap, the page count and architecture are assumptions, not agreements.
Wireframes or Low-Fidelity Layout Plan
Wireframes are structural page layouts without visual styling — boxes and placeholders showing where content, images, navigation, and calls to action will appear. They answer layout questions before design decisions are made. Wireframes cost less to revise than high-fidelity mockups. A professional build uses wireframes to align on structure before investing time in visual design.
Keyword and Intent Mapping for Each Page
Each page should have a defined primary keyword and a clear understanding of the search intent it serves (informational, navigational, transactional). This mapping ensures the page architecture reflects how people search — not just how the client thinks about their own business. Missing this step produces sites with poor SEO architecture that require restructuring within a year.
Design Deliverables
Design is what clients see first and remember longest. It also has the most revision risk — expect this phase to have the most back-and-forth, and budget for it accordingly.
Visual Design Mockups: Desktop and Mobile
High-fidelity mockups show exactly how each unique page layout will look: typography, color, imagery, spacing, and component styling. You should receive mockups for desktop and mobile for each distinct layout. A “unique layout” means a different page structure — not necessarily every page. A 10-page site might have 4–5 distinct layouts (homepage, interior page, contact, blog, single post).
If a designer shows you only desktop mockups, mobile design is being deferred to the development phase — which means mobile layout decisions are made during coding, not design, with less iteration available.
Brand Integration: Typography, Color, and Iconography
The visual design should implement your existing brand consistently: the exact brand fonts, color palette (with HEX/RGB values), logo usage, and any iconography or illustration style. If you don’t have a style guide, the designer should establish one during this phase — what fonts and sizes are used for headings and body text, what button styles exist, what the spacing system is. Without this, visual consistency deteriorates over time as the site is updated.
Revision Rounds: Defined Scope
Know exactly how many revision rounds are included and what constitutes a revision. A standard professional engagement includes 2 rounds of design revisions. Unlimited revisions is a red flag — it signals either a vague scope or a mechanism for scope creep. Revisions should address feedback from the delivered concept; they are not redesigns.
Style Guide or Component Library
At project close, the design system should be documented: type sizes, color values, button states, form styles, card components, spacing values. This documentation allows any designer or developer to add new pages or features that match the existing site without reverse-engineering the design from the production code.
Development Deliverables
Development is where the design becomes a working website. The technical decisions made here determine the site’s performance, maintainability, and SEO architecture for its entire lifespan.
Custom WordPress Theme: No Third-Party Page Builder
A professional WordPress build uses a custom theme — code written specifically for your site, with no page builder (Elementor, Divi, WPBakery) in the stack. Page builders add 200–400ms of render-blocking JavaScript to every page load, producing Lighthouse mobile scores of 38–65 even on well-optimized sites. A custom theme produces Lighthouse scores of 85–98 without optimization overhead. If your quote doesn’t specify “custom theme” or “hand-coded,” ask directly: “Will this site use a page builder?” The answer determines your performance ceiling.
Mobile-Responsive Code Across All Breakpoints
Mobile-responsive means the site adapts correctly to every screen width — not just desktop and one mobile size. A professional build specifies and tests at minimum 4 breakpoints: large desktop (1440px+), standard desktop (1280px), tablet (768px), and mobile (375px). Every layout and component is tested at each breakpoint before launch.
Contact Forms With Spam Protection
Every contact form should include CAPTCHA or honeypot spam protection. Without it, bots will fill your inbox with spam within days of launch. The form should be tested end-to-end on the live site — submission through to inbox delivery — before the project closes.
Performance Optimization: Caching, Images, CDN
A professional build delivers a site that meets its performance targets at handoff — not a site that needs additional optimization work after launch. That means: caching plugin configured (WP Rocket or equivalent), images compressed and served in WebP format, lazy loading enabled for below-fold images, and CDN routing in place (Cloudflare). The Lighthouse mobile score should be tested and documented before handover.
SSL Certificate Configuration
All sites should serve over HTTPS. This requires an SSL certificate installed and correctly configured — all HTTP URLs redirecting to HTTPS, no mixed content errors (HTTP resources loading on an HTTPS page). SSL is a basic security requirement and a minor Google ranking signal. It’s not optional and it’s not a billable extra.
Accessibility Compliance: WCAG 2.1 AA Basics
WCAG 2.1 AA compliance means the site is usable by people using screen readers, keyboard navigation, and other assistive technologies. Practical requirements: all images have descriptive alt text, color contrast ratios meet minimums (4.5:1 for body text), all interactive elements are keyboard-navigable, and form fields have proper labels. ADA website lawsuits increased 23% in 2023 — accessibility is both a legal consideration and an SEO factor (semantic HTML that works for assistive technologies also works better for search crawlers).
SEO Setup Deliverables
SEO setup is the most commonly omitted category in under-budget web builds. It’s invisible at launch and clients rarely know to ask for it specifically. Demand each item by name.
On-Page SEO: Meta Titles, Descriptions, Heading Hierarchy
Every page needs a written meta title (under 60 characters, primary keyword included), a meta description (under 160 characters, value statement included), and a logical heading hierarchy (one H1 per page, H2s for sections, H3s for subsections). These are not optional fields — they determine how Google displays your pages in search results and how crawlers understand page structure.
XML Sitemap: Generated and Submitted to Google Search Console
Your XML sitemap lists every page Google should crawl. It should be generated automatically by your SEO plugin (Yoast, Rank Math) and submitted to Google Search Console on launch day. Google Search Console takes 2–4 weeks to begin populating data after a site launch — delayed submission means delayed ranking visibility. If your developer doesn’t submit the sitemap on launch day, do it yourself.
Schema Markup: Organization, LocalBusiness, or Appropriate Type
Schema markup is structured data in your site’s HTML that tells Google what type of entity you are. For a local business: LocalBusiness schema with your address, phone, hours, and service area. For a professional services firm: Organization schema. For a blog: Article schema on posts. Sites with correct schema markup are eligible for rich results (star ratings, address in search listings, FAQ dropdowns) — these improve click-through rates significantly. Sites without schema miss those opportunities. Approximately 30% of Google searches return a rich result or featured snippet (SparkToro) — schema is what makes your site eligible.
robots.txt Configuration
The robots.txt file tells search crawlers which pages to index and which to skip. A properly configured robots.txt blocks admin pages, login pages, and staging paths from indexing. An incorrectly configured robots.txt — particularly one that blocks all crawling, a common staging server setting left live — can prevent Google from indexing your site at all. Verify this file before launch.
301 Redirect Structure (If Replacing an Existing Site)
If the new site changes any URL from the existing site, every old URL needs a 301 redirect to the new destination. Missing redirects cause 404 errors on pages that may have backlinks or accumulated ranking signals. A missing redirect on even one high-traffic page causes measurable ranking loss. The redirect map should be built during the project, tested on staging, and verified on production at launch.
Google Analytics 4 Installation With Goal Tracking
GA4 should be installed and verified firing on every page — not just the homepage. Goal tracking means the specific actions you care about (form submissions, phone link clicks, e-commerce transactions) are configured as conversion events in GA4. Without goal tracking, you have traffic data but no conversion data — you cannot measure whether the site is working.
Content Deliverables
Content scope varies by project. Understand exactly what’s included before signing.
Page Copywriting: If Included, Clarify Scope
Many web design quotes do not include copywriting — you’re expected to provide content. If copy is included, understand: how many pages, how many words per page, how many rounds of revision, and what keyword research informs the copy. Copywriting is a significant labor item — $100–$200 per page is a reasonable rate for professional web copy. Clarify scope or budget accordingly.
Image Sourcing and Optimization
All images should be sourced (either from your library, a stock photography subscription, or a licensed source), sized correctly for their display dimensions, compressed to WebP format, and given descriptive alt text. An image handed off at 4000px wide and 3MB is not a production-ready image — resizing and optimization should happen before upload, not after.
Content Migration From Existing Site
If you have an existing website with pages, blog posts, or product content that needs to transfer, content migration should be explicitly in scope. It involves copying content, reformatting it for the new structure, checking for broken links, and updating internal references. Unscoped content migrations are a common source of project delays and cost overruns.
Launch and Handover Deliverables
The launch phase and what you receive at the end of the project matter as much as the build itself.
Pre-Launch QA Checklist: Minimum 30 Points
Before launch, a professional build passes a thorough QA review: all pages load correctly on iOS Safari and Chrome Android, all forms submit and deliver to the correct inbox, no broken internal links, no accidental noindex tags on any page template, Core Web Vitals pass on mobile, all redirects verified, and Analytics firing on all pages. This checklist should be documented and available to you as a client.
Less than 20% of web projects under $2,000 include documented QA in our observation. That’s where post-launch form failures, mobile display errors, and tracking gaps originate.
Staging to Production Migration
The build should be developed on a staging server (a private test environment, not live) and migrated to the production server for launch. You should never be asked to review a site that’s being built live on your domain — that’s a signal of a poorly structured process.
WordPress Admin Training
At project close, you should be able to update your own pages, add blog posts, and manage basic content without calling your developer for every change. Training should include a screen-recorded walkthrough of the admin interface — how to edit a page, how to upload images, how to add a new blog post, where to find settings. Without this, you’re dependent on your developer for every content update.
Complete Documentation and Login Credentials
At handoff, you receive: WordPress admin login (username + password), hosting account login (cPanel, server dashboard, or equivalent), domain registrar login, and a written guide to common admin tasks. You also receive documentation for any custom functionality built for the site. Without this, you cannot manage your own site or hand it to a future developer without starting from scratch.
For more on how these deliverables relate to project cost, see our custom website cost breakdown. If you’re planning a redesign, read the website redesign checklist to understand which of these deliverables are most critical during a migration.
Frequently Asked Questions
What should a professional WordPress website include?
Discovery and sitemap, wireframes, visual design mockups (desktop and mobile), custom-coded WordPress theme (no page builder), mobile-responsive development, contact forms with spam protection, SSL configuration, performance optimization, on-page SEO setup (meta tags, heading hierarchy), schema markup, XML sitemap submission to GSC, Google Analytics installation, pre-launch QA, and admin training at handover. Copywriting and image sourcing are separate scope items.
Does a custom WordPress build include SEO?
It should include technical SEO setup: meta titles and descriptions on every page, XML sitemap generated and submitted, Organization or LocalBusiness schema markup, robots.txt configuration, and 301 redirects if replacing an existing site. This is not the same as ongoing SEO (content creation, link building, ranking improvement) — that’s a separate service. A professional build gives you the technical SEO foundation; ongoing SEO builds on top of it.
What is the difference between a wireframe and a mockup?
A wireframe is a structural layout — boxes and placeholders showing where elements go, without visual styling. It answers layout questions before design effort is invested. A mockup is a high-fidelity design showing typography, color, imagery, and component styling — it looks like the finished site. Both should be included in a professional build process: wireframes first, mockups second, after structure is approved.
Should a web developer set up Google Analytics for me?
Yes. GA4 installation and basic goal tracking should be included in a professional web build. If the developer doesn’t set up Analytics, you’ll launch with no traffic data — and you won’t notice until you try to pull a report. At minimum: GA4 pageview tracking on all pages, and one conversion event configured (form submission or phone click). Without goal tracking, Analytics shows you traffic but not whether the site is working.
What is schema markup and should my website have it?
Schema markup is structured data embedded in your site’s HTML that tells Google what type of entity you are and what information is relevant — your address, hours, services, reviews. Sites with correct schema are eligible for rich results in Google search (star ratings, address information, FAQ dropdowns). These rich results improve click-through rates. LocalBusiness or Organization schema is appropriate for most small business sites and should be installed at launch.
How many revision rounds should I get in a web design project?
Two rounds is standard for a professional engagement. The first round addresses your initial feedback on the design direction. The second round resolves remaining details. Additional rounds are typically billable. The key to minimizing revision rounds: a clear brief before design starts, with specific examples of sites you like and specific elements you want to avoid. “Make it look more modern” produces more revision rounds than “I want a design similar to these three sites I’ve bookmarked.”
What documentation should I receive when my website launches?
At minimum: a written guide to updating page content in WordPress (how to edit text, how to upload images), instructions for adding new blog posts, login credentials for WordPress admin, your hosting account, and your domain registrar — plus screen-recorded walkthrough of the admin interface. For sites with custom functionality, documentation for how that functionality works and how to manage it. Without this documentation, every content change requires your developer’s time and your money.
The gap between a professional build and a cheap one isn’t visible in the mockup. It shows up in the SEO setup that wasn’t done, the mobile QA that was skipped, the admin training that never happened, and the schema markup that never shipped. Our custom WordPress builds include every deliverable on this list as standard. See our fixed-price packages for the entry point — no hidden scope items, no post-launch surprises.