Acting — Phase 04 of the SEOlogie Cycle

← Back to the Cycle of Visibility

A plan can be as good as you like — until it's put into action, it changes nothing. Only action puts a decision into effect.

But acting doesn't mean building just anything, as fast as possible, as impressive as possible. You don't recognize good execution by whether it works today. You recognize it by whether it still works tomorrow.

How much depends on how you build — I once experienced that in a meeting room.

The simplest solution was the safest

A few years ago, a bank brought me into a project. It was about their public web presence — the pages where the bank presents itself to the public: information, services, people to contact. Internet banking lives in a world of its own, strictly sealed off, with its own security systems; this was about the website in front of it. But that website, too, was to be as secure as humanly possible — no risk, no compromises. And the bank wanted someone with experience at the table; they'd heard that I came from the Unix-and-Linux world and had been dealing with website security since the early years of the web.

In the meeting room sat the specialists of two agencies and the bank's IT people. For two hours I listened to everything that could be done: how the database might be secured, how the web server would have to be hardened, what should happen with the PHP files, which protective layers the CMS would need. All of it technically correct. And with every quarter of an hour, the whole construction grew more complicated.

For a long time I said nothing and only thought: good God, this is complicated. If it gets built like this, even I would find a way in — let alone the people who make a living from it. A database, a CMS, dynamic pages, everything live on a public server: that will never be secure. It can't be.

Then one of the bank's IT people turned to me: "Ortwin, you're the oldest one in this room, you have the experience — you tell us: how should we do it?"

And something came back to me that I'd built around the year 2000: a shop that had to run from a DVD — offline, no server, nothing at all. Back then, a generator had produced nothing but finished HTML pages. That was all it took.

So I said: I wouldn't put myself through any of this. The CMS stays inside — protected, unreachable from the outside. With every change, finished HTML pages are generated from it, and only those pages sit on the server. No PHP. No database. None of the things we'd just spent two hours talking about.

Where there is no database, nobody can hack a database. And the HTML pages — they're welcome to take those.

At first there was debate: without a database — surely that can't work. I asked in return: why not? What exactly was the argument against it? There weren't even three hundred pages to generate. And finished HTML pages load faster than any page that first has to be assembled dynamically from a database. The longer we searched, the clearer it became: there was no argument against it — except habit.

It was built exactly that way. We won the contract, and to this day the website does what it's supposed to do, without complaint. By the way: the wiki you're reading right now is built exactly the same way — finished pages from a generator, no CMS on the server, no database.

What made the difference in that meeting room was no secret knowledge. It was a way of building: not ever more protective layers around a complicated system — but a system so simple that the attack surface never arises in the first place. The safest feature is the one that doesn't exist. And it's by exactly this principle that boats are built, too.

Do we keep adding protection to a complicated system — or do we build one so simple that there's hardly anything to attack?

Two ways to build: for show or to endure

There are boats built for the harbour. And there are boats built for the open sea.

The first kind impresses: big displays, complex electronics, luxurious fittings, gleaming surfaces. In the harbour they look fantastic. But when a system fails, things get complicated — and the more is built in, the more can fail.

A bluewater boat is built for something else: for wind, salt, waves and weeks alone at sea, thousands of nautical miles from the nearest shipyard. Whoever builds a boat like that doesn't ask "What else can we fit in?" but "What do we really need?" Every additional system raises the complexity. Every unnecessary part can fail later. So: as little as possible, as robust as necessary. Everything must stay reachable, everything understandable, everything has to keep working under the harshest conditions — not just today, but ten years from now.

That often looks unspectacular. But on a bluewater boat, every detail has a reason.

Are we building for the harbour photo — or for the open sea?

Visibility that survives the storm

SEOlogie puts solutions into practice by exactly this principle. Digital visibility, too, is often built for the harbour: pretty looks, plenty of tools, gleaming features, impressive dashboards for the next pitch. But out there, in the real digital space, other things count — stability, understandability, findability, maintainability and effect.

Because the digital space is no calm harbour. Search engines change their rules. AI systems answer differently. Competitors grow stronger. The questions of the people who fit shift. Employees leave, budgets shrink. The storm is coming — not if, but when.

And that isn't pessimism; it's craft: a bluewater boat isn't built because you're afraid of the storm today, but because you know it will come someday. The visibility of a source must not go under — so it is built to hold even when the digital sea changes.

SEOlogie doesn't build visibility for calm seas. It builds it for the storm.

The craft: what actually gets built

So much for the image. But what does execution concretely build? Two things — and in this order.

First, seal the foundation. Before new content is created, the technical blockers have to go. These are the one-time interventions. The source is made cleanly readable for the gatekeepers: structured data, a clear technical structure, load times brought down, cleared crawl barriers — so that search engines and AI systems can read it without error and classify it as a reliable entity. The core data — name, address, services — are synchronized without contradiction across all places, so that the source appears as one coherent whole. And orphaned, outdated profiles are cleaned up before they do damage. First you seal the foundation of the house — then you set up the furniture. (Here the SEOloge — the practitioner of SEOlogie — works closely with specialized developers.)

Then build the question/answer bridge. Now comes the production of what was decided in planning: the answers to the real questions of the people who fit. Every answer is produced twice — once as cleanly structured text that machines can read and cite, once as a video a human being understands. The same answer along two paths, consistent, builds trust over time — with the human and with the algorithm. Production is bundled and efficient; publishing happens at the places where the people who fit already are.

And even while building, the tool for the next round takes shape. With every measure you don't just define how you'll later recognize whether it works — the measurement itself has to be built in: clean tracking, the right events, a plain watchdog that raises the alarm when reachability breaks or the enquiries dry up. What isn't built in can't be perceived in the next round. And as with the boat: don't install the most impressive gauges, install the few that count in the storm — and make them so simple that they still work when nobody is watching. Execution calibrates the sensors for the next perceiving.

Do we build the foundation first — or do we set the furniture on the bare floor?

Less, but more stable

What shapes bluewater building most is a word that rarely comes up in marketing: doing without. Not as many systems as possible, but as few as possible — ones that keep working for good. Every feature you don't build is one that can't fail.

There's an old law among engineers, half in jest, half dead serious: whatever can go wrong will, sooner or later, go wrong — Murphy's law. The good builder doesn't laugh at it; he plans for it. He builds so that a single failure doesn't paralyse the whole system, so that critical parts exist twice or are easy to replace. Robustness is no accident. It is built.

And there is a reason why simple means robust here: a small, clearly bounded thing can be thought through to the end, down to the last failure case. A large, nested system never can — somewhere in it there's always a gap nobody thought of. That's why the SEOloge builds from small, self-contained building blocks, each of which works on its own. Better ten simple modules, one of which jams now and then — isolated, without dragging down the rest — than one single big one that comes to a complete standstill at the first crack.

Simplicity, then, is not laziness. It is foresight. A lean, understandable system rides out storms that would capsize an overloaded one.

Do we build systems that hold when it matters — or systems that capsize when it matters?

Build it complicated today, and you make tomorrow's perceiving harder

There is a reason the SEOloge builds this way, and it is astonishingly self-interested. After acting comes no rest. What comes is perceiving, again. The cycle never ends.

Which means: whoever builds chaotically, confusingly, needlessly complicated today makes their own next round hard. Not "after me, the deluge" — but "ahead of me, the perceiving". Whoever leaves behind a nested system will have to untangle it again themselves in three months, maintain it, extend it. And that becomes torture.

Every craftsman knows this. Botch the job, and tomorrow somebody curses — either the customer or — if you're lucky — you yourself. A good craftsman doesn't work only for the moment. He also works for whoever will later have to maintain, check and develop the work further. Often that is himself.

And this is exactly where the seemingly dry virtues of execution get their meaning: clean standards, checklists, traceable documentation, repeatable procedures. Not because some norm demands it. But because the next round of the cycle builds on them — and because a system nobody understands anymore can no longer be perceived either.

Are we building something we'll still understand a year from now — or digging ourselves a hole?

Every execution prepares the next perceiving

With this the circle closes — and really closes, not just as a diagram.

Every implemented measure changes reality. A new structure, a new hub, a new video — and already new signals arise: changed user behaviour, new judgements from the gatekeepers, new questions. The hand approaches twelve again. The next perceiving doesn't begin at some point after the execution. It begins inside it.

This is perhaps the greatest difference between SEOlogie and classic methods. Classic methods treat execution as the goal, the endpoint: done, ticked off. SEOlogie knows no endpoint. Visibility is not a project that gets finished — it is a living system.

That is why the SEOloge builds like the builder of a bluewater boat: not for the completion, but for the life that comes after it.

Execution done well has no finish line: it prepares the next perceiving.

What emerges in the end: visibility that holds

Four phases have now been passed through. Perceiving asks: What is happening? Understanding asks: Why? Planning asks: What do we do — and what do we leave undone? And acting asks: How do we build it so that it holds for good?

What emerges in the end is more than a pretty website. It is bluewater visibility: robust, understandable, maintainable, open to further development — a visibility that doesn't go under when the digital sea changes. Not because it's perfect, but because it's built for reality.

And then everything begins again. The deed has changed reality, new signs are there, and someone has to perceive them. The cycle keeps turning — and with it, visibility: alive, round after round.

Visibility is not a state you reach. It is something you build — and keep on building.

→ And with that, back to the beginning: Perceiving

Sources and literature

• Ortwin Oberhauser: Die SEOlogie – Die Kunst des Sich-Finden-Lassens ("SEOlogie — The Art of Being Found"). Book manuscript, in progress.

Cite this entry