Templates

30-60-90 day plan for SEO specialists

On this page
  1. What does an SEO specialist own that a content marketer does not?
  2. What does the 30-60-90 day plan look like?
  3. What should the day-30 technical audit check?
  4. What does Google say about AI features and AI-written content?
  5. Which numbers should a new SEO specialist baseline?
  6. What does "on track" look like at day 30, 60 and 90?
  7. A filled example
  8. How should the hiring manager use this plan in the final interview?
  9. What should the manager ask at the check-ins?
  10. What the manager owes a new SEO specialist
  11. Common mistakes
  12. Adapting the plan
  13. Questions people ask

A 30-60-90 day plan for a new SEO specialist should get verified access to Google Search Console and Bing Webmaster Tools, baseline organic performance and audit crawling, indexing and page experience in the first 30 days; own a ranked backlog of technical and content fixes with engineering and content in days 31-60; and by day 90 ship fixes measured in Search Console against the baseline, plus a release checklist that stops SEO regressions. As of November 2026, Google says pages need nothing extra to appear in AI Overviews or AI Mode beyond being indexed and eligible for a snippet, and it counts that traffic in the Performance report's Web search type, so the same baseline covers classic and AI results.

This page is for the marketing manager, head of growth or product lead hiring an SEO specialist, SEO analyst or technical SEO. The editorial side, a content audit, a style guide and the calendar, is in the 30-60-90 day plan for content marketers; online stores, product feeds and checkout in the 30-60-90 day plan for ecommerce managers; channel budgets in the 30-60-90 day plan for marketing managers.

What does an SEO specialist own that a content marketer does not?

AreaSEO specialistContent marketerWeb developer
Search dataSearch Console and Bing Webmaster Tools: performance, indexing, sitemaps, manual actionsUses the data to choose topicsUses it to check releases
Crawling and indexingRobots.txt, sitemaps, canonicals, redirects, noindex rules, internal linksFollows the rules when publishingImplements them in templates and the server
Page experienceMeasures Core Web Vitals by template and ranks the fixesKeeps images and embeds lightMakes the fixes
Structured dataChooses the markup and validates itKeeps the visible content it describes accurateAdds it to templates
ContentFinds gaps, cannibalization and pages to merge or retirePlans, writes and updates the pagesNone
Releases and migrationsReviews changes that touch URLs, templates or rendering before launchFlags content movesShips the change

What does the 30-60-90 day plan look like?

30-60-90 day plan — [Name], SEO Specialist, [site(s)]
Reports to: [marketing manager / head of growth]    Start date: [date]
Sites and sections: [ ]    CMS / framework: [ ]
Tools: [Search Console, Bing Webmaster Tools, analytics,
        crawler, rank or log tools if any]
Engineering contact: [name]    Release cycle: [weekly / other]

DAYS 1-30 — Access, baseline and audit
Goals:
- Verified access to Search Console (all property versions) and
  Bing Webmaster Tools; analytics and tag manager read access
- Baseline: clicks, impressions, CTR and average position by page
  group for the last [3] months, and organic conversions
- Read the Page indexing, Sitemaps, Core Web Vitals and Manual
  actions reports; check robots.txt and every sitemap
- Crawl the site; compare crawled, sitemap and indexed URLs
- Learn the release process and who approves template changes
Deliverables by day 30:
- Audit ranked by traffic or revenue at stake, agreed with manager
- Baseline report the team will use every month

DAYS 31-60 — Own the backlog
Goals:
- Turn the audit into tickets with engineering: owner, effort,
  expected effect, how it will be measured
- Fix the quick items in the CMS (titles, internal links,
  redirects, noindex mistakes) within the content team's process
- Agree with content which pages to update, merge or retire
- Review every release that touches URLs, templates or rendering
Deliverables by day 60:
- Backlog in engineering's tracker with the top [5] items scheduled
- Content consolidation list agreed with the content lead

DAYS 61-90 — Measure and protect
Goals:
- Measure shipped fixes against the day-30 baseline by page group
- Release checklist for SEO, adopted by engineering
- Monthly report: what changed, why, what is next
Deliverables by day 90:
- At least [2] fixes shipped and measured
- Release checklist in use; no unreviewed URL changes

Check-ins: weekly with [manager]; reviews at day 30, 60 and 90.

Numbers in brackets are examples; size them to the site and the release cycle.

What should the day-30 technical audit check?

The checks below follow Google's own Search documentation as it reads in November 2026. Each one links to the page the specialist should cite when asking engineering for a fix.

CheckWhat Google's documentation saysSource
Indexing"Most sites have at least a few unindexed pages," and not every URL should be indexed; what matters is that important pages are. Reasons such as "Crawled - currently not indexed" and "Duplicate without user-selected canonical" each need a different responsePage indexing report
SitemapsEach sitemap is limited to 50MB uncompressed or 50,000 URLs; lastmod is used only if it is consistently and verifiably accurate; Google ignores priority and changefreqBuild and submit a sitemap
Robots.txtGoogle enforces a 500 KiB limit and ignores content beyond it; a URL disallowed for crawling may still be indexed and shown without a snippetHow Google interprets robots.txt
Core Web VitalsGood thresholds are LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile of page loads; INP became a stable Core Web Vital in 2024web.dev: Web Vitals
Redirects and movesUse server-side permanent redirects such as 301 or 308; keep redirects for as long as possible, generally at least one year; use the Change of Address tool only for moves between domains or subdomainsSite moves with URL changes
Paid and user linksMark advertisements and paid placements with rel="sponsored" and user-generated links with rel="ugc"Qualify outbound links
Spam policiesIncludes scaled content abuse (many pages generated mainly to manipulate rankings and not to help users), the site reputation policy for third-party content published mainly because of the host site's established ranking signals, expired domain abuse and link spamSpam policies for Google web search

For Bing and several other engines, the IndexNow protocol lets a site report new, changed or deleted URLs; IndexNow says a submission "will be shared across all IndexNow-enabled search engines," and lists Amazon, Bing, Naver, Seznam.cz, Yandex and Yep (IndexNow FAQ). Google is not on that list, so Search Console and sitemaps remain the route for Google.

What does Google say about AI features and AI-written content?

Two pages of Google's documentation answer most of the questions a new SEO specialist will get in the first month, as of November 2026:

  • AI Overviews and AI Mode: "There are no additional requirements to appear in AI Overviews or AI Mode." A page must be indexed and eligible to show with a snippet. Preview controls (nosnippet, data-nosnippet, max-snippet) and noindex limit what appears, and the traffic is reported in the Performance report under the Web search type (AI features and your website).
  • Generative AI content: using AI to generate many pages without adding value for users can violate the scaled content abuse policy; Google says it is critical to fact-check AI-generated content, including titles, meta descriptions, structured data and alt text, and suggests giving readers context on how content was made (Using generative AI content).

The practical consequence for the plan: there is no separate "AI SEO" workstream to start in month one. Indexing, snippet eligibility, accurate structured data and pages worth citing serve both.

Which numbers should a new SEO specialist baseline?

Search Console defines its core measures plainly: clicks, impressions, click-through rate (clicks divided by impressions) and average position, "the average position of the topmost result from your site" (Performance report help). Group pages by template or section so changes can be measured where they were made. The measures below are examples.

Measure (examples only)What it shows
Clicks and impressions by page group, brand and non-brandWhere organic demand and traffic actually sit
Click-through rate by page group at similar positionsTitles and snippets worth rewriting
Important pages indexed, out of those submitted in sitemapsWhether the pages that matter can be found
Page templates passing Core Web VitalsPage experience problems that are fixed once per template
Organic conversions or revenue, from analyticsWhether search traffic does anything for the business
Releases reviewed for SEO before launchWhether regressions are being prevented

Allow for lag. Recrawling and reprocessing take time, so a fix shipped in week seven may not show in the numbers until after the day-90 review. Agree that timing with the manager when the fix is scheduled, not after.

What does "on track" look like at day 30, 60 and 90?

CheckpointOn trackWorth a direct conversation
Day 30Baseline by page group; audit ranked by traffic at stake with Google's documentation cited; release process understoodA tool's generic audit pasted in; no baseline; no contact with engineering
Day 60Top items in engineering's tracker and scheduled; content consolidation agreed; releases reviewedA long backlog nobody has scheduled; fixes requested by message with no owner
Day 90Fixes shipped and measured against the baseline; release checklist adoptedProgress reported as rankings for a few keywords; an unreviewed migration broke URLs

A filled example

SEO specialist: Daniel Osei (invented), joining a B2B software company whose site has a marketing section, a blog and a help center, reporting to the head of growth. All details are examples.

Day 30: The Page indexing report showed thousands of help center URLs with tracking parameters reported as duplicates, while a group of product pages sat in "Crawled - currently not indexed." The blog sitemap listed redirected URLs. The robots.txt blocked a script folder the product pages needed to render.

Day 60: Engineering scheduled a canonical fix for parameter URLs, a sitemap rebuild from live URLs only, and the robots.txt change. The content lead agreed to merge several overlapping blog posts, with redirects from the old URLs. He reviewed a navigation redesign before launch and caught internal links that would have been removed.

Day 90: The duplicate URLs began dropping out of the report and more product pages were indexed. Clicks to the merged blog page grew compared with the separate posts it replaced. The release checklist now covers URL changes, robots.txt, canonicals and structured data.

How should the hiring manager use this plan in the final interview?

Give every finalist the same brief: the site, read-only screenshots of the Search Console Performance and Page indexing reports, and the release cycle. Score the plans with the rubric in how to evaluate a 30-60-90 day plan in an interview. A strong SEO plan baselines before it promises, ranks problems by what is at stake, and gets fixes into engineering's process rather than a slide. Questions that test it:

  • "Organic clicks dropped 20 percent last month. What do you check first, and in what order?"
  • "Engineering has capacity for two of your ten fixes this quarter. Which two, and how do you decide?"
  • "Leadership asks how we show up in AI answers. What do you tell them, and what do you measure?"
  • "We are moving the blog to a new subdomain next month. What do you need before launch?"

The interview guide for marketing roles covers analytics and prioritization questions that fit SEO candidates as well.

What should the manager ask at the check-ins?

  • Day 30: Which problem has the most traffic or revenue at stake? What can engineering fix this quarter?
  • Day 60: What is scheduled, and when will we see it in the data? Which releases did you review?
  • Day 90: What changed against the baseline, and what has not had time to show yet? What would break if the checklist were skipped?

What the manager owes a new SEO specialist

  • Verified access to every Search Console property and Bing Webmaster Tools in week one, plus analytics and the CMS.
  • A named engineering contact and a place in the release review for changes that touch URLs or templates.
  • A content owner who can approve merging or retiring pages.
  • Patience with lag: search results respond to fixes over weeks, not days.

Common mistakes

  • Judging the ramp by a few keyword rankings. Page-group trends in Search Console are steadier and closer to revenue.
  • A backlog that never reaches engineering. An audit in a slide deck fixes nothing.
  • Using robots.txt to hide pages. Disallowed URLs can still be indexed without a snippet; use the right control for the goal.
  • Publishing AI-generated pages at scale. Without added value and fact-checking, it risks Google's scaled content abuse policy.
  • Launching migrations without a redirect map. Years of links and signals can be lost in a weekend.

Adapting the plan

  • Ecommerce sites: add faceted navigation, product structured data and out-of-stock handling to the audit; Google's generative AI guidance says AI-generated product titles and descriptions must be labeled as AI-generated in Merchant Center. The ecommerce manager plan covers the funnel the traffic lands in.
  • Site migrations: if a redesign or domain move is planned inside the first 90 days, it becomes the plan: a redirect map, a pre-launch crawl, the Change of Address tool where it applies and daily monitoring after launch.
  • Content-led companies: weight months two and three toward consolidation and updates with the content team, using the content audit from the content marketer plan.
  • Agencies: each client site gets its own baseline and release contact; agree in writing who can change what in each client's CMS.

Questions people ask

What should a new SEO specialist do in the first 30 days?

Get verified access to Google Search Console, Bing Webmaster Tools and the analytics account; baseline clicks, impressions and average position by page group; read the Page indexing, Sitemaps and Core Web Vitals reports; crawl the site and compare the results with the sitemap and robots.txt; and learn how releases reach production. The month ends with an audit that ranks problems by the traffic or revenue at stake, agreed with the manager.

Do pages need special optimization to appear in Google's AI Overviews or AI Mode?

Google says no, as of November 2026: there are no additional requirements to appear in AI Overviews or AI Mode, and a page only needs to be indexed and eligible to be shown in Search with a snippet. Traffic from those features is included in Search Console's Performance report under the Web search type. Preview controls such as nosnippet and max-snippet limit what Google can show.

Which metrics should an SEO specialist's 30-60-90 day plan track?

Search Console clicks, impressions, click-through rate and average position by page group, the share of important pages indexed, Core Web Vitals by page template, and organic conversions from analytics, all measured against a day-30 baseline. Rankings for a handful of head terms swing too much to judge a 90-day ramp; trends across page groups say more.

How is an SEO specialist's plan different from a content marketer's?

A content marketer's plan is built around the editorial calendar, the style guide and what to publish. An SEO specialist's plan is built around whether search engines can crawl, index and understand the site: Search Console data, sitemaps and robots.txt, canonicals and redirects, page experience and structured data, plus a release process that stops changes from breaking them. The two share keyword and topic research.