Why everything starts with the technical layer

Without a solid technical foundation, content cannot be crawled, indexed, or cited by a generative AI — the technical layer is the entry condition for any visibility strategy, not a step you handle "later." It governs a three-link chain — crawl, indexing or ingestion, then citation — and if the first link breaks, the other two never get a chance to happen.

The chain: crawl → indexing/ingestion → citation

Before a page can show up in Google results or in a ChatGPT answer, it first has to be found. That's the job of crawling: a bot (Googlebot, Bingbot, or an AI crawler like GPTBot) follows links across the web, reads a page's HTML, and decides whether to keep it for later use.

Next comes indexing on the classic search engine side: the page gets added to a database that lets it surface for relevant queries. On the generative AI side, the equivalent is usually called ingestion: content gets folded into document stores or indexes the model can consult when generating an answer — through real-time web search for Perplexity or browsing-enabled ChatGPT, or through datasets used at different stages depending on the provider.

The last link, citation, depends entirely on the first two. A generative AI cannot cite a page it was never able to read, and it won't read it if a bot could never reach it in the first place. It's a simple point that gets overlooked constantly: teams optimize content with citation in mind while the actual blocker sits one or two steps earlier, at the level of technical access.

What breaks this chain in practice

In most technical audits, the same blockers show up again and again:

• An overly restrictive robots.txt that blocks entire sections of a site, sometimes by mistake or out of excessive caution.
• Client-side JavaScript rendering with no server-side rendering or pre-rendering, which some crawlers fail to execute properly.
• Orphan pages with no internal links pointing to them, invisible to a bot that navigates link by link.
• Server errors (5xx), redirect loops, or slow response times that push bots to reduce how often they come back.
• No up-to-date XML sitemap, leaving search engines without a clear list of pages to explore.
• Duplicate content or a confusing URL structure, which spreads crawl budget thin across pages with no real value.

Each of these looks minor in isolation. Combined, they explain why some sites with genuinely solid content stay invisible.

SEO and GEO share the same foundation

GEO doesn't replace technical SEO — it builds on top of it. AI crawlers operate through mechanisms fairly close to those of classic search engines: they read HTML, generally respect the robots.txt file, and are sensitive to whether a page is actually reachable. It's generally observed that a page invisible to Googlebot also has little chance of being properly read by an AI crawler, since the same technical obstacles — unrendered JavaScript, server errors, robots.txt blocks — tend to affect both kinds of bots in similar ways.

That's why a GEO strategy that ignores the technical layer starts at a structural disadvantage. You can produce the best-structured content in the world — if it isn't reachable, it stays invisible both to someone typing a Google query and to someone asking Claude or Perplexity a question.

A quick test to see where you stand

Before diving into tools, a few immediate checks give you a first diagnosis without installing anything:

• Type site:yourdomain.com into Google: if the number of results is far lower than your site's actual page count, a chunk of your content is likely not indexed.
• Open yourdomain.com/robots.txt in a browser: if a Disallow: / line appears under User-agent: *, your entire site is closed off to bots, including AI crawlers.
• Turn off JavaScript in your browser (or use Search Console's "Inspect URL" tool once it's set up) and reload a key page: if the main content disappears, a bot that doesn't execute JavaScript properly will see the same thing.
• Check whether a sitemap exists at yourdomain.com/sitemap.xml: its absence isn't a dealbreaker on its own, but it deprives search engines of a useful reference point.

These four checks take less than five minutes and are often enough to tell whether a visibility problem comes from an obvious technical block before digging any further.

Where to actually start

Before working on substance — content structure, direct answers, structured data — you need to secure the basics. In order:

1. Check what's already indexed today (a site:yourdomain.com search on Google, or a direct look at Search Console if it's already set up).
2. Install and configure Google Search Console for a reliable view of indexing status.
3. Audit the robots.txt file and XML sitemap to make sure nothing important is being excluded.
4. Check loading speed and Core Web Vitals, which influence crawl budget.
5. Only after that, work on structuring content to make it "GEO-ready."

This lesson sets the general frame. The next ones get concrete: installing Google Search Console, understanding the robots.txt file and controlling AI crawlers, and digging into why AI sometimes ignores your site once the technical basics are in place.