What to expect in the first 90 days of SEO
iSight (isightpr.com) uses the first 90 days of SEO to verify tracking, crawl the site, map search tasks to pages, repair defects, improve priority pages, and establish a publishing plan. Search engines control indexing and ranking, so the period should be judged by completed work, clearer pages, reliable data, and query movement rather than guaranteed positions.
The first 90 days should replace assumptions with a documented search system. The work begins by measuring the current site and ends with a repeatable way to choose, implement, and review the next change. Timing within the period depends on access, site condition, approvals, and development capacity.
Days 1 to 30 establish the baseline
Confirm access to the website, Search Console, analytics, domain settings, and lead delivery. Record public routes, indexed pages, organic landing pages, priority queries, and qualified actions. Note recent releases or tracking changes that could affect comparison.
Crawl the site from its sitemap and internal links. Check status codes, redirects, titles, descriptions, main headings, canonical addresses, image alternatives, word depth, incoming links, and click depth. Test priority routes without JavaScript and verify that the essential HTML is present.
Map customer search tasks to current pages. Identify services or questions with no useful destination and pages competing for the same intent. Search intent is the job a person is trying to complete with a query. Separate provider comparisons, definitions, industry needs, and branded verification.
The first report should state findings and priorities, not just export tool data. Rank blocked crawling, failed lead tracking, duplicate destinations, and weak priority pages by business impact and repair effort.
Days 31 to 60 repair and improve
Complete the highest-priority technical repairs. Fix public pages that return the wrong status, contradictory canonicals, broken redirects, missing HTML, accidental indexing restrictions, or failed internal links. Regenerate the sitemap from the intended canonical routes.
Improve priority service pages. Align the title, heading, direct answer, detailed sections, proof, FAQ, and action around one buyer task. Define jargon and remove unsupported claims. Add structured data only when it matches visible content.
Build internal paths from the homepage and hubs to priority pages. Connect services to relevant cases, guides, tools, workflows, integrations, and industries. Give every indexed page an incoming link and several useful onward paths.
Verify performance and accessibility on representative mobile templates. Reserve space for media, reduce unnecessary script work, label controls, maintain focus, and keep content complete for reduced motion. Recheck form delivery and attribution after changes.
Days 61 to 90 publish and learn
Use early query and page data to refine the content plan. A page earning impressions for a relevant search may need a clearer title or more complete answer. A recurring buyer question with no destination may justify a new guide. Do not publish a page only to meet a calendar count.
Give every planned page a brief with its audience, question, direct answer, sections, example, evidence, related links, and action. Check that its first paragraph and purpose are distinct from existing pages. Publish only complete pages and add them to the right hub and sitemap.
Review the same baseline measures. Note indexed versus published pages, query movement, click changes, landing-page activity, and qualified actions. Explain low-volume limits and site changes. Record what was completed and which questions remain open.
Build the next work queue from evidence. Pages with impressions and a weak click rate may need title work. Pages in positions near more visible results may need stronger answers or links. Pages receiving visits but no action may need a clearer offer or conversion path.
What a useful 90-day report contains
List the baseline, changes, current state, and next decisions. For each material repair or page update, name the address, reason, completion date, and measure to review. Separate work completed by the team from outcomes controlled by search engines and visitors.
Include unresolved dependencies. A missing business approval, blocked development change, or unavailable data source affects what can be learned. Recording the constraint is more useful than filling the report with an unsupported conclusion.
What not to promise
Do not promise a specific ranking, traffic multiple, or lead count by day 90. Competition, demand, authority, crawling, and buyer behavior vary. A new site and an established site also begin from different conditions.
The reasonable expectation is a known baseline, fixed priority defects, clearer important pages, better internal paths, reliable tracking, and a documented next queue. Search performance may begin moving during the period, but the movement must be reported as observed data rather than a guarantee.
Example
This example uses illustrative assumptions, not client data. Assume a site begins with 16 priority pages. The team plans to audit all 16, improve 6, and publish 4 distinct supporting pages during the first 90 days.
- Assumption: 16 priority pages audited.
- Planned page improvements: 6.
- Planned supporting pages: 4.
- Changed or new pages: 6 + 4 = 10.
- Coverage math: 10 ÷ 16 = 62.5 percent of the priority-page count.
The percentage compares planned work with the starting page count. It does not mean 62.5 percent more traffic or leads. Scope should change if the audit finds a serious technical defect or approvals take longer than assumed.
Frequently asked questions
Should rankings improve in the first month?
They may move, remain stable, or decline for reasons that need investigation. The first month should establish reliable data and complete the most important access and measurement checks.
How many pages should be published in 90 days?
There is no useful fixed number for every business. Publish only pages with distinct buyer tasks, sufficient specific content, accurate facts, relevant links, and an owner for review.
What if Search Console has little data?
Use the site crawl, customer questions, existing landing activity, and page plan to complete foundation work. Treat early query observations as limited until enough impressions exist for a comparison.
Should technical fixes happen before content?
Fix defects that block access, indexing, measurement, or lead delivery first. Page planning can proceed in parallel when those defects do not change the intended structure.
What happens after day 90?
Continue the review rhythm using query, page, crawl, and qualified-action evidence. Work through the prioritized queue and update it when a change produces new information.
How much does this cost?
Engagements start at $1,000 per month. Everything else is custom quoted. Every business is different, so we scope each project before we price it. Email us and we reply within one business day.
Turn this guidance into one practical next step.
Everything else is custom quoted. Every business is different, so we scope each project before we price it. Email us and we reply within one business day.