SEO, AEO, and GEO are not separate tricks. They are three views of the same problem: can the internet understand, trust, and recommend your business accurately?
At True North, we build search and AI visibility as part of the website operating system. That includes technical SEO, content SEO, structured data, server-rendered content, sitemaps, robots.txt, llms.txt, markdown summaries, internal linking, page speed, off-page trust, backlinks, partner profiles, and measurement. It also includes restraint. If the content is generic, no schema type will make it authoritative.
How does people-first content become machine-readable?
Google's current guidance on creating helpful, reliable, people-first content is still the cleanest editorial test: content should be made for people, demonstrate experience and expertise, and leave the reader satisfied. That does not conflict with AEO or GEO. It is the foundation.
The mistake is writing for a crawler first and then trying to humanize it. That creates the obvious patterns: repeated intros, keyword-loaded headings, fake certainty, generic "ultimate guide" structure, and source lists added for decoration.
Our order is different:
- define the reader decision;
- write the useful answer from our direct experience;
- add examples, limits, and implementation detail;
- structure the page so search and AI systems can extract it cleanly;
- connect it to the rest of the site through internal links and schema.
That is how promotional content can appear naturally. We do not interrupt a technical article to say "hire us." We explain how we solve the problem and link to the relevant services, case studies, or partnerships only where it helps the reader verify the method.
Why does rendering matter for technical SEO?
Critical content must exist in the initial HTML, before any JavaScript runs. If a crawler or an AI system has to execute your page to see the words, you have already lost reliability, because not every bot renders JavaScript, and the ones that do render it later, slower, and less completely. So rendering strategy is the first technical SEO decision, not an afterthought.
Three modes matter, and serious sites use all three deliberately:
- SSG, static generation. The page is built to HTML at deploy time, then served from the edge. Fastest to load, cheapest to cache, and perfectly crawlable. This is the default for marketing pages, blogs, docs, and anything whose content does not change per request.
- SSR, server-side rendering. The server builds the HTML on each request. The right call when content is dynamic or personalized but still has to arrive fully formed for crawlers and LLMs, not assembled in the browser.
- Hybrid and incremental, ISR. Static where possible, server-rendered where needed, with individual pages regenerated on a schedule or on demand. This is how most real sites ship: static speed with dynamic freshness, and no full rebuild to update one page.
We build these on modern, engineering-grade frameworks. Next.js gives full control over SSG, SSR, ISR, route metadata, image optimization, and server functions. Nuxt gives the same rendering model for Vue teams. TanStack Start is excellent React tooling for app-heavy products that need full-document SSR and typed routing. Shopify Hydrogen, built on Remix, is the right layer for headless commerce when Shopify stays the source of truth. What they share is the point: the meaningful content, copy, headings, links, and structured data, is server-visible by default.
This is why stack selection belongs inside SEO strategy. On a modern, server-rendered stack, good content is crawlable, fast, and easy to connect to conversion data. On a slow, plugin-heavy legacy build, the same content fights the rendering the whole way.
Should structured data describe visible truth?
Structured data is not a place to hide sales claims. It should clarify the page's visible content and relationships.
Google's structured data guidelines are clear that structured data should represent content on the page. I treat JSON-LD as a trust surface. If the schema says something the user cannot verify on the page, it weakens the system.
For service and ecommerce sites, we usually inspect:
For our own site, we also care that llms.txt, markdown mirrors, visible copy, and JSON-LD do not contradict each other. AEO/GEO is partly consistency engineering.
How do you write AEO answers with real judgment?
Answer Engine Optimization works when sections answer real questions directly. It fails when every heading becomes a forced question and every paragraph sounds like a snippet farm.
The structure I like:
- direct answer first;
- when the answer changes;
- what we do in practice;
- what the reader should not assume;
- one internal link to the next useful page.
Example: "Should every page be indexable?" The answer is no. Index pages that deserve discovery. Noindex thin, duplicate, private, temporary, internal search, and low-value filter pages. Then connect that rule to the sitemap, canonical tags, CMS workflow, and measurement.
This is not anti-SEO. It is better SEO because it respects the reader's decision.
What does GEO need beyond llms.txt and markdown?
Generative Engine Optimization is about making it easier for AI systems to identify the right source, parse the page, and summarize the business accurately.
The llms.txt convention, described at llmstxt.org, proposes a clean markdown file that helps language models find useful site context. I treat it as a supporting layer, not a magic file.
Our GEO stack usually includes:
The content has to match across those surfaces. If the article says one thing, schema says another, and llms.txt says a third, AI systems are more likely to summarize the brand badly.
Is content SEO about architecture or blog volume?
Content SEO is not publishing more posts. It is creating the minimum set of pages that answer real buyer, operator, and search questions better than the alternatives.
I separate content into four jobs:
This is where our agency context matters. A blog on voice agents should connect to AI automation, development, and contact only when the reader has enough context to act. A technical SEO post should connect to case studies when proof matters, not as a random CTA.
Google's SEO starter guide still emphasizes useful content, clear links, descriptive titles, crawlability, and avoiding practices that make pages worse for users. That is not basic advice. It is the part many sites skip while chasing advanced tactics.
How should internal links move the reader forward?
Internal links should not be sprinkled like seasoning. They should express the site's logic.
For a growth agency, that logic might be:
- a strategy article points to the about page because operating model matters;
- a development article points to web and software development;
- a creative article points to the studio;
- an SEO/AEO article points to partnerships when platform credibility matters;
- case-study mentions point to the case studies index or the exact public case.
The anchor text should describe the destination. "Read more" is weak. "How we choose website tech stacks" tells both the reader and the crawler what the link is doing.
How does off-page SEO prove your entity is real?
Backlinks still matter, but the lazy version of link building is dangerous. Buying irrelevant links, submitting to junk directories, or producing guest posts nobody reads may create short-term noise and long-term risk.
I care about off-page signals that strengthen the entity:
For TNM, our formal partner and certification ecosystem includes Google, Meta, HubSpot, Vercel, DigitalOcean, and Cloudflare. Tools we use, such as Shopify, WP Engine, PostHog, Typeform, Klaviyo, Pinecone, n8n, Make, Claude, and ElevenLabs, are part of the working stack, but I do not call them formal partnerships unless they are verified as such.
That distinction matters. Trust grows when claims are precise.
Technical SEO includes speed, but not only speed
Core Web Vitals, image strategy, script loading, crawl health, redirects, canonicals, metadata, hreflang, schema, and sitemap hygiene all affect visibility. But technical SEO is not only a PageSpeed score.
For a serious audit, I check:
- indexable route inventory;
- canonical and alternate language rules;
- status codes and redirect chains;
- title and meta description uniqueness;
- structured data validity and visible-content match;
- image size, alt text, loading, and format;
- JavaScript required to read primary content;
- duplicate and thin pages;
- internal link depth;
- event and conversion tracking;
- page templates that carry paid or organic demand.
The LaserYou case study is a good example of the full shape: performance, treatment content, structured data, llms.txt, markdown mirrors, tracking, accessibility, and a dated PageSpeed proof point. The point is not that Next.js magically ranks. The point is that the rebuild treated content, semantics, performance, and measurement as one system.
Backlinks and partnerships should support the same story
A good backlink strategy should make the same claim the website makes. If the site says the agency specializes in performance marketing, development, AI automation, and creative, external surfaces should support that reality.
That can include partner listings, trusted directories, client references, founder profiles, speaking pages, case studies, and useful educational content. It should not include irrelevant posts placed only for anchor text.
The anchor profile should look natural because the work is natural: brand name, founder name, service categories, case-study subjects, and useful resources. If every link uses a commercial keyword, it looks manufactured because it is.
Measurement connects visibility to revenue
SEO can create traffic that never helps the business. AEO can produce snippets that never produce trust. GEO can create AI visibility that cannot be measured perfectly. That is why I connect visibility back to business records where possible.
I look at:
- indexed pages and crawl errors;
- query and landing-page movement;
- qualified organic enquiries;
- assisted conversions and revenue;
- lead quality from organic journeys;
- branded search growth after stronger proof;
- backlink quality and referring domains;
- AI system summaries when tested manually;
- whether pages reduce repetitive sales questions.
This connects SEO to performance marketing, web development, AI automation, and creative. Search does not live in a corner. It touches the page, the proof, the offer, the CRM, and the follow-up.
The SEO, AEO, and GEO checklist I trust
Before I call a site ready, I want this operating stack in place:
That is the difference between SEO as a checklist and visibility as an operating system.
If your site is on Next.js, Nuxt, Shopify, or a hybrid modern stack, the principle stays the same: make the truth visible, structured, fast, connected, and externally credible. That is how we build search and AI visibility without turning content into spam.
