JAMES MENESES
ENPT

CASE STUDY / TECHNICAL LEADERSHIP

SEO Marketing Brasil: turning repeated fixes into a capability

One employer, three years, two roles. As SEO Analyst I diagnosed and implemented; as Technical Coordinator I turned the recurring work into a team, a workflow, and a set of reusable implementations the agency could keep using.

See the enterprise growth case
  1. Foundation
  2. Components
  3. Variants
  4. Pages
SEO MARKETING BRASILCONCEPTUAL DIAGRAM
CASE ANATOMY
Role
SEO Analyst, then Technical Coordinator (one employer, two roles)
Timeframe
June 2016 to June 2019

Context and scope

SEO Marketing Brasil served a large portfolio of client accounts. The same technical problems kept arriving: slow pages, missing structured data, broken navigation, migrations that lost rankings. Each one was solved by hand, and then solved again at the next client.

I started as an SEO Analyst and moved to Technical Coordinator. The promotion was really a change in the unit of work: from fixing an account to building the thing that fixed accounts.

The problem

  • The same technical fixes were rebuilt for every client instead of being reused.
  • Performance work was reactive, after a client complained about load time.
  • Structured data and technical implementation depended on whoever happened to be free.
  • There was no documented workflow, so knowledge left with people.
  • The team had more demand than senior engineering capacity.
System map
SurfaceComposed modules
Hotels
  • Search
  • Result
  • Hotel detail
  • Booking
Packages
  • Build
  • Price
  • Package detail
  • Checkout
Transfers
  • Route
  • Options
  • Schedule
  • Confirmation
Tours and tickets
  • Catalog
  • Availability
  • Purchase
  • Confirmation
CONCEPTUAL VIEW / PUBLIC SCOPE

Constraints

  • Many client accounts, each on a different stack, with different levels of access.
  • A small internal team, so the answer had to be process and reuse rather than more headcount.
  • Results had to be repeatable, because a one-off win did not help the next account.
  • Client names stay out of the record, so examples are described by category and method.

What I built

  • As SEO Analyst: keyword strategy, technical analysis, content and on-page SEO, migrations, crawl and indexation work, information architecture, and direct implementation for a broad client portfolio.
  • As Technical Coordinator: established the technical SEO capability inside the agency.
  • Hired and coordinated interns and external developers, and selected the stacks they worked in.
  • Defined workflows and documentation so the same fix could be repeated by someone else.
  • Built reusable implementation: structured data (JSON-LD), landing page systems, and responsive refactors.
  • Wrote up the method as reference material the team and clients could reuse.

Decisions and trade-offs

01

Turn repeated fixes into reusable systems instead of heroics

What it cost: More work writing and maintaining the system up front, and a capability that outlasted any single account.

02

Build a team around the work rather than doing it all myself

What it cost: Time spent hiring and reviewing, repaid in throughput the next year.

03

Document as part of delivery, not after it

What it cost: A slower close on each project, and knowledge that did not disappear.

04

Implement, do not only advise

What it cost: A wider skill demand on the role, and recommendations that survived contact with the code.

Outcome

Load time improved by 60 to 80% for many client projects, and by more than 90% on selected AMP pages. The larger result is what stayed behind: a technical SEO team, a documented workflow, and a set of reusable implementations. This is the first place the pattern shows up that runs through everything after it, from hotel.express to ocalendar to Kyros.

60 to 80% load-time improvement across many client projects
Over 90% load-time improvement on selected AMP pages
3 years one employer, two roles, one progression

Stack

  • Technical SEO: crawling and indexation, migrations, information architecture, and performance work.
  • Structured data with JSON-LD, landing page systems, and responsive refactors.
  • AMP on selected client pages.

What I would do next

  • Keep the method in the record as a reference for how a technical capability is built, not just used.
  • Apply the same reuse pattern when a new client portfolio needs technical SEO capacity.
Back to all projects