Technical SEO

Yes. Some people search for SEO tech, technical search optimisation or site health; it's the same work. It covers how search engines crawl, render and index the site, separate from the words on the page or the links pointing at it. We keep it on one page because the diagnosis, the developer tickets and the validation belong together, whatever the service is called on someone's quote.

Not necessarily on its own. The PageSpeed Insights score is a lab test on one simulated device. Google uses Core Web Vitals from real Chrome users as a ranking signal, and it's one of many. A site can score poorly in the lab and pass in the field, or the reverse. We look at field data for your key templates first. Slow mobile pages still lose enquiries from impatient visitors, so speed work can pay off even where rankings don't move.

For a service business, LocalBusiness markup with your name, address or service area, phone and hours is worth having, and Service markup can describe what you offer. It helps search engines and AI tools read the page; it is not a ranking boost by itself, and it must match visible content. Google now shows FAQ rich results only for a small set of authoritative government and health sites, so adding FAQ schema to win extra space in results no longer works.

Yes. Technical SEO removes barriers; it doesn't give Google a reason to prefer you. If the pages are thin, the business has few reviews or links, or competitors answer the search better, clean code won't change that. Our recommendations say so when content or authority is the bigger constraint, so you don't spend developer time on fixes that can't move the result.

Start with the free marketing audit. We check indexation, mobile performance and obvious crawl problems on your main service pages, then give you a ranked checklist. If the findings point to deeper technical problems, we can scope a full technical review with your developer involved from the start.