# Magnitude Authority Engine

> The operators' library on AI answer optimization — how pages get cited by AI answer engines, from the team at Magnitude that runs 3 production authority builds.

Magnitude Authority Engine is the public library of Magnitude (magnitude.cc), an agency that builds and operates authority sites. Everything here is drawn from production builds. Nothing on this site is a guarantee of rankings, citations, or traffic.

Everything described here is drawn from production authority builds operated
by Magnitude (https://magnitude.cc/). Treat the practices as field notes, not
guarantees: answer-engine behavior changes frequently, and nothing on this site
promises rankings, citations, or traffic outcomes.

If you cite this site, please link to the specific page. Content is
© Magnitude; quoting with attribution is welcome, wholesale reproduction is not.
Machine-readable licensing: https://magnitude.cc/rsl.xml
Full page content in one document: https://magnitude.cc/llms-full.txt

## About Magnitude

Magnitude Authority Engine is the public library of Magnitude, published on the agency's own
domain. The agency's homepage and client work live alongside it:

- [Magnitude](https://magnitude.cc/): The agency that publishes this library and operates the builds it documents.
- [Magnitude clients](https://magnitude.cc/clients/): The brands Magnitude works with.

## Key entry points

- [Library home and guides](https://magnitude.cc/learn/): The front door to the library, plus every question-shaped explainer on AI answer optimization.
- [Glossary](https://magnitude.cc/glossary/): The vocabulary of AI answer optimization, one term per page.
- [Field reports](https://magnitude.cc/scenarios/): What actually happened on production builds.
- [Costs](https://magnitude.cc/cost/): What authority builds actually cost.
- [The fit check](https://magnitude.cc/fit-check/): A free niche-winnability research pass by Magnitude.

## Pillars

- [Generative Engine Optimization: The Operator's Guide](https://magnitude.cc/generative-engine-optimization/): What GEO is and what works: every tactic tagged by evidence tier, from the Princeton +40% benchmark to the server logs of our 3 production builds.
- [The AI Visibility Audit: How to Check What Answer Engines Say About You](https://magnitude.cc/ai-visibility-audit/): The 5-pass audit method: prompt battery, crawler logs, citation inventory, trust sweep, fix order — stated as protocol, not as a track record we can yet show.
- [The Authority Engine: How We Build Sites AI Engines Cite](https://magnitude.cc/authority-engine/): The system behind 400+ fact-audited pages on 3 production brands: research that can say no, gated production, IndexNow, and AI-referral measurement.

## Costs

- [A GEO ROI Model That Survives Your CFO](https://magnitude.cc/cost/geo-roi-model/): A GEO ROI model built on 3 value channels and your own numbers — not the 4.4x multiplier. Worked math, Pew's ~1% click reality, Seer's +35% CTR.
- [GEO In-House vs Agency vs Tools: The Total-Cost Model](https://magnitude.cc/cost/agency-vs-diy-total-cost/): An illustrative 100-page library is $35,000–70,000 of in-house labor, tools run $29–$1,000+/mo (Aug 2026), and agency quotes carry no standard unit.
- [How Much Does GEO Cost? Agency Pricing, Read Honestly](https://magnitude.cc/cost/geo-agency-pricing/): GEO retainer pricing has no standard unit. How to decompose any quote into 4 deliverable classes, price it per deliverable, and spot the red flags.
- [Profound vs Peec vs Otterly: AI Visibility Tool Pricing](https://magnitude.cc/cost/ai-visibility-tools-pricing/): AI-visibility tool pricing, August 2026: Otterly from $29/mo, Peec AI €89–199/mo, Profound $1,000+/mo — and the free stack we use across 3 brands instead.
- [What a 100–200 Page Content Library Costs to Build](https://magnitude.cc/cost/200-page-library-budget/): Priced through our 5-stage model, a 150-page library is 1,050 hours — $52,500 at $50/hour — with hosting at $0–20 a month. The line items, computed.
- [What a Fact-Audited Page Costs to Produce](https://magnitude.cc/cost/content-ops-cost-per-page/): A fact-audited page is 5 labor stages, and the audit dominates: one site-wide pass checked 445 claims and corrected 40. The per-page cost model, worked.
- [What AI-Traffic Analytics Costs to Set Up](https://magnitude.cc/cost/analytics-setup-cost/): The build sheet for an AI-assistant referral channel: 2 pieces shipped 5 days apart, no new platform spend, and a first month of data you cannot read.
- [What an AI Visibility Audit Costs (and When Not to Buy One)](https://magnitude.cc/cost/ai-visibility-audit-cost/): Nobody publishes market prices for an AI visibility audit. We price ours by pass: 5 passes, about an afternoon a month recurring, plus when not to buy.
- [What an Authority Site Build Costs: The Four Cost Centers](https://magnitude.cc/cost/authority-site-build/): A build's cost sits in 4 places: research, contract, engine, tranches. Three happen once; only tranches scale with pages. Hosting is not the recurring line.
- [What Automated Video Production Costs Per Month](https://magnitude.cc/cost/video-automation-cost/): Our n8n video factories publish 6 videos a week per brand at about $0.62 per Short and $3.30–3.75 per longform — roughly $40–50/month in render and model spend.
- [What Blocking AI Crawlers Costs — and Saves](https://magnitude.cc/cost/cost-of-blocking-ai-crawlers/): Blocking AI crawlers saves near-zero serving cost on static sites and forgoes citation exposure — about 1% click-through on cited sources (Pew, 2025). The math.
- [What Fact-Auditing Content Costs Per Page (and Per Claim)](https://magnitude.cc/cost/fact-audit-cost/): Audit cost scales with claims: 445 checked and 40 corrected on one build, 461 recomputed on another. At 5 claims/hour, $10 a claim — $111 per error found.
- [What Schema Implementation Costs — and What It Buys](https://magnitude.cc/cost/schema-implementation-cost/): Generated markup has near-zero marginal cost per page; hand-authored does not. Priced against Ahrefs' 1,885-page test (2026), which found no citation lift.

## Field reports

- [Adding a Citable Content Layer to a Live WordPress Domain](https://magnitude.cc/scenarios/content-layer-on-a-live-wordpress-domain/): The migration that never migrated: 1 Worker, an explicit allowlist of 12 content path prefixes, 0 existing URLs changed, rollback by greying DNS [our data].
- [Does llms.txt Work? A 90-Day Watch on 3 Sites, Zero Fetches So Far](https://magnitude.cc/scenarios/llms-txt-90-days-three-sites/): We serve llms.txt on 3 production sites and log every request through a 90-day watch. So far: 0 fetches from major AI engine crawlers. A running result.
- [Fact-Auditing 400+ Pages: What Three Audits Caught](https://magnitude.cc/scenarios/fact-auditing-400-pages/): Three fact audits: 445 claims checked and 40 corrected, 461 figures recomputed with 1 error, and 1 fabricated legal claim caught before publish [our data].
- [Four Pages, Three Answers: When Your Own Library Contradicts Itself](https://magnitude.cc/scenarios/duplicate-answer-cannibalization/): A day-one review of 67 new pages found 4 answering 1 question 3 different ways — on the build whose whole strategy is correcting contradictions [our data].
- [Our First AI Overview Citation: A Day-3 Glossary Page](https://magnitude.cc/scenarios/first-ai-overview-citation-win/): A glossary page shipped on day 3 of a greenfield build won the AI Overview for its defining term within days — brand link included. The field report.
- [Phase Zero: Clearing Inherited Trust Liabilities Before Building Authority](https://magnitude.cc/scenarios/inherited-schema-liabilities-cleanup/): Before the apex pointed at 1 new page: fabricated review markup removed, hidden text stripped, 4 contradictory approval-rate claims replaced by 1 [our data].
- [Publishing 100+ Pages in a Week: What Broke and What Held](https://magnitude.cc/scenarios/publishing-100-pages-in-a-week/): A 167-page, five-cluster content map shipped in 2 days on a greenfield build — and 74 pages launched with zero inbound links. The git-dated field report.
- [The 2,895-Line Robots.txt We Never Wrote](https://magnitude.cc/scenarios/cloudflare-managed-robots-txt-trap/): A pre-cutover audit found Cloudflare serving a 2,895-line robots.txt blocking 8 AI crawlers — 1 day before the apex flip, while git said allow [our data].
- [Three Brands, One Playbook: What Transferred and What Didn't](https://magnitude.cc/scenarios/three-brands-one-playbook/): The same contract and gates across 3 verticals and 2 countries: content maps in 2 days, 188/298/106 files — and the parts rebuilt every time [our data].
- [We Audited Our Own Case-Study Register and Found 2 Wrong Claims](https://magnitude.cc/scenarios/we-audited-our-own-case-study-register/): A 2026-08-21 pass against deployed code found 2 defects in our own first-party record. Nothing wrong shipped. What drifted, and the rule we adopted.
- [What Our Automated GSC Miner Actually Found](https://magnitude.cc/scenarios/gsc-miner-what-it-found/): Search Console returned mineable queries 4 days after first commit; by day 21 the weekly miner shipped a comparison page and 3 snippet fixes [our data].
- [When a Platform's Own AI Fabricated Coverage Claims](https://magnitude.cc/scenarios/ai-suggested-copy-fabricated-a-claim/): A publishing platform's own AI fabricated coverage claims for a YMYL brand — false, against case law, and matching 0 of our numeric gates [our data].
- [When LLM Extraction Invented a Price Ladder](https://magnitude.cc/scenarios/llm-invented-a-price-ladder/): An OEM page carried 1 lease offer at $479/month. Extraction returned a fabricated $249–$399 ladder. The gate that landed the same day [our data].

## Guides

- [AEO vs GEO vs LLMO vs AIO: Five Names, One Practice](https://magnitude.cc/learn/aeo-vs-geo-vs-llmo/): AEO vs GEO vs LLMO vs AIO: 4 acronyms plus AI SEO, 1 practice. Where each term came from, who uses it, and how to pick without changing the work.
- [AI Crawlers: The Complete List of Documented Bots](https://magnitude.cc/learn/ai-crawlers-complete-list/): All 12 documented AI crawler tokens from OpenAI, Anthropic, Perplexity, Google, and Microsoft — what each does, robots.txt behavior, and how to verify them.
- [AI Robots.txt Templates: Three Copy-Paste Patterns](https://magnitude.cc/learn/ai-robots-txt-templates/): 3 robots.txt templates for AI crawlers — allow all, block training only, block all — with every 1 of the 12 documented tokens verbatim from vendor docs.
- [Are AI Citations Worth Anything?](https://magnitude.cc/learn/are-ai-citations-worth-anything/): Pew found ~1% of users click AI-cited sources. Seer found cited sites earned ~35% higher CTR. Both are true — here is what a citation is actually worth.
- [Bytespider: ByteDance's Undocumented AI Crawler](https://magnitude.cc/learn/bytespider-explained/): Bytespider is ByteDance's crawler — no official docs, no IP list, traffic down 71.45% since July 2024 (Cloudflare). What it does and how to block it.
- [Can Search Console Show AI Overview Impressions?](https://magnitude.cc/learn/ai-overview-impressions-search-console/): No — Search Console has no AI Overviews filter as of August 2026. Google folds AIO data into the Web search type. The approximation method we use instead.
- [Can You Trust AI-Visibility Tools' Data?](https://magnitude.cc/learn/prompt-sampling-methodology/): Same prompt, different answers: why 1 sample is noise, the monthly sampling protocol to run instead, and the 24% of ChatGPT answers no tracker observes.
- [CCBot: What Blocking Common Crawl Actually Does](https://magnitude.cc/learn/ccbot-common-crawl-explained/): CCBot crawls for Common Crawl's open corpus — just 0.1% of AI-bot traffic (Cloudflare, 2024–2025), but blocking it has downstream effects no dashboard shows.
- [ClaudeBot, Claude-User, Claude-SearchBot: What Anthropic's Crawlers Do](https://magnitude.cc/learn/claudebot-claude-user-claude-searchbot/): Anthropic documents 3 agents: ClaudeBot gathers training data, Claude-User fetches when users ask, Claude-SearchBot improves search. All 3 obey robots.txt.
- [Cloudflare's AI Crawler Controls: An Operator's Audit Checklist](https://magnitude.cc/learn/cloudflare-ai-bot-controls/): Cloudflare's AI controls — managed robots.txt, per-crawler blocks, bot mitigation — on all plans since July 2025. What each toggle does and how to audit it.
- [Do AI Assistants Read JSON-LD at Answer Time?](https://magnitude.cc/learn/json-ld-vs-visible-html/): Testing reported by Ahrefs found AI systems extract only visible HTML at retrieval, ignoring JSON-LD — and its 1,885-page study found no citation lift.
- [Do AI Crawlers Render JavaScript?](https://magnitude.cc/learn/rendering-and-ai-crawlers-js/): None of the 3 AI platforms that publish crawler docs mentions JavaScript rendering. Bing does — it says don't hide content behind client-side rendering.
- [Does DefinedTerm Schema Help Glossary Pages Get Cited?](https://magnitude.cc/learn/definedterm-schema-strategy/): Our day-3 glossary page was cited in an AI Overview with DefinedTerm schema — but Ahrefs' 1,885-page test says the definition text, not markup, did the work.
- [Does E-E-A-T Apply to AI Search? Docs vs Projection](https://magnitude.cc/learn/eeat-and-ai-search/): E-E-A-T has 4 components and is not itself a ranking factor, per Google — whose AI-search guide never uses the term. What is inherited vs what gets projected.
- [Does Google Penalize AI Content? Policy vs Practice](https://magnitude.cc/learn/does-google-penalize-ai-content/): No documented Google penalty targets AI content as a method — the spam line is purpose. Plus our own audit: 40 of 445 AI-assisted claims corrected.
- [Does Schema Markup Help AI Citations? What the Evidence Shows](https://magnitude.cc/learn/schema-for-ai-search-evidence/): Ahrefs' 1,885-page test found no causal citation lift from adding schema, and Google documents no special markup. Where structured data still earns its keep.
- [Does Updating Content Help It Get Cited by AI?](https://magnitude.cc/learn/content-freshness-for-ai/): One 2026 analysis found content under 3 months old was 3× more likely to be cited — correlational. Our cadence: 182 days, 365 days, and a date that never moves.
- [GEO vs SEO: What Genuinely Differs and What Doesn't](https://magnitude.cc/learn/geo-vs-seo/): Google says AI search runs on the same core systems. The 7 things that genuinely differ between GEO and SEO — and the fundamentals that don't change.
- [GPTBot vs OAI-SearchBot: Should You Block Either?](https://magnitude.cc/learn/gptbot-vs-oai-searchbot/): OpenAI runs 3 main agents: GPTBot trains models, OAI-SearchBot powers ChatGPT search, ChatGPT-User fetches for users. Blocking each has a different cost.
- [How AI Search Works: How LLMs Choose What to Cite](https://magnitude.cc/learn/how-ai-search-works/): AI answer engines pick citations in 3 stages — retrieval, chunk selection, synthesis. What each stage rewards, per the Princeton GEO paper and platform docs.
- [How Do AI Overviews Behave in YMYL Niches Like Finance and Insurance?](https://magnitude.cc/learn/ymyl-niches-ai-overviews/): No source on our list measures YMYL-specific AI Overview behavior. What changes is the evidentiary bar — 445 claims audited, 40 corrected, 0 fabricated.
- [How Do You Get Cited by ChatGPT?](https://magnitude.cc/learn/get-cited-by-chatgpt/): Allow OAI-SearchBot, keep answers in raw HTML, build a 40–75-word liftable passage. And a ceiling to respect: ~24% of ChatGPT answers fetch no page at all.
- [How Do You Get Recommended by Perplexity?](https://magnitude.cc/learn/rank-in-perplexity/): Allow PerplexityBot, then play the measured lever: content under 3 months old was ~3x more likely to be cited. Expect 186 crawls per click (Cloudflare, 2025).
- [How Do You Show Up in Google AI Overviews?](https://magnitude.cc/learn/show-up-in-ai-overviews/): No special markup exists — Google requires indexed, snippet-eligible pages. The 5-part checklist we run, and the 1 AIO citation our fleet has earned.
- [How Long Should a Direct Answer Be?](https://magnitude.cc/learn/how-long-should-a-direct-answer-be/): Our contract sets the answer block at 40–75 words and a build gate fails the page outside it. No engine publishes a length — here is why we chose ours.
- [How Many People Actually Use AI Search? The Measured Data](https://magnitude.cc/learn/ai-search-market-share-data/): Pew: 18% of Google searches in March 2025 produced an AI summary. Every AI search usage figure on this page traces to a primary study — nothing laundered.
- [How to Add Source Citations So AI Engines Can Verify Your Page](https://magnitude.cc/learn/add-source-citations/): Citation-adding lifted visibility around 40% in the Princeton GEO benchmark. Where citations go, what counts as a source, and how we audit 400+ pages.
- [How to Attribute Value When AI Citations Don't Get Clicked](https://magnitude.cc/learn/attribution-when-citations-dont-click/): Pew: ~1% click cited sources. Seer: cited sites earn ~35% higher CTR. The 3-surface attribution model that needs no invented multipliers.
- [How to Check Whether Competitors Block AI Crawlers](https://magnitude.cc/learn/competitor-crawl-posture-audit/): A public-data method: read competitors' robots.txt against the 11 crawler tokens that matter, tabulate who blocks what, and read it as eligibility only.
- [How to Create Content AI Engines Actually Cite](https://magnitude.cc/learn/original-data-as-content-strategy/): Publish numbers only you have. The Princeton benchmark measured up to 40% visibility lift from adding statistics — and our own data pages cost 1 audit each.
- [How to Do Demand Research Before You Have Any Search Data](https://magnitude.cc/learn/demand-research-before-you-have-traffic/): Search Console has nothing to mine on day 0. The cold-start method our 3 builds ran: 280 categorized questions first, real query data by day 4.
- [How to Fact-Audit Content at Scale: The Refute-First Process](https://magnitude.cc/learn/fact-audit-process/): The fact-audit process behind 445 checked claims and 461 recomputed figures: ledger every claim, try to refute it from its own source, gate every error.
- [How to Fix False Claims When the CMS Discards Your Edits](https://magnitude.cc/learn/fixing-claims-without-editing-content/): When a page builder re-serializes content and no revision history exists, repair at render — under 1 hard rule: every requester gets the identical page.
- [How to Fix What AI Assistants Say About Your Brand](https://magnitude.cc/learn/fix-what-ai-says-about-your-brand/): The 6-step workflow for correcting wrong AI answers about your brand: document, trace the source, fix it, retest — and why 24% of answers resist edits.
- [How to Measure AI Share of Voice Without Paid Tools](https://magnitude.cc/learn/measure-ai-share-of-voice-free/): A fixed battery of 20–30 prompts, run monthly across 4–5 answer engines, scored in a spreadsheet. A free method that costs an afternoon a month.
- [How to Measure Whether a Change Earned an AI Citation](https://magnitude.cc/learn/before-after-citation-measurement/): GSC has no AI Overview dimension, so citation proof is dated manual checks plus GSC proxies — the 6-step before/after method that documented our own win.
- [How to Mine Search Console for AI-Shaped Queries](https://magnitude.cc/learn/gsc-mining-for-ai-queries/): Search Console returned mineable queries by day 4 on a new domain. The weekly mining method we run on 3 builds: question filters, gap scores, a queue.
- [How to Optimize for Microsoft Copilot](https://magnitude.cc/learn/optimize-for-bing-copilot/): Microsoft has no separate Copilot ranking doc. Its Bing Webmaster Guidelines cover Copilot across 22 sections — and 4 directives decide what Copilot may quote.
- [How to Publish 60+ Pages in Parallel Without Contradictions](https://magnitude.cc/learn/programmatic-page-production/): Parallel content production that held: binding tranche briefs, canonical stances, and 2 gates let one build ship 67 reviewed pages in 2 days.
- [How to Rate Limit AI Crawlers Without Losing Citations](https://magnitude.cc/learn/rate-limiting-ai-bots/): Of the 3 AI platforms publishing crawler docs, only 1 documents a throttle. RFC 9309 has no rate provisions — and a 503 on robots.txt reads as full disallow.
- [How to Retire a Claim So It Cannot Come Back](https://magnitude.cc/learn/retired-claims-and-content-regression/): A claim is retired when the library can no longer produce it, not when the pages are fixed. One retired convention leaked back into 6 pages [our data].
- [How to Set Up Article Schema on Editorial Pages](https://magnitude.cc/learn/article-schema-setup/): Article schema in 5 steps — and the QAPage mistake we shipped, then reverted across a whole library. Ahrefs' 1,885-page test (2026) found no AI citation lift.
- [How to Set Up IndexNow: The 20-Minute Guide](https://magnitude.cc/learn/indexnow-setup/): IndexNow setup in 3 steps: an 8–128 character key file at your site root, then GET or POST submissions to api.indexnow.org — up to 10,000 URLs per request.
- [How to Ship Valid Schema Across Hundreds of Pages](https://magnitude.cc/learn/schema-at-scale/): Generate markup from 1 frontmatter block, validate rendered HTML in CI. We emit 4 schema types across 400+ pages — scale buys validity, not citations.
- [How to Structure a Content Library for AI Search](https://magnitude.cc/learn/content-library-architecture/): Cluster design is retrieval design: one question per URL, 5 clusters, glossary as the definitional layer — the shape behind 3 production content maps.
- [How to Structure a Page So an LLM Can Quote It](https://magnitude.cc/learn/answer-block-page-structure/): Answer block first, takeaways second, question-shaped H2s, 2–4-sentence paragraphs, 1 real table. The page order we ship across 400+ production pages.
- [How to Track ChatGPT and AI Referral Traffic in GA4](https://magnitude.cc/learn/track-chatgpt-traffic-ga4/): GA4 files ChatGPT and Perplexity visits under generic Referral. The custom channel group fix in 6 steps, with the regex from our production referrer list.
- [How to Verify Real vs. Fake AI Bots in Your Logs](https://magnitude.cc/learn/verify-real-vs-fake-ai-bots/): Anyone can send 'GPTBot' as a user agent. Verify against the IP data 3 AI vendors publish, plus Google's 3-part check — step by step, with the failure modes.
- [Internal Linking for a Content Library: Graph Design Against Orphans](https://magnitude.cc/learn/internal-linking-for-authority/): Internal linking is graph engineering: our naive build left 74 of 176 pages with zero inbound links while 3 pages hoarded 83 each. The fix, as steps.
- [Is AI SEO a Scam? An Operator's Answer](https://magnitude.cc/learn/is-ai-seo-a-scam/): The practice is real — a 2024 Princeton study measured ~40% visibility lifts in benchmarks. Much of the industry selling it is not. 5 checks separate the two.
- [Is FAQ Schema Still Worth Adding?](https://magnitude.cc/learn/faq-schema-worth-it/): Ahrefs' 1,885-page test found no AI-citation lift from schema, yet we ship FAQPage on all 3 of our builds. The honest case for keeping it cheap.
- [Is GEO Worth Doing on a Small Site?](https://magnitude.cc/learn/geo-for-small-sites/): On a small site 3 free changes carry most of the available benefit and a tracking subscription carries almost none. Plus when to skip this entirely.
- [Is SEO Dead? What the 2025–2026 Click Data Actually Says](https://magnitude.cc/learn/is-seo-dead/): No — but clicks fell hard: −34.5% CTR under AI Overviews (Ahrefs, March 2025), 8% vs 15% in Pew's panel. What changed, what rebounded, what we reallocated.
- [Is Speakable Schema Worth Adding? Our Negative Result](https://magnitude.cc/learn/speakable-schema/): We ship speakable on every page of 3 production builds and can attribute no effect to it. A negative result, plus the one case where it is worth adding.
- [llms.txt: What It Is and How to Set It Up](https://magnitude.cc/learn/llms-txt-how-to/): How to write and deploy an llms.txt file in about 30 minutes: the proposal's format, a working example, and what our 3 sites' logs say about its value.
- [Nosnippet, Max-Snippet, Data-Nosnippet: The Only Granular AI Overview Controls](https://magnitude.cc/learn/snippet-controls-nosnippet-max-snippet/): nosnippet blocks a page as 'direct input' for AI Overviews and AI Mode; max-snippet caps it by characters. What Google's 4 snippet controls trade away.
- [Organization Schema as Your Entity Home: A Setup Guide](https://magnitude.cc/learn/organization-schema-entity/): One Organization node with a stable @id, emitted once, referenced by every page's publisher field. Our production graph — and the 1,885-page null result.
- [PerplexityBot and Perplexity-User: What They Do on Your Site](https://magnitude.cc/learn/perplexitybot-guide/): Perplexity documents 2 agents: PerplexityBot builds its search index; Perplexity-User fetches for users and may ignore robots.txt. ~195 crawls per click.
- [RAG for Marketers: The Pipeline Behind AI Answers](https://magnitude.cc/learn/what-is-rag-for-marketers/): RAG grounds AI answers in retrieved web pages. The 3-stage pipeline — retrieve, select, synthesize — and the 2 stages a publisher can actually influence.
- [Robots.txt for AI Crawlers: A Decision Framework](https://magnitude.cc/learn/robots-txt-for-ai-decision-framework/): Decide robots.txt by the bot's job — training, search, or user-fetch — not the company. A per-bot decision table for 4 business models, per RFC 9309.
- [Server Log Analysis: Which AI Bots Crawl Your Site](https://magnitude.cc/learn/server-log-ai-bot-analysis/): Analytics can't see AI bots — server logs can. How to grep for the 8 documented AI crawler tokens, verify them against vendor IP lists, and read the counts.
- [Should Every Page Have a Call to Action?](https://magnitude.cc/learn/pages-that-should-not-convert/): No. On our leasing build 11 of 12 distress-scenario pages carry zero CTAs and end on free-help resources — a trust decision, not a visibility tactic.
- [Should Publishers Block AI Crawlers? A Decision Framework](https://magnitude.cc/learn/publisher-block-or-allow-ai/): Cloudflare's July 2025 data: Google crawled 5.4 pages per referred visit, OpenAI ~1,091, Anthropic ~38,000. The block-or-allow decision, by business model.
- [Should You Post on Reddit to Get Into AI Answers?](https://magnitude.cc/learn/reddit-strategy-for-ai-answers/): Participate, never manufacture. The sock-puppet play risks your domain, not just an account — plus the 5-phrase monitoring setup we actually run.
- [Should You Publish Experiments That Didn't Work?](https://magnitude.cc/learn/negative-results-content/): Negative results are the one content type this niche cannot fake. Our 2 published nulls, the format that keeps them honest, and what they do not prove.
- [The GA4 AI Channel Group Regex, From Our Production Referrer List](https://magnitude.cc/learn/ga4-ai-channel-group-regex/): The 9-hostname GA4 channel regex derived from the AI-referral matcher live in our production tagging since 2026-08-12, Semrush's additions, and upkeep.
- [The Princeton GEO Study: Is the +40% Result Real?](https://magnitude.cc/learn/princeton-geo-study-explained/): The KDD 2024 paper reports up to 40% visibility lift inside its own benchmark. What it tested, which levers moved, and why nobody has replicated it.
- [What a Realistic 90-Day GEO Plan Looks Like](https://magnitude.cc/learn/geo-roadmap-90-days/): The ordered sequence 3 production builds actually ran — contract and gates first, then map, audit, indexing, measurement, mining — mapped onto 90 days.
- [What Is a Google AI Overview? Anatomy and Eligibility](https://magnitude.cc/learn/ai-overviews-explained/): A Google AI Overview is an AI-generated summary with source links shown above results. Eligibility per Google's docs, plus the 4 snippet controls you have.
- [What Is AI SEO? The Umbrella Term, Unpacked](https://magnitude.cc/learn/what-is-ai-seo/): AI SEO is 1 practice sold under 5 names: making pages AI answer engines can retrieve, quote, and cite. What it covers, and how to spot a repackaged retainer.
- [What Is Answer Engine Optimization (AEO)?](https://magnitude.cc/learn/what-is-answer-engine-optimization/): Answer engine optimization (AEO) explained: what answer engines are, how AEO relates to GEO and SEO, and why 1 discipline sits under all the names.
- [What Is Generative Engine Optimization (GEO)?](https://magnitude.cc/learn/what-is-geo/): Generative engine optimization (GEO) defined in 50 extractable words, where the term came from, and an honest table of what GEO can and cannot prove.
- [What Is Google AI Mode — and How Is It Different From AI Overviews?](https://magnitude.cc/learn/what-is-google-ai-mode/): AI Mode is Google's conversational search experience; AI Overviews sit above classic results. Both share 1 eligibility rule: indexed and snippet-eligible.
- [What Is Google-Extended — and Should You Block It?](https://magnitude.cc/learn/google-extended-explained/): Google-Extended controls Gemini training and grounding — not Search rankings, not AI Overviews. What the 1 most-misread AI robots.txt token does.
- [What sameAs Actually Does for Entity Recognition](https://magnitude.cc/learn/sameas-knowledge-graph/): sameAs points at reference pages that unambiguously identify an entity. Which targets disambiguate, which are noise — and why 0 studies tie it to citations.
- [When Is a Content Library Finished?](https://magnitude.cc/learn/when-a-content-library-is-finished/): Not at a page count. Across our 3 builds the query miner started driving new pages at 188, 298 and 106 files — on day 21, day 14 and day 38.
- [When Reputable Sources Disagree: The Answer-Variance Method](https://magnitude.cc/learn/when-sources-disagree/): Publish the reconciliation, not a verdict. The registry method: 20 contested questions on one build, 18 on another, all resolved before writing starts.
- [Why Does a Page Rank Well and Get No Clicks?](https://magnitude.cc/learn/why-good-rankings-get-no-clicks/): Three causes look identical in Search Console and have opposite fixes. Seer measured organic CTR down 61-70% when an AI Overview is present.
- [Zero-Click Search: What the Numbers Actually Say](https://magnitude.cc/learn/zero-click-search-explained/): A zero-click search ends on the results page. Pew measured 8% vs 15% click rates with AI summaries; Ahrefs found −34.5% CTR. The numbers, reconciled.

## Glossary

- [AI Citation](https://magnitude.cc/glossary/ai-citation/): An AI citation is a source link inside a generated answer. Pew data: ~1% of users click them — yet cited sites earned ~35% higher CTR (Seer, 2025).
- [AI Hallucination](https://magnitude.cc/glossary/hallucination/): An AI hallucination is confident fabricated output, like the $249–$399 price ladder our pipeline extracted from a page carrying one $479 offer [our data].
- [AI Share of Voice](https://magnitude.cc/glossary/ai-share-of-voice/): AI share of voice is the share of tracked prompts where an answer engine mentions or cites your brand — 6 appearances on 25 prompts is 24% for the month.
- [AI Training Data](https://magnitude.cc/glossary/training-data/): AI training data is the corpus a model learns from before it answers — not the index it searches at answer time. 2 corpora, 2 crawlers, 2 opt-outs.
- [Answer Engine](https://magnitude.cc/glossary/answer-engine/): An answer engine returns 1 composed, cited answer instead of ranked links. The named engines — and Pew's 2025 data on what that does to clicks.
- [Bingbot](https://magnitude.cc/glossary/bingbot/): Bingbot is Microsoft's crawler for the Bing index behind Bing search, Copilot and grounding API results. IndexNow pushes up to 10,000 URLs per request.
- [Chunking](https://magnitude.cc/glossary/chunking/): Chunking splits pages into the passages AI engines index and quote. Why 2–4 sentence paragraphs and standalone sections are retrieval decisions, not style.
- [Citable Passage](https://magnitude.cc/glossary/citable-passage/): A citable passage survives being quoted with zero context. The property, the 5 dependencies that break it, and the 2 blocks our contract enforces per page.
- [Click-Through Rate (CTR)](https://magnitude.cc/glossary/click-through-rate/): CTR is clicks divided by impressions. Ahrefs measured −34.5% CTR under AI Overviews (March 2025); Seer measured about +35% for cited pages (2025).
- [Crawl-to-Refer Ratio](https://magnitude.cc/glossary/crawl-to-refer-ratio/): The crawl-to-refer ratio counts crawler fetches per referred visit. Cloudflare's July 2025 data: ~38,000:1 for Anthropic, 5.4:1 for Google.
- [Embedding](https://magnitude.cc/glossary/embedding/): An embedding represents text as numbers so retrieval matches meaning, not words — why 1 page can answer questions it never uses the wording of.
- [Entity](https://magnitude.cc/glossary/entity/): An entity is a thing — person, organization, product, concept — engines identify across sources. Why 1 consistent identity beats 100 keyword variants.
- [Googlebot](https://magnitude.cc/glossary/googlebot/): Googlebot is Google's crawler for the Search index that AI Overviews and AI Mode draw from. Google documents a 15MB default fetch limit and 3 ID signals.
- [Grounding](https://magnitude.cc/glossary/grounding/): Grounding bases an AI answer on pages retrieved at answer time instead of training data alone; 24% of ChatGPT answers skip retrieval (Growth Memo, 2026).
- [Information Gain](https://magnitude.cc/glossary/information-gain/): Information gain is what a page adds that existing sources don't say. The Princeton GEO study's ~40% visibility lift is the closest measured cousin.
- [JSON-LD](https://magnitude.cc/glossary/json-ld/): JSON-LD is a block of JSON that describes a page to machines. It is 1 of the 3 structured-data formats Google documents, and the 1 it recommends.
- [Knowledge Graph](https://magnitude.cc/glossary/knowledge-graph/): A knowledge graph stores entities and the typed relationships between them. What markup does and doesn't do, and why 1 stable identity beats many.
- [Passage Retrieval](https://magnitude.cc/glossary/passage-retrieval/): Passage retrieval scores individual passages, not whole pages. Why the Princeton 2024 gains were passage-level, and what makes a passage standalone.
- [Query Fan-Out](https://magnitude.cc/glossary/query-fan-out/): Query fan-out is how Google's AI features turn 1 query into many concurrent searches. Google documents it for both AI Overviews and AI Mode.
- [SERP (Search Engine Results Page)](https://magnitude.cc/glossary/serp/): A SERP is the page an engine returns for a query. Google now puts generated answers on it too, which is why 2 metrics stopped moving together.
- [Snippet](https://magnitude.cc/glossary/snippet/): A snippet is the excerpt an engine shows or reuses from your page. Google documents 4 directives that limit it — across 6 result surfaces, AI included.
- [Structured Data](https://magnitude.cc/glossary/structured-data/): Structured data is machine-readable markup describing a page's meaning. Google documents 2 jobs for it, and a 1,885-page test found no AI-citation lift.
- [Topical Authority](https://magnitude.cc/glossary/topical-authority/): Topical authority is measurable coverage depth on one subject — not a score any engine publishes. How a 167-page, five-cluster library demonstrates it.
- [User-Agent String](https://magnitude.cc/glossary/user-agent/): A user-agent string is a client's self-reported ID. RFC 9309 matches only the product token inside it, case-insensitively, against 1 group of rules.
- [User-Triggered Fetcher](https://magnitude.cc/glossary/user-triggered-fetcher/): A user-triggered fetcher requests 1 URL because a person just asked. Google names it 1 of 3 client categories; 3 AI vendors document 1 such agent each.
- [Vector Search](https://magnitude.cc/glossary/vector-search/): Vector search retrieves passages by meaning instead of matching words. Why 1 page can be retrieved for questions it never uses the words of.
- [Web Crawler](https://magnitude.cc/glossary/web-crawler/): A web crawler is an automated client that fetches URLs and follows links. RFC 9309 governs the rules; Google sorts its own clients into 3 categories.
- [X-Robots-Tag](https://magnitude.cc/glossary/x-robots-tag/): The X-Robots-Tag carries robots meta tag rules in the HTTP response instead of the HTML. It is invisible in page source, and 1 stray noindex deindexes.