Realm IV
Reference modules
Researched guidance on search engines, AI surfaces, crawling, structured data and measurement, plus the records of how the library was audited.
47 volumes · 27,803 words · Reviewed 9 Sep 2026 · Whole realm as Markdown
AI search and answer engines
-
Agent access, MCP and security boundaries
A readable website and an authenticated tool interface solve different problems. Do not install an MCP server, expose a database or publish privileged actions merely to satisfy an SEO checklist.
-
AI answer observation and controlled evaluation
An observation panel is a controlled sample, not a census of every answer an engine gives. Begin with a business question such as whether a factual service page is cited for a defined set of customer needs.
-
AI referrals, analytics channels and qualified outcomes
GA4 now documents an AI Assistant default channel, while Google AI Overviews and AI Mode are included in Organic Search.
-
AI citation engineeringControllable inputs and observable outcomes
The engineering objective is to make accurate public information retrievable and useful to the intended consumers, then measure actual visibility and business outcomes where observable.
-
Google AI Overviews and AI ModeEligibility, controls and measurement
Google's AI Search features build on its Search systems. A supporting page must meet the documented indexing and snippet eligibility conditions, and no special AI schema or auxiliary text file guarantees selection.
-
Bing AI Performance and citation share interpretation
Bing introduced AI Performance as a public preview in February 2026. Its June expansion adds Intents, Topics, Citation Share and period comparison.
-
Engine specific discovery, training and user access controls
Roles above are from S03, S08, S10, S11 and S12. OAI-AdsBot is an ad landing page workflow, not a prerequisite for organic search visibility.
-
Google generative AI performance: current reporting contract
Google announced dedicated generative AI performance reporting on June 3, 2026 and states that rollout reached websites worldwide on August 31.
-
Preferred Sources and publisher relationship design
Google provides a Preferred Sources workflow and publisher guidance, including an interactive button option. The feature is based on reader choices and supported Search contexts.
-
ChatGPT SearchPublisher access and measured referrals
This filename is retained for compatibility with the earlier library, but the subject is ChatGPT Search and the currently documented publisher controls.
Crawling, delivery and URLs
-
Content delivery firstWithout false crawler absolutes
A website should deliver useful content reliably before decorative or interactive complexity obscures its purpose.
-
Crawl payload budgets and content delivery
Google's March 2026 clarification describes a 2 MB Googlebot fetch limit for supported files other than PDF, with response headers included; resources such as scripts and styles are fetched separately.
-
Crawler identity, logs and safe edge access
A request's user agent text is a claim anyone can send. Store claimed_agent separately from verification_result, verification_method and verification_data_date.
-
Faceted navigation and crawl space control
Inventory filter dimensions, sorting modes, pagination, tracking parameters and variant selection. Estimate the generated URL space from actual application behavior, not only from links found in one crawl.
-
Field performance and interaction acceptance
Current Core Web Vitals are LCP, INP and CLS. 1, assessed at the 75th percentile with mobile and desktop segmentation.
-
Titles, descriptions and preview copy without false limits
Google does not impose a fixed 50 to 60 character title requirement or a 140 to 160 character description requirement.
-
Migration contract, checkpoints and rollback
Write down the old and new states: domains, URL patterns, content, rendering, infrastructure, analytics, structured data and business workflows.
-
Next.js metadata, streaming and rendering validation
js and React versions, router, runtime, hosting target, cache strategy and deployment adapter. Do not copy a server configuration from another client's machine or assume that a framework version mentioned in an old document matches the project.
-
Next.js SEO implementationVersioned route contracts
js/React versions, App versus Pages Router, runtime, deployment adapter and caching strategy. js deployment. Choose the project's actual supported hosting path.
-
Regional Search eligibility and policy differences
Record the business's operating jurisdiction, the content's intended market and the searcher's location. They are not interchangeable.
-
URL lifecycle, canonical decisions and safe retirement
Maintain one record per URL with current status, desired state, content owner, business purpose, incoming/internal links, observed traffic, canonical relationship and planned action.
Structured data
-
Commerce data consistency across page, feed and structured data
Use a controlled product record as the source for visible price, currency, availability, product identity and the matching structured data output.
-
Structured data lifecycle and feature eligibility
Ask whether the JSON is syntactically valid, whether the vocabulary describes the page truthfully, and whether a named consumer currently supports a related feature.
-
Schema types in 2026Semantic validity versus search features
org vocabulary and search engine feature support are separate layers. A valid type can describe content even when Google does not offer a corresponding rich result.
-
Schema examplesFictional, not deployable as supplied
These four files illustrate graph structure, not real businesses, credentials, offers, addresses or ratings. They pass local JSON syntax tests only.
Measurement
-
GA4 implementationCurrent AI channels, scopes and outcome quality
Define the customer action and the independently verifiable business result. A page view, button interaction, form submission, accepted lead and completed sale are different stages.
-
Search Console analysisCurrent reports and defensible diagnostics
Start with the actual property scope, permissions, reporting dates and available features. A domain property, URL prefix property and platform property do not automatically represent the same assets.
-
Social and video platform properties in Search Console
Google's July 29, 2026 announcement describes globally available platform properties for supported social/video services, including Instagram, TikTok, X and YouTube.
Evidence, policy and acceptance
-
Client scope, tier applicability and acceptance
The existing tier names and numbering are retained, including Tier 13's retired status. A tier is a commercial grouping, not proof that every client requires every item.
-
Evidence governance and claim authorization
The old library mixes engine requirements, useful house style, experiments and confident predictions. This edition uses separate evidence classes.
-
Location page evidence and genuine local utility
Approve a location page only when it answers a real local customer need and the business can substantiate its relevance.
-
Research maintenance and documentation drift control
Each maintained rule needs an owner, current source, observed date, affected modules and a next review condition.
-
SEO release contracts and reproducible acceptance tests
“SEO installed” is not a release criterion. Define contracts for each page class: public service, product, article, location, search/filter, account, error and retired URL.
-
First party facts, provenance and reusable evidence
A website should draw business facts from approved records: services actually offered, real qualifications, current availability, genuine project outcomes and verifiable contact details.
-
Search spam policyScoped interpretation and operational controls
Google's spam rules cover manipulative practices including doorway pages, scaled content abuse, hidden content abuse and site reputation abuse.
-
Tier applicability and deliverable map
The original 1 to 14 numbering and names are retained. Tier 13 remains retired. Names such as “AI DOMINATION” and “LOCAL DOMINATION” are legacy packaging labels, not literal promises of platform outcomes.
Library records and audit
-
SEO libraryCanonical master index
09-d26: Route engineering, SEO, AI visibility and publication work through the discipline operating library. Read the master router, cross discipline playbooks and public expertise layer.
-
SEO build reference: intake to production evidence
09-d26: Route engineering, SEO, AI visibility and publication work through the discipline operating library. Read the master router, cross discipline playbooks and public expertise layer.
-
Universal Search Delivery FrameworkNot a ranking formula
The original library linked to this filename without supplying the document. This edition creates a real decision framework while rejecting the implication that a universal ranking algorithm is available.
-
Executed validation2026.09.09
All 24 unit tests passed locally. txt. Tests exercise the four new utilities, including deliberately invalid inputs; they do not execute the preserved original script or legacy code examples.
-
SEO library audit and research update
09
-
Coverage matrixEvery unique original
This is a coverage disclosure, not a pass/fail score. Complete structural inventory and hash preservation apply to all 146 unique originals.
-
Findings and dispositions
28 selected finding records. Classifications distinguish confirmed errors, outdated features, unsafe universal instructions, unsupported generalizations, unverified numerical claims and audit method limits.
-
Remaining review queue and explicit limits
This release is a completed structural audit and targeted research update, not a line by line factual certification of approximately one million original words.
-
Primary source register
Research snapshot: 9 September 2026. These 52 primary sources were consulted for the stated scopes: 50 search, analytics, web platform and agent sources, plus two sources for the proposed CI workflow.
-
Implementation templates
The 12 JSON files in this folder are working data contracts and fictional examples, not populated client reports.
-
Offline tools and test scope
10 or newer, standard library only. These tools make no network requests, do not execute uploaded historical scripts and do not change a website or account.