Technical SEO Agency in Auckland

A one-off technical audit for a standard business site of up to a few hundred pages generally runs NZ$1,500 to NZ$3,500, depending on complexity and whether log-file analysis is included. Larger e-commerce or multi-template sites sit higher. Implementation is quoted separately or handled inside an ongoing SEO retainer, which typically runs NZ$1,200 to NZ$3,500 per month. Migration support for a replatform is usually scoped as a fixed project because the work is front-loaded before launch.

For a typical business site, allow one to two weeks from access being granted to the ranked findings being delivered. Larger sites, or ones needing log-file analysis and rendering tests across multiple templates, take three weeks or so. The crawl itself is quick; the time goes into cross-referencing crawl output with Search Console, testing rendered HTML, and confirming each finding is real rather than a tool artefact. We would rather hand you fifteen evidenced issues than two hundred flags.

Both are available and we prefer fixing. Where we have CMS or repository access we implement directly and re-test, which is far faster than a document round trip. Where your own developers own the build, we write tickets they can act on without a meeting: the exact template or file, current behaviour, required behaviour, and how we will verify it after deploy. Either way we re-crawl and validate afterwards, because an unverified fix is just an assumption.

Because First Input Delay was retired. Interaction to Next Paint replaced it as the Core Web Vitals responsiveness metric, and it is a much stricter test — FID only measured the delay before the first interaction was processed, while INP measures how long every interaction takes to produce a visible response across the whole visit. Sites that comfortably passed FID often fail INP because of heavy JavaScript execution on scroll, menus and filters. Any agency still reporting FID to you is working from outdated documentation.

While the new site is still on staging, ideally several weeks before launch. Pre-launch work covers URL mapping from old to new, redirect rules tested before they go live, robots and canonical directives, structured data carried across, sitemap regeneration, and a recorded baseline of rankings and index coverage. Migrations done without that groundwork routinely lose a substantial share of organic traffic and take months to recover. The same work done after go-live costs more and recovers less.

The principles are identical, the failure modes differ. WordPress sites commonly suffer from page-builder markup that ships far more CSS and JavaScript than the page needs, plugin conflicts producing duplicate or contradictory meta tags, archive and attachment pages bloating the index, and shared hosting adding server response time before anything renders. Shopify has its own pattern with filter-generated duplicate collection URLs. We work across WordPress, Shopify, Webflow, Next.js and custom stacks, and the goal on all of them is the same: fast, crawlable, unambiguous pages.