A WordPress website QA checklist should answer one question before you hand over a site: can a visitor complete the task the client is paying for? Start with the most important journey. On a service website, that might mean opening the mobile menu, finding the right service, submitting an enquiry and receiving it in the client’s inbox. Record what happens at each step. A polished homepage tells you little about whether that journey works.
Consider a five-page website for a training centre in Dhaka. A prospective student opens the site on a phone, compares two courses and asks about the next batch. The centre considers the website successful when its admissions team receives the student’s question and can reply. We will use that example throughout this guide. You can adapt the same tests to a consultant, agency, local shop or professional portfolio by changing the visitor’s goal.
If website delivery is one of the services you want to offer, see the freelancing skills guide for Bangladesh. The Freelancing in Bangladesh hub connects that skill to portfolio building, client work and payments.
WordPress website QA checklist at a glance
Use this table during your final review. Copy it into your project sheet and give each row a result: Pass, Fail, Blocked or Not applicable. “Blocked” is useful when you can submit an enquiry but need the client to confirm delivery to an inbox you cannot access. Keep that row open until someone with access completes the check.
| Check | Pass condition | Evidence to keep |
|---|---|---|
| Primary visitor journey | A signed-out visitor can move from the landing page to the agreed outcome. | Starting URL, steps and final result |
| Contact or enquiry form | A valid submission reaches the agreed destination with the correct details. | Test reference and recipient confirmation |
| Invalid form input | The visitor can identify the field, correct it and finish the submission. | Error text and result after correction |
| Mobile navigation | The menu opens, reveals every key link, closes and leaves the page usable. | Device, browser and menu result |
| Keyboard navigation | Key actions are reachable, focus is visible and the visitor can leave each control. | Keyboard sequence and any blocked step |
| Responsive layout | Text, images and controls remain readable and usable between design widths. | Page URL and width of any failure |
| WordPress templates | Representative pages, posts and navigation elements display the intended content. | One tested URL per template |
| Production handover | The essential journey passes on the public domain and the client can maintain the agreed content. | Live test result, owner and sign-off date |
1. Agree on what “ready for delivery” means
Ask the client to finish this sentence: “A customer should be able to visit our website and…” Their answer gives you your first acceptance test. The training centre might say, “Choose a course and ask when the evening batch starts.” Write that down using the client’s words. You now know which menu item, course page, form field and notification destination belong in the same test.
List the templates and integrations included in the job. Five pages may share a header and footer but use three different layouts. Test the shared menu once in depth, then check its placement on each layout. If the blog uses a separate header built with a page builder, treat that header as a separate item. Sharing a logo does not guarantee the navigation uses the same implementation.
Agree on the browsers, devices and special features you will cover. Record what you actually have available. For example, you might test on a physical Android phone and use browser tools to inspect intermediate widths. If the client specifically requires an iPhone Safari check, assign it to someone with access to that environment. A resized desktop browser gives you useful layout evidence, but it cannot complete that particular device check.
2. Test the contact form from submission to receipt
Open the contact page in a signed-out browser window. Enter recognisable test data and include a unique reference such as “QA evening course 01” in the message. Use an email address you control for the reply field. Tell the recipient in advance that you are testing, especially if a submission creates a lead, sends an automatic reply or alerts several team members.
Submit once and observe the page. Does the button indicate that a request is in progress? Is the confirmation easy to find on a small screen? Does it tell the visitor what happens next? Then follow the data. Ask the admissions team to locate the unique reference and compare the course selection, email address and message with the original submission. If the agreement includes a CRM entry, verify that record as well.
Check who receives the reply
Have the recipient press Reply on the test notification and inspect the destination address before sending. A form can deliver every submission successfully while directing replies back to the website’s own mailbox. In that situation the developer sees a successful delivery, the client believes they responded and the prospective student hears nothing. One reply using your test address exposes the problem.
If the website shows success but the recipient cannot find the message, record those as two separate results. Note the submission time, time zone, destination and test reference. Check any submission record available in the site’s form setup, then ask the person responsible for email delivery to trace that reference. After a correction, send a fresh enquiry with a new reference so an old delayed message cannot be mistaken for a successful retest.
3. Try the mistakes a real visitor might make
Leave a required field empty and enter an incomplete email address. Submit the form, read the feedback and correct one field at a time. The instructions should identify the affected field and explain the correction. A red outline on its own gives little help to someone who cannot distinguish the colour or who is looking at a different part of a long form.
On the mobile version, begin at the bottom of the form when you press Submit. If the invalid field is above the visible area, can you tell where to go? Check that the message you already typed survives the correction. For a detailed enquiry, losing two paragraphs because a phone number was incomplete can be enough to make the visitor abandon the form.
Pay attention to local input where it matters. If the training centre accepts Bangla names or messages, try both in your test enquiry and check the received text. Ask which phone-number formats the client intends to accept. An optional phone field should also allow a successful submission when left blank. These checks take only a few minutes and can reveal a form that works with the developer’s usual sample data but fails for its intended audience.
Start at the top of the homepage. Open the menu, expand a submenu, choose a course and return using the browser’s Back button. Open the menu again. Watch for leftover overlays, lost scroll position or a page that no longer scrolls. A menu can pass the simple open-and-close test yet fail after a visitor actually follows a link.
Repeat the journey after scrolling far enough for the sticky header to appear. Look at the lowest item in the expanded menu. On a short screen, a fixed call button, chat widget or cookie banner may sit above it. Try to tap the visible text with your thumb. If you have to rotate the device or dismiss an unrelated widget to reach Contact, record the combination that caused the obstruction.
In the training centre example, use the longest real course title in the menu. “Courses” fitting neatly on one line proves very little about “Weekend Professional Development Courses.” Test the label the client intends to publish and note the exact device orientation. That detail helps whoever fixes the header reproduce the same layout.
5. Complete the main journey using only the keyboard
Put the mouse aside. Use Tab to move forward, Shift and Tab together to move backward, and Enter to follow a link. On a menu button, test the keyboard interaction appropriate to the control, including Space where applicable. Move from the navigation to a course page and through the enquiry form. Keep your eyes on the focus indicator. At every step, you should be able to tell which control will respond next.
If a menu or dialog opens, explore what happens at its boundaries. Can you reach its controls? Can you close it using the keyboard? When it closes, can you tell where focus has gone? A common failure is a visually closed panel whose hidden links still consume several Tab presses. Record the last visible control before focus disappears and the first visible control where it returns.
Check error recovery with the keyboard too. Trigger a validation message, return to the incorrect field and submit successfully. If the form contains a custom dropdown, verify that you can choose the intended course without a pointer. Describe your result narrowly at handover: “Completed the course enquiry journey using keyboard controls” tells the client what you tested. A single keyboard pass does not establish accessibility across the whole website.
6. Check responsive layouts between the design frames
Open a page with the most demanding content, such as a course comparison, a long heading or a pricing table. Slowly resize the viewport between the supplied desktop and mobile layouts. Pause wherever the page changes structure. Two polished screenshots at the endpoints can hide a width where the navigation wraps, the price overlaps a button or a column shrinks until each word occupies its own line.
Test with real copy and images. A portrait headshot, a service title twice as long as the sample and a paragraph containing an email address can each change the layout. Look for unwanted sideways scrolling on the page. If a wide comparison table is designed to scroll horizontally, check that visitors can move the table while the rest of the page stays steady.
Increase the browser zoom and repeat the primary action. Notice whether fixed elements take up most of the screen or hide the field you are editing. Record an exact observation such as “At 200% desktop zoom, the sticky footer covers the Send enquiry button.” That is more useful than “responsive issue,” and it gives the developer a clear condition to retest after adjusting the layout.
7. Review the WordPress pages the client will maintain
Ask the client which updates they expect to make in the first month. For the training centre, that might mean changing a batch date, replacing an instructor photo and publishing a new course announcement. On a staging site or test draft, perform those actions using the role the client will actually have. Preview the result on desktop and mobile. An attractive layout that breaks after a routine edit creates a handover problem.
Check a representative URL for each template in scope. For a site with a blog, open the posts listing, an individual article and any category archive linked from the menu. Follow the logo, footer contact link and primary call to action. Read the destination page title and URL. A button can open a perfectly functional staging page and still send a real customer to the wrong place.
Review the signed-out experience after making a visible test change in staging. A logged-in editor may see an updated header while ordinary visitors receive an older cached version. Record which version appeared and where. Once the client approves the content, remove test pages, placeholder contact details and sample messages from the agreed delivery surfaces. Keep any evidence needed for sign-off in the project record.
8. Write a defect report someone else can reproduce
Give every issue a URL, environment, action, expected result and actual result. Include the browser and device when they matter. A screenshot helps illustrate an overlap, while a short sequence of steps explains a menu failure. Use fictional test data in evidence shared with the client. Crop personal inbox details from a delivery confirmation.
| Example defect field | What to record |
|---|---|
| Issue | Course enquiry loses the selected course in the notification email. |
| Environment | Staging, signed out, contact page, Android Chrome. |
| Steps | Select Evening Excel, enter valid test details and submit once. |
| Expected | The admissions email includes Evening Excel and the reply reaches the test sender. |
| Actual | The email arrives, but its course field is blank. |
| Owner and retest | Form owner checks field mapping. QA sends a fresh enquiry and asks admissions to confirm the course value. |
Prioritise according to the visitor and business outcome. A missing enquiry or an unreachable mobile menu may block delivery. An inconsistent gap below an instructor bio might be accepted for a later revision. Let the client see both, along with the impact and owner. After a shared component changes, repeat its related checks on other templates. Fixing navigation on the homepage can affect the same navigation on the contact page.
9. Run a short live check before asking for sign-off
Changes between staging and production can affect destinations, form recipients and cached files. Once publishing has been authorised, open the public domain in a fresh signed-out window. Follow the primary mobile route, submit a clearly identified live test enquiry and confirm the final destination with the client. For a download, open the actual file and check that it is the approved version. For a booking, coordinate any test reservation with the person managing the calendar.
Send a short handover note with the date, the URLs tested, the completed journeys and any open items the client accepted. A useful sentence is specific: “Admissions confirmed that test enquiry QA-07 arrived with the selected course and that Reply reached the test sender.” If the client has yet to confirm receipt, say who will check it and when. This gives both parties the same understanding of what delivery includes.
Reserve time for this final pass when you prepare the original quote. Include time for the checks, one agreed correction cycle and a retest of affected journeys. Blogerhub’s freelance pricing guide can help you account for delivery work. With permission, you can also turn an anonymised before-and-after fix into a freelance portfolio case study.
When is a WordPress site ready for client delivery?
A site is ready for sign-off when the agreed visitor journeys work on the agreed environments, the client has verified outcomes only they can confirm, and every remaining issue has a named owner and an accepted next step. For the training centre, the decisive evidence is an enquiry a prospective student can send and the admissions team can answer. Finish your WordPress website QA checklist by recording that outcome, who confirmed it and the date.
