The short answer to how to perform SEO is five rows written before any page is touched: the action, the owner, the completion test and the date. Then move through four phases, each with a gate you are not allowed to pass until the evidence exists. The difference between teams that perform SEO and teams that talk about it is not talent. It is a signed sheet.
Bring one URL and one month of Search Console access. That is enough to open the sheet.
Performing SEO means each change is assigned to a person, dated, and tied to a completion test that can fail. A plan lists intentions. An execution sheet records what was deployed, what the page looked like afterwards, and what the data said fourteen days later, so the next decision is based on evidence instead of memory.
Ask five people on the same team what was changed last quarter and you will usually get five answers, none of them dated. The idea was fine. The execution leaked between the person who decided, the person who edited, the person who deployed and the person who reports. By the time anyone checks, nobody can say which change belongs to which result.
A sheet fixes that with unglamorous mechanics. Every row has one owner, one completion test and one date. If a row has no test, it is not a task, it is a wish. If a row has no owner, it will be done by everyone and finished by no one. If a row has no date, it will be revisited forever and shipped never.
This is also the honest answer to the question behind the keyword. Performing SEO is not a burst of optimisation. It is the discipline of closing rows in order and refusing to move on while a gate is unproven.
One cycle, one page set, one sheet. The rows below are the minimum we would accept before anyone claims a page has been optimised. Notice that only two rows involve writing, and three involve proof.
| Phase | Action | Owner | Done when | Time |
|---|---|---|---|---|
| Baseline | Save 90 days of queries, clicks and impressions per URL | Analyst | Every target URL has a saved row with date | 2 h |
| Fix | Rewrite title, opening paragraph and internal links | Editor | All ten pages changed and logged with a date | 6 h |
| Ship | Deploy markup, compress images, remove blocking scripts | Developer | Zero schema errors and LCP under 2.5s | 4 h |
| Verify | Read Search Console on day 14 against the baseline | Analyst | Keep or revert written per page, with numbers | 1 h |
| Report | One page: what moved, what did not, what is next | Lead | A reader can name the metric that changed | 1 h |
The signature is not ceremony. It forces a named person to look at the gate before the next phase starts, which is the moment most projects quietly skip. Teams that sign tend to argue about evidence instead of opinions, and arguments about evidence end faster.
A gate is a condition, not a date. If the condition is not met, the next phase waits. That rule is the entire method, and it is the one most teams break first.
Every target URL must have ninety days of impressions, clicks and average position saved in a sheet, with the date of the pull. Without this, no later claim can be tested.
Pass conditionThe sheet shows a number for last month that you would be willing to defend in a meeting.
The title names the query in the first four words, and the opening paragraph answers it inside ninety words. A second reader must be able to state the answer after reading only paragraph one.
Pass conditionA colleague who has not seen the page can repeat the answer back to you without scrolling.
Structured data validates with zero errors, the page returns a 200, images are compressed, and the mobile first screen loads under 2.5 seconds in field data rather than on a laptop.
Pass conditionRich Results Test clean, and field LCP under 2.5s for mobile.
Day fourteen and day twenty-eight reads are logged, each page marked keep or revert, with the numbers that justified the call. No verbal summaries, no screenshots of a good morning.
Pass conditionEvery page in the set has a written verdict and a next action.
When the sheet is complete and the numbers have not moved, the cause is almost always one of these four. Work down the list before you rewrite anything a second time.
Check the served page source, not the CMS preview. Template caching, a page builder override or a staging deploy can leave the old title in place for weeks while everyone believes the work is done.
Confirm with a fetch of the live URL, then request indexing for that URL in Search Console.
Consolidate or differentiate. If a category page and a blog post both target the same phrase, the engine picks one and flip-flops. Choose the page that sells, merge the useful parts of the other, and link them deliberately.
A definition query lands on a product page and the visitor leaves. Either answer the question on the page before the pitch, or build the page the query actually asks for and link across to the product.
Chat widgets, review badges and tag managers load before your content. Audit what executes before first paint, defer what can wait, and remove what nobody uses. Lab scores will not show the phone on a train.
Execution stalls when a row belongs to a team rather than a person. Three roles cover the sheet on most small sites, and the same person can hold two of them as long as the sheet says so.
Owns the fix row: titles, opening answers, internal links. Needs query language, not keyword tools. Signs when all target pages are changed and dated.
Owns the ship row: templates, markup, images, scripts. Needs an acceptance test written down before the deploy, not after it. Signs when the test passes on the live URL.
Owns the gate. Decides keep or revert, holds the calendar, and refuses to open the next cycle while a gate is unproven. Signs the report, not the edits.
If you are the only person on the sheet, write your own name in every owner column. It feels excessive for a week, then it becomes the reason the work actually ships.
Some teams have the discipline and not the hours. Others have the hours and cannot tell which pages deserve them. Both problems are solved by the same first step: a baseline read that ranks pages by impressions without clicks, so the sheet starts with the ten URLs that can actually move.
We run that baseline as part of Whats Is SEO?, and the delivery cycle afterwards is covered under SEO Audit Services. You keep the sheet either way. A report you cannot act on is just paper with better fonts.
What we will not do is skip a gate to hit a launch date. If the evidence is not there, the honest answer is that the phase is not finished, and we would rather say that on day fourteen than explain it in a quarterly review.
Performing means the work has an owner, a date and a pass or fail check on every row. A plan lists intentions. An execution sheet records who changed which page, when it was deployed, and what the data said fourteen days later.
Baseline takes two to four hours on a small site. The fix phase runs one to two weeks for ten pages. Shipping is usually a single deploy. Verification is an hour on day fourteen and an hour on day twenty-eight.
The person accountable for the outcome, not the person who did the edit. On a small team that is the founder. On a larger one it is the marketing lead, with the editor and the developer signing their own rows.
Three signals together: the change is visible in the served HTML, the page is indexed, and impressions for the target query moved against the saved baseline. Any one of those alone can mislead, especially a ranking screenshot taken on a good day.
No. Without a baseline you cannot separate an improvement from a seasonal swing, and you cannot defend the budget next quarter. Two hours of baseline protects every hour spent afterwards.
Split the sheet. Keep the content rows in house if you can, and hand the deploy and markup rows to a specialist with a written acceptance test. The gate does not change because the work moved.
Ten is a workable cycle for a small team. Fewer than five rarely produces a readable pattern. More than twenty makes each cycle long enough that the data goes stale before the report.
Send one URL. We will return the five rows, the gate you are stuck at, and the evidence missing.
