The First 90 Days on a New SEO Program

The quarter that decides everything

Walking into a new SEO program is a trust exercise before it is a technical one. In the first 90 days, the people around you are deciding one thing: is this person going to move the number, or is this another quarter of decks and promises. Get that wrong and you spend the rest of the year fighting for budget and attention. Get it right and doors open, engineering gives you time, and leadership stops asking whether SEO is worth it. I have started programs inside large brands and inside scrappy in house teams, and the pattern that separates the ones that stick is almost never talent. It is sequencing.

The temptation in month one is to do everything at once: rip into the technical debt, rewrite the content, redesign the reporting. That is how you end up busy and invisible. The first 90 days have a job, and the job is to earn the right to the next 90. Here is how I run them.

Days 1 to 30: listen, baseline, and find the truth

The first month is not for shipping. It is for understanding what is actually true, because most of what you were told in the interview is wrong in interesting ways.

• Interview the humans first. Sit with sales, support, product, and whoever owns the money. They know which pages close deals and which queries the sales team hears every week. That context is worth more than any tool export in week one.
• Baseline the metrics before you touch anything. You cannot prove lift you did not measure the start of. Lock down organic sessions, conversions, revenue, and the query mix, and write down the numbers so nobody relitigates them in month six.
• Run the audit that finds the leverage, not the audit that finds everything. A 300 item spreadsheet is a way to look thorough while accomplishing nothing. I anchor this month on the audit that finds the 20 percent that matters, because the whole point is to separate the handful of issues moving revenue from the busywork that just feels productive.

By the end of week four you should be able to say, in one sentence per item, the three things holding the program back and roughly what fixing each is worth. If you cannot, you audited the wrong things.

Days 31 to 60: ship a quick win, on purpose

Month two is where trust gets built or lost. You need a visible win, and it needs to be visible to the people who control your runway, not just to you.

A quick win has three properties. It is small enough to ship inside the month. It is measurable, so the lift is undeniable. And it touches a page that someone senior already cares about, so the win registers where it counts. A title and internal linking fix on a page that already ranks on the second page of results is a classic: cheap, fast, and it moves. Resist the urge to pick the technically interesting problem over the politically useful one. In the first 90 days those are rarely the same page.

This is also the month you meet the constraint that decides your ceiling: engineering time. Nothing ships without developers, and developers are booked. How you handle that first negotiation sets the tone for the year. I treat it as a leadership problem, not a ticket queue problem, and the way I think about it comes straight out of leading technical and creative teams: you win developer time by making the work legible and the payoff obvious, not by escalating.

The 30-60-90 SEO onboarding checklist

Here is the concrete framework I hand to anyone taking over a program. One page, three phases, and a clear job for each.

Phase 1, Days 1 to 30, Learn and baseline:

• Interview five stakeholders across sales, support, product, and finance.
• Lock a metrics baseline: sessions, conversions, revenue, top queries, index coverage.
• Run a focused audit and rank issues by revenue impact, not effort.
• Map the current publishing and dev workflow, including who approves what.
• Write a one page "state of the program" for leadership.

Phase 2, Days 31 to 60, Prove and build trust:

• Ship one measurable quick win on a page leadership cares about.
• Establish the reporting cadence and the single metric you will be judged on.
• Negotiate a standing block of engineering time, however small.
• Document the two or three fixes that are worth real investment.

Phase 3, Days 61 to 90, Commit to a roadmap:

• Publish a four quarter roadmap tied to forecasted outcomes.
• Get explicit sign off on priorities and the resources they require.
• Stand up the operating rhythm: intake, prioritization, review.
• Set the expectation for when compounding results actually arrive.

If you finish 90 days with those boxes checked, you are no longer the new hire being evaluated. You are the person running a program.

Days 61 to 90: turn the win into a roadmap

The mistake I see even experienced operators make is stopping at the quick win. One good month buys you attention, not a mandate. Month three is where you convert that attention into a plan people will fund.

The roadmap has to speak the language of the people approving it, which means it cannot be a list of tactics. It has to connect the work to outcomes over time. This is where forecasting earns its keep. When I present a 90 day roadmap I bring numbers, and I build them the way I describe in forecasting SEO for the C suite: ranges, not false precision, tied to traffic and revenue leadership already tracks. A roadmap without a forecast is a wish list. A roadmap with a defensible forecast is a budget request that gets approved.

The other half of month three is operational. A program that depends on you personally chasing every fix does not survive your first busy week. You need a repeatable rhythm: how work gets requested, how it gets prioritized, how it gets reviewed. On larger organizations this is the difference between a program and a hero, and the structure I build toward is the one I lay out in the enterprise SEO operating model. Even a small team benefits from borrowing its bones: clear intake, honest prioritization, and a review loop that catches drift before it costs a quarter.

What to resist in the first 90 days

A few traps swallow good operators early:

• Do not promise compounding results by month three. SEO pays back slowly. Set the expectation that the first quarter buys credibility and a plan, and the returns land later. Overpromise the timeline and you lose the trust you spent the quarter building.
• Do not fix everything you find. Triage is the job. Half of what the audit surfaces is real and not worth doing this year.
• Do not skip the baseline. The single most expensive mistake is changing things before you recorded where you started. You will spend month six arguing about causation you could have proven.
• Do not go around engineering. The shortcut that ships without them is the shortcut that breaks trust with the one team you cannot succeed without.

The takeaway

The first 90 days of an SEO program are not about how much you ship. They are about proving, with one measurable win and one credible plan, that this program moves the number. Listen and baseline in month one. Ship a deliberate, visible win in month two. Turn it into a forecasted roadmap and an operating rhythm in month three. Do that and the rest of the year is yours to run instead of yours to defend.

Keep reading: How to Budget for SEO, and Defend It.

If you are stepping into a new program, or handing one to someone who is, and you want a second set of eyes on the sequencing before the clock starts, the channel is open by introduction. Bring your baseline and your org chart, and we will build the 90 day plan that earns the room.