We look at the customer path first: whether services and areas are obvious, whether contact details look real, and whether phone links, buttons and forms are present and reachable. We do not submit live forms or send test enquiries unless you have authorised that.

On a phone we check readability, thumb-sized controls, and obvious overflow or cut-off blocks. Accessibility notes we can make from the public page (missing alternative text, poor contrast we can see, unclear labels) are observations. This is not a WCAG certificate.

Structure and discovery stay on pages we can reach from the public site unless we agree a crawl. A wider crawl — internal links, a published sitemap, orphaned pages, redirect chains, and a count of URLs discovered versus URLs successfully checked — is included only when that scope is agreed, or inside the separately commissioned Technical SEO Project, which also fixes the technical issues found. Login-blocked or robots-blocked URLs are recorded as not checked, not as fine.

Service pages should help someone decide, not only repeat the business name. Two similar URLs are not automatically duplicates: a trade overview and a specific job, or two towns you genuinely serve, can both stay. On-page SEO here means titles, descriptions, H1s, internal links, canonical and indexability signals, and structured data that is actually present — not a promise of rich results. A missing meta description is an opportunity, not proof of a penalty.

Technical notes cover HTTP responses, redirect chains we follow, broken assets we request, and robots or noindex instructions. Performance is included only where we take a measurement. Lab PageSpeed figures are laboratory numbers, not real-user Chrome data. A review is not a penetration test, malware scan or hosting migration.

If tracking tags are visible in the page source we say so. Seeing a tag is not the same as proving it fires or that conversions are recorded. One failed detection is not proof you have no analytics. Name, phone and area wording should agree across the pages we check; listing management and town-and-trade visibility are separate services.

The sequence is ordinary on purpose. You tell us what the site is for, the towns and services that matter, and anything you already know is awkward. We agree scope: public-site review, crawl-backed audit, analytics access, or a later implementation project. We do not start a full crawl or ask for logins until that is agreed.

We then fetch the public pages in scope, keep findings tied to URLs and dates, and write the report. You decide what to do yourself, hand to a developer, or commission from us. Public access is enough for what visitors see. CMS, analytics, Search Console or hosting access is only for deeper agreed checks. We can review WordPress and other common platforms as they appear on the public internet. A review does not mean we can edit every platform.

Please send the live URL, the main services and towns, any pages you already worry about, and whether you can share analytics or Search Console if you want those included.

The report is written for the business owner, not as a dump of crawler output. You receive the site, town and services you asked us to review, and the date of the evidence. Genuine strengths — only what we can support. Findings with affected URLs where we have them, and why each issue matters for customers or for keeping the site maintainable. Prioritised recommended changes, with a suggested owner and effort where we can reasonably say: you, your developer, or us if you later buy implementation. We will not invent a same-week guarantee. A single clear next step, not a twenty-page wish list.

An observed issue is something we saw on a checked URL. An opportunity that needs more investigation stays labelled as an open question — for example whether analytics conversions are firing, or why a page is slow for real users. Examples in a sample report are illustrations. Your site is described from its own evidence.

After the report you have three honest options. A review does not automatically become a recommendation to rebuild. You can act independently, hand the ordered list to an existing developer, or commission implementation through Website Optimisation — quoted changes, Growth (up to three agreed tasks a month after setup) or Premium Managed Growth (substantially more monthly website work, with technical SEO included). The review itself does not include making those changes.

If the review finds technical issues, we’ll quote for fixing them based on what the review finds. There’s no obligation to go ahead.

See pricing for how larger technical work is priced

A new website is recommended only when the current site is not a practical base and the evidence says so — not as a default upsell. Monthly Free or Monitoring visibility reports are not the same as re-crawling the whole website every month.