On this page
What is measured first
Before any change is made, four things are recorded with dates. First, ownership of measurement: Google Search Console verified for the site, analytics connected, and the actions that count as a lead or a sale defined as conversion events. Second, an observed visibility baseline: exact Google result snapshots for the priority queries, taken from a stated location and device, together with the site's current Search Console impressions, clicks and positions by query and page. Third, a first-party crawl of the site: which URLs exist, how they link to each other, which are indexable, and which are unreachable. Fourth, the external picture: independent referring domains at page level, and lab performance runs for representative templates.
The reason measurement comes first is not ceremony. A programme without a dated baseline cannot show what it changed, and a site without Search Console cannot tell whether its pages are indexed at all. Google's own performance report is the only source that reports what Google showed for the site; a third-party rank tracker is a useful sample, not a substitute.
Which workstreams depend on others
Five workstreams make up a programme, and the order between them is forced by how search engines work rather than by preference. A page must be discoverable and indexable before its content can be judged; research has to decide which page owns which task before pages are written, or new pages compete with old ones; authority work needs pages worth referencing before outreach has anything to offer. The table sets out the dependencies and what each stream waits for.
| Workstream | What it produces | Waits for | Why it waits |
|---|---|---|---|
| Measurement and baseline | Verified Search Console and analytics, conversion events, dated observations | Nothing | Everything after it is compared with this |
| Technical eligibility | Pages that can be crawled, rendered and indexed; consistent canonicals, redirects and sitemaps | Baseline crawl and indexing reports | Content on pages Google cannot store is wasted effort |
| Research and architecture | Which tasks matter, which page owns each, how pages relate | Demand evidence, result snapshots, the crawl | Writing before deciding ownership creates pages that compete with each other |
| Content and internal links | Pages that answer one task each, linked to the tasks before and after them | Architecture decisions, technical eligibility | A good page on the wrong URL, or one that cannot be reached, does not perform |
| Authority and mentions | Independent, relevant references to pages worth referencing | At least one page worth citing per topic | Outreach with nothing to point at produces nothing durable |
Dependencies are not the same as strict phases. Once measurement and the first technical fixes are in place, research, content and authority work overlap; what the dependency table forbids is starting a stream before the one it needs has produced something. That is also why an established site with clean technical foundations spends its first weeks differently from a new site with none, as the alternative paths below show.
The six months, month by month
The programme we run is structured as six dated months, each with an operating focus and a set of outcomes that are only reported once verified. The focus of a month is what the team is working on; the verified outcomes are what can be shown to have happened by the time the month is reported.
| Month | Operating focus | Typical verified outcomes |
|---|---|---|
| 1 | Establish and repair | Access and measurement ownership, Search Console and analytics where available, crawl and indexation baseline, remediation of redirects, canonicals, sitemaps, schema and performance, core business profiles |
| 2 | Entity, citation and page foundations | Citation clean-up and expansion, additional controlled profiles, query-to-page accountability, initial content and internal-link planning, first press-release distribution |
| 3 | Topical network and first-tier reinforcement | Priority pages and supporting content live with contextual internal links; profiles, citations and releases verified; measured supporting links to selected first-tier placements |
| 4 | Assets and editorial authority | Demand-validated tools, studies or other linkable assets; publisher-specific pitching; editorial, partnership and digital-PR acquisition |
| 5 | Scale what responds | Continued outreach and negotiation, the next evidence-backed assets and pages, reinforcement of valuable placements, adaptation from Search Console and ranking response |
| 6 | Consolidate and decide | Successful work continued, overlap and link losses resolved, comparison with the baseline, documented learning, and the next 180-day plan |
How rankings, leads and revenue are interpreted
Three different quantities get called "results", and a programme is only honest if it keeps them apart. Demand estimates, such as Keyword Planner's average monthly searches, describe how often a query might be searched in a location and language; they are rounded estimates and say nothing about visits. Rankings are observed, not estimated, but only for the location, device and moment of the observation; Search Console's average position is an average across every impression in a date range, not the rank any one person saw. Business outcomes come from conversion events and, ultimately, from your own sales records.
| Lane | What is recorded | Source | What it does not tell you |
|---|---|---|---|
| Delivered work | Tasks completed, dated, with the evidence that proved completion | The programme record | Whether search engines have responded yet |
| Verified external outcomes | Listings, releases and links that are live, with follow state and survival | Direct observation of each placement | Whether they changed rankings |
| Observed performance | Impressions, clicks and position by query and page; exact result snapshots | Search Console; dated snapshots | Why the numbers moved |
| Business outcomes | Enquiries, bookings, sales attributed to organic sessions | Analytics conversion events; your records | Precise attribution when several channels are active |
| Limits | What could not be measured this month and why | Stated in the report | Nothing, which is the point |
Alternative paths for different starting points
The dependency chain is fixed; where a site starts on it is not. The audit places a site on the chain, and the first two months are planned from that position rather than from a template.
| Starting point | What the audit typically finds | Where months one and two go |
|---|---|---|
| Technically blocked site | Pages not indexed, redirect chains, duplicate URLs, slow templates | Eligibility repairs and re-verification before any new content is written |
| New site with no authority | Clean but small, few referring domains, no measurement history | Measurement, a small set of accountable pages, and early assets worth referencing |
| Established site with content gaps | Good authority, pages that compete with each other, missing tasks | Query-to-page ownership, consolidation, and the highest-value missing pages |
| Location-led business | Visibility depends on Business Profile and local facts more than on articles | Eligibility check, profile and citation foundations, grid-based local measurement |
What cannot be promised in six months
- A ranking, traffic, lead or revenue figure. Search results are decided by the search engine; a programme controls inputs and measures outputs.
- A fixed date for response. Recrawling and reprocessing take time that differs by site, and competitors act in the same period.
- Results without access. Work that depends on accounts, deployment or approvals that were not granted is reported as blocked, not quietly skipped.
- A single score. Authority, technical health, content, architecture and observed performance are separate measurements; blending them hides which one moved.
- Links bought in bulk. Paid or exchanged links intended to manipulate ranking are a violation of Google's spam policies, and a programme that relies on them is borrowing against the site's future.
What to do next
- Verify Search Console for your site and define one conversion event that represents real business value. Without these, no programme can be evaluated.
- Ask any provider, including us, to show the dependency order in their plan and where your site starts on it. A plan that begins with content on an unaudited site has skipped a step.
- Ask what their monthly report separates: delivered work, verified outcomes, observed performance and stated limits should be different sections.
- Read the complete SEO audit guide to see what the baseline has to cover before the first month starts.
Where to go next
- SEO programmes for Malaysian businesses →
The engagement this sequencing is built into, including what we need from you and what stays yours.
- Complete SEO audit guide →
The month-one baseline in detail: what a comprehensive audit has to cover and how coverage is stated.
- Search Console for SEO measurement →
How to read the monthly performance observations without overclaiming.
- How search visibility works →
The crawling, indexing and ranking chain that the sequence below follows.
Rather have this handled?
This is part of how we run seo programmes for Malaysian businesses. Ask us about your site — no pitch, a straight answer.
Sources and further reading
- Google Search Central — In-depth guide to how Google Search works — read 15 September 2026
- Google Search Central — Search Engine Optimization (SEO) Starter Guide — read 15 September 2026
- Google Search Central — Spam policies for Google web search — read 15 September 2026
- Search Console Help — Performance report (Search results) — read 15 September 2026
- Google Ads Help — About Keyword Planner forecasts and historical metrics — read 15 September 2026