Your First 30/60/90 Days as a New SEO Specialist

Day three. You have partial GSC access and a CMO who has asked twice when you'll "move the needle." You also have four years of canonical chaos, a redirect backlog older than your career, a CMS that strips schema on publish, and a marketing ops person who tells you on day eight that the last contractor "left things in a weird state."

Here's the part nobody warned you about. Most new in-house SEO hires get fired in month four. The pattern is consistent: someone promises traffic in 60 days, ships changes the dev team didn't approve, a site update overwrites half their work in week ten, and by the next QBR there's nothing defensible to point at.

Organic SEO compounds on a six-to-nine-month lag. Anything you ship today shows up in the data in October. Your job in the first 90 days is not to move the traffic line. Your job is to (a) build a defensible baseline so future you can prove what changed, (b) ship one technical and one content win that prove you can execute inside this org, and (c) earn one recurring engineering sprint slot. That's the whole job.

Why the 30/60/90 Frame Matters Here

Every other framing gets you fired. "Grow organic 30% in Q1" dies when Q1 ends with the line flat. "Fix all the technical issues" loses because there are 14,000. "Launch a content engine" loses because you don't have brief adoption, dev support, or a baseline yet.

The 30/60/90 frame works because every milestone is something you control. Audit completion. One technical fix. One content optimization. A baseline spreadsheet. A recurring meeting with engineering. None depend on Google's crawler mood.

Days 1-30: Audit and Baseline

Month one is access, audit, baseline. Resist every urge to ship a fix in week two.

Get access, but don't expect it on day one. Chase weekly. Realistic order: GSC, GA4, CMS in days 1-3 (without GSC you're blind). Ahrefs or Semrush seat, Screaming Frog license, dev and content Slack channels by day 10. Server log access, staging login, GTM by day 21. GSC BigQuery export, analytics dashboards, and intros with the lead engineer and content lead by day 30.

When access blocks you, document the request and move on. Don't escalate in week one. You haven't earned the capital.

Run a full crawl. Screaming Frog or Sitebulb. Crawl with JS rendering on, then again with rendering off, then compare. The delta is your CSR-vs-SSR problem. Note canonical issues, redirect chains over two hops, orphan pages, noindex pages still in the sitemap, and any URL returning a different status to Googlebot than to Chrome. Re-run monthly.

Pull the GSC last-16-months export. Top 200 queries by clicks, top 200 by impressions, and a separate cut: queries where impressions are decaying month-over-month. The decay list is gold: pages where rankings are slipping and nobody noticed because clicks haven't dropped yet.

Backlink audit, not link disavow. Segment the profile: the 10-20 links driving real referral traffic, the 50-200 from real publications, and the thousands of low-quality links that look toxic but aren't worth the disavow risk. Do not disavow anything in month one. The "obvious spam" is sometimes a 2022 partnership someone fought for.

Competitor gap analysis. Three closest competitors. Top 50 keywords each ranks for that you don't. Filter to intent that matches your product. The gap list is input to your Q3 content plan, not Q1.

Document baseline rankings for 100 priority terms. A spreadsheet with five columns: keyword, current rank, search volume, target URL, last-checked date. Re-pull monthly. This is the single most important artifact you'll create in the first 30 days. When the CMO asks in month seven what changed, this is what answers.

Identify three quick wins. Pages already ranking on page two or three for real-volume terms. Page seven is not a quick win; that's a rewrite, which is a month-three problem. Classic pattern: page sits at position 14 for a 5,000-volume term, the page is decent, the title tag is generic, internal links are sparse. Fix the title, add five internal links from relevant pages, watch it move to 7-9 within six weeks.

By day 30 you should have: a crawl report, the GSC export, backlink segmentation, the competitor gap list, the baseline rankings spreadsheet, three documented quick wins, and a written audit summary. Two pages, not twenty. If your audit doc is 47 pages, nobody read it.

Days 31-60: Ship One of Each

Month two is for shipping. Not shipping a lot. Shipping one of each thing that proves the pattern works.

Ship one technical fix that needs zero dev time. Title tag rewrites on a template-controlled page. Internal links on a top-traffic page. A canonical fix on a category template you can edit in the CMS yourself. Criteria: zero eng tickets, ships within a week, measurable in GSC within 30 days. Pick the highest-impression quick win from month one. Ship it. Document before-and-after.

Ship one content optimization play. Take a top-10-impression-but-page-three article. Read every first-page result for the same query. Note what they cover that yours doesn't. Note what the People Also Ask box reveals about intent. Rewrite to match intent, expand thin sections, add the H2s the SERP rewards. Block four hours, ship, iterate.

Build the content brief the team will actually use. The brief that fails is six pages with sections for "tone of voice" and "secondary keyword density." The one that works is a single page: target query, search intent, word count, three competitors to read, mandatory H2s, internal links, one-sentence angle. Get the content lead to use it on the next brief, not the next ten.

Get a weekly GSC report into a CMO-visible Slack channel. Auto-generated. Five lines. Total clicks last 7 days vs prior 7. Top three movers up. Top three down. One line of commentary. Visibility builds trust. Trust earns the dev sprint slot.

Start the political work. Two 1:1s. One with the lead engineer about JS rendering and how the team handles SSR. Don't ask for anything. Listen. The second is with the content lead about brief adoption. Listen first. You're gathering intelligence on how decisions get made and what the team has been burned by.

By day 60 you should have: one technical win shipped and tracked, one content optimization shipped and tracked, a one-page brief template in use, a weekly GSC report posting to a CMO-visible channel, and notes from the engineering and content 1:1s. You haven't asked for anything yet. You're about to.

Days 61-90: Own a Cluster, Book the Sprint

Month three is when you stop being the new hire and start being the SEO function.

Pick one topic cluster you can own end-to-end. A pillar page plus four to six supporting articles, all targeting a coherent set of queries that match a single buyer journey. Not "all SEO content." One cluster. Small enough to ship in a quarter, material enough that the win is visible. The cluster is your H2 ask. You'll own the brief, publish schedule, internal linking, and 90-day rank check.

Present the 90-day report. One document. Five sections.

What I found. Top three audit findings, in plain language. The CMO is not learning what hreflang is in this meeting.
What I shipped. The technical fix and the content optimization, with before-and-after data from your baseline spreadsheet.
What moved. GSC data on the two shipped items. Honest. If the fix moved it from position 14 to 11, say that. Don't extrapolate to "expected traffic gain."
What's blocked on engineering. Two or three concrete items. For each: what it is, why it matters in plain English, what you're asking for.
The H2 ask. One topic cluster + one recurring dev sprint slot. That's the entire ask. Do not bring 14 things to this meeting.

The recurring dev sprint slot is the win condition. It can be small. Two engineering days every two-week sprint. One half-sprint per month. Size matters less than recurrence. A recurring slot means SEO work goes through the normal product backlog the same way feature work does. A non-recurring slot means you fight every quarter for the same two days, lose three out of four times, and quit in 18 months.

By day 90 you should have: a documented baseline, one shipped technical win, one shipped content win, a brief template in use, a weekly CMO-visible GSC report, an owned topic cluster, and one recurring dev sprint slot booked. The traffic line is probably flat. That's expected. That's the job.

The "Show Traffic in 60 Days" Anti-Goal

You'll get asked this repeatedly, often by leadership who've never managed an SEO function. The wrong answer is to commit to a number, miss it, and get fired in month four. The right answer has three parts.

First: explain the lag without sounding defensive. "Ranking changes from work shipped today show up in the index over 4-12 weeks, then take another 2-6 months to translate into clicks at scale. Work I ship in May reaches stable rankings by August and material click volume by October. That's how the index works."

Second: redirect to leading indicators you can show in 60 days. Impressions for new pages. Position changes on quick wins. Crawl coverage. Indexation rate of priority pages. These move within weeks. Report them weekly.

Third: anchor the right time horizon. "I'm reporting leading indicators weekly starting week eight. Material click-volume lands in months six through nine. The 90-day report documents baseline + shipped wins, not traffic. The next traffic milestone is the H2 review."

Anyone selling faster is selling, not doing SEO.

The Cosmic Redirect Backlog

Every four-year-old site has it. 302s that should be 301s. Chains five hops deep from old product renames. Killed product pages still ranking for branded terms because their redirects point to a 404. /blog/ paths redirecting to the homepage instead of the relevant article. 2022 migrations that left half the URL structure on the legacy host.

Don't fix all of it in month one. Document it: source URL, current behavior, expected behavior, impact, proposed fix. Triage by traffic-weighted impact. Bring the top 20 to your 90-day report.

The backlog is also where you find buried treasure: killed product pages still pulling thousands of monthly impressions, sunsetted blog content that should redirect to current cluster pages. Those are quick wins for month four, once the dev sprint slot is live.

JavaScript Rendering Issues Nobody Told You About

If your product site runs React, Next.js, Vue, or Angular, you have a JS rendering problem. The questions: which pages are server-rendered, which are client-rendered, which use hydration, and what does Googlebot actually see.

Test it. GSC URL Inspection, "Test Live URL," then "View Tested Page." Compare the rendered HTML to Chrome DevTools. Look for missing H1s, internal links, structured data, meta tags, and lazy-loaded content that never appears in the rendered output.

Common patterns: CSR pages where the body is JavaScript-injected and Googlebot sees a near-empty <div id="root">. Hydration mismatches where SSR and CSR produce different HTML and Google indexes the wrong version. Below-fold "Read more" sections that never reach the indexer. Client-side schema, so structured data isn't there for crawl.

These are dev problems, not content problems. They go on the engineering ask list. They're also why your dev sprint slot matters. Without one, JS rendering issues sit forever and your content work compounds into half-indexed pages.

The Political Reality of Getting Engineering Time

Engineering teams have a roadmap. The roadmap is full. Every SEO ask competes with feature work, infra, and bugs the PM is also fighting for. "This will increase traffic" is the weakest possible pitch. It loses to "this unblocks the launch" every time.

The pitches that work:

"This unblocks indexation of our top three commercial pages, which currently aren't reachable to Googlebot." (Specific, scoped, ties to revenue.)
"This fixes a redirect chain costing us link equity on our highest-converting acquisition page." (Names the page, names the cost.)
"One-sprint task that prevents the issue from last release where 1,400 product pages dropped from the index for 11 days." (References pain the team already felt.)

The pitch that loses: "We need to fix Core Web Vitals to improve SEO rankings." Nobody on the engineering side cares about your rankings. They care about not getting paged at 2am, shipping the next feature on time, and not breaking production. Frame every ask in terms of one of those three.

The recurring sprint slot solves this politically. Once it's on the calendar, you're not pitching every quarter; you're filling a slot that already exists. That's why it's the 90-day win condition.

What Not to Do in the First 90 Days

Don't propose a site migration in month one. You don't know the history. The previous migration probably failed for reasons nobody documented.
Don't disavow links until you've talked to whoever built them. "Obvious spam" from 2023 might be a partnership that closed two enterprise deals.
Don't promise a traffic number you can't defend. Once you commit, you own it.
Don't fight the CMS in week two. Document limitations; don't propose replacing it. Re-platforms take 18 months with no upside until they ship.
Don't ship 40 things in month one. One thing, shipped and tracked, beats 40 half-finished.
Don't skip the engineering 1:1. Lead engineer = highest-leverage relationship in this role.

Measuring Success at Day 90

Open your 90-day report. Each item is binary.

Check all 10 and you're ahead of 90% of new in-house SEOs at the same tenure. Traffic? Probably flat. Doesn't matter. Baseline documented, wins shipped, dev slot booked. The traffic curve bends in months six through nine. By then you've earned the trust to ride out the wait.

The SEOs who survive month four set the right expectations on day one and stuck to them. The ones who got fired tried to show traffic in 60 days. You have 90 days to build something defensible. That's enough.

SEO Specialist Playbooks