Baseline before tactics
Search demand, current rankings, indexed URLs, conversion data, competitors and AI visibility are recorded before recommendations begin. Without a baseline, movement becomes opinion.
METHOD + OWNERSHIP + EVIDENCE
A public operating system for turning search research, technical findings, content and authority work into implemented changes that can be measured.
DIRECT ANSWER
My methodology is a repeating three-month system: establish the search and business baseline, ship prioritized technical, content and authority changes, then measure what reached production and how the market responded. Every task has evidence, an owner and an acceptance test. Classic SEO, AEO and GEO share one roadmap where their foundations overlap, while rankings, AI visibility and business outcomes are measured separately. The goal is not a larger audit or more published pages. It is a controlled sequence of decisions that compounds.
The exact workload changes by business model. A local company may need location architecture, reviews and Google Business Profile governance. An ecommerce store may need category demand, facets and product data. A publisher may need taxonomy, templates and editorial quality control. The operating rules stay the same.
01 / OPERATING PRINCIPLES
These rules decide what enters the roadmap, what gets delayed and what counts as completed.
Search demand, current rankings, indexed URLs, conversion data, competitors and AI visibility are recorded before recommendations begin. Without a baseline, movement becomes opinion.
Queries are clustered by intent and mapped to one primary destination. Pillar pages, supporting pages and internal links form a deliberate system instead of a flat publishing calendar.
A repeated title, schema or indexation error is traced to the template, CMS rule or workflow that creates it. Fixing the recurring system has more leverage than editing URLs one by one.
Each recommendation names who can implement it, what should change and how the rendered result will be checked. A report without ownership is not a delivery plan.
Release notes, recrawls, Search Console, analytics and business outcomes are read together. I do not attribute growth to work that never reached production.
Classic SEO, AEO and GEO share the same foundation: accessible HTML, clear entities, useful answers, independent authority and consistent facts. They are measured separately but planned together.
02 / THE 90-DAY CYCLE
Each month has a different job. The sequence prevents a team from publishing around technical constraints or measuring work that never shipped.
The first month establishes what demand exists, which pages should capture it and which technical or trust constraints can block the plan.
The second month turns the backlog into pages, templates, tickets and authority work. The focus is controlled releases, not a content quota.
The third month checks what Google and users actually did after release, then uses that evidence to set the next cycle.
03 / IMPLEMENTATION OWNERSHIP
Research has value only when it changes a page, template, workflow or decision. The handoff therefore includes an owner and a test, not just a priority label.
See SEO consulting formats →Query set, evidence source and affected page group are documented.
Priority, expected outcome, implementation owner and trade-offs are agreed.
The change reaches staging or production against written acceptance criteria.
Rendered HTML, schema, links, tracking and representative URLs are checked.
Search movement is connected to release timing, conversions and commercial context.
04 / FIRST-HAND EVIDENCE
The cases do not promise the same result for another site. They show how architecture, implementation and measurement work at different scales.
Semantic architecture, technical execution and scalable content across 11 cities. GA4 recorded 1,598,017 monthly Organic Search sessions.
Open the evidence →A six-month operating plan connected commercial pages, technical work and authority. The measured period recorded 44.4M impressions.
Open the evidence →SEO and GEO strategy for a YMYL product across four markets. The roadmap was built first; compounding growth appeared after implementation.
Open the evidence →05 / MEASUREMENT
Search performance can move before revenue, and a release can be valuable before rankings react. The report keeps these layers separate so the team knows what is leading, what is lagging and what is blocked.
Non-brand clicks, impressions, rankings, indexed pages, landing-page groups and conversion paths in Google Search Console and analytics.
Repeatable prompt sets, brand mentions, cited domains, AI referral sessions, crawler activity and incorrect AI-generated URLs.
Recommendations shipped, tickets accepted, templates affected, recrawl status and unresolved dependencies.
Qualified leads, revenue or another agreed outcome. Traffic is useful only when it supports the operating goal.
06 / BOUNDARIES
Constraints are part of the method. They prevent easy activity metrics from replacing evidence and protect the team from work that cannot compound.
07 / ENGAGEMENT FORMAT
Best when the constraint is unclear. The output is a prioritized issue and opportunity map with owners and acceptance criteria.
See SEO audits →Best when the team can implement but needs senior decisions, tickets, reviews and release QA without an agency layer.
See consulting →Best when research, content planning, technical coordination, authority work and measurement need one continuous operating rhythm.
Discuss the scope →08 / FAQ
Direct answers about timing, implementation, content, links, AI search, reporting and guarantees.
Three months is long enough to research the market, release meaningful work and observe early search response without pretending that every competitive result arrives in 90 days. Month one establishes the baseline and architecture, month two ships prioritized changes, and month three validates recrawl, indexation, visibility and business signals. The cycle then repeats with better evidence. Large migrations, new domains and authority-heavy markets usually need several cycles, while a focused technical problem may be resolved faster.
The first month maps search demand to URLs, audits technical and rendering constraints, records the performance baseline and identifies the competitors that shape the search results. It also checks commercial trust, analytics, AI-crawler access and current generative visibility where relevant. The result is not a generic PDF. It is a prioritized backlog with affected page groups, implementation owners, acceptance criteria and a clear decision about which pages, templates and authority gaps deserve work first.
A developer is needed when the highest-priority work touches templates, rendering, routing, performance, structured data or CMS behavior. Small content and configuration changes may not require one. I can work with an existing developer, prepare implementation tickets and validate releases. If no one can change the website, the first task is establishing implementation capacity. Continuing to produce recommendations without an owner would create a larger report, not better search performance.
New pages are selected from clustered search demand, user questions, competitor gaps and the commercial role of the page. Each cluster receives one primary destination so multiple pages do not compete for the same intent. Content briefs include the entities, evidence, questions, internal links and conversion path needed to make the page complete. A page is not commissioned merely because a keyword has volume, and a monthly article quota is not treated as a strategy.
Authority work starts after the priority pages and their evidence are clear. Donors are assessed by relevance, real traffic, editorial context and the probability of a genuine click, not only by a third-party authority metric. Outreach, digital PR, guest contributions and community participation are used selectively. After a link is earned, distribution can help the source page receive real attention. The objective is independent corroboration and qualified referral paths, not a monthly count of placements.
They share one technical and factual foundation but use different measurement layers. SEO work makes pages crawlable, relevant and authoritative for traditional search. AEO improves direct answers, structure and retrievability for answer systems. GEO strengthens the evidence, entity consistency and independent sources that generative systems can synthesize or cite. The roadmap avoids duplicating the same task under three labels. One page or release can support all three when the underlying problem is shared.
Reporting connects completed work with recrawl, indexation, non-brand visibility, landing-page performance, conversions and known dependencies. It separates leading indicators from business outcomes and records which recommendations did not ship. When AI search is in scope, the report also tracks prompt visibility, cited sources, referral traffic, crawler activity and incorrect AI-generated URLs. Rankings are included, but they are not presented without page groups, release dates and commercial context.
No. Search engines and generative systems are external platforms whose rankings, sources and outputs cannot be controlled permanently. I guarantee a defined process, documented deliverables, honest evidence, implementation QA and reporting that states what changed. Forecasts can set a decision range, but they are not promises. Anyone guaranteeing a number-one ranking or permanent inclusion in ChatGPT, Gemini, Perplexity or AI Overviews is claiming control they do not have.
START WITH THE CONSTRAINT
Send the website, target market and the result your team needs. I will identify the likely starting constraint, the evidence required and which engagement format fits.
Cookies, briefly. Essential ones run the site; analytics cookies (Google) only switch on if you say yes. Details in the Privacy Policy.