The redesign that lost half the traffic
A site five years old. Decent content, a few hundred referring domains, traffic flat for two years. The owner decides it is time for a proper rebuild: new theme, new structure, cleaner URLs, better navigation.
Six weeks later the site is faster, better looking, and down sixty percent in organic traffic.
Nothing in the rebuild was wrong on its own. The URLs really were better. The navigation really was clearer. What went wrong is that the rebuild was executed on top of damage nobody had looked at: redirect chains from a migration three years earlier, a hundred pages nobody had pruned, a link profile with a chunk of toxicity in it, and no map of which old URLs carried the equity.
The design work was fine. The order was wrong. And order, in execution, is not a preference. It determines whether the work compounds or cancels itself out.
Three modes, in sequence
Execution has three modes, and they run in this order for a reason.
Repair
Repair is removing damage. Broken redirect chains, orphaned pages, cannibalising content, lost equity from old migrations, indexation of things that should never have been indexed.
This comes first because damage is subtractive. Every piece of it is a tax on everything you do afterwards. Adding good work to a damaged site means paying that tax on the new work too.
It is also the least satisfying phase, which is why it gets skipped. Nothing looks better at the end of it. The site simply stops leaking.
Design
Design is deciding the structure before building in it. Which topics get a pillar. What supports each one. How the internal links will run, and in which direction. Which of the standard page types the site actually needs, and which would be filler.
Design comes second because structure is expensive to change once content exists. A decision made here costs an hour. The same decision made after forty pages exist costs a migration.
Build
Build is producing and publishing inside the structure. It comes last, and it is the only one of the three that most people ever think about.
That is the whole problem: Build is the visible phase. It is what looks like work. Repair and Design are invisible, and skipping them is invisible too, right up until the point where it is not.
Structural Debt
What accumulates when this order is not respected has a name: Structural Debt.
It behaves like financial debt. It is taken on in small amounts, usually to move faster today. It carries interest, paid as work that underperforms for reasons nobody can trace. And it compounds silently, until a routine change like a redesign or a migration triggers a repayment far larger than anything that was borrowed.
Every skipped repair is a loan. Every structural decision made in a hurry is a loan. Every page published without a place in the architecture is a loan. None of them hurt on the day they are taken.
The characteristic symptom of a site carrying heavy Structural Debt is not a drop. It is a flat line: sustained effort, quality content, nothing moving. Because the work is real and the ground underneath it is not.
Where Phase Zero fits
Repair assumes there is something to repair.
A site in Phase Zero has nothing broken because it has nothing at all: no external recognition, no entity presence, nothing that search engines or language models have registered. The sequence does not apply until that is resolved, and the work there is mechanical rather than strategic. Existence first, then Repair, Design and Build.
The common error is the opposite one: treating an established site as if it were in Phase Zero, and starting to build on top of five years of untouched damage.
What this pillar page does not do
It does not give you the protocol. Which repairs come first, how to map equity before a migration, what the audit actually checks, how to decide which page types a given site needs, and how to sequence the build is the operating manual, not the map.
What a map does is stop you working in the wrong order. That alone is worth more than most of the tactics that come after.
The book: The Authority System
This pillar page is the map. The operating manual is the second book in the AMS collection, The Authority System (AMS Execution, Book 02), which is being written now.
It follows the same three modes in the same order, and turns each one into work:
- Repair. Backlink audits, disavow decisions and redirects.
- Design. The architecture, and how internal links run through it.
- Build. The CMS, schema markup and the entity stack.
It closes with the first 30 days: a deployment calendar that puts the three modes in order on a real site.
It builds on the vocabulary of the first book, The Authority Gap. Execution can be read on its own, but the reasoning behind each decision is clearer with Foundations in place. Both are on the books page.
Until the book is out
Supporting articles for Authority Execution are published here as the book is written. The concepts on this page are defined in the glossary.
The Authority Brief will announce the book first, and subscribers get early access to new volumes. Subscribe to The Authority Brief.