From SEO audit to implementation: what we changed across 24 sites

Owned-portfolio implementation case study · October 28–29, 2026. We reviewed a group of websites with a substantial publishing footprint and found a practical problem: some pages described the brand more clearly than the service, while others gave advice without enough material to help a reader finish the task.

We turned the audit into changes across 24 owned sites, delivered through 30 merged pull requests. This case study explains the decisions, the illustrated teaching pattern and the verification process. It documents implementation, not a measured increase in rankings, traffic or bookings.

The brief: make the existing pages more useful

The request was to improve search visibility, remove duplication, replace vague titles and turn tutorials into in-depth instructions with graphics. We started with existing pages and concrete inconsistencies. Publishing more pages with similar advice would have left those problems in place.

Our working diagnosis was that the portfolio needed clearer distinctions between sites, more firsthand evidence and more focused promotion. That diagnosis was based on content inspection. Ahrefs plan access and a subscription requirement on the Search Console connector prevented a reliable search-performance baseline during the audit. We could not conclude which query, backlink or ranking change explained the traffic shortfall.

The useful question became: what can we improve now, verify publicly, and measure honestly later?

How the work moved from finding to release

1. Record the evidence. Attach the URL and observed issue to each proposed change. Keep missing analytics separate from observed content problems.
2. Choose the reader's task. State what a visitor should understand, create or do after using the page.
3. Build the correction. Update the copy, example, graphic and next step together so they agree.
4. Review the release. Keep changes scoped, preserve the source history and deploy through the site's existing publishing path.
5. Check the live page. Verify the content and selected links, downloads, metadata and responsive layouts.
6. Leave the next decision clear. Record what passed, what remains untested and what outcome data is needed.

That sequence matters because a completed edit is easy to confuse with a completed outcome. A title can be corrected today while its effect on relevant search clicks is still unknown.

Decision 1: clarify the promise before adding more content

We replaced slogan-led search titles on Ecom Coach, JobCoach, Date Night, Fun Things To Do and StartupCoach. For example, Ecom Coach moved from “More from every customer journey” to “Shopify Conversion & Retention Coaching | Ecom Coach.” The new title states the subject and service directly.

Local pages named their genuine location. Career and startup pages named the help on offer. We then checked that all five intended titles appeared in public HTML. This establishes what we published; it does not establish which title Google will display or whether clicks improved.

On Waymaker Agency, the priority was the gap between an enquiry and a booked conversation. The Growth Fix page needed to explain that problem and its implementation scope clearly. We aligned the promise and next steps around reviewing one customer journey and implementing one agreed improvement.

A useful implementation example is the Wealth Experiment workshop journey. A workshop request is not a confirmed place. The page and follow-up process need to explain who confirms it and what happens next. That is an observable communication problem; a claim of higher conversion would require real, consistently defined records.

Decision 2: make the tutorial show the mistake and its correction

We used a repeatable teaching structure: starting materials, numbered actions, an expected result, a visible mistake, a correction and a reusable artifact. The structure stayed consistent while the examples changed to fit each audience.

The AI Teachers meeting-notes lesson is a concrete example. Fictional source notes contain a tentative date. An incorrect draft converts that into a definite commitment. The corrected record preserves uncertainty and leaves unsupported ownership unassigned. The reader can inspect the exact prompt, compare the outputs and test an added contradiction.

This teaches a transferable skill: trace a claim back to evidence before using it. The graphic supports that comparison. It does not claim that a fictional example is a real meeting, client result or benchmark.

Different sites needed different finished artifacts

Site	What we improved	What the reader can inspect
AI Teachers	A workplace tutorial with inputs, outputs and corrections.	Practice notes, a PDF and a checking worksheet.
CodeTeachers	A sample character project, parent questions and local context.	Numbered project steps and an example bug; interest-list status remains explicit.
MyWishbook	A seasonal four-gift planning resource.	A blank and completed printable, with a fictional $100 budget.
Wealth Experiment	A workshop learning record distinct from first-offer advice.	Definitions for requests, attendance, artifacts and the next decision.

We also improved Website Traffic's GA4 tutorial with specific verification steps. Publishing those instructions did not configure a visitor's analytics account. Similarly, a measured craft drawing still needed a physical build test, and an AI tool comparison still needed actual recorded outputs before it could support performance claims.

Decision 3: remove repetition without erasing useful distinctions

We compared the purpose of overlapping pages before deciding what to merge. A broad West Palm Beach activity hub and a specific outing plan can both be useful when each answers a different question. We preserved distinct roles, self-referencing canonicals and navigation between them.

Across sites, Wealth Experiment became more clearly about documented experiments and workshop learning, while AI Side Hustle focused on defining and practicing a first paid offer. Shared structure was useful; interchangeable examples were not.

We also corrected concrete inconsistencies, including obsolete event cards, conflicting offer descriptions and unsupported review claims. The goal was to make the visible promise, supporting evidence and next action agree. Where genuine photos, reviews or test results did not exist, we left an evidence gap instead of manufacturing proof.

What passed—and what remains open

Historical checks recorded on October 29, 2026

Evidence	Recorded result	Limit
Implementation history	24 sites; 30 merged pull requests.	A delivery count, not an outcome metric.
Selected public URLs	49 of 49 returned successful responses in the follow-up check.	Does not prove indexing or every interaction.
Replacement titles	All five matched the intended title text.	Does not prove the displayed Google title or CTR.
Responsive snapshots	15 selected snapshots at three widths; 45 viewport checks.	Sampled layout checks, not complete accessibility or device coverage.
Search and conversion outcomes	No validated before-and-after result available for this case study.	Ranking, traffic, booking and revenue lift remain unproven.

The next round needs reliable analytics access, a consistent baseline, genuinely tested examples and relevant distribution. Compare equal reporting periods, document concurrent changes and account for seasonal demand. If a metric improves, investigate the explanation before attributing it to this release.

Apply the process to one customer journey

Start with the page that creates the most uncertainty for a visitor. Bring its URL, the intended next action, the current offer and any permissioned evidence. Define the observable problem, one agreed improvement and the checks that will establish completion.

Useful handoff: the original issue, the published change, the source evidence, the verification result, remaining limitations and the date for reviewing outcomes. A person taking over should be able to repeat the checks without reconstructing the whole project.

This multi-site portfolio project was broader than a single Growth Fix. The Growth Fix reviews one customer journey, implements one agreed improvement with you and provides a written handoff. It is not a promise to deliver a 24-site overhaul or a guaranteed ranking increase.

For the detailed instructions, all five title replacements and an editable checklist, use the companion Website Traffic SEO implementation guide.

About the evidence

This is our own portfolio work, documented from the October 28–29 audit, implementation log and follow-up checks. Examples labeled fictional are teaching materials. The live resources show what was built; they are not independent customer testimonials.

Our content decisions are consistent with Google's people-first content guidance: make the page useful and support its claims. That guidance does not guarantee a particular ranking. Source reviewed October 29, 2026.