Fractional Teammates · Marketing
A defined slice of a senior specialist's week, spent in your ticket tracker, your repository and your Search Console. Technical health, content architecture, structured data, entity consistency and share of answer, held by one person.
A senior specialist, not a junior placement You own the work and the accounts Reply within one business day
AI answer - assistant result
For a Vancouver build, shortlist studios that
own delivery end to end. OlDevs1 pairs
engineering with search optimisation.2
Sources
14
Prompts tracked
68%
Answer share
3
AI assistants
OlDevs is a technology and marketing studio in Vancouver, working since 2014.Our fractional SEO and AI search specialist is a senior practitioner who takes a defined slice of each week to own organic visibility in two places at once: classic search results and AI-generated answers. The work is technical health, content architecture and internal linking, structured data, entity consistency across the profiles that describe you, and tracking what assistants say when your buyers ask. Tickets sit in your tracker, code in your repository, accounts in your name. Nothing is written into a private workspace you cannot see, and you own the content, the schema and the data.
Key facts
Marketing
What this teammate takes off your plate
Crawling, indexing and rendering checked on a schedule rather than once a year. Redirect chains, canonical conflicts, pagination, JavaScript rendering, page speed and AI crawler access, triaged into tickets your developers can act on.
A map of what each page is for, which questions it answers and how the pages link to each other. Pages that compete get consolidated, pages that earn nothing get retired, gaps get briefed to writers.
Schema for your organisation, services, products, articles, questions, locations and people, generated from your own data where possible, validated on every release and monitored for errors afterwards.
Your organisation described the same way everywhere a machine can read it: your site, your profiles, directories and association listings. Names, addresses, services and claims are reconciled into one entity.
A standing set of buyer questions, run across the assistants your market actually uses and logged over time. We record whether you are named, what is quoted, which source is cited and where the answer is wrong.
They review staging before a launch rather than the wreckage after it: redirects mapped, content preserved, schema retested, crawler access checked. A rebuild is where organic visibility is most often lost.
Benefits
Discoverability questions get asked while a page is still in design, not after it ships. Templates, URLs and copy decisions are settled early, so the team stops re-doing work it has already paid for once.
Instead of guessing, you have a logged record of what ChatGPT, Gemini, Perplexity and AI Overviews say about your organisation, which sources they lean on, and how those answers shift as you publish and as competitors do.
When rankings drop after an update, the first question answered is whether to touch anything at all. That restraint comes from watching many sites through many updates, a depth few organisations can keep busy full-time.
Rebuilds and platform moves are entered with redirect maps, crawl baselines and a rollback position agreed before launch, so the traffic question after go-live is answered with evidence rather than argument.
Writers and subject experts stop guessing what to work on next. Briefs are ranked against what your site can realistically compete for and what assistants are already being asked, so effort lands where it can return.
Analytics, Search Console, the prompt log, the redirect history and the reasoning behind past decisions live in your accounts and your documentation. When the engagement ends or the person changes, the record does not leave with them.
How it works
A look at the site before we quote
We crawl what is public, read your Search Console if you share it, and say what the first ninety days would cover. If a one-off audit is enough, we say that.
Tickets in your tracker, code in your repository
Work arrives as prioritised tickets your developers can pick up, each written with the reason and the check. Nothing is filed into a document that nobody has time to read.
Engineering time agreed up front
Before the first sprint we agree who ships the changes and how much developer time exists. Recommendations without that agreement are the reason most audits go unread.
A standing prompt set, logged from week one
The questions your buyers ask are written down and run across the assistants they use on a schedule, so movement in AI answers can be seen rather than guessed at.
Weekly demo, quarterly re-plan
Each week you see what shipped and what moved. Each quarter the plan is rewritten around what the data now says, not around the audit we wrote in month one.
Who it's for
Search work is continuous and slow to show, which is why it is so often the thing nobody owns. These are the states we are usually called into.
Capable generalists shipping content every week, and no one senior answering for whether it can be found, or for what the next site rebuild would do to it.
Impressions hold, clicks fall, and buyers arrive already briefed by an assistant. Somebody has to establish what those assistants say about you and which sources they read.
A redesign, a replatform or a domain change is scheduled. The time to involve a search specialist is before the URLs are decided, not after the traffic drops.
Associations, government bodies and franchise networks where approvals take weeks. The work needs someone who stays across it for months, not a one-off audit and a farewell.
12+
Years of studio experience since 2014
1–2
Typical commitment — 1–2 days a week
EN/FR
Languages this engagement can be delivered in
Other fractional roles
Landing pages, product pages, ads, emails and long-form articles, written by one senior person who learns how your organisation actually talks.
Explore02A senior marketer from our Vancouver studio, working a defined part of each week inside your team.
Explore03One senior specialist owns your GA4 and server-side tracking, the event design underneath it, and the experiment programme that tests pages, forms and funnels.
ExploreFAQ
With a standing set of questions your buyers actually ask, run across the assistants they use and logged on a schedule so movement is visible over time. We record whether your organisation is named, what is quoted, which sources the answer cites and which competitors appear. It is sampling rather than rank tracking: answers vary between runs, and we report that variation instead of hiding it.
No, and we would be wary of anyone who does. Results and generated answers move for reasons nobody outside the platforms controls, and the same prompt can return different answers on different days. What we commit to is the work and the record of it: fixes shipped, pages consolidated, schema validated, the prompt set logged, and an honest read of what moved and what did not.
Whichever suits your setup, agreed before we start. Usually the specialist writes and prioritises the tickets and your developers ship them, because they know the codebase. Where you have no engineering capacity, the studio can implement on your repository and your release process. What we will not do is file recommendations nobody has committed time to build. That is how audits end up unread.
The specialist is in that project from the URL decisions onward, rather than being called afterwards. Redirects are mapped page by page, content and internal links are preserved, schema is retested on staging and crawler access is checked before launch. Expect some movement anyway: a migration is where organic visibility is most often lost, so we plan for a dip instead of promising there will not be one.
The specialist writes the briefs, which is the query a page answers, the questions to cover and the internal links in and out, then edits what comes back. If you have no writer, a content writer from the studio can be quoted alongside the engagement. We would rather brief your subject-matter experts than replace them, because their knowledge is what makes a page worth citing.
When search is your primary channel and the queue of work never empties, hire. When you want one audit with an end date, buy that as a project. When nobody internally can approve changes or free any engineering time, the arrangement stalls whatever we recommend. And on a brand-new site with no content and no history, build the thing first: there is nothing yet to optimise.
Let’s connect
Tell us what is not getting done and roughly how much of a week it needs. We’ll reply within one business day with who would cover it and a tailored quote — no obligation.