Most sites don't have a technical problem. Some sites have nothing else.

Work through the symptoms above. If your traffic dropped after a redesign, pages are missing from the index entirely, you're on a JavaScript framework, or you have thousands of URLs - probably yes. If your rankings slipped slowly over a year, or you've never ranked at all, almost certainly not, and the honest answer is that your budget belongs in content and links instead. We'd rather tell you that on the first call.

An SEO audit is a diagnosis across four areas like technical, content, links and conversion - delivered as prioritised tickets. This is the implementation of the technical ones. If you already know what's broken, come here. If you know something is wrong but not what, start with the audit; buying implementation before diagnosis is how businesses spend a quarter fixing something that was never the problem.

Either. Where you have a development team we write the specification and work alongside them, because they know your stack and their deployment process better than we will. Where you don't, we make the changes ourselves. Every change is one your own developer can verify independently - we don't do anything that only works because we did it.

Some of it, and a good developer will have handled the basics. The gap is that developers build for users and browsers, while a lot of this is about crawlers - which behave differently, render on a delay, and follow rules nobody encounters during normal QA. A site can pass every functional test and still have a canonical tag quietly telling Google to ignore it. If you're planning a build, our web design team handles both sides from the start.

Depends entirely which fix. Indexation problems can resolve within days - remove whatever was blocking a page and it can reappear on the next crawl. Redirect and canonical corrections after a migration typically take four to eight weeks to consolidate. Core Web Vitals improvements are slowest to show in search because Google uses field data collected over a rolling period, so expect a month or more before the change is even reflected in the reporting.

No, and be careful with anyone who does. Core Web Vitals are measured from real users on real devices and real connections - a visitor on a five-year-old phone with poor signal will record worse numbers than any lab test, and that's counted. We can make meaningful, measurable improvements and get most sites into the passing range. We can't promise a number that partly depends on who visits you.

Before it launches, and ideally before the URL structure is decided. Pre-launch URL mapping is the cheapest technical work available and it prevents the single most expensive problem in this category. Post-launch recovery is possible, takes longer, costs more, and some of the lost authority doesn't fully return. See the three timings above - the difference between the first column and the third is substantial.