Skip to content

Chapter 12: GEO in Practice

Entries #546–#600 · 55 entries · 4 sections · Chinese edition
Why this chapter exists Once you know how models retrieve and cite, the work becomes engineering: self-contained passages, clean facts, schema, and measurable share of answer. This chapter is the playbook.

12.1 The 15 content shapes models quote most

15 entries

12.2 Entities, fact density and trust signals

15 entries

12.3 Off-site consensus: Wikipedia, Reddit, G2, press

15 entries

12.4 Monitoring, prompt mining and attribution

10 entries

Chapter SOP and interview questions

Ten-minute pre-publish check for a page you want quoted

  • Key takeaways block under the H1: three to five bullets carrying the core entity and at least one hard number.
  • Answer capsule under every question heading: the first paragraph is a 40–60 word standalone answer, with no warm-up sentence.
  • Pronouns resolved at the start of each section: the brand or product name written out, not “it”, “this tool”, “they”.
  • At least one native HTML table using real <table>, <thead> and <th> — not a div grid, not an image of a table.
  • Fact density: every 150 words carries something checkable — a percentage, a price, a year, a measured result. Delete the “in today’s fast-paced world” opener entirely.
  • Attribution: two external links to primary sources, and one or two direct quotes from a named internal expert with a title.
  • Honest verdict: if it is a comparison, state who it is best for and who should avoid it. A page with no downside is read as marketing.
  • Semantics and schema: <main> and <article>, author and reviewer fields, dateModified, and an instant-indexing ping after publish.

Interview questions and answer frameworks

Q1: Take a post that ranks fifth in Google but has never been cited by ChatGPT or Perplexity. What exactly do you change?

Framework: Ranking fifth means you are already in the candidate pool, so the problem is extraction, not discovery. Four surgical passes. Structure — add a takeaways block, rewrite vague headings as the questions people ask, and put a 50-word answer directly under each one; consolidate any comparison that is currently scattered in prose into one native table. Chunk integrity — walk the page and replace every ambiguous pronoun at the start of a section with the actual entity, so a 300-word slice still makes sense when it is pulled out of context. Evidence — strip the preamble, add current figures, add your own measured numbers, add a quote from a named expert, link two primary sources. Freshness signals — update the visible date and dateModified, request a recrawl, push the URL to the instant-indexing endpoint. Then say the honest part: recrawl is fast, but whether a model starts citing you is not on your schedule, and repeating the same prompt daily is not a measurement.

Q2: When someone asks an AI for “the top five brands in a category”, it keeps citing third-party sites instead of our own. What do you do?

Framework: Accept the premise — for recommendation queries, a model has a structural reason to discount the brand’s own site, so the battlefield is off-site. Run the prompts, collect the citations, and build a list of the pages that are actually being quoted: the roundups, the review platforms, the community threads. That list is your target list. Then earn your way in, by legitimate means: pitch an update to the roundup with a factual reason you belong, complete and maintain the review profiles so the ratings and recency are competitive, and make sure genuine third-party discussion exists rather than posting it yourself. The test of whether this is working is co-occurrence — your brand appearing next to the category term on pages you do not control. That is what a synthesis step draws on; your own homepage cannot fake it.

Q3: How much of GEO is writing and how much is engineering?

Framework: Roughly half and half, and they are sequential. Engineering decides whether you are eligible: crawlability, index freshness, static HTML for anything that matters, entity clarity in schema, clean URLs for the canonical statement of a fact. Writing decides whether you are useful once read: a definition that stands alone, numbers that are specific, tables that can be lifted, a verdict that commits. Teams that treat GEO as a copywriting exercise produce beautiful pages that never get quoted; teams that treat it as pure technical work produce perfectly crawlable pages with nothing worth quoting.

Q4: What does “entity clarity” mean in practice?

Framework: That every system reading the web gets the same answer to “what is this thing”. Practically: one canonical description used consistently across your site, your profiles and your press mentions; the same name spelled the same way everywhere, including the legal entity; structured data that names the entity and its type; and a knowledge-base entry or industry listing that anchors it. When those disagree, a model has to hedge, and hedge is what an answer does when it says “one of several options” instead of naming you.