Start with the templates customers use
Choose the homepage, a service or product page, a category and a page with a form. If the site has many similar posts, check several URLs that use the same template. If the problem repeats, the developer can look for a shared cause.
At each URL, check the server response, title, internal links and route to the enquiry form. If a booking button disappeared after a theme update, save the URL and a screenshot. The screenshot shows what's missing.
To find the cause, the developer can check the theme, block settings and plugins.
Separate public observations from WordPress settings
Site Health in the WordPress dashboard reports internal checks and configuration details. Use it to make a list of questions. Reproduce the problem before concluding that plugins conflict or a hosting setting is responsible.
| Task | What you can see on public pages | What the owner or authorised specialist checks |
|---|---|---|
| Theme and templates | How pages look and which elements are missing | Active theme, template settings and recent changes |
| Plugins | Repeated errors, visible scripts and requests | Active plugins, versions and compatibility |
| Indexing | Page response, robots.txt, noindex and canonical | Visibility settings, where directives are set and URL status in Search Console |
| Form | Labels, field order and whether the button is reachable | Form handler and delivery of an approved test enquiry |
| Backups | A public page doesn't show whether backups exist or work | Files, database, date of the latest backup and a test restore |
Follow the path from a service to the enquiry form
Open the service page on a phone. See if you can find who it's for, what the work includes and how to contact the business. If the form opens blank, record the page you started on and how you got there.
An approved test submission and a matching record in an inbox or CRM can confirm delivery. The fields and button show what the visitor sees. The site owner checks what happens at the receiving end.
Measure speed on the template with the problem
If the catalogue is slow, measure a category page. Save the URL, mobile profile, date and a recording of the load. Look for the file or task that delays the content. Check the dashboard or code to confirm which plugin owns a file.
On a staging copy, a developer can change one setting at a time and rerun the test. After each change, check the menu, forms and blocks that depend on the theme or plugin.
Agree where to make the fix and how to recover the site
Record the observation, the owner of the task and how to check the result. For theme or plugin changes, schedule a release window and check who can restore the files and database. Use a staging copy first if you have one.
A review of public pages can't establish what's happening in the admin area or whether the site has vulnerabilities. If the business needs that assessment, agree its purpose, access and scope separately with a specialist.
Choose the audit that matches your question
Choose the free audit when you need to understand your own website first. Choose the competitive audit when your next decision depends on comparing your website with relevant alternatives. Both turn supported evidence into practical actions.