A fifteen-person export company decides to get serious about SEO. The founder posts one line in the group chat, grow organic traffic this year, and three people take on three tasks. The content person starts publishing two blog posts a week, the technical person checks site speed, and the operations person trades links. Three months later there are twenty posts, a speed score that moved a little, a handful of links, and zero organic inquiries. Nobody can explain what went wrong, because nobody translated the original sentence into something checkable.
Execution is rarely the problem. The goal was never translated, the roles were never assigned, and the learning order was scrambled. This article covers the organization and capability side. Search mechanics and troubleshooting already have a section in the pillar guide, and metric definitions, ROI framing, and monitoring belong to the data and tools piece. Here the focus is how to state a goal in business language.
Turn the Goal Into a Sentence You Can Check
A checkable goal has four parts, a baseline, a time window, a definition, and an owner. Miss one and the team ends up arguing about opinions.
| Vague version | Checkable version |
|---|---|
| Grow organic traffic this year | Within six months, non-brand organic clicks rise from 1,200 to 2,000 per month, measured on the same Search Console property with brand queries excluded |
| Do SEO and get inquiries | Within 90 days, qualified inquiries from non-brand organic search rise from zero to five per month, where qualified means a completed form from a matching industry |
| Fix the website | Within Q1, twenty core landing pages reach the good range for LCP and mobile indexability reaches 100 percent |
| Improve brand awareness | Within six months, brand impressions fall from 35 to 25 percent of total impressions, compared on the same property and window |
The numbers in the table are examples. Look up your own baseline and set a window you can reach. A goal without a baseline is a wish, and the team has no way to judge whether it did well.
Set goals at three levels, business, stage, and work. The business goal is the sentence leadership cares about. The stage goal is where the quarter or half year should land. The work goal is what gets delivered this month, such as a keyword table or a technical audit. The three have to line up. If work goals get completed and the stage goal does not move, the work was aimed at the wrong thing.
One more item belongs in the goal, what you are not doing. No link building this quarter, no new language, no ecommerce build. Writing the exclusions down keeps the team from being pulled apart by whatever request arrives on Tuesday.
A 90-Day Route With One Deliverable per Stage
Divide the learning route into stages and attach a checkable deliverable to each. Watching courses without producing anything leaves the team in the same place three months later.
| Stage | What to learn | What to do | Deliverable | Done when |
|---|---|---|---|---|
| Days 0 to 30 | Search intent, keyword basics, how to read Search Console and Analytics | Build the baseline, inventory existing pages and queries | A keyword table of 50 to 100 terms plus a baseline snapshot | Every term has an intent, a priority, and a page that could serve it |
| Days 31 to 60 | Site structure, technical audits, content-to-page fit | Run one technical audit, publish three pilot pieces on one topic | A prioritized issue list and three published pieces | Every issue has an owner, and each pilot has a target page |
| Days 61 to 90 | Link building, digital PR, reporting and review | Build a link target list, run one full monthly review | A link target list, a monthly report, and next quarter's plan | The report answers which track worked and what to add next |
| Beyond day 90 | Process, roles, and training others | Write the method into an SOP and expand to a second topic | A one-page SOP and a new-hire checklist | A new hire can complete one publish cycle from the checklist |
Do not touch link building in the first 30 days, and do not start a redesign either. Establish the baseline first, so later actions have something to compare against. The keyword table is not an export dump. Every term has to answer three questions. Who searches for it, what they want to do next, and which existing page can serve it. On-page structure and title work are covered in the on-page guide, and intent classification is covered in the keyword research piece.
The days 31 to 60 technical audit looks at three things. Whether pages can be crawled, whether they can be indexed, and whether core pages load quickly. Engineering standards and structured data live in the technical SEO piece, and this article will not repeat them. Sort the audit by impact. A hundred-item list handed to engineering without priorities is a list that never gets worked.
Link building starts in days 61 to 90. Types, digital PR, and risks are covered in the backlinks piece. One red line here. Do not buy links, do not mass-produce low-quality pages, and do not use tactics designed to evade review. They may produce a short-term bump and a much harder problem later. Content strategy and production cadence live in the AI-era content strategy piece, while this article only covers who does what.
After day 90, the focus shifts from doing the work yourself to helping others do it. Write the topic selection, production, publishing, and checks into an SOP. When a new hire can complete one cycle from the checklist, the team has built real capability.
Four Tracks, Assigned to Real People
RACI makes the division of labor explicit. R does the work, A makes the final call, C is consulted before the decision, and I is informed afterward. One person can appear in several cells, but each track has exactly one A.
| Work | Content track | Technical track | Links and PR track | Data track |
|---|---|---|---|---|
| Goal definition | C | C | C | R, head of marketing A |
| Keywords and topics | R, SEO C | I | I | C |
| Production and publishing | R, design C | C | I | I |
| Technical audit and fixes | I | R, technical lead A | I | C |
| Link outreach | C | I | R, head of marketing A, legal C | I |
| Data and monthly report | C | C | I | R, head of marketing A |
Small teams cannot copy the table directly, because one person often covers several tracks. Even then, split the process. Build the baseline on the data track before choosing topics on the content track, otherwise topic selection runs on instinct.
Order the work for a multi-role person by evidence first, growth second.
Data and baseline come first. They decide whether later judgments have any basis, and usually take two weeks.
Technical crawlability and indexability come second. They decide whether content has a chance to be seen, and the main issues usually clear within a month.
Content and keywords come third. This is the most visible track and the easiest one to get wrong, which is why it follows the baseline and the technical work.
Links and PR come fourth. They are slow and expensive, and they make sense once the site can convert and there are assets worth linking to.
A time split is an illustration, not a standard. A small team with ten hours a week for SEO might spend three on data and reporting, three on content, two on technical follow-up, and two on learning and documentation. Raise the data share for the first two weeks to get the baseline done. Adjust the ratio to the team, and do not treat it as a template.
Collaboration Rests on Templates, Not Reminders
Cross-role work loses context fastest. A usable content brief has at least seven parts, the target page, the search intent, primary and secondary keywords, the questions to answer, internal link placements, acceptance criteria, and an owner with a due date.
Set three gates before publishing. The technical gate checks indexability, speed, and structured data. The content gate checks whether the brief's questions are answered, whether there is first-hand information, and whether claims are overstated. The data gate checks that UTMs and conversion events are in place so the piece can be tracked on its own.
Passing all three before publishing is cheaper than fixing after. The gates do not need a complex system. A checklist and one accountable person are enough.
Keep knowledge in three places. A one-page SOP for the steps from topic to publish. A template library for briefs, audit sheets, and monthly reports. A decision log that records each judgment and result, so the next similar problem starts from the record instead of from scratch. These three shorten onboarding more than any course.
Four Capability Levels
Describe the learning route in four levels, each with observable behavior.
| Level | What the person can do | Test |
|---|---|---|
| One | Read reports and explain metrics | Can explain what impressions, clicks, CTR, and conversions each show |
| Two | Execute a single workstream | Can complete a piece or a page optimization from a brief |
| Three | Design a track | Can set topics, priorities, and acceptance criteria from the baseline |
| Four | Set goals, lead people, work across teams | Can translate a business goal into a route and get content, technical, and data moving together |
Most people stall between two and three because they have executed but never made a judgment alone. The way through is to own one small project end to end, from baseline to review. Another course helps less than that one full cycle.
Common Misconceptions
Collecting courses instead of producing work. A folder of saved lessons and no keyword table leaves the team where it started.
Starting with links. Without content and a site that can convert, link traffic does not stay and proves little.
Goals that cannot be checked. Improve brand awareness goes into the quarterly plan, and at year end the score comes from a feeling.
One person covering everything without priorities. Data, content, technical, and links all start at once, each gets a little attention, and none ships.
No deliverables. Learning fades because nothing checkable came out of it.
Buying links or mass-producing low-quality pages to move faster. Both are high-risk practices. The short-term numbers look better and the long-term cleanup costs more.
Related Reading
- What is SEO, the pillar guide and the search mechanics section.
- Keyword research and search intent, how to build the keyword table.
- On-page SEO, titles, page structure, and internal links.
- SEO data and tools, metric definitions, monitoring, and ROI framing.