Most of what a B2B site needs is not a twelve-month retainer. It is four or five specific jobs done properly, once. Here is each of them, how long it takes, and why it moves anything. Tell me what you have and I’ll price it properly, or bundle a few together, which is usually the cheaper way to do it.
Each one is scoped and delivered on its own. Take one, take three as a package, or take none and start with an audit to find out which you actually need.
013–5 days
Title & structure clean
Every page title, meta description and heading hierarchy on your site, rewritten and put in the right order.
Why it moves anything
Titles and headings are how Google and every AI engine decide what a page is about. Most B2B sites have titles that were typed into a CMS field once and never looked at again, and heading levels that skip from H1 to H4 because that size looked right. This is the cheapest ranking movement available, and it takes days rather than months.
Rewritten title and meta for every indexable page
Heading hierarchy corrected page by page
Delivered as a sheet your team can paste in, or implemented by me
022–4 days
Schema pack
Structured data written, validated and installed across your whole site.
Why it moves anything
Schema is what a machine reads before it reads your words. It turns your services, prices, reviews and answers into facts that can be quoted directly, instead of prose an engine has to interpret and might get wrong. It is also the single most common thing missing from a B2B site.
Organisation, Service, FAQ, Article and Breadcrumb markup as your site needs it
Validated against Google's rich results requirements
Installed, or handed over as ready-to-paste JSON-LD
032 days
AI crawler access & llms.txt
Making sure AI engines can actually reach you, and telling them what you are when they do.
Why it moves anything
OpenAI runs three separate crawlers, not one. Plenty of sites blocked all of them in 2023 to opt out of training, and in doing so removed themselves from ChatGPT search entirely. Most have no idea. This is a two-minute check and a two-day fix, and for some sites it is the only thing standing between them and being cited.
Crawler access audited and corrected across every major AI engine
Training and search access separated, so you choose each independently
An llms.txt file written for your business and published at your root
041 week
AI answer pack
Twenty questions your buyers ask, answered in passages built to be quoted.
Why it moves anything
Answer engines do not read your page the way a person does. They look for a self-contained chunk that answers the exact question asked. A section that opens with three sentences of throat-clearing before reaching the point cannot be lifted, so it never gets cited, however good it is.
20 real buyer questions, researched not guessed
Each answered in the first line, sized to be lifted whole
FAQ schema on every one so the answer is machine-readable too
051–2 weeks
Competitor comparison pack
Five pages covering "you vs them" and "alternatives to them".
Why it moves anything
These are the highest-intent pages on the internet. Someone searching "alternatives to" is already mid-shortlist with a budget. If a competitor has that page and you do not, they get to frame the comparison, choose the criteria, and decide where you look weak. Writing your own is how you get back in the room.
5 comparison or alternatives pages, researched against live SERPs
Honest feature tables that hold up to scrutiny
Schema and internal links so they rank and get cited
061 week
Topic cluster map
A plan for what to publish, in what order, linked to what.
Why it moves anything
Most B2B blogs are a pile of posts that quietly compete with each other for the same term. A cluster map fixes the shape: which page owns which question, what links to what, and where the holes are. It is also what makes an AI engine treat you as a source on a topic rather than a single result.
Clusters built from real SERP overlap, not guesswork
A hub-and-spoke plan with the page that owns each question
An internal link matrix you can hand to whoever publishes
071 week
Content brief pack
Ten briefs detailed enough that your own writers can hit the target.
Why it moves anything
Most in-house teams can write perfectly well. What they usually do not have is a view of what is already ranking, why, and what shape the piece needs to take to beat it. That is the half that gets skipped, and it is why good writers produce content that never lands.
Target question, search intent and the angle that is missing
Section-by-section outline with word counts and what each must answer
The pages you are up against and where they are weak
083 days
Local visibility grid
Where you actually rank across a map, not one averaged number.
Why it moves anything
If you have locations or a service area, a single rank position tells you almost nothing. You can be first in the suburb your office sits in and invisible four kilometres away, where most of the searching happens. A grid shows you exactly where the drop-off starts and which competitor owns that ground.
Rank grid across your real service area, point by point
Who is beating you where, and on what
The profile and citation fixes that close the gap, in priority order
No prices on this page on purpose. Every one of these depends on how many pages you have, what state they are in, and how much of it you want me to implement rather than hand over. Tell me what you have and you will get a fixed number back, not a range. Take several together and it comes in under the sum of the parts.
Ongoing, not a one-off
Site Watch. Because sites drift.
An audit is a photograph. Then someone ships a release, a canonical points at the wrong page, a noindex escapes to production, robots.txt gets edited by a developer who was solving a different problem. Nobody notices for six weeks, and by then the traffic has already gone.
Site Watch takes a baseline of everything an audit checks, then re-checks it on a schedule and tells you what changed. Not a dashboard you have to remember to open. An email when something actually breaks, and silence when it does not.
Priced on how often you ship and how big the site is. Tell me both and I’ll give you a number.
Titles, meta descriptions and heading structure, page by page
Canonicals, noindex tags and anything that drops a page out of the index
robots.txt, including AI crawler access
Schema appearing, breaking or silently disappearing on a redeploy
Internal links that start returning redirects or 404s
Page speed and layout stability drifting the wrong way
Pages that quietly vanish from your sitemap
Monthly by default. Weekly, or on every deploy, if you ship often.
Not sure which you need
Start with an audit. Two sizes.
Buying a job you do not need is worse value than buying nothing. Both of these tell you which of the eight above would actually move something for you, and both come off the price if you go ahead with one.
Sales decks and one-pagers, AI setup and brand context with an interactive demo if you want to see what it does, interactive tools and calculators, and technical fixes implemented rather than handed over. Published from-prices for those are on the pricing page.
And if you would rather this ran every month instead of as one-off jobs, that is what the retainers are for.
No. Every job on this page is scoped and delivered on its own. Plenty of clients take one, fix the thing that was broken, and never take another. The retainers exist for teams who want this running every month, not as a gate in front of the one-off work.
Start with an audit. The Short List is NZ$149 and gives you a ranked list of what is broken, same day, with no call. The full Website Audit is NZ$497 and adds real code and two hours with your dev team. The cost of either comes off the price if you then book one of the jobs.
An audit is a photograph of one moment. Sites change: a release ships a noindex, a canonical starts pointing at the wrong page, robots.txt gets edited, schema disappears on a redeploy. Site Watch takes a baseline of everything an audit checks, re-checks it on a schedule, and emails you when something actually breaks. Priced on how often you ship and how big the site is.
Either. Every job can be delivered as files and instructions your own team applies, or implemented directly if you give me access. Implementation is included in the quoted price for most of these, and where it is not I will say so before you pay.
Yes, and it is usually cheaper to. A lot of the research overlaps, so three jobs scoped together come in under three jobs scoped separately. If you tell me what you are trying to fix I will often suggest a package rather than a single job.
Usually within a week. The turnarounds listed are working time once the job starts, not a queue estimate. If something is urgent, say so and I will tell you honestly whether it can jump.
Because they would be wrong. What each of these costs depends on how many pages you have, what state they are in, and whether you want it implemented or handed over. A list price would either overcharge a ten-page site or undercharge a thousand-page one. Tell me what you have and you get a fixed number back, in NZD excluding GST, before any work starts. The audit tiers and the monthly retainers do have published prices, because those are genuinely the same job every time.
That is my problem, not yours, provided the scope has not changed. Once you have a number it is fixed. If you add pages or change the brief midway I will tell you before doing the work, not after.
Next step
Not sure which one you need?
Send me your domain and what is bothering you. I will tell you which of these would actually move something, which would not, and whether you need any of it yet.