Earth

This is the first in a series extracting marketing strategy from old books on conflict and mastery — starting with Musashi’s Book of Five Rings, applied to search and AI visibility.

Musashi opens with Earth for a specific reason. Before you can fight well, you need to understand the ground you’re standing on — your tools, your environment, your own discipline. He spends almost no time on technique in the Earth Book. It’s mostly about posture, preparation, and the refusal to treat mastery as something you can shortcut into. It’s the least exciting section of the book, and I think that’s deliberate. He’s filtering out the readers who want the exciting part before they’ve earned it.

Search has an Earth layer too, and it gets skipped for the same reason Musashi’s readers probably wanted to skip his.

Foundations don’t feel like strategy

Nobody opens a marketing meeting excited to talk about canonical tags, XML sitemaps, or whether a page returns a 200 or a 301. It doesn’t feel like the interesting work. The interesting work feels like the content — the clever angle, the killer headline, the piece that goes on to actually rank or get cited.

But none of that matters if the ground underneath it is unstable. A brilliant piece of writing sitting on a page that a crawler can’t reach, on a site with broken internal linking, wrapped in JavaScript that never renders for anything but a browser, might as well not exist. It doesn’t get indexed. It doesn’t get crawled by whatever process an AI system uses to build its own understanding of the web. It doesn’t get cited, because it was never actually read by the thing doing the citing.

This is the uncomfortable truth about Earth: it’s invisible when done right, and catastrophic when ignored. Nobody praises a site for having clean crawlability. They just don’t notice the content that should have ranked and didn’t.

What Earth actually is, technically

Stripped of metaphor, Earth is the mechanical layer that determines whether a machine — search engine or AI model — can access, parse, and trust what you’ve built. A few things sit inside it:

Crawlability and indexation. Can the thing responsible for discovering your content actually reach it? Robots.txt misconfigurations, orphaned pages with no internal links pointing to them, JavaScript-rendered content that never resolves for a crawler — these are the equivalent of writing something brilliant and locking it in a drawer.

Structured data. Schema markup doesn’t just help traditional search engines categorize a page. It’s increasingly how AI systems build a machine-readable understanding of who you are, what you do, and how your content relates to other entities — your company, your author identity, the organizations you’re affiliated with. Skipping schema is choosing to communicate in a language the machine doesn’t parse as confidently.

Site architecture. How content relates to other content. A flat pile of disconnected pages tells a crawler nothing about hierarchy or authority. A deliberate structure — pillar pages, clustered subtopics, clear internal linking — tells the machine what you consider foundational versus supporting, which shapes what gets treated as authoritative.

Speed and technical health. Page load times, mobile rendering, broken links, redirect chains. None of this is glamorous. All of it compounds. A site riddled with small technical debt is a site that quietly loses trust with every crawl.

Entity clarity. Machines increasingly aren’t just indexing pages, they’re building models of entities — a person, a company, a brand — and connecting them across the web. If your name, your company, your published work, and your professional profiles aren’t consistently and clearly linked, you’re asking the machine to guess at something you could have simply told it.

None of these are strategy in the sense that content or positioning are strategy. They’re prerequisites. They determine whether strategy gets a chance to work at all.

The cost of skipping it

I’ve watched this pattern more than once: a team pours real effort into content — genuinely good, well-researched, well-positioned content — while the technical foundation underneath it is quietly broken. The content doesn’t perform. The instinct, almost every time, is to blame the content. Maybe the angle was wrong. Maybe it needs a rewrite. Maybe the topic wasn’t as good as it seemed.

Often, the actual problem was never the content. It was that the content never had a fair chance to be seen by whatever was supposed to see it. Fixing Earth doesn’t feel like a creative win, so it rarely gets credited when it fixes the underlying problem. But I’d guess a meaningful share of “our content isn’t working” complaints are actually “our foundation was never sound” problems wearing a content-shaped disguise.

Earth doesn’t win. It permits.

This is the part of Musashi’s framing that I think translates most precisely. Earth isn’t where fights are won. Nobody defeats an opponent through superior foundational posture alone. But without it, none of the more sophisticated techniques in the later books — the adaptability of Water, the decisive timing of Fire — have anywhere to operate. A stance built on unstable ground collapses the moment real pressure is applied, regardless of how refined the technique layered on top of it happens to be.

Earth is permission, not victory. It’s the layer that decides whether you’re allowed into the actual contest, not the layer that decides whether you win it.

Why it’s tempting to skip

The honest answer is that Earth is slow, unglamorous, and hard to point to as an achievement. Nobody puts “fixed our schema markup” in a highlight reel. It doesn’t photograph well in a case study. The payoff is diffuse and delayed — you don’t see a spike from fixing your site architecture, you see the absence of an invisible ceiling you didn’t know was there.

Everything about how we’re wired to value visible, immediate wins pushes against spending real time here. Which is exactly why it’s usually the actual bottleneck, sitting quietly underneath problems that get diagnosed as something else entirely.

Where this leaves you

If you’re building anything meant to be found — by a person typing into a search bar or a model synthesizing an answer from what it can access — Earth is where the accounting has to start honestly. Not because it’s interesting, but because it’s load-bearing. Every later layer assumes it’s already solid.

Musashi wrote Earth first, and I don’t think that was a stylistic choice. I think it was a bet that most people would try to skip straight to Fire, and he wanted the book itself to stop them.