Edits without diagnosis
Someone ships a batch of "best practice" changes, then looks for a metric that improved. This is backwards, and it is why the same page gets rewritten every quarter with no compounding gain.
SEO optimization is not a launch task you finish and file away. It is a repeating cycle of four moves: diagnose the page, change one thing, test it over a fixed window, and re-diagnose with what you learned. Teams that treat it as a loop get steadily cheaper results. Teams that treat it as a checklist keep paying for the same discovery twice.
One round typically runs 14 to 28 days. We will scope the first one for free.
Answer Block
SEO optimization is the repeating process of diagnosing why a page underperforms, changing one variable, testing the result over a fixed window, and re-diagnosing with what you learned. Each round narrows the gap between what a searcher wants and what the page delivers, and each finished round makes the next one faster and cheaper to run.
Most stalled sites are not badly optimised. They were optimised once, correctly, against a market that has since moved. Three failure patterns show up again and again.
The query still exists, but what searchers want from it changed: more comparison, more pricing transparency, more proof. The page now answers last year's question well, and ranks accordingly. Only re-diagnosis catches this, because nothing on the page looks broken.
Five pages rewritten in one week, three new internal links, a speed plugin switched on. Traffic moves, and nobody can say which change did it. Without a comparison group and a fixed window, you have activity rather than evidence.
Someone checks rankings on day two, panics, edits again. Now two changes overlap, the window resets, and the page never gets a clean read. Iteration without a stop rule is just churn with extra steps.
If you want the plain definition of the field before the method, our explainer on Whats Is SEO? covers what search optimisation is and is not, in about the time it takes to drink a coffee.
The loop only works if each segment has a fixed output. A segment that ends with an opinion instead of a record is where rounds start to blur together.
Count what the first three results offer that you do not: sections, data, formats, answers.
Record: a numbered gap list, not a score.If this number is above one, the round is already compromised. Track it honestly.
Target: exactly one, with a screenshot.Compare the same query set before and after. Ignore sitewide totals.
Read at 14 and 28 days, never at day 3.Did the specific blocker clear, and did a new one replace it? That is progress.
Output: the next round's diagnosis.Send one URL and the query you care about. We will name the constraint for free.
Discipline here is what separates optimisation from redecorating. Each round picks a lane, and the lane determines what the test can possibly prove.
Rewrite the title, the opening answer, and the section order so the page matches what the query actually asks. This is the round with the fastest payoff, because it changes which queries the page is eligible for. Test window: fourteen days.
Add the artefact that the top results all have and you lack: a comparison table, a real specification, a process diagram, a worked example. You are not adding words, you are adding reasons to trust the page. Test window: twenty-one days.
Internal links, canonical tags, pagination, duplicate variants, heading order. Results here are usually indirect: the page gets crawled more often, and its internal link equity changes. Test window: twenty-eight days.
Cover the adjacent questions the page currently ignores, each as its own section with its own heading. This widens the query set rather than lifting a single position. Test window: twenty-eight to fifty-six days.
Most optimisation programmes fail at the stop condition, not the diagnosis. These four rules end the ambiguity. Use them literally, even when the numbers are unexciting.
A separate rule covers retirement: if a page has had two full rounds and still earns no clicks on a query with real demand, merge it into a stronger page rather than optimising it a third time. Deleting a weak page is a legitimate optimisation result.
The loop is only as good as the read at the end of it. Four habits keep the read honest, and none of them require a paid dashboard.
Pick a similar page you did not touch. If your target page moved and the control did not, the change is plausible. If both moved, the season or an algorithm update did it, and your edit is unproven.
Write the control page's name into the log before you make the edit, not after. Choosing it afterwards is how people talk themselves into credit.
Branded impressions rise when you run ads, send email, or get mentioned. Mixing them into one total hides the only signal that matters: whether strangers found the page for a problem they were trying to solve.
Filter the query report to non-branded terms, then compare that set against your baseline. It is a smaller number and a much more useful one.
Moving from 8.4 to 7.9 is noise. Moving from a 6-to-10 bucket into the 1-to-5 bucket is a real change with a real click difference. Track the bucket and the impressions per bucket, and ignore the decimal.
Decide the review date when you make the edit. Fourteen days for intent and proof, twenty-eight for structure and depth. Then do not open the report in between, because mid-window reading always produces an unnecessary second edit.
Three places account for most of the wasted effort we see when a team inherits an optimisation history and cannot tell what worked.
Someone ships a batch of "best practice" changes, then looks for a metric that improved. This is backwards, and it is why the same page gets rewritten every quarter with no compounding gain.
Testing single pages in isolation is slow but safe. The mistake is not grouping similar pages into a cohort test, so a template-level fix never gets a fair read at all.
The page improves, everyone celebrates, and nobody asks which constraint is now binding. The momentum dies in the gap between the win and the next question.
In practice, the loop is mostly an on-page discipline: intent, structure, proof, and links on pages that already have demand. Our On-Page SEO Services page breaks that work into the same four segments, with the deliverables listed for each one.
Our version is deliberately unglamorous: fewer changes per month, each one attributed. It suits teams who are tired of activity reports and want a decision at the end of every cycle.
Access, crawl, query map, and a control set. We record the starting position in buckets so later movement is unambiguous.
Priority pages diagnosed by constraint, not by traffic. One change per page, logged with a screenshot and an expected effect.
Fourteen to twenty-eight days after the edit we compare target against control, then close or extend the round. You get the reasoning, not just the number.
New constraints, same discipline. Every quarter we retire the pages that will not respond, because stopping work is also a result.
Six things clients ask in the first meeting, answered the way we would answer them on a call.
SEO is the field; optimization is the work inside it. In practice, "SEO optimization" means the repeated edits and measurements applied to specific pages and templates, as opposed to strategy, research, or content production on their own.
Two to four, usually. The first round fixes intent, the second adds proof, the third clears structure. After that a page is mostly in maintenance, and further effort is better spent on a different page or on conversion.
You can, but you will not learn much. If you must, apply the second change after the first window closes, or accept that the result is a package rather than a proven single cause. Say that out loud in the report.
A new page has no baseline, so the first round is intent and coverage rather than optimisation. Expect the first real read at sixty to ninety days. Judging a new page at three weeks is the most common false negative we see.
Better than for a large one. With twenty pages you can give each one a real round and a control, which is impossible at ten thousand pages. Small sites should test deeply, not broadly.
When the marginal round costs more than the traffic it can win. That usually shows up as a page in the top three with stable clicks, or a query set that is too small to matter. Park the page, revisit it in two quarters.
Content is usually the change inside a depth or proof round. Producing it without a diagnosis is how sites end up with a library nobody reads. Write to close a named gap, then test it.