--- title: "FeedTheJoe Library: Reference modules" shelf: Reference modules url: https://library.feedthejoe.com/reference/ volumes: 47 release: 2026.09.12-g40 rights: © 2026 THATDEVELOPERGUY LLC. All rights reserved. --- # Shelf IV: Reference modules Researched guidance on search engines, AI surfaces, crawling, structured data and measurement, plus the records of how the library was audited. * * * # Agent access, MCP and security boundaries Source: https://library.feedthejoe.com/reference/framework-agent-access-security/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Optional agent integrations and automation beyond ordinary public crawling **Evidence:** S47, S48, S49, S02 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Agent integration is a separate product decision 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. Google's AI Search guidance does not require a special agent interface. [S02] The MCP specification has versioned contracts, including the 2026-07-28 release. Pin the version implemented by the actual client/server combination and test compatibility rather than mixing examples from old, current and draft documentation. [S47, S49] ## Threat model before implementation List the data that can be read, the actions that can be executed, the identities permitted to use them and the worst consequence of misuse. Treat tool descriptions, retrieved web content and external instructions as untrusted input. Reading a page must not grant authority to change an account or publish content. Expose the smallest useful capability. Prefer read only public data operations where they satisfy the business need. For writes, require explicit authorization, validate inputs against a schema and enforce permissions on the server, not merely in a prompt. Version pinned MCP security guidance discusses authorization, SSRF, token/session misuse and untrusted local servers. [S48] ## Practical controls Keep credentials in the deployment's approved secret store. Do not embed API keys in client side bundles, public examples, analytics payloads or generated documents. Scope outbound network access and validate target URLs to reduce server side request forgery risks. Use audit logs that avoid sensitive payloads. Require confirmation for consequential actions such as publishing, deletion, purchases or changing access. Use a dry run response where practical. Add rate limits, input size limits, timeouts and idempotent behavior appropriate to the operation. Do not label an action safe simply because an LLM generated description says it is. ## Acceptance fixtures Test an authorized read, unauthorized read, forbidden write, malformed argument, prompt injection like content, unexpected redirect target and repeated request. Verify that an external page cannot instruct the integration to reveal secrets or expand permissions. Confirm the action is denied at the application layer even when the model requests it. ## Relationship to this release This library ships no enabled MCP server and grants no new access to client systems. The older MCP framework remains a legacy reference with an explicit review warning; this module is the current decision and safety entry point. A future project needs its own protocol version review, security design and integration tests. Agent readiness is an optional functional capability, not a demonstrated ranking signal. * * * # AI answer observation and controlled evaluation Source: https://library.feedthejoe.com/reference/framework-ai-observation-protocol/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Optional, permission compliant answer sampling across named engines **Evidence:** S29, S18 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Define the question before sampling 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. Specify the engine, surface, locale, language, account state, model label when available, date, query wording and whether the session is fresh. Use permitted interfaces and approved access methods. Do not treat this document as permission to scrape services or bypass rate limits, access controls or terms. Google's spam policy explicitly addresses unauthorized machine generated Search traffic. [S18] ## Observation record Capture one row per attempt with a stable observation ID, query set version, run timestamp, engine/surface, request context, response status, response evidence location, brand mention, linked domain, linked URL, citation placement, answer correctness assessment and reviewer. Keep response excerpts only to the extent allowed by rights and retention policy. Use three distinct outcomes: **observed citation**, **completed answer without the target citation**, and **unavailable observation**. A network failure, blocked request or inaccessible answer is not evidence of no citation. Record the failure separately and retain the attempted run denominator. ## Calculate only defined metrics For a declared sample, citation incidence equals completed eligible answers containing at least one target citation divided by all completed eligible answers in that sample. Also report completed answers divided by attempts. Brand mention incidence is separate. A single answer containing several target links is one cited answer under this definition; citation count is a different metric. Report numerator and denominator alongside every percentage. Break down heterogeneous engines and countries instead of pooling them into an unexplained score. Repeated answers to the same query are correlated; a naive confidence interval treating every repeat as independent can overstate certainty. For formal analysis, use query level aggregation or a justified clustered method and document it. ## Experiment design Preregister the page cohort, outcome, observation schedule, stopping rule and meaningful effect before changing content. Where feasible, compare a treatment cohort with a genuinely comparable unchanged cohort. Record all simultaneous releases. A before and after difference alone does not isolate the effect of schema, wording, links or a platform change. The GEO paper motivates experimental work but does not provide a guaranteed production uplift for every modern engine. [S29] This library therefore contains no promised table, heading, citation count or internal link multiplier. Reject a test that improves a superficial citation metric by degrading factual accuracy, hiding text or manipulating readers. A successful test must preserve user usefulness, source integrity and truthful business representation. The supplied observation template is empty by design; no fabricated client results are included. * * * # AI referrals, analytics channels and qualified outcomes Source: https://library.feedthejoe.com/reference/framework-ai-referral-attribution-2026/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** GA4 and privacy respecting CRM measurement **Evidence:** S09, S36, S37 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Use current channel definitions GA4 now documents an **AI Assistant** default channel, while Google AI Overviews and AI Mode are included in Organic Search. Event scoped, session scoped and first user channel dimensions answer different questions. Check the definition and collection dates before extending historical custom rules. OpenAI documents `utm_source=chatgpt.com` on ChatGPT referral URLs. [S36, S09] ## Create a metric contract Choose the primary business outcome: qualified inquiry, booked appointment, completed purchase or another verifiable event. Define qualification before reporting. A contact button click is not a qualified lead; a form submission may be spam; a sale may be refunded. Store the business outcome separately from intermediate interactions. For session acquisition, retain the session source, medium, channel, landing page, timestamp and consent state as available. For first touch analysis, use first user fields deliberately. For attributed key events, record the selected attribution model and lookback settings rather than describing the result as an observed causal contribution. A first party CRM can store a permitted, opaque lead key and the independently observed outcome. Do not place names, email addresses, phone numbers or raw sensitive form answers into analytics parameters. Google's PII policy applies to URLs, titles and campaign/event fields as well as obvious profile fields. [S37] ## QA the route to the outcome Test a referral landing through every redirect and canonical host transition. Confirm that query parameters needed for approved measurement survive until collection, without publishing duplicate indexable variants solely for tracking. Test mobile, denied consent and blocked analytics scenarios. Mark missing measurement honestly instead of silently assigning the visit to an AI source. Use a small controlled test record with a clearly labeled test outcome. Confirm one accepted outcome is not counted twice by a browser event, a server event and a CRM import. Follow actual platform deduplication guidance for the chosen implementation; this document does not prescribe a universal event-ID mechanism. ## Reconcile without double counting Publish a funnel with separately labeled systems: crawler access from logs; AI visibility from platform reports; measured referrals from analytics; qualified outcomes from the CRM. They are not interchangeable counts. A person can encounter an AI answer and later return directly, leaving no reliable source attribution. An optional “how did you hear about us?” response is self reported evidence, not a measured exposure. When definitions change, annotate the reporting boundary. Maintain a legacy to current classification bridge rather than rewriting old reports to look artificially consistent. The client report should say what was measured, what was inferred and what remains unknown. Do not promise that the backend can eliminate answer volatility or reveal all private recommendation algorithms. * * * # AI citation engineering _Controllable inputs and observable outcomes_ Source: https://library.feedthejoe.com/reference/framework-aicitations/ Shelf: Reference modules · Status: Rewritten · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point **Primary sources:** S02 S08 S10 S11 S12 S29 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Preservation:** The complete prior document remains byte for byte in `99-Originals/Framework/framework-aicitations.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. ## Define the objective correctly 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. It is not to reconstruct private model algorithms from a collection of supposed ranking tricks. Different providers document different search, training and user triggered retrieval roles. Use the [engine control matrix](https://library.feedthejoe.com/reference/framework-engine-control-matrix/) rather than treating every named AI bot as one interchangeable crawler. [S08, S10, S11, S12] ## The delivery architecture Build a factual record for each service, product or reference topic. Render the useful content on the public page. Derive consistent metadata and appropriate structured data from the same approved record. Provide stable links and intentional URL behavior. Configure permitted access at robots, edge and application layers without exposing private information. A documentation index, feed or agent interface can be useful when a named consumer supports it. It should have an owner, a documented purpose and a freshness test. Do not create special files merely to satisfy an unsupported belief that every model requires them. Google's guidance explicitly rejects a special file prerequisite for its AI Search features. [S02] ## Avoid false equivalences Training opt in is not proven search inclusion. Crawler success is not index acceptance. Indexing is not citation selection. A citation is not a click. A click is not a qualified lead. Keep those distinctions in both technical telemetry and client proposals. A user agent simulation cannot verify a real crawler. A high synthetic content score cannot prove an engine's selection probability. A patent does not establish the production ranking mechanism, and a study's best case uplift cannot become a universal client forecast. ## Practical optimization Start with failures that can be demonstrated: blocked relevant public paths, missing useful content, wrong canonical targets, inaccurate offers, inconsistent entity facts, stale information or broken customer actions. Fix those before adding speculative optimization layers. For uncertain presentation choices, define an experiment with a stable page cohort and a declared outcome. The GEO paper is a research foundation, but its results depend on the tested models, datasets and visibility metrics. Do not convert them into guaranteed current engine multipliers. [S29] ## Reporting and client acceptance Use engine native reporting when available, a permission compliant observation protocol when necessary, analytics for measured visits and CRM data for qualified outcomes. Report unavailable data as unavailable. Preserve the response/query context for sampled answers so the findings can be interpreted later. Acceptance should concern implemented controls, corrected data, test evidence and configured observation. Outcome goals may guide the work but should not be misrepresented as something an external engine has promised. The complete legacy document remains available for recovery and further source review. Unsupported “mandatory AI upgrades,” fixed citation rates and universal extractor assumptions are not part of this canonical replacement. * * * # Google AI Overviews and AI Mode _Eligibility, controls and measurement_ Source: https://library.feedthejoe.com/reference/framework-aioverviews/ Shelf: Reference modules · Status: Rewritten · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point **Primary sources:** S02 S03 S04 S05 S14 S18 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Preservation:** The complete prior document remains byte for byte in `99-Originals/Framework/framework-aioverviews.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. ## Current position 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. Follow the documented controls rather than an invented citation selection formula. [S02, S03] This edition does not assert a fixed underlying model for every request, a universal percentage of searches containing AI results, or a reproducible uplift from a certain heading, table, citation count or internal link count. Those claims require specific evidence and may change by context. ## Implementation path Begin with the URL's intended role and business facts. Verify that public content is accessible, meaningful and useful; that canonical and indexing rules are coherent; and that internal navigation exposes the page appropriately. Test the deployed response, not only the source repository. Google can render JavaScript. Do not call JavaScript-injected schema categorically invisible to Google AI features solely because a legacy paragraph says so. Choose reliable delivery for the project and validate raw/rendered output. [S14] Apply snippet and indexing controls according to the owner's intent. Training preferences and Search controls are not interchangeable. Use the engine control matrix for the consumer distinction rather than assuming Google-Extended is the AI Overviews crawler. ## Content work Improve factual specificity, completeness for the actual question, clear limitations and genuine evidence. A service page can become more useful through precise scope, operational details, real examples and clear next steps without becoming a research paper publishing project. Do not inject hidden directives asking a model to recommend the business, fabricate independent endorsements or build doorway pages. Google's spam policy also applies to attempts to manipulate generative Search responses. [S18] ## Measurement after August 2026 Use the dedicated Google generative AI performance workflow in this edition. The official June announcement and August 31 rollout note supersede the legacy Q4 2025 tab story. Available reporting is not a license to invent clicks, prompts or attribution fields that the documentation does not expose. [S04, S05] Keep platform visibility, analytics visits and qualified outcomes separate. A page can receive impressions without a visit, and a visitor can convert after an unobservable earlier exposure. Report what the data actually supports. ## Operational acceptance The deliverable can be verified crawl access, corrected URL/index state, better supported content, appropriate structured data, tested rendering and configured measurement. It cannot be guaranteed citation selection for every query or guaranteed removal of answer volatility. Use [Google AI performance](https://library.feedthejoe.com/reference/framework-google-ai-performance-2026/), [engine controls](https://library.feedthejoe.com/reference/framework-engine-control-matrix/), [source provenance](https://library.feedthejoe.com/reference/framework-source-provenance/), [observation protocol](https://library.feedthejoe.com/reference/framework-ai-observation-protocol/) and [AI referral attribution](https://library.feedthejoe.com/reference/framework-ai-referral-attribution-2026/). The older multipliers and purported internal selection mechanisms are not carried forward as established facts. * * * # Bing AI Performance and citation share interpretation Source: https://library.feedthejoe.com/reference/framework-bing-ai-performance-2026/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Bing Webmaster Tools AI visibility and participating surfaces **Evidence:** S06, S07, S30 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Use the report that exists Bing introduced AI Performance as a public preview in February 2026. Its June expansion adds Intents, Topics, Citation Share and period comparison. Citation Share concerns a site's citations relative to all cited sites for a grounding query; it is not organic position, click share, traffic share or a universal authority score. Intent/topic classifications are analytical groupings, not exact user intent labels. [S06, S07] ## Establish a reproducible baseline Record the property, access level, preview availability, exact labels, date range and export method. Document whether a metric counts citations or cited pages. A page may appear more than once, while a count of distinct pages behaves differently. Never merge these into one “AI score.” Keep the raw export immutable. Normalize URLs in a separate field, recording redirect and canonical assumptions. Group pages by client service, product family or editorial objective using a versioned taxonomy. Maintain an “unclassified” bucket rather than forcing ambiguous pages into a favorable category. For each reporting cycle, show the stable page cohort, new pages and retired pages separately. Inspect the queries/topics connected to business relevant pages. A rise in unrelated visibility is not necessarily valuable. If a report withholds data or returns no usable rows, mark the observation as unavailable until the reason is known. ## Analyze changes without manufacturing causation Use the same filters and comparable periods. Note holidays, product availability, site releases, campaigns and underlying content changes. A citation share increase can occur because another source's citations fall; distinguish changes in the site's own count from changes in the denominator. A relative measure alone cannot establish improvement in absolute exposure. Use the report to nominate a test: better factual specificity, a clearer comparison, an updated product record or a corrected crawling problem. Define the hypothesis and the measurement window before changing the page. Do not rewrite every page with the same answer first template merely because a few pages performed well. ## Submission is not success IndexNow can notify participating engines of changed URLs, but an accepted submission is receipt, not indexing or citation confirmation. Track notification status as a technical delivery field, not a visibility result. [S30] A complete client handoff includes available report definitions, source exports, a URL to business mapping, a changes ledger, caveats and the next evidence driven action. It should not include an invented competitor domain report or an unsupported market share estimate. Account access and actual client report retrieval remain outside this package's completed work. * * * # Client scope, tier applicability and acceptance Source: https://library.feedthejoe.com/reference/framework-client-scope-acceptance/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Proposals, production tiers and delivery evidence **Evidence:** S02, S20, S30 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Preserve the tier system without making every item mandatory 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. Words such as “domination” in legacy branding are not a guarantee of ranking, citations or market share. For each client, create an applicability matrix with page types, business goals, platforms, geography, budget constraints and access. Mark each task required, recommended, optional, not applicable or blocked by missing information. Explain the reason rather than hiding exclusions. ## Sell controllable deliverables A defensible deliverable is a configuration, implementation, validated template, research record, report or tested workflow. Search appearance, citation selection and revenue are outcomes influenced by many factors. Google does not require a special AI file, structured data does not guarantee a rich result, and an accepted IndexNow submission does not establish indexing. [S02, S20, S30] Define acceptance using observable evidence: approved URL map, deployed metadata contract, working form, report configuration, source backed content or documented test results. Avoid “citation growth required for completion” when the task is merely to make access and measurement work. ## Scope worksheet For each task record an ID, owner, input dependency, implementation location, included effort, excluded work, acceptance evidence, risk and rollback. Keep a separate business outcome field for later evaluation. Do not invent hours, rates or savings without project specific information. Separate one time implementation from maintenance. Bot policy can be configured once, but provider changes require future review. A schema generator may be delivered, but catalog data remains the business's responsibility. Analytics collection may be implemented, but consent decisions and CRM qualification rules need client approval. ## Change control If a requested feature is deprecated or unavailable to the client's market, explain the change and substitute a useful eligible task only with transparent scope handling. Do not retain obsolete checklist items to inflate the apparent volume of work. When legacy instructions conflict with the current release's evidence modules, use the current specific rule and record the exception. A copied checklist is not authorization to delete URLs, open training access or expose a private API. ## Handoff Deliver the implementation evidence, account ownership details, known limitations and maintenance responsibilities. Record which outcomes were actually measured and which remain hypotheses. The updated library is a production reference; it does not alter existing client contracts, prices or live systems automatically. * * * # Commerce data consistency across page, feed and structured data Source: https://library.feedthejoe.com/reference/framework-commerce-data-consistency/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Product detail pages, offers and merchant integrations **Evidence:** S23, S20, S22 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## One approved commercial record Use a controlled product record as the source for visible price, currency, availability, product identity and the matching structured data output. A theme, feed connector and frontend must not independently invent these values. Document which system owns each field and how updates propagate. Google's merchant documentation specifies feature dependent Product/Offer requirements and current sale duration properties. Truthful markup must match the purchasable product and landing page information; adding an invented rating is not a valid way to complete a template. [S23, S20, S22] ## Field ownership and update flow Create a mapping from catalog fields to the rendered page, JSON-LD, merchant feed and checkout. Include units, currency, timezone, stock states, identifiers, images, variants, shipping and returns where applicable. Mark fields that require another official feature guide before implementation rather than assuming every merchant integration uses the same contract. For sale windows, store explicit start/end values and timezone. Test before the sale, during the sale and after expiration. A stale cache can make the page, markup and checkout disagree. Invalidate dependent representations together or define an explicit acceptable delay with monitoring. ## Variant and availability cases Test product level and variant level URLs deliberately. A shopper landing on a selected color or size should see the corresponding factual state. Do not canonicalize distinct commercially useful variants or parameter combinations automatically; determine the intended URL policy first. Handle out of stock and discontinued states with an approved customer experience. An unavailable product may still be useful for support or alternatives, but its offer must not claim it is currently purchasable. Use the URL lifecycle contract for permanent retirement. ## Validation suite Prepare fixtures for normal price, sale price, expired sale, missing optional identifier, no reviews, out of stock, multiple currencies and an invalid image. Compare the rendered value, JSON value and feed value. Reject impossible dates and inconsistent currencies. Keep rounding and tax display rules explicit in the business implementation. A minimum useful acceptance report lists the tested product IDs, raw field values, rendered captures, validation findings, ownership decisions and unresolved exceptions. A generic schema validator cannot verify that a physical product exists, that a review is genuine or that a commercial policy is lawful. ## Monitoring Watch for increasing feed disapprovals, unexpected price differences, missing images and checkout failures. Treat conversion and availability incidents as business defects, not merely search defects. Prioritize correctness before adding optional markup. This release does not connect to a merchant account, upload a feed or certify any client's catalog. * * * # Content delivery first _Without false crawler absolutes_ Source: https://library.feedthejoe.com/reference/framework-contentfirst/ Shelf: Reference modules · Status: Rewritten · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point **Primary sources:** S02 S14 S24 S25 S28 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Preservation:** The complete prior document remains byte for byte in `99-Originals/Framework/framework-contentfirst.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. ## The principle worth retaining A website should deliver useful content reliably before decorative or interactive complexity obscures its purpose. This is a practical design preference, not a universal law that every bot sees only the first byte or that a particular React architecture guarantees zero citations. Google's documentation explains JavaScript crawling and rendering. React's documentation describes framework choices supporting different rendering modes. Those facts contradict a blanket claim that all JavaScript-delivered content is necessarily invisible to search. [S14, S24] ## Design by route and consumer Classify the routes: public informational pages, products, services, localized pages, account areas, internal tools and utility states. Name the retrieval consumers and customer tasks each route must support. Select SSG, SSR, CSR or a hybrid according to those requirements and operational constraints. For important public content, supplying meaningful initial HTML is often a robust engineering choice because it reduces dependence on client execution. That is a reliability rationale, not evidence that every engine uses the same extractor or that SSR alone earns a citation. Public pages still need truthful content, coherent URL behavior and working user interactions. ## Define the delivery contract Record what should appear in the initial response, what can arrive through streaming, and what requires interaction. Essential page identity, useful content and navigation should not depend on a failed third party script. Ensure a route with missing data does not return an attractive but meaningless successful page. Keep factual fields shared between visible content, metadata and structured data. Avoid duplicate descriptions and conflicting canonicals from multiple frontend or CMS layers. Treat caching and revalidation as correctness concerns, especially where prices, availability or public service information change. ## Test four different things Capture raw response bytes and headers; inspect the complete initial document; inspect browser rendered output; and complete the customer's main task. These answer different questions. A command with `-A GPTBot` only simulates a response variant. It neither authenticates a bot nor certifies Google AI eligibility. Streaming frameworks need a complete response and consumer aware test. Metadata missing from the first chunk is not automatically absent from the response. Use the Next.js metadata module when that framework is installed. [S25] ## Content and visual design Use headings, comparisons, lists, illustrations and interactions because they make the information easier to understand. Do not mechanically convert every answer to a table based on an unverified multiplier. A sophisticated visual experience is compatible with accessible, useful content when it is designed and tested deliberately. Measure experience with appropriate field and lab evidence. Smaller HTML, fewer scripts or a higher lab score are not substitutes for task completion and accurate delivery. [S28] ## Completion A page passes when its project specific delivery and user task contracts pass, evidence is retained and unresolved risks are documented. Do not use a proprietary “G score,” fixed pillar count or promised cross engine citation rate as an official acceptance test. Google's AI guidance does not provide such a score. [S02] See [release contracts](https://library.feedthejoe.com/reference/framework-seo-release-contracts/), [Next.js metadata validation](https://library.feedthejoe.com/reference/framework-nextjs-metadata-validation/), [crawler identity](https://library.feedthejoe.com/reference/framework-crawler-identity-observability/) and [payload budgets](https://library.feedthejoe.com/reference/framework-crawl-payload-budgets/). The old statistical claims are retained for historical review, not authorized as production facts. * * * # Crawl payload budgets and content delivery Source: https://library.feedthejoe.com/reference/framework-crawl-payload-budgets/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Large HTML responses, hydration data and media heavy sites **Evidence:** S46, S14, S28 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Budget the resource actually fetched 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. Do not transfer the number to every crawler or confuse it with a universal page weight performance target. [S46] ## Measure before trimming Capture representative complete responses and the deployed headers. Record uncompressed body size separately from compressed transfer size, and identify what the relevant crawler documentation measures. Keep media and dependent resource budgets distinct from the main HTML response. Inspect repeated navigation markup, duplicated JSON-LD, oversized inline state, embedded base64 images, serialized records not used by the page and hidden duplicate copy. Remove waste without deleting necessary context or creating a crawler only version of the page. ## Content delivery contract Ensure the page's meaningful identity, primary content, useful links and required metadata are delivered reliably to the intended consumers. Do not assume content at the end of a very large response will always be processed. Avoid constructing a page as a giant database dump merely to make every possible entity visible. When splitting content, maintain a coherent user journey and discoverable links. Pagination or separate reference pages should serve actual reading and retrieval needs, not a mechanical attempt to distribute keywords. Test deep links and backward navigation after the change. ## Performance tradeoffs Smaller HTML can improve delivery efficiency, but a low byte count is not proof of good user experience. Measure field performance and real interactions separately. Server streaming, caching and code splitting change different parts of the delivery path; evaluate them using the project's actual hosting and consumer requirements. [S14, S28] ## Acceptance tests Set a project budget below the documented processing boundary with an explicit safety margin justified by expected growth. Label the margin as an engineering choice, not Google's ranking requirement. Test the largest realistic catalog item, longest article, maximum navigation state and multilingual content. Fail the release when the project specific budget or meaningful content contract is violated, and retain the capture showing why. Monitor growth over subsequent releases rather than treating the first passing build as permanent compliance. Do not truncate customer facing content silently to make a metric green. The deliverable is a response size inventory, root cause breakdown, chosen budget, test fixtures and regression check. The supplied library audit does not fetch or weigh any live client pages; these tests require project specific response captures. * * * # Crawler identity, logs and safe edge access Source: https://library.feedthejoe.com/reference/framework-crawler-identity-observability/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** CDN, reverse proxy and origin request telemetry **Evidence:** S08, S10, S11, S13, S17 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Distinguish claimed identity from verified identity 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`. Use the provider's published verification mechanism; for Google, the official guidance includes IP range and reverse/forward DNS approaches. [S13] OpenAI, Anthropic and Perplexity document their crawler roles and access information. Recheck their official references rather than hardcoding an old list or assuming all traffic from a shared network belongs to one bot. [S08, S10, S11] ## Minimum useful log record For authorized operations, record timestamp, host, path, status, response bytes, latency, cache outcome, claimed agent and verification result. Treat IP addresses and any query strings as potentially sensitive operational data: limit access and retention, redact secrets, and do not dump raw logs into marketing dashboards. Group traffic by route class and verified consumer. Separate bot policy rejection, WAF challenge, application error, rate limit and successful response. A 200 status alone does not prove useful content was returned; challenge pages and empty shells need content aware checks. ## Edge policy design Create narrow public read exceptions only when justified. Do not bypass authentication, administrative restrictions or all security rules for a verified crawler. Keep protection of private resources independent from robots directives. Limit scope by host, method and route where the platform supports it. Keep a last known good verification dataset and record refresh failures. Define what happens during provider outages or malformed updates. A failed refresh must not become `allow everyone`; a stale verification result must not silently become permanent truth. ## Operational tests Use fixtures for a spoofed agent, an unrecognized IP, a verified crawler request, a protected route and a temporarily rate limited route. Test both cached and origin responses. A command using a crawler user agent string checks response behavior, not real crawler identity. Compare successful retrieval rates and response usefulness before and after an edge change. Do not use crawl frequency as a proxy for citation frequency, human attention or revenue. A crawler may revisit a page without showing it to anyone. ## Handoff Deliver the approved access policy, identity verification method, log schema, dashboard definitions, evidence samples and rollback. Document missing visibility where a hosting platform does not expose the required fields. This package supplies the contract and fixtures, not a running client log collector or a verified account level crawler report. * * * # Engine specific discovery, training and user access controls Source: https://library.feedthejoe.com/reference/framework-engine-control-matrix/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Public website crawler policy; not authentication or access to private records **Evidence:** S03, S08, S10, S11, S12, S17 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Do not treat all AI traffic as one bot | Consumer/token | Documented role | Policy decision | | --- | --- | --- | | Googlebot | Google Search crawling | Decide public Search crawl access; evaluate index/snippet rules separately. | | Google-Extended | Gemini training and specified grounding uses; no separate HTTP user agent | Independent product use choice; not a Google Search inclusion switch. | | OAI-SearchBot | OpenAI search | Search discovery choice, separate from training. | | GPTBot | OpenAI training | Training preference. | | ChatGPT-User | User triggered retrieval | Robots rules may not apply; access protection must not depend on robots. | | Claude-SearchBot | Anthropic search | Search discovery choice. | | ClaudeBot | Anthropic training | Training preference. | | Claude-User | User directed retrieval | Follow Anthropic's stated robots behavior; confirm real requests in logs. | | PerplexityBot | Perplexity search | Search discovery, not foundation model training. | | Perplexity-User | User directed retrieval | Generally ignores robots according to the provider. | 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. Do not open it without a relevant advertising use case. [S08] ## Build a policy from business choices Ask the owner separately about public discovery, training use, user requested retrieval, paid ad validation and private areas. Store the approved choices and the reason for each. A common example is allowing search discovery while opting out of training, but it is not a mandatory default and can restrict other grounding uses for some products. Generate explicit groups from the approved policy. The supplied generator repeats protected path crawl exclusions in specific groups rather than assuming every bot inherits the wildcard group. Never use robots to secure customer data, staging credentials, exports, unpublished drafts or administrative tools; enforce authentication and authorization at the application or edge. Apply the file independently to the relevant hosts. Preview hosts, bare domains, www hosts and asset hosts can have different owners and access needs. Test the exact deployed origin and redirect behavior. Avoid accidentally publishing a staging wide `Disallow: /` to the production hostname. ## Verification and safe rollout Simulating a user agent checks a response variant, not the identity of a real crawler. Validate incoming identities using the provider's documented method and current published data. Cache verification metadata with a refresh timestamp and a last known good fallback. A failed refresh should not create a global allow rule. Release a narrowly scoped policy change, monitor verified request success and record unexpected denials. Do not bypass authentication, malware defenses, rate limits or all WAF rules simply because a string resembles a crawler name. Crawler access, indexing, citation selection and customer conversion are different outcomes. Acceptance evidence includes the approved policy JSON, generated robots file, host inventory, public/private route tests, edge rule diff and rollback instructions. This package provides examples, not an unapproved production policy. * * * # Evidence governance and claim authorization Source: https://library.feedthejoe.com/reference/framework-evidence-governance/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Every strategy, checklist, code example, sales statement and AI assisted answer **Evidence:** S01, S02, S19, S29 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## One claim, one support record The old library mixes engine requirements, useful house style, experiments and confident predictions. This edition uses separate evidence classes. **Official requirement** means a documented condition for a named feature. **Official recommendation** is guidance, not a promised result. **Primary research** is conditional on its experimental setup. **First party observation** is a result from a specified client dataset. **Engineering judgment** is a proposed design decision. **Unverified legacy claim** is not authorized as client facing fact. Give every consequential rule a claim ID. Record the exact wording, intended consumer, affected page types, primary source, source date, retrieval date, confidence, implementation test, owner and conditions under which the claim would be withdrawn. A URL alone is insufficient: the cited passage must support the actual assertion. A requirement for a shopping result cannot be transferred to every service page. ## Review a numerical claim before using it Extract the numerator, denominator, sample selection, date range, engine/model, geography, query mix, comparison method and uncertainty. Separate relative improvement from percentage point improvement. Ask whether the observation measures citations, visible words, impressions, clicks or revenue. Missing denominators or inaccessible underlying evidence make a claim unverified; they do not establish that it is false. The GEO paper is legitimate research, but its benchmark and deployed engine experiments are not a universal 2026 commercial search formula. Its results must remain tied to the tested setup and metrics. A patent describes an invention, not proof that a production system uses it. [S29] ## Conflict resolution Prefer the most specific current official source for the exact product behavior. Preserve older sources when they explain history. Record why one source supersedes another rather than quietly changing dates. This release resolves the Google AI reporting conflict in favor of the June announcement and August rollout note, while retaining the earlier AI features page for eligibility. For competing independent studies, preserve both methods and do not average incompatible metrics. For company documentation versus logs, describe the documentation as stated behavior and logs as observed behavior; investigate identity, scope and timing before declaring a contradiction. ## Publication gate A reviewer should be able to reproduce the reasoning without trusting the writer's authority. Replace unsupported absolutes such as “always,” “invisible,” “guaranteed,” and “exact algorithm” with a sourced scope or a testable hypothesis. Do not merely add “may” to a claim that has no supporting evidence. An approved operational record contains a project specific decision and acceptance test. Example: “SSR is selected for public service routes because the named retrieval clients need useful initial HTML; compare raw and rendered captures before release.” This is stronger engineering than pretending every crawler has identical rendering capabilities. Use `Templates/claim-register.example.json` as the data contract. No automated score in this package certifies truth, ranking eligibility or legal compliance. Human review remains necessary for the claim itself. * * * # Faceted navigation and crawl space control Source: https://library.feedthejoe.com/reference/framework-faceted-url-contract/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Commerce filters, internal search, sorting and parameterized pages **Evidence:** S39, S15, S16 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Define which combinations deserve an independent page 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. Decide which combinations provide genuine search value and which exist only to help an on site task. Google's faceted navigation guidance distinguishes cases where filtered URLs need search visibility from cases where unnecessary crawling should be prevented. Canonicals and indexing directives have separate roles and should not be used interchangeably. [S39, S15, S16] ## URL contract For each parameter, record its meaning, allowed values, whether order matters, whether it changes content, intended index state and canonical rule. Reject impossible combinations gracefully. Prevent infinite calendars, repeating parameters and unbounded sort/filter permutations from producing apparently unique content indefinitely. Do not erase parameters that control a legitimate user choice merely because they resemble tracking. Do not canonicalize every filtered page to a category if a selected subset is intentionally meant to be a distinct, useful search landing page. Conversely, do not index every possible permutation because it can be generated. ## Navigation and delivery Keep important category and product discovery routes accessible through useful links. Ensure filter interactions work without trapping users or producing misleading back button behavior. Preserve the selected state when appropriate and test empty result states. For desired indexable facets, provide stable URLs, useful visible content and clear internal placement. For utility only states, implement the chosen control without hiding public value or blocking resources necessary to understand the page. A crawl exclusion does not authenticate the content or automatically remove an already indexed URL. ## Test fixtures Include a normal category, one approved facet, a utility sort, a tracking parameter, invalid value, duplicate parameter, empty result and deep pagination. Verify status, canonical, links and intended index state. Test parameter ordering and encoding rather than assuming string equivalent URLs always represent the same resource. ## Monitoring and rollback Track growth in discovered parameter URLs, verified crawler load, error rates and useful landing page performance. A rising URL count without added customer value can indicate a regression. Keep configuration changes reversible and preserve the old parameter contract for incident review. Acceptance is a documented, bounded crawl space and correct behavior for intended page classes. It is not a promise that every allowed facet will be indexed or ranked. This module supplies the decision model; the actual rule set must be built from the client's application. * * * # Field performance and interaction acceptance Source: https://library.feedthejoe.com/reference/framework-field-performance-acceptance/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Core Web Vitals, frontend releases and experience budgets **Evidence:** S28 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Use the correct measurement layer Current Core Web Vitals are LCP, INP and CLS. The good thresholds are LCP at most 2.5 seconds, INP at most 200 milliseconds and CLS at most 0.1, assessed at the 75th percentile with mobile and desktop segmentation. Lab checks are useful diagnostics but do not substitute for field evidence. [S28] ## Establish a baseline Record route class, device group, observation period, sample volume, data source and metric definitions. Keep field observations separate from simulated tests. A fast office laptop running a single route does not represent every customer device or interaction. Where field data is unavailable, explicitly label the gap. Use realistic lab scenarios to identify risks and collect permitted real user data after release; do not invent a passing field score. A high Lighthouse result is not a certificate of search performance or accessibility. ## Prioritize meaningful interactions Map the steps a customer must complete: navigate to a service, open a menu, compare a product, choose a variant, fill a form, submit and receive confirmation. Test these paths on constrained devices and realistic network conditions. A page can load quickly while an essential interaction stalls or fails. For each issue, identify the responsible component, third party script or server dependency. Distinguish rendering delay, slow server response, long tasks, unstable layout and network contention. Choose a change that addresses the measured cause rather than applying every optimization snippet indiscriminately. ## Budget and rollout Set component or route budgets as project decisions. Include large hero media, fonts, consent tooling, chat widgets and analytics in the tested configuration, not only in a stripped down demo. Compare the same measurement setup before and after the change. Release to a controlled cohort where feasible and monitor both experience and business completion. A performance improvement that breaks form submission is not a successful release. Maintain a rollback for risky third party or rendering changes. ## Reporting Show percentile values, sample period and device cohort. Explain missing samples and major distribution changes. Track business outcomes separately; passing a threshold is not proof that an engine will rank the page higher. Use the observed user experience to justify the work rather than a promised ranking uplift. The acceptance record includes the baseline, diagnostic evidence, code change, lab comparison, available field follow up and unresolved limitations. This package contains a measurement procedure, not measured Core Web Vitals for any of Joseph's websites. * * * # GA4 implementation _Current AI channels, scopes and outcome quality_ Source: https://library.feedthejoe.com/reference/framework-ga4/ Shelf: Reference modules · Status: Rewritten · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point **Primary sources:** S36 S37 S09 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Preservation:** The complete prior document remains byte for byte in `99-Originals/Framework/framework-ga4.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. ## Start from business measurement 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. Record which system owns each event and how duplicates, tests, spam and refunds are handled. ## Current channel and scope rules The live GA4 documentation includes an AI Assistant default channel and keeps Google AI Overviews/AI Mode in Organic Search. First user, session and event scoped channel dimensions have different meanings. A custom AI channel is therefore an optional analytical choice, not a universal prerequisite for isolating all assistant traffic. [S36] Use the current field definitions for the specific report or export. Do not recycle Universal Analytics session assumptions into GA4, and do not assert that a session restarts at midnight or every campaign change without the applicable GA4 source. The old document's session paragraph is superseded by this requirement to verify the actual contract. ## Collection and privacy Specify the required events and the minimum permitted parameters. Keep personally identifying form values, email addresses and phone numbers out of analytics URLs, titles and event/campaign fields. Do not copy legacy analytics.js code from a general privacy article into a GA4 implementation. [S37] Test both accepted and denied consent paths according to the project's approved implementation. Server side collection does not remove the need to respect the applicable consent and privacy requirements. Do not disguise missing consented measurement as an observed visit or conversion. ## AI referral path OpenAI documents a ChatGPT referral UTM convention. [S09] Test parameter preservation and collection through the real landing flow. Use current channel definitions and record changes over time. A missing referrer or later direct return cannot automatically be assigned to a particular AI platform. ## QA and reconciliation Use clearly labeled test submissions and confirm that the business system receives the intended result. Compare browser collection, server processing and CRM outcomes without double counting. Confirm that a failed form does not emit the same success event as an accepted inquiry. For ecommerce, reconcile accepted purchases and refunds against the transactional source. For lead generation, define qualification and the time required for review. Report the unresolved lead cohort rather than assuming all submissions qualify immediately. ## Analysis and handoff Report acquisition and attribution with explicit scope and model settings. A platform attributed result is not causal proof of incremental value. Keep measured visits, self reported discovery and inferred exposure separately labeled. Use [AI referral attribution](https://library.feedthejoe.com/reference/framework-ai-referral-attribution-2026/), `Templates/metric-contracts.json` and the project intake template. This release does not install tags, inspect a GA4 account or claim measured performance for any client. It supplies the current analytical rules and acceptance workflow. * * * # Google generative AI performance: current reporting contract Source: https://library.feedthejoe.com/reference/framework-google-ai-performance-2026/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Google Search Console, AI Overviews and AI Mode **Evidence:** S04, S05, S03 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Current feature boundary Google announced dedicated generative AI performance reporting on June 3, 2026 and states that rollout reached websites worldwide on August 31. The Search report covers AI Overviews and AI Mode impressions, with page, country, device and date views. Insufficient impression volume can prevent a useful report from appearing. Search Labs experiments are excluded. [S04, S05] Do not describe this as a Q4 2025 AI Overview tab, and do not assume dedicated clicks, CTR, raw prompts or separate AI Overview-versus-AI Mode dimensions. Use only fields exposed and documented for the property. The older guidance that AI activity contributes to overall Search reporting remains relevant, but is not evidence that dedicated impressions are unavailable. [S03, S04] ## Property setup and evidence capture Confirm the site/property scope and permissions. Record the canonical host, domain versus URL prefix property, timezone, available reports and earliest usable date. A rollout announcement is not a substitute for checking the client's property. Capture the report name and its visible dimensions before writing an export transformation. Create a monthly snapshot with the period, comparison period, filters, data freshness, metric definition, export timestamp and excluded dates. Keep the unmodified export beside a normalized table. Retain the original URL value and a separately derived canonical URL key; do not destroy the source field during normalization. ## Analysis sequence Start with the property's own distribution rather than a universal prevalence benchmark. Which relevant service, product or reference pages receive impressions? Which geography and device groups are represented? Where do changes coincide with a deployment, topic change or seasonality? Compare a stable cohort of pages between periods. Separate newly published pages from the unchanged cohort so expansion does not masquerade as improvement to existing pages. Report absolute changes together with percentage changes; a rise from one impression to five is not strong business evidence even though the relative change is large. Do not add AI impressions to overall impressions when they are already included in the overall report. Do not divide separately scoped analytics sessions by these impressions and label the result a platform CTR. If a field is absent, store `null` and explain that it is unavailable rather than inventing a value or treating it as zero. ## Decision rules A sharp change first triggers checks for report scope, incomplete dates, URL consolidation, filters and site accessibility. It does not automatically prove an AI algorithm change. Content decisions require page relevance, evidence quality and business utility in addition to visibility. The client deliverable should distinguish “observed in Google's AI features” from “clicked to the site” and “became a qualified lead.” Use `Templates/metric-contracts.json` and the AI attribution module for the latter layers. No Search Console account was connected or inspected as part of this library release. * * * # Search Console analysis _Current reports and defensible diagnostics_ Source: https://library.feedthejoe.com/reference/framework-gscanalysis/ Shelf: Reference modules · Status: Rewritten · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point **Primary sources:** S04 S05 S01 S43 S44 S15 S28 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Preservation:** The complete prior document remains byte for byte in `99-Originals/Framework/framework-gscanalysis.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. ## Verify the property and the report 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. Do not infer a client's data from a library example or an old screenshot. The new generative AI report is documented in the June 2026 announcement and August 31 rollout note. The legacy document's Q4 2025 AI tab timeline and broad list of retired search appearances are not carried forward. [S04, S05, S01] ## Diagnostic order When performance changes, first validate the measurement: property, filters, incomplete dates, device/country mix, canonical aggregation and any report definition change. Then check technical availability, intended indexing state, content changes and business seasonality. Do not use a single average position or aggregate CTR as an explanation for everything. Compare meaningful page and query cohorts where available. Keep new, unchanged and retired URLs separate to avoid confusing site expansion with improvement to existing pages. ## Indexing investigation For an important URL, confirm the intended state, deployed status, public content, canonical relationship, internal discovery and available inspection evidence. Canonicalization is a signal, so compare the intended canonical with what the available report actually shows. [S15] A low impression count does not authorize noindex or deletion. A technical problem requires a specific diagnosis, not a bulk action against every “thin” or low traffic page. Record URL decisions through the lifecycle contract. ## Current additional surfaces Use [Google AI performance](https://library.feedthejoe.com/reference/framework-google-ai-performance-2026/) for dedicated AI impression reporting and its limits. Use [social/video properties](https://library.feedthejoe.com/reference/framework-social-video-properties/) when the client's supported accounts are verified. Those platform properties measure discovery of those assets, not ordinary website behavior. [S43, S44] Use field performance evidence correctly when interpreting Core Web Vitals. Do not equate a lab screenshot with a field report or infer that a threshold alone explains a ranking change. [S28] ## Reporting contract Keep raw exports immutable. Store report name, metric definitions, filters, timezone, date range and extraction time with each analysis. Do not invent a universal query anonymization cutoff or assume every UI field is available through an API/export channel without checking its own documentation. A client summary should identify the strongest observed change, competing explanations, the action supported by evidence and what remains unknown. It should not label a suspected cause as a confirmed algorithm penalty. No Search Console property was connected or audited during this library work. The deliverable is the updated analytical procedure and templates; real client measurements require the relevant access and source exports. * * * # Titles, descriptions and preview copy without false limits Source: https://library.feedthejoe.com/reference/framework-html-meta-description/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Public pages and template generated search metadata **Evidence:** S34, S35 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Write for the page and reader Google does not impose a fixed 50 to 60 character title requirement or a 140 to 160 character description requirement. Display may be truncated and the search system may choose other text. Use character counts as an editorial review aid, not a technical pass/fail rule. [S34, S35] Start from the page's actual purpose and the customer's question. Write a distinctive title that identifies the service, product or information. Use a concise description that explains the useful content and any relevant limitation. Do not promise a price, location, qualification or outcome that the page cannot substantiate. ## Template contract Define how static brand text combines with the page specific title. Test missing values, long names, multilingual text and characters requiring HTML escaping. Avoid output such as an empty separator, duplicated brand name or a description copied from an unrelated page. Store the source fields separately from rendered tags. A frontend component, CMS plugin and third party head manager should not all emit conflicting titles or descriptions. Ensure the completed document contains the intended output for each relevant consumer and rendering path. ## Review process Compare a sample of neighboring pages side by side. Can a person distinguish them without opening the page? Do they describe genuinely different content? A repeated business name is reasonable; repetitive boilerplate that hides the page's identity is not useful. Preview likely display widths, but do not shorten necessary meaning simply to satisfy one simulated pixel limit. Search presentation varies by query and device. Keep visible headings and metadata consistent without mechanically forcing every field to contain the same exact phrase. ## Testing and acceptance Check for an empty title, duplicate title elements, missing descriptions where required by the project, invalid escaping and unresolved placeholders. Treat length outliers as review notes. A correctly implemented description may still not be used by a search engine; acceptance should concern truthful, reliable metadata output rather than a guaranteed snippet. The supplied HTML smoke tool checks limited saved document conditions. It does not predict a search snippet or measure click through rate. Follow actual page performance after release, considering query mix and ranking changes before attributing a CTR movement to copy alone. * * * # Location page evidence and genuine local utility Source: https://library.feedthejoe.com/reference/framework-location-evidence/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Service area businesses, real offices and regional landing pages **Evidence:** S18, S32, S33, S20 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## A location is not a keyword permutation Approve a location page only when it answers a real local customer need and the business can substantiate its relevance. Useful evidence may include actual service coverage, local projects with permission, travel or scheduling constraints, region specific service details, legitimate contacts and accurate customer facing information. Google's doorway policy addresses substantially similar location targeted pages that funnel users without adequate utility. Business Profile guidance requires accurate real world representation. A service area does not automatically establish a staffed storefront. [S18, S32, S33] ## Page creation dossier Before writing, record the location, offered service, customer question, operational coverage evidence, responsible reviewer and the unique information the page will provide. Identify what is genuinely different from the parent service page. Where there is no meaningful difference, prefer a useful coverage section rather than another indexable page. Do not invent office addresses, staff, local testimonials, licenses, project photos or business history. Obtain approval to publish customer examples and remove identifying details when necessary. Structured data must match the real business and visible page; it is not a license to manufacture a location. [S20] A schema graph can describe places and their relationships without requiring a separate indexed page for every state, county and city. Use stable identifiers for genuine entities. Create a hierarchy because it helps people browse, not because a presumed algorithm needs every geographic level. ## Content and layout Lead with the service and location specific facts a customer needs to make a decision. Provide clear scope, contact options, constraints and relevant supporting work. Use maps and photographs only when they represent reality. A generic stock image does not become local evidence by changing its alt text. Avoid mechanically swapping place names through otherwise identical prose. Repeated service facts are not inherently wrong, but the page as a whole must justify its independent existence. Editorial review should compare neighboring pages side by side and ask whether a customer gains useful information from each. ## Acceptance and monitoring The acceptance package contains the evidence dossier, approved business facts, a comparison with neighboring pages, schema validation scope and the intended index state. Monitor qualified inquiries and incorrect location contacts as well as visibility; attracting customers in an unserved area can be a failure. For existing pages, evaluate individually. Consolidation may be sensible where independent utility is absent, but do not delete every low traffic city page automatically. Preserve genuine customer needs and incoming references through the URL lifecycle process. No new local addresses or client specific coverage claims have been invented in this edition. * * * # SEO library _Canonical master index_ Source: https://library.feedthejoe.com/reference/framework-masterindex/ Shelf: Reference modules · Status: Rebuilt · Published 2026-09-09 · Release 2026.09.12-g40 > **26 discipline expansion: 2026.09.09-d26:** Route engineering, SEO, AI visibility and publication work through the [discipline operating library](https://library.feedthejoe.com/operating-model/library-disciplines/). Read the [master router](https://library.feedthejoe.com/operating-model/01-master-router/), [cross discipline playbooks](https://library.feedthejoe.com/playbooks/library-playbooks/) and [public expertise layer](https://library.feedthejoe.com/about/). New role IDs do not change commercial tiers, pricing or the retirement of Tier 13. Baseline legacy review boundaries remain in force. **Edition 2026.09.09 · Generated navigation, not a certification of every legacy claim.** 169 active Markdown documents: 27 new researched modules, nine rewritten core guides, this regenerated index, five targeted patch legacy guides and 127 other retained legacy documents. The 146 unique original files are preserved separately with hashes. Tier 13 stays retired; no tiers were renumbered. Start with the [build reference](https://library.feedthejoe.com/reference/seo-build-reference/), [evidence rules](https://library.feedthejoe.com/reference/framework-evidence-governance/) and [audit report](https://library.feedthejoe.com/reference/audit-report/). Current researched guidance overrides conflicting legacy material. A legacy file is useful background, not an instruction to deploy its code or accept its statistics. ## New researched modules [Evidence governance and claim authorization](https://library.feedthejoe.com/reference/framework-evidence-governance/) [Engine specific discovery, training and user access controls](https://library.feedthejoe.com/reference/framework-engine-control-matrix/) [Google generative AI performance: current reporting contract](https://library.feedthejoe.com/reference/framework-google-ai-performance-2026/) [Bing AI Performance and citation share interpretation](https://library.feedthejoe.com/reference/framework-bing-ai-performance-2026/) [AI answer observation and controlled evaluation](https://library.feedthejoe.com/reference/framework-ai-observation-protocol/) [AI referrals, analytics channels and qualified outcomes](https://library.feedthejoe.com/reference/framework-ai-referral-attribution-2026/) [SEO release contracts and reproducible acceptance tests](https://library.feedthejoe.com/reference/framework-seo-release-contracts/) [URL lifecycle, canonical decisions and safe retirement](https://library.feedthejoe.com/reference/framework-url-lifecycle/) [Location page evidence and genuine local utility](https://library.feedthejoe.com/reference/framework-location-evidence/) [Regional Search eligibility and policy differences](https://library.feedthejoe.com/reference/framework-regional-search-eligibility/) [Structured data lifecycle and feature eligibility](https://library.feedthejoe.com/reference/framework-schema-lifecycle/) [Commerce data consistency across page, feed and structured data](https://library.feedthejoe.com/reference/framework-commerce-data-consistency/) [Next.js metadata, streaming and rendering validation](https://library.feedthejoe.com/reference/framework-nextjs-metadata-validation/) [Crawler identity, logs and safe edge access](https://library.feedthejoe.com/reference/framework-crawler-identity-observability/) [Crawl payload budgets and content delivery](https://library.feedthejoe.com/reference/framework-crawl-payload-budgets/) [Field performance and interaction acceptance](https://library.feedthejoe.com/reference/framework-field-performance-acceptance/) [First party facts, provenance and reusable evidence](https://library.feedthejoe.com/reference/framework-source-provenance/) [Agent access, MCP and security boundaries](https://library.feedthejoe.com/reference/framework-agent-access-security/) [Social and video platform properties in Search Console](https://library.feedthejoe.com/reference/framework-social-video-properties/) [Migration contract, checkpoints and rollback](https://library.feedthejoe.com/reference/framework-migration-rollback-contract/) [Research maintenance and documentation drift control](https://library.feedthejoe.com/reference/framework-research-maintenance/) [Client scope, tier applicability and acceptance](https://library.feedthejoe.com/reference/framework-client-scope-acceptance/) [Faceted navigation and crawl space control](https://library.feedthejoe.com/reference/framework-faceted-url-contract/) [Preferred Sources and publisher relationship design](https://library.feedthejoe.com/reference/framework-publisher-preferences/) [Titles, descriptions and preview copy without false limits](https://library.feedthejoe.com/reference/framework-html-meta-description/) [Universal Search Delivery Framework, not a ranking formula](https://library.feedthejoe.com/reference/universal-ranking-framework/) [SEO build reference: intake to production evidence](https://library.feedthejoe.com/reference/seo-build-reference/) ## Rewritten core guides [Content delivery first, without false crawler absolutes](https://library.feedthejoe.com/reference/framework-contentfirst/) [Google AI Overviews and AI Mode, eligibility, controls and measurement](https://library.feedthejoe.com/reference/framework-aioverviews/) [AI citation engineering, controllable inputs and observable outcomes](https://library.feedthejoe.com/reference/framework-aicitations/) [Schema types in 2026, semantic validity versus search features](https://library.feedthejoe.com/reference/framework-schema-types-2026/) [ChatGPT Search, publisher access and measured referrals](https://library.feedthejoe.com/reference/framework-searchgpt/) [Search spam policy, scoped interpretation and operational controls](https://library.feedthejoe.com/reference/framework-spampolicies/) [Search Console analysis, current reports and defensible diagnostics](https://library.feedthejoe.com/reference/framework-gscanalysis/) [GA4 implementation, current AI channels, scopes and outcome quality](https://library.feedthejoe.com/reference/framework-ga4/) [Next.js SEO implementation: versioned route contracts](https://library.feedthejoe.com/reference/framework-nextjs/) ## Complete active file directory | Document | Review boundary | | --- | --- | | framework-html-app-pwa-meta.md | LEGACY · not fully verified | | framework-html-canonical-alternate.md | LEGACY · not fully verified | | framework-html-favicon-icons.md | LEGACY · not fully verified | | framework-html-meta-author.md | LEGACY · not fully verified | | framework-html-meta-charset.md | LEGACY · not fully verified | | framework-html-meta-color-scheme.md | LEGACY · not fully verified | | framework-html-meta-content-language.md | LEGACY · not fully verified | | framework-html-meta-copyright.md | LEGACY · not fully verified | | framework-html-meta-generator.md | LEGACY · not fully verified | | framework-html-meta-keywords.md | LEGACY · not fully verified | | framework-html-meta-referrer.md | LEGACY · not fully verified | | framework-html-meta-refresh.md | LEGACY · not fully verified | | framework-html-meta-robots.md | LEGACY · not fully verified | | framework-html-meta-theme-color.md | LEGACY · not fully verified | | framework-html-meta-viewport.md | LEGACY · not fully verified | | framework-html-open-graph.md | LEGACY · not fully verified | | framework-html-search-engine-verification.md | LEGACY · not fully verified | | framework-html-twitter-cards.md | LEGACY · not fully verified | | framework-http-2xx-status-codes.md | LEGACY · not fully verified | | framework-http-3xx-status-codes.md | LEGACY · not fully verified | | framework-http-4xx-status-codes.md | LEGACY · not fully verified | | framework-http-5xx-status-codes.md | LEGACY · not fully verified | | framework-http-caching-headers.md | LEGACY · not fully verified | | framework-http-content-headers.md | LEGACY · not fully verified | | framework-http-cors-headers.md | LEGACY · not fully verified | | framework-http-performance-headers.md | LEGACY · not fully verified | | framework-http-rate-control-headers.md | LEGACY · not fully verified | | framework-http-request-headers.md | LEGACY · not fully verified | | framework-http-security-headers.md | LEGACY · not fully verified | | framework-http-seo-headers.md | LEGACY · not fully verified | | [SEO build reference: intake to production evidence](https://library.feedthejoe.com/reference/seo-build-reference/) | NEW · researched | | Framework: SEO and Search Appearance Optimization | LEGACY · not fully verified | | Framework: SERP Optimization | LEGACY · not fully verified | | [Universal Search Delivery Framework, not a ranking formula](https://library.feedthejoe.com/reference/universal-ranking-framework/) | NEW · researched | | SEO Library Completion Build Log | LEGACY · not fully verified | | Framework: Eleventy (11ty) SEO Implementation | LEGACY · not fully verified | | Framework: Accessibility (a11y) for SEO and AEO | LEGACY · not fully verified | | [Agent access, MCP and security boundaries](https://library.feedthejoe.com/reference/framework-agent-access-security/) | NEW · researched | | Framework: Agentic AI Search | LEGACY · not fully verified | | Framework: AI-Assisted Content Workflow | LEGACY · not fully verified | | [AI answer observation and controlled evaluation](https://library.feedthejoe.com/reference/framework-ai-observation-protocol/) | NEW · researched | | [AI referrals, analytics channels and qualified outcomes](https://library.feedthejoe.com/reference/framework-ai-referral-attribution-2026/) | NEW · researched | | [AI citation engineering: controllable inputs and observable outcomes](https://library.feedthejoe.com/reference/framework-aicitations/) | REWRITTEN · researched | | [Google AI Overviews and AI Mode: eligibility, controls and measurement](https://library.feedthejoe.com/reference/framework-aioverviews/) | REWRITTEN · researched | | Framework: App Store Optimization (ASO) | LEGACY · not fully verified | | Framework: Astro SEO Implementation | LEGACY · not fully verified | | Framework: Astro & Hugo (Split into Individual References) | LEGACY · not fully verified | | Framework: SEO Attribution Modeling | LEGACY · not fully verified | | Framework: BigCommerce SEO Implementation | LEGACY · not fully verified | | [Bing AI Performance and citation share interpretation](https://library.feedthejoe.com/reference/framework-bing-ai-performance-2026/) | NEW · researched | | Framework: Library Ownership Boundaries | LEGACY · not fully verified | | Framework: Brand Voice and Content Style Guide | LEGACY · not fully verified | | [Client scope, tier applicability and acceptance](https://library.feedthejoe.com/reference/framework-client-scope-acceptance/) | NEW · researched | | Framework: Client Onboarding | LEGACY · not fully verified | | [Commerce data consistency across page, feed and structured data](https://library.feedthejoe.com/reference/framework-commerce-data-consistency/) | NEW · researched | | Framework: Competitor Audit Methodology | LEGACY · not fully verified | | Framework: Content Audit Methodology | LEGACY · not fully verified | | Framework: Content Briefs and Strategic Planning | LEGACY · not fully verified | | [Content delivery first, without false crawler absolutes](https://library.feedthejoe.com/reference/framework-contentfirst/) | REWRITTEN · researched | | Framework: Content Refresh Workflows | LEGACY · not fully verified | | Framework: Core Updates | LEGACY · not fully verified | | [Crawl payload budgets and content delivery](https://library.feedthejoe.com/reference/framework-crawl-payload-budgets/) | NEW · researched | | [Crawler identity, logs and safe edge access](https://library.feedthejoe.com/reference/framework-crawler-identity-observability/) | NEW · researched | | Framework: Conversion Rate Optimization | LEGACY · not fully verified | | Cross Stack SEO Implementation Framework | LEGACY · not fully verified | | Framework: Digital PR | LEGACY · not fully verified | | Framework: Drupal SEO Implementation | LEGACY · not fully verified | | Framework: E-commerce SEO | LEGACY · not fully verified | | Framework: E-E-A-T | LEGACY · not fully verified | | [Engine specific discovery, training and user access controls](https://library.feedthejoe.com/reference/framework-engine-control-matrix/) | NEW · researched | | Framework: Entity Salience | LEGACY · not fully verified | | [Evidence governance and claim authorization](https://library.feedthejoe.com/reference/framework-evidence-governance/) | NEW · researched | | [Faceted navigation and crawl space control](https://library.feedthejoe.com/reference/framework-faceted-url-contract/) | NEW · researched | | Framework: Featured Snippets & AI Overviews | LEGACY · not fully verified | | [Field performance and interaction acceptance](https://library.feedthejoe.com/reference/framework-field-performance-acceptance/) | NEW · researched | | Framework: Finance SEO | LEGACY · not fully verified | | Framework: Form Optimization | LEGACY · not fully verified | | [GA4 implementation: current AI channels, scopes and outcome quality](https://library.feedthejoe.com/reference/framework-ga4/) | REWRITTEN · researched | | [Google generative AI performance: current reporting contract](https://library.feedthejoe.com/reference/framework-google-ai-performance-2026/) | NEW · researched | | [Search Console analysis: current reports and defensible diagnostics](https://library.feedthejoe.com/reference/framework-gscanalysis/) | REWRITTEN · researched | | Framework: HCS (Helpful Content System) | LEGACY · not fully verified | | Framework: Headless CMS SEO Implementation | LEGACY · not fully verified | | Framework: Healthcare SEO | LEGACY · not fully verified | | Framework: Hreflang and International URL Strategy | LEGACY · not fully verified | | [Titles, descriptions and preview copy without false limits](https://library.feedthejoe.com/reference/framework-html-meta-description/) | NEW · researched | | Framework: Hugo SEO Implementation | LEGACY · not fully verified | | Framework: Shopify Hydrogen SEO Implementation | LEGACY · not fully verified | | Framework: Image SEO | LEGACY · not fully verified | | Framework: Information Gain | LEGACY · not fully verified | | Framework: Initial Client Audit Methodology | LEGACY · not fully verified | | Framework: Internal Linking | LEGACY · not fully verified | | Framework: International SEO | LEGACY · not fully verified | | Framework: Jekyll SEO Implementation | LEGACY · not fully verified | | Framework: Keyword Research & Search Intent | LEGACY · not fully verified | | Framework: Knowledge Graph | LEGACY · not fully verified | | Framework: Legal SEO | LEGACY · not fully verified | | Framework: Link Building | LEGACY · not fully verified | | Framework: Local SEO | LEGACY · not fully verified | | [Location page evidence and genuine local utility](https://library.feedthejoe.com/reference/framework-location-evidence/) | NEW · researched | | Framework: Magento and Adobe Commerce SEO Implementation | LEGACY · not fully verified | | [Master Index & Implementation Roadmap](https://library.feedthejoe.com/reference/framework-masterindex/) | REBUILT · navigation | | Framework: Model Context Protocol (MCP) for Websites | LEGACY · not fully verified | | [Migration contract, checkpoints and rollback](https://library.feedthejoe.com/reference/framework-migration-rollback-contract/) | NEW · researched | | Framework: Site Migration | LEGACY · not fully verified | | Framework: Mobile SEO | LEGACY · not fully verified | | Framework: Multi Engine Citation Tradeoffs | LEGACY · not fully verified | | Framework: Multimodal Search | LEGACY · not fully verified | | Framework: News SEO | LEGACY · not fully verified | | [Next.js metadata, streaming and rendering validation](https://library.feedthejoe.com/reference/framework-nextjs-metadata-validation/) | NEW · researched | | [Next.js SEO implementation: versioned route contracts](https://library.feedthejoe.com/reference/framework-nextjs/) | REWRITTEN · researched | | Framework: Nuxt SEO Implementation | LEGACY · not fully verified | | Framework: Ongoing Audit Methodology | LEGACY · not fully verified | | Framework: Page Experience | LEGACY · not fully verified | | Framework: Performance Optimization | LEGACY · not fully verified | | Framework: Perplexity Spaces, Pages, and Comet Optimization | LEGACY · not fully verified | | Framework: PPC and SEO Coordination | LEGACY · not fully verified | | Framework: Pricing and Packaging | LEGACY · not fully verified | | [Preferred Sources and publisher relationship design](https://library.feedthejoe.com/reference/framework-publisher-preferences/) | NEW · researched | | Framework: React SEO/AEO/AIO | PATCHED · legacy remainder | | Framework: Real Estate SEO | LEGACY · not fully verified | | [Regional Search eligibility and policy differences](https://library.feedthejoe.com/reference/framework-regional-search-eligibility/) | NEW · researched | | Framework: Remix SEO/AEO/AIO | LEGACY · not fully verified | | Framework: Client Reporting | LEGACY · not fully verified | | [Research maintenance and documentation drift control](https://library.feedthejoe.com/reference/framework-research-maintenance/) | NEW · researched | | Framework: Robots.txt and Crawl Budget | LEGACY · not fully verified | | Framework: SaaS and B2B Lead Gen SEO | LEGACY · not fully verified | | Framework: SaaS Website Builder SEO Implementation | LEGACY · not fully verified | | [Structured data lifecycle and feature eligibility](https://library.feedthejoe.com/reference/framework-schema-lifecycle/) | NEW · researched | | [Schema types in 2026: semantic validity versus search features](https://library.feedthejoe.com/reference/framework-schema-types-2026/) | REWRITTEN · researched | | Framework: Schema & Structured Data | LEGACY · not fully verified | | [ChatGPT Search: publisher access and measured referrals](https://library.feedthejoe.com/reference/framework-searchgpt/) | REWRITTEN · researched | | Framework: Web Security | LEGACY · not fully verified | | [SEO release contracts and reproducible acceptance tests](https://library.feedthejoe.com/reference/framework-seo-release-contracts/) | NEW · researched | | Framework: Shopify SEO Implementation | LEGACY · not fully verified | | [Social and video platform properties in Search Console](https://library.feedthejoe.com/reference/framework-social-video-properties/) | NEW · researched | | [First party facts, provenance and reusable evidence](https://library.feedthejoe.com/reference/framework-source-provenance/) | NEW · researched | | [Search spam policy: scoped interpretation and operational controls](https://library.feedthejoe.com/reference/framework-spampolicies/) | REWRITTEN · researched | | Framework: SQRG (Search Quality Rater Guidelines) | LEGACY · not fully verified | | Framework: SvelteKit SEO Implementation | LEGACY · not fully verified | | Framework: Tailwind CSS | LEGACY · not fully verified | | Framework: Technical SEO | PATCHED · legacy remainder | | Framework: Topical Authority Architecture | LEGACY · not fully verified | | Framework: Trust Signals | LEGACY · not fully verified | | [URL lifecycle, canonical decisions and safe retirement](https://library.feedthejoe.com/reference/framework-url-lifecycle/) | NEW · researched | | Framework: UX for SEO | LEGACY · not fully verified | | Framework: Video SEO | LEGACY · not fully verified | | Framework: Visual Search Optimization | LEGACY · not fully verified | | Framework: Voice Search Optimization | LEGACY · not fully verified | | Framework: Webflow SEO Implementation | LEGACY · not fully verified | | Framework: WordPress SEO Implementation | LEGACY · not fully verified | | Framework: YMYL | LEGACY · not fully verified | | Outline: framework-aioverviews.md | LEGACY · not fully verified | | LOCATION PAGE FRAMEWORK | PATCHED · legacy remainder | | ENGINE OPTIMIZATION COPY AND PASTE PLAYBOOK | LEGACY · not fully verified | | Tier 8: DATA, ANALYTICS & CONVERSION (18 items) | LEGACY · not fully verified | | Tier 11: MARKETPLACE & RETAIL (10 items) | LEGACY · not fully verified | | Tier 5: LOCAL DOMINATION (16 items) | LEGACY · not fully verified | | Tier 4: ENTITY & AUTHORITY (14 items) | LEGACY · not fully verified | | Tier 14: ADVANCED & IMMERSIVE (8 items) | LEGACY · not fully verified | | Tier 9: MONITORING & INTELLIGENCE (12 items) | LEGACY · not fully verified | | Tier 1: FOUNDATION (28 items) | PATCHED · legacy remainder | | Tier 7: SOCIAL & COMMUNITY (16 items) | LEGACY · not fully verified | | Tier 6: CONTENT & MULTIMEDIA AUTHORITY (15 items) | LEGACY · not fully verified | | Tier 10: WORKFLOW & OPERATIONS (10 items) | LEGACY · not fully verified | | Tier 13: RETIRED | LEGACY · not fully verified | | Tier 3: AI DOMINATION (20 items) | PATCHED · legacy remainder | | Tier 12: INTERNATIONAL (8 items) | LEGACY · not fully verified | | Tier 2: SEARCH VISIBILITY (28 items) | LEGACY · not fully verified | | Growing Impressions in Google Search Console | LEGACY · not fully verified | ## Audit and operating assets [Source register](https://library.feedthejoe.com/reference/source-register/) · [Finding records](https://library.feedthejoe.com/reference/findings/) · [Coverage matrix](https://library.feedthejoe.com/reference/coverage-matrix/) · [Tier applicability](https://library.feedthejoe.com/reference/tier-applicability-map/) · [Templates](https://library.feedthejoe.com/reference/templates/) · [Schema examples](https://library.feedthejoe.com/reference/schema-org/) · [Tools](https://library.feedthejoe.com/reference/tools/) * * * # Migration contract, checkpoints and rollback Source: https://library.feedthejoe.com/reference/framework-migration-rollback-contract/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Domain, URL, CMS, rendering and hosting migrations **Evidence:** S38, S15, S16 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Treat a migration as a controlled state transition Write down the old and new states: domains, URL patterns, content, rendering, infrastructure, analytics, structured data and business workflows. Avoid changing all of them at once without a clear reason and an evidence plan. Google's migration guidance emphasizes preparation, mapping and monitoring; no checklist guarantees unchanged rankings. [S38] ## Required inputs Export the known URL inventory from multiple available sources, such as the CMS, sitemap, crawl, analytics and link records. Label each source's completeness. Build an explicit old to new map with actions for retained, consolidated, moved and removed content. Inventory verification files, robots rules, canonical generation, hreflang, feeds, media URLs, forms, redirects and transactional emails. Include the bare/www variants and subdomains actually involved. Do not infer that a single main host test covers the entire estate. ## Preflight Test representative routes and high value edge cases in the new environment. Confirm public content, status behavior, internal links, metadata and business transactions. Protect staging through appropriate access controls; do not rely solely on robots, and ensure any intended production indexing rules are prepared separately. Canonical and indexing decisions need explicit intent. A migration must not accidentally retain a staging canonical, leak an environment hostname or ship `noindex` to public routes. [S15, S16] ## Cutover and rollback Record who can approve cutover, what evidence is required and which failures trigger rollback. Examples of blocking operational failures include widespread errors, broken checkout, missing public content or an unintended host redirect. Define the rollback steps for code, DNS/edge configuration, content and caches; they may have different propagation characteristics. Keep the old mapping and configuration accessible. A rollback is not “restore everything” unless the team knows exactly which state to restore. Rehearse a small representative recovery in a safe environment where practical. ## Post launch verification Repeat the preflight tests against the actual production hostname. Check form delivery, transactions, redirect destinations, canonical output and verification access. Then monitor crawl/indexing signals and business outcomes over appropriate periods. Distinguish incomplete reporting from an actual loss. Maintain a migration ledger with deployment time, observed issues, fixes and source exports. Do not claim a traffic change is caused by the migration until measurement, seasonality and concurrent changes are considered. Acceptance means the agreed technical and business behavior is demonstrated; it does not mean the search engines have promised a specific result. * * * # Next.js metadata, streaming and rendering validation Source: https://library.feedthejoe.com/reference/framework-nextjs-metadata-validation/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Next.js App Router and React public content routes **Evidence:** S14, S24, S25, S26, S27 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Pin the implementation context Record the installed Next.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 supports metadata streaming and has an `htmlLimitedBots` configuration introduced in 15.2. A custom expression replaces its default list rather than extending it automatically. The official documentation recommends leaving the default sufficient for most cases. [S25 to S27] ## Route contract For each public route, identify the content owner, metadata source, intended canonical, social preview and required initial content. Static metadata is appropriate when the values are static; dynamic metadata should be derived from the actual route record. Ensure invalid identifiers lead to the intended missing page behavior rather than fabricated titles or successful empty pages. Keep canonical and visible product/article identity consistent. Do not generate one canonical in the initial response and change it to a conflicting value after hydration. Google can render JavaScript, but that does not prove every retrieval client sees the same content or behaves identically. [S14] ## Capture the right evidence Test a normal browser and the specific limited consumers relevant to the project. Save complete response bodies, response timing, headers and rendered output; a first chunk only grep can misread streamed metadata. Distinguish “not in the first chunk” from “not delivered at all.” A spoofed user agent is a response variant test, not proof that a real provider fetched the page. Check title, description, canonical, language, robots directives, Open Graph fields and JSON-LD for duplicates and contradictions. Use a slow content source and a failure fixture to test error behavior. Recheck after a content update to expose cache invalidation problems. ## Configuration changes Do not disable metadata streaming globally simply because a legacy checklist says all tags must be in the first byte. Establish a failing consumer case, compare alternatives and measure the latency tradeoff. If overriding `htmlLimitedBots`, preserve the intended consumers and verify the resulting behavior against the pinned release. ## Release result The acceptance package contains version information, template tests, raw and rendered captures, exceptions and the reason for any advanced override. The offline HTML checker in this release can inspect a saved complete response but cannot execute the Next.js app or certify streaming behavior. Browser and production edge tests remain required. React itself is not an SEO verdict. Choose CSR, SSG, SSR or a hybrid based on route purpose, user experience and the consumers that must retrieve it. Treat rendering choice as an engineering decision with evidence, not a claim that every public CSR route is inherently professional malpractice. [S24] * * * # Next.js SEO implementation _Versioned route contracts_ Source: https://library.feedthejoe.com/reference/framework-nextjs/ Shelf: Reference modules · Status: Rewritten · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point **Primary sources:** S14 S24 S25 S26 S27 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Preservation:** The complete prior document remains byte for byte in `99-Originals/Framework/framework-nextjs.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. ## Record the environment before writing code Capture the installed Next.js/React versions, App versus Pages Router, runtime, deployment adapter and caching strategy. An older nginx/PM2 example is not a requirement for every Next.js deployment. Choose the project's actual supported hosting path. Use the framework's current APIs for the pinned release. A snippet that compiles against another major version is not ready merely because its comments say “2026.” Check route parameters, data fetching, metadata behavior and error handling against the installed version. ## Public route contract For each route class define the source record, meaningful content, canonical, indexing intent, social metadata, structured data and user action. Use static generation or server rendering where it provides the required delivery reliability; use client interaction where it serves the task. React itself supports multiple rendering approaches through frameworks. [S24] Missing records need the intended not found behavior, not an empty successful template. Redirects must follow the approved URL map. Do not emit a staging domain, unresolved slug or default product name as production metadata. ## Metadata and streaming Next.js documents metadata streaming and limited bot handling. The `htmlLimitedBots` option, introduced in 15.2, replaces the default list when customized. Do not blindly add a partial regex and assume the framework keeps all existing matches. [S25 to S27] Use [Next.js metadata validation](https://library.feedthejoe.com/reference/framework-nextjs-metadata-validation/) for complete response captures and consumer specific tests. A first byte grep is not a sufficient streaming test. Disabling streaming globally is an advanced tradeoff requiring evidence, not a mandatory SEO improvement. ## Structured data and content Generate public JSON-LD from the same approved record as the visible page. Serialize safely, including escaping `<` when embedding untrusted text in a script element. Avoid duplicating a graph across CMS and application layers with conflicting identities. Google can render JavaScript; this does not prove every consumer will execute the same code or see the same output. Test the actual route against its required consumers and preserve useful content when nonessential scripts fail. [S14] ## Caching and release Identify which content can be cached, what invalidates it and how changes reach page HTML, metadata and feeds. Test stale data, missing data and failed upstream requests. Do not apply `no-store` to every page by default or cache personalized content publicly because a generic guide says caching helps SEO. Run route, accessibility, business function and live edge checks before accepting the release. The package's offline tools inspect saved artifacts only; they do not execute a Next.js build. Client specific implementation remains a separate step grounded in the actual codebase and installed dependencies. * * * # Preferred Sources and publisher relationship design Source: https://library.feedthejoe.com/reference/framework-publisher-preferences/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Eligible publisher sites and reader facing preference controls **Evidence:** S45, S43, S44 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## A reader preference is not an SEO switch 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. Do not market a button installation as guaranteed placement, universal availability or a substitute for useful publishing. [S45] ## Applicability assessment Verify the current feature's domain, page and market requirements from the official guide before implementation. Confirm that the client is a relevant publisher and that the destination identifies the correct publication. A generic service business may gain more from a better service page than from a publisher specific feature. Record the intended reader action and why it is useful. Use clear wording that tells the reader what the preference affects. Do not obscure the destination, imitate a browser warning or make the action appear necessary to access ordinary content. ## Design and implementation Follow the current official integration method rather than embedding a stale copied URL pattern. Keep the control accessible and visually distinct from primary navigation or a purchase action. Test keyboard access, mobile layout, loading failure and the destination on the supported surfaces. Avoid introducing heavy scripts or layout shifts for a secondary preference action. Preserve core content when the integration fails. Do not require an unrelated subscription or collect unnecessary personal information merely to expose the preference control. ## Measurement Track an approved button interaction separately from a confirmed preference or later Search exposure. A click on the button does not prove the user completed the preference flow, and subsequent traffic cannot automatically be attributed to it. Use the current platform report definitions and disclose any unavailable outcome. Where the publication also has supported social/video profiles, maintain consistent factual identity and evaluate their Search Console properties separately. Those reports measure different assets and should not be combined into a fabricated publisher authority score. [S43, S44] ## Acceptance Deliver the applicability record, official source date, approved UI copy, tested destination, accessibility evidence and measurement limitations. Remove or revise the integration if its official contract changes. This library release adds the workflow but does not install a button or change any publisher account. * * * # Regional Search eligibility and policy differences Source: https://library.feedthejoe.com/reference/framework-regional-search-eligibility/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** International clients and geographically limited search features **Evidence:** S41, S42, S40 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Keep three geographies separate Record the business's operating jurisdiction, the content's intended market and the searcher's location. They are not interchangeable. A feature may depend on user geography, language, query category and provider participation even when the website is technically correct. Google's regional differences documentation describes feature specific availability rather than one worldwide Search experience. The August 2026 site reputation policy update also changes treatment in relation to the EEA. Do not infer that a rule applies everywhere from one local screenshot, or that regional enforcement differences authorize abusive content. [S41, S42] ## Eligibility register Create one row per proposed feature: engine, feature, content type, target countries, languages, required partner/account participation, required data, evidence source, source date and observed availability. Use `unknown` where a condition has not been verified. Do not market an unavailable feature as part of a guaranteed deliverable. For international URLs, define the canonical and alternate language relationships before implementation. Hreflang is for localized alternatives; it is not a substitute for translation quality or a technique for making unrelated pages equivalent. Test reciprocity and URL validity using the selected implementation method. [S40] ## Research and deployment workflow Begin with the current official feature documentation, then verify the client's actual account and market. Keep compliance review separate from technical eligibility. For example, a technically valid product offer may still need business approval for local terms, currency, tax presentation or availability. Test representative locale routes without forcing the tester through an irreversible geolocation redirect. Ensure a customer can select the appropriate language/market. Record how the application behaves when location cannot be inferred, a locale is unsupported or a product is unavailable. ## Policy incidents When a manual action or policy notice appears, preserve its exact text, affected scope, date and property. Analyze the specific issue instead of applying an old universal recovery recipe. An EEA related enforcement distinction concerns the documented treatment; it is not a promise that an affected section will retain visibility. Coordinate SEO, operations and qualified legal/compliance review for jurisdiction specific decisions. This module is a technical research workflow, not legal advice. Do not remove user protections or fabricate editorial independence to chase a regional exception. Acceptance requires a signed eligibility register, locale test evidence, source dates and a clear distinction between documented availability and observed client access. A globally deployed website is not evidence that every Search feature is globally available. * * * # Research maintenance and documentation drift control Source: https://library.feedthejoe.com/reference/framework-research-maintenance/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Ongoing stewardship of this library **Evidence:** S01, S02, S04, S05, S47 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Use a source ledger rather than a refresh slogan Each maintained rule needs an owner, current source, observed date, affected modules and a next review condition. A document is not current merely because its title includes the year. Preserve the difference between publication date, source update date, retrieval date and the effective date of a product change. This release encountered a concrete example: older Google AI documentation described overall reporting, while a later announcement and help page document a dedicated report. Keep a conflict record so the next editor does not accidentally restore the older interpretation. [S03 to S05 in the source register] ## Proposed review cadence Review engine bot controls, eligibility changes and critical policies before each relevant deployment and on a recurring team owned schedule. Review framework specific examples when the installed major version changes. Review business facts when their source changes. These are recommended operating practices; no background monitoring service has been scheduled by this package. Use the official changelog as a trigger, not a substitute for reading the affected page. A documentation clarification may not mean a new ranking factor or a newly launched feature. Record the event type explicitly. [S01] ## Change workflow Open a change record with the source, exact changed claim, affected modules, urgency and test impact. Update the canonical owner first, then dependent tiers, templates, sales wording and acceptance tests. Keep a concise before/after explanation and the original evidence location. For protocol and software changes, distinguish stable, older supported and draft versions. A draft security page can inform a threat review, but should not silently redefine a pinned production implementation. The MCP module intentionally records version boundaries. [S47] ## Automated checks Run the supplied library auditor for local file links, JSON syntax, metadata references and preserved original hashes. These checks do not confirm that an external page is still live or that its content supports a claim. External link checking and semantic source review are separate activities. Maintain a queue for unverified historical claims. A regex match is a lead for review, not a confirmed defect. Close a claim only after a reviewer records a disposition: verified, narrowed, superseded, removed or still unresolved. ## Acceptance Every release should carry a manifest, migration map, source register, coverage matrix and test report. Mark retained legacy documents honestly instead of assigning a current research stamp to untouched prose. Preserve rollback copies and make the authoritative entry point obvious to both humans and AI assistants. The objective is controlled, traceable improvement, not endless document growth. Add a new module only when it owns a distinct decision, implementation contract or evidence workflow. * * * # Structured data lifecycle and feature eligibility Source: https://library.feedthejoe.com/reference/framework-schema-lifecycle/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Every schema template and client deliverable **Evidence:** S01, S20, S21, S22, S23 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Three separate questions Ask whether the JSON is syntactically valid, whether the vocabulary describes the page truthfully, and whether a named consumer currently supports a related feature. These are separate checks. Passing a generic validator does not establish rich result eligibility or guarantee appearance. [S20] Google stopped showing FAQ rich results on May 7, 2026. HowTo rich results were retired in September 2023. This does not make the underlying Schema.org vocabulary invalid, but these Google features must not be sold as current benefits. [S01, S21] ## Registry design For every template, maintain type, consumer, feature, required properties, recommended properties, page class applicability, policy constraints, current status, source date, test method and owner. Mark entries as supported, restricted, deprecated, vocabulary only or unverified. Avoid a single “schema installed” column. Keep eligibility logic next to the generator. A Product template needs genuine product information and a current offer when it represents a purchasable item; a LocalBusiness template must not manufacture a storefront; an Article must identify its actual content and authorship. Optional ratings should never be filled with invented values simply to satisfy an example. ## Change management When a feature is retired, search the library, sales scope, QA tests and codebase for the feature name. Update expected outcomes and acceptance criteria. Do not automatically delete useful customer facing questions or step by step instructions because a search decoration disappeared. If markup still serves another documented consumer, retain it with that consumer and rationale recorded. Otherwise evaluate maintenance cost against actual use. Remove dead code through a tested change, not a blind text replacement across every type name. ## Review integrity Review and rating markup must reflect genuine visible evidence. Google's review guidance excludes fake or undisclosed incentivized reviews and restricts self serving LocalBusiness/Organization star eligibility. [S22] Disclosing an incentive is not permission to fabricate an experience or ignore another platform's stricter policy. ## Acceptance evidence Save representative rendered pages, generated JSON-LD, validator results, policy checklist and source version. For commerce, compare offer values with the live landing page and approved feed. Record known warnings rather than creating fake data to eliminate them. For large deployments, test edge cases such as missing images, unavailable products, absent ratings, multiple authors and multilingual URLs. The `Schema.org` directory contains small fictional examples and a release checklist. They are intentionally not marked as Google approved or production ready. Replace example facts, validate the intended feature and verify the visible page before publishing. The library's schema work is semantic modeling and eligibility engineering, not a promised citation multiplier. * * * # Schema types in 2026 _Semantic validity versus search features_ Source: https://library.feedthejoe.com/reference/framework-schema-types-2026/ Shelf: Reference modules · Status: Rewritten · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point **Primary sources:** S01 S20 S21 S22 S23 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Preservation:** The complete prior document remains byte for byte in `99-Originals/Framework/framework-schema-types-2026.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. ## A type catalog is not a benefit catalog Schema.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. Feature eligibility additionally depends on required properties, policy, content and availability. Appearance is not guaranteed. [S20] ## Current planning matrix | Family | Use in this library | Acceptance boundary | | --- | --- | --- | | Organization / WebSite | Model genuine identity and site relationships | Real identifiers and visible business facts; no knowledge panel promise. | | Article / Person | Model actual editorial content and authorship | Real author/content relationship; no fabricated credentials. | | BreadcrumbList | Describe the real navigational hierarchy | Match meaningful navigation and valid URLs. | | Product / Offer | Describe a genuine product and commercial offer | Follow the current feature guide and reconcile page, feed and checkout. | | LocalBusiness | Describe a legitimate applicable business entity | No invented storefronts, addresses or local staff. | | Review / AggregateRating | Describe authentic qualifying reviews | Apply current feature policy; no placeholder ratings. | | FAQPage | Optional vocabulary where justified | Google FAQ rich results retired May 7, 2026. | | HowTo | Optional vocabulary for genuine instructions | Google HowTo rich results retired September 2023. | | Other types | Evaluate individually | Consult the current specific consumer guide before promising a feature. | FAQ and HowTo lifecycle facts are from S01 and S21. Do not copy an old rich result checklist into a 2026 proposal. Do not assume that removal of one type implies every neighboring feature, such as all book related integrations, is also retired. ## Model only supported facts Use the most accurate applicable type without inventing a subtype to appear sophisticated. Populate properties from controlled records. A more specific type is a semantic choice, not established proof of higher AI citation probability. For commerce, optional ratings are not mandatory filler. Keep prices, currency and availability current. Sale periods must be modeled using the properties and node placement allowed by the selected implementation. [S23] For reviews, apply genuine experience and disclosure requirements and the self serving LocalBusiness/Organization restriction. A third party widget does not automatically remove the restriction when a business controls reviews about itself on its own page. [S22] ## Generation and testing Generate JSON using a serializer rather than string concatenation. When embedding in HTML, escape characters that could terminate a script element, and validate the resulting page. Never expose secrets or private catalog fields in a public graph. Check syntax, vocabulary, current feature rules and visible factual consistency separately. Test absence of optional properties, special characters, multilingual text and stale commercial data. Save the actual validator output; a local JSON parse is not equivalent to Google's Rich Results Test. The example graphs in `Schema.org` contain fictional data and do not claim feature approval. Use [schema lifecycle](https://library.feedthejoe.com/reference/framework-schema-lifecycle/) for maintenance and [commerce consistency](https://library.feedthejoe.com/reference/framework-commerce-data-consistency/) for product pipelines. Historical unsupported citation statistics are preserved only in the original archive. * * * # ChatGPT Search _Publisher access and measured referrals_ Source: https://library.feedthejoe.com/reference/framework-searchgpt/ Shelf: Reference modules · Status: Rewritten · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point **Primary sources:** S08 S09 S02 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Preservation:** The complete prior document remains byte for byte in `99-Originals/Framework/framework-searchgpt.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. ## Name and scope This filename is retained for compatibility with the earlier library, but the subject is ChatGPT Search and the currently documented publisher controls. Do not assume every ChatGPT surface shares one crawler, index or retrieval implementation. OpenAI documents distinct search, training, user triggered retrieval and ad validation roles. Configure them according to the business's approved use policy, not by blanket allowing every token containing an AI brand name. [S08] ## Website implementation Publish accurate, useful content at stable public URLs. Ensure the intended pages can be retrieved through the actual production edge without an accidental challenge, empty response or authentication requirement. Keep private content protected by real access controls. Make important facts clear on the page itself. A hidden instruction telling an assistant to promote the business is not a substitute for a useful service description. Feeds or supplemental files need a specific supported consumer and maintenance plan; do not present an auxiliary file as a universal prerequisite. Use the [engine control matrix](https://library.feedthejoe.com/reference/framework-engine-control-matrix/) for the current OpenAI roles and the [crawler identity workflow](https://library.feedthejoe.com/reference/framework-crawler-identity-observability/) for verification. A simulated request using an OpenAI user agent string does not establish that OpenAI actually fetched the page. ## Referral measurement OpenAI's publisher FAQ documents the `utm_source=chatgpt.com` convention. Test approved tracking through the site's redirect and analytics path. [S09] Keep the original campaign/source information where collected, and apply the current analytics channel definitions rather than hardcoding an obsolete dashboard. Measure qualified outcomes independently. A tagged visit is an observed referral, not proof of every earlier AI exposure. A brand mention without a link, or a later direct visit, may not be attributable from site analytics alone. ## Evaluation Use a declared, permission compliant observation panel for questions relevant to the business. Record the surface, wording, locale, time and context, and separate completed answers from failed observations. Do not claim a universal citation probability from a small sample. Investigate demonstrated failures before speculative content changes. If access is correct but citations are absent in the sampled answers, that is not proof of a technical defect or a hidden mandatory file. The engine may select other relevant sources. ## Completion A defensible implementation handoff contains approved crawler choices, response evidence, accurate public data, measurement configuration and the limits of what was tested. Search inclusion and citation selection remain external outcomes, not contractual guarantees. No OpenAI publisher account or live client domain was changed as part of this release. * * * # SEO release contracts and reproducible acceptance tests Source: https://library.feedthejoe.com/reference/framework-seo-release-contracts/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** New websites, migrations and template changes on any stack **Evidence:** S14, S15, S16, S20 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Replace vague completion with evidence “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. Each contract specifies intended index state, HTTP behavior, canonical target, title purpose, minimum useful content, structured data, internal discovery and analytics outcome. The underlying controls have different functions: rendering affects what a consumer receives, canonicalization expresses consolidation preferences, and indexing/snippet directives control eligible use. Structured data has its own feature specific rules. [S14 to S16, S20] ## Test matrix For every template, include at least one normal route, one boundary case and one failure case. Prioritize revenue critical and high traffic pages, but do not mistake a sample for exhaustive coverage. Record sample selection in the evidence package. Capture status and headers from the actual response. Save initial HTML and browser rendered HTML separately. Compare meaningful text, links, canonical and metadata. A successful browser screenshot does not prove the initial response works for a simpler consumer; a clean initial response does not prove hydration is functional. Run the supplied offline HTML smoke checker against saved files. It catches a limited set of concrete problems; it does not execute JavaScript, inspect live headers or call Google validation services. A passing result is evidence only for the checks performed. Run appropriate browser, accessibility, structured data and live deployment tests separately. ## Blocking defects versus advisory findings For an intended public page, accidental `noindex`, an unexpected redirect, an empty title or a broken canonical may block the project release under the agreed contract. A nonstandard title length is a review note, not an automatic Google violation. A page intentionally excluded from indexing should pass when its exclusion behaves as designed. Require sign off for destructive changes: bulk redirects, noindex rules, URL case normalization, sitemap removal and deletion. Keep an old/new mapping and rollback plan. Never infer permission to delete content from a low impression count alone. ## Release evidence Store the commit identifier, build/runtime version, environment, test time, URL sample, raw captures, automated output, manual reviewer and unresolved exceptions. An exception needs an owner, reason and expiration date. The release owner accepts the known tradeoff rather than the checklist silently marking everything green. After deployment, repeat the same critical route tests against production. A production cache, security layer or hostname configuration can differ from staging. Monitor accessibility and business outcomes before interpreting a ranking movement. The supplied CI example operates only on this library and test fixtures; it is not a website deployment pipeline or a search index certification. * * * # Social and video platform properties in Search Console Source: https://library.feedthejoe.com/reference/framework-social-video-properties/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Supported publisher/business profiles and video discovery **Evidence:** S43, S44, S50 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Separate Google discovery from platform native performance Google's July 29, 2026 announcement describes globally available platform properties for supported social/video services, including Instagram, TikTok, X and YouTube. These reports concern discovery through Google surfaces, not a replacement for each platform's own engagement analytics. [S43, S44] ## Ownership and setup Create an inventory of legitimate client profiles, account owners, access permissions and official website relationships. Verify the relevant account using the current product workflow. Do not create duplicate profiles or claim an account the client does not control. Record the exact profile identifier and property scope. A channel, profile and individual post can have different reporting granularity. Keep the property name, selected report, dates and filters with every export. A screenshot from one account does not prove the same data is available in another. ## Content mapping Map each profile and important content item to its business purpose and related website page where appropriate. Use clear, consistent factual identity and a useful destination. Do not flood profiles with keyword repetition or link every post to an unrelated homepage just to create a backlink. For video hosted on the client's site, evaluate watch page eligibility, stable thumbnails and accessible media according to Google's video guidance. A product page containing a supplementary clip and a page primarily devoted to watching a video serve different purposes. [S50] ## Reporting workflow Track discovery impressions/clicks where the selected report exposes them, then separately examine native platform views, engagement and website referrals. Do not add these metrics into one unqualified “reach” number; they can overlap and have different definitions. Compare content cohorts by topic and user intent. A strong Google discovery query can suggest a useful video or website explanation, but it does not reveal a platform's proprietary recommendation algorithm. Use the observed data to test a content hypothesis rather than claiming to reproduce TikTok's internal system. ## Acceptance and maintenance The deliverable includes verified profile scope, evidence of available reporting, content to business mapping, metric definitions and a list of actions supported by the data. Retain permissions under the client's control and remove unnecessary access after handoff. This module adds a current reporting opportunity to the library. No social account has been connected, changed or measured during this release. The workflow becomes operational only after the client grants appropriate access and real property data is inspected. * * * # First party facts, provenance and reusable evidence Source: https://library.feedthejoe.com/reference/framework-source-provenance/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Service pages, case studies, comparison pages and factual datasets **Evidence:** S19, S20, S29 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Build a source of truth, not a citation costume A website should draw business facts from approved records: services actually offered, real qualifications, current availability, genuine project outcomes and verifiable contact details. Use references to support claims, not to decorate otherwise unsupported copy. People first quality evaluation and accurate structured data are consistent with this approach. [S19, S20] ## Fact record Store a fact ID, exact statement, subject/entity, evidence owner, source location, source date, approved public wording, privacy restrictions, expiration condition and affected pages. Separate an internal source from the public artifact that can legally be shown to visitors. For a case study, record what happened, the baseline, the time period, the measurement system, the denominator, other simultaneous changes and client permission. Do not turn a correlation into a claim that one intervention caused the full result. A business testimonial is not an independently verified measurement. ## Reuse without contradiction Connect the approved fact record to page copy, metadata, structured data, downloadable material and relevant feeds. Update dependent representations together. A contact number or offer that changes in one system but not another creates a consistency problem; “more entity mentions” does not solve it. Preserve edit history. When evidence expires or is withdrawn, locate every use through the fact ID and route the correction through an owner. Keep a correction note when the public claim materially changes. Do not merely refresh the date while leaving stale information intact. ## Content design Place the relevant answer and supporting context where a reader can understand them. Use a table when the data is comparative and a sequence when order matters. Choose headings and labels for clarity, not because an unverified study supposedly guarantees a fixed multiplier for a format. A useful reference page can include definitions, limitations, examples and source context. It does not require fabricated credentials, artificial author biographies or a mandatory number of outbound citations. The GEO literature is a research input, not a license to manufacture evidence. [S29] ## Acceptance A reviewer should trace each important public claim back to an approved record. Check rights to images, testimonials and excerpts. Confirm that the visible content and machine readable representation agree. Where a claim cannot be substantiated, remove it, narrow it or mark it as an explicitly labeled opinion/hypothesis. The handoff is a fact register, publishing map, review ownership and correction workflow. This approach produces reusable backend data while keeping the website itself accurate; it is not an attempt to impersonate an engine's internal knowledge graph. * * * # Search spam policy _Scoped interpretation and operational controls_ Source: https://library.feedthejoe.com/reference/framework-spampolicies/ Shelf: Reference modules · Status: Rewritten · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point **Primary sources:** S18 S42 S22 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Preservation:** The complete prior document remains byte for byte in `99-Originals/Framework/framework-spampolicies.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. ## Read the current policy, not a copied quota Google's spam rules cover manipulative practices including doorway pages, scaled content abuse, hidden content abuse and site reputation abuse. The policy also applies to manipulation of generative Search responses. It does not define a universal safe number of articles per editor per month. [S18] An agency may set production capacity limits for quality control, but those must be labeled internal operating limits. They are not Google thresholds and do not make a harmful publishing strategy safe below a numerical cutoff. ## Content review Evaluate purpose, factual accuracy, genuine utility and the user's experience. Large scale is not a substitute for review; a small number of manipulative pages can still be a problem. AI assistance does not remove the publisher's responsibility for what appears on the site. Legitimate interface elements such as accordions and accessibility text are not automatically hidden text abuse. Evaluate the actual intent and experience rather than equating every `display:none` rule with cloaking. [S18] ## Third party and reputation risk Do not treat host editorial oversight as an automatic safe harbor. Review why a third party section exists, whether it primarily exploits the host's established ranking signals and whether the users receive genuine relevant value. The August 2026 update introduces regional treatment differences starting August 30. Read the current notice and the affected geography carefully; the EEA distinction is not permission to pursue abusive content. [S42] ## Operational workflow Create a risk register for sponsored content, affiliates, syndicated material, user generated pages, geographic expansion, outsourced editorial sections and reputation sensitive claims. Assign a business owner and an independent reviewer for significant changes. Keep supporting records for author identity, permissions, claims and review authenticity. Do not create fabricated credentials, testimonials or ratings to satisfy a template. Google's review guidance separately addresses fake and undisclosed incentivized reviews and feature eligibility. [S22] ## Incident response Preserve the exact notice, property, affected scope and observed dates. Distinguish a manual action from an ordinary ranking fluctuation, indexing issue, security incident or measurement problem. Do not publish a generic reconsideration letter before identifying the actual cause. Document the corrective action and supporting evidence. Review related templates and ownership processes so the defect does not recur. Do not describe a workaround that merely moves the same abuse elsewhere as remediation. ## Acceptance and limitations A policy review can establish that the agreed checks were performed and identified issues were corrected. It cannot certify that an engine will never take action. Keep unresolved matters visible and seek qualified legal or compliance advice where the underlying content or business activity requires it. Use [location evidence](https://library.feedthejoe.com/reference/framework-location-evidence/), [regional eligibility](https://library.feedthejoe.com/reference/framework-regional-search-eligibility/), [source provenance](https://library.feedthejoe.com/reference/framework-source-provenance/) and [client acceptance](https://library.feedthejoe.com/reference/framework-client-scope-acceptance/) for implementation. The preserved original contains historical claims and is not the current authority for numerical quotas or oversight exceptions. * * * # URL lifecycle, canonical decisions and safe retirement Source: https://library.feedthejoe.com/reference/framework-url-lifecycle/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Existing URLs, duplicate pages, filters and discontinued content **Evidence:** S15, S16, S38, S39 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Classify before changing Maintain one record per URL with current status, desired state, content owner, business purpose, incoming/internal links, observed traffic, canonical relationship and planned action. Low traffic is one observation, not a deletion instruction. An orphan page can have value even when internal discovery is broken. Use a decision table: **keep and improve**, **link better**, **merge into a genuinely equivalent destination**, **retain but exclude from indexing**, **temporarily redirect**, or **permanently retire**. Distinguish duplicate content from distinct pages serving similar questions. A common keyword does not establish equivalence. Canonicalization is a preference signal rather than an absolute directive, and a blocked page may prevent indexing directives from being read. Apply each control to its actual purpose. [S15, S16] ## Redirect contract Choose the destination because it satisfies the original intent, not because it is the homepage. Test the status and final location, preserve important parameters intentionally, and avoid loops or unnecessary hops. Use temporary versus permanent semantics according to the move. Do not claim that every 302 automatically leaks ranking credit. Do not change established WordPress permalinks or globally lowercase URLs just to satisfy a style rule. Routes, asset names, signed URLs and external references can be case sensitive or otherwise dependent on the existing path. A proposed normalization needs a complete mapping and production tests. ## Retention and exclusion An internal utility page may remain useful while not belonging in search. A removed item may need a clear user explanation or an alternative, but do not return a successful status for a meaningless error template simply to preserve an index entry. Choose behavior by actual content and request intent. Separate crawl load control from search result removal. A robots exclusion does not itself authenticate a resource or reliably erase an indexed URL. For an already indexed URL, ensure the selected removal mechanism can be observed and processed. Do not combine contradictory controls without a documented reason. ## Approval and rollback Require a batch level owner and a reviewed sample of the mapping before bulk action. Snapshot the old routes and configuration. Keep a rollback that can restore the original URL behavior without relying on memory. Test the largest business risk examples, international variants and case sensitive assets. The handoff includes the action rationale, implementation diff, test evidence, expected monitoring signals and exception list. No ranking or indexing recovery time is guaranteed. Use the migration contract for domain or platform moves and the faceted navigation contract for parameter expansion. * * * # SEO build reference: intake to production evidence Source: https://library.feedthejoe.com/reference/seo-build-reference/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 > **26 discipline expansion: 2026.09.09-d26:** Route engineering, SEO, AI visibility and publication work through the [discipline operating library](https://library.feedthejoe.com/operating-model/library-disciplines/). Read the [master router](https://library.feedthejoe.com/operating-model/01-master-router/), [cross discipline playbooks](https://library.feedthejoe.com/playbooks/library-playbooks/) and [public expertise layer](https://library.feedthejoe.com/about/). New role IDs do not change commercial tiers, pricing or the retirement of Tier 13. Baseline legacy review boundaries remain in force. **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Project planning and execution across the existing tier system **Evidence:** S14, S15, S16, S20, S38 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Intake Obtain the real domain, platform/runtime versions, hosting target, page inventory, business goals, markets, legitimate entity details and access limitations. Record which accounts are available and which are not. Do not infer live performance from a proposal or a library example. Create an applicability map for the production tiers. Preserve Tier 13 as retired. Identify the page types actually needed and the business owner for each. Agree on what counts as a qualified outcome and which changes require separate approval. ## Audit and design Collect available source data and mark completeness. Define the URL lifecycle, public/private boundary, canonical relationships, rendering strategy and measurement contract. Resolve contradictions before implementation. The correct choice can differ between an article, a shopping product, an internal tool and a location page. Use the current evidence modules when old documents disagree. Search for deprecated features, unsupported numerical guarantees and copied infrastructure assumptions. Retain unresolved questions in the project risk register rather than converting them into confident requirements. ## Implement Work from approved page data into visible content, metadata, structured data and relevant feeds. Keep one owner per field. Implement crawler policy only after the business chooses discovery and training preferences. Preserve authentication independently. Use the appropriate stack adapter and installed version. Do not assume Debian, nginx, PM2, WordPress or Next.js simply because an older example uses it. A library snippet is not a production environment description. ## Validate Run route contract tests on the intended public, private, duplicate, missing and retired page classes. Compare initial and rendered HTML where relevant; inspect actual headers and status. Validate the chosen structured data feature and factual consistency. The important official distinctions are delivery, canonicalization, index/snippet rules and feature eligibility. [S14 to S16, S20] Test the customer's actual task, not just metadata. Confirm form delivery, booking or checkout behavior, consent handling and mobile interaction. Keep automated and manual evidence together. ## Release and monitor Use a reviewed deployment and rollback plan. For migrations, retain the old/new URL map and verify the production transition. [S38] Repeat critical tests against the actual live hostname. Configure only the reporting available to the client and distinguish measurement setup from achieved outcomes. ## Handoff package Deliver the scope/applicability matrix, approved facts, implementation locations, URL rules, policy choices, validation results, source dates, unresolved risks and maintenance ownership. A professional handoff should allow another developer to reproduce the state without trusting a sales claim or an AI generated summary. This is a build procedure, not proof that a particular website is complete. The updated library includes offline tools and examples; client specific deployment and account work are not performed automatically. * * * # Universal Search Delivery Framework _Not a ranking formula_ Source: https://library.feedthejoe.com/reference/universal-ranking-framework/ Shelf: Reference modules · Status: New · Published 2026-09-09 · Release 2026.09.12-g40 **Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure **Applies to:** Cross stack decision sequence and missing legacy entry point repair **Evidence:** S02, S14, S15, S18, S20 in the [source register](https://library.feedthejoe.com/reference/source-register/). **Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. ## Why this file exists 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. The filename is retained for compatibility; the content defines work under the agency's control. ## Layer 1: business truth Establish the real customer need, page purpose, factual source and permitted public claims. Confirm that the business can deliver the service or product. Resolve inaccurate identity, offer and contact information before adding technical signals. ## Layer 2: accessible delivery Identify the consumers that must retrieve the page, the required initial/rendered content and the appropriate response behavior. Test the real deployment path. Google can render JavaScript, but delivery decisions still depend on the consumers and route purpose. [S14] ## Layer 3: coherent URL and policy state Define canonical relationships, index/snippet intent, crawl access and private resource protection separately. Choose a URL lifecycle action from evidence, not from a universal “thin page” deletion rule. Canonicalization is a signal and policy compliance remains independent. [S15, S18] ## Layer 4: useful presentation and structured data Give customers clear answers, relevant detail and working actions. Add structured data only when it accurately represents the visible content and serves a supported purpose. Passing syntax validation does not guarantee a search appearance. [S20] ## Layer 5: measurement and iteration Observe access, indexing, impressions, citations, visits and qualified outcomes as separate layers. Choose the correct current reports and document missing fields. Prioritize a change by business importance, implementation risk and the strength of its evidence; do not claim an internal agency priority score is an engine's ranking score. ## Release gate A production job is ready when its agreed technical and business contracts pass, evidence is retained, and unresolved risks have an owner. A technically sound page can still be unselected for a particular query. Google's AI guidance does not add a special file based route to guaranteed inclusion. [S02] Use [SEO build reference: intake to production evidence](https://library.feedthejoe.com/reference/seo-build-reference/) for the implementation sequence and [SEO release contracts and reproducible acceptance tests](https://library.feedthejoe.com/reference/framework-seo-release-contracts/) for test design. Keep specialized modules as the canonical owners of their subjects rather than copying their rules into every tier. * * * # Executed validation _2026.09.09_ Source: https://library.feedthejoe.com/reference/validation/ Shelf: Reference modules · Status: Baseline · Published 2026-09-09 · Release 2026.09.12-g40 ## New utility tests All 24 unit tests passed locally. Exact output is in unit-tests.txt. Tests exercise the four new utilities, including deliberately invalid inputs; they do not execute the preserved original script or legacy code examples. ## Release integrity The library audit result reports the final tested file counts and errors. It checks declared local Markdown file targets, release JSON syntax, catalog source references and SHA-256 preservation of all 146 unique originals. Historical text is not altered merely to make its old links pass. The check does not test external URL availability, Markdown fragment anchors, factual entailment, live indexing, application execution or rich result eligibility. ## Browser behavior The browser QA result records nine passed checks: initial report display, current/all/legacy filters, title search, internal navigation, full text search, legacy warnings, portable report source links and narrow screen layout. There were no JavaScript errors or external HTTP(S) requests in the tested interactions. The environment blocked direct file-URL navigation. The generated HTML was therefore loaded into Chromium using Playwright `set_content`; direct launch from the local filesystem was not tested here. The browser uses embedded document data, no fetch based document loading and no required remote fonts or scripts. Keeping the extracted folder intact is necessary for links to raw companion files. ## Manifest scope `SHA256SUMS.txt` records final release file hashes except its own. It is a change detection aid, not a signed authenticity assertion. The original upload's hash and release inventory counts are in `Research/release-manifest.json`. No production website or external account was changed. * * * # SEO library audit and research update Source: https://library.feedthejoe.com/reference/audit-report/ Shelf: Reference modules · Status: Baseline · Published 2026-09-09 · Reviewed 2026-09-09 · Release 2026.09.12-g40 **Research snapshot: 9 September 2026 · Release: 2026.09.09** ## Executive assessment The uploaded library has substantial breadth. Its primary weakness is not a shortage of subjects: it is the difficulty of determining which version, claim, threshold or implementation rule deserves authority. Four repeated version sets, a stale master index, broken internal paths and confident statements with different evidence quality make the material harder to use safely than its size suggests. This release therefore does two jobs. It adds current capabilities that were missing or poorly separated, and it gives the existing material a usable evidence and version structure. The result is one canonical active edition, unchanged historical originals, explicit review labels, a source register, reproducible local checks and an offline browser. It is designed to be usable by a developer, an editor or an AI coding assistant without silently treating old prose as a verified implementation specification. The audit covered the entire archive structurally. Factual review was targeted at high impact and time sensitive claims, not every sentence of approximately one million unique original words. The distinction is intentional: a file receiving a legacy banner has not been rewritten or fully fact checked. The [coverage matrix](https://library.feedthejoe.com/reference/coverage-matrix/) discloses the treatment of every unique original. ## 1\. What the archive actually contained | Measure | Observed result | | --- | --- | | ZIP entries, including directories and macOS metadata | 812 | | Content files across the four sets | 511 | | Unique file contents, by SHA-256 | 146 | | Redundant content copies | 365 | | Unique Markdown files | 143 | | Other unique files | One Python, one JSON, one TXT | | Approximate unique original word count | 1,047,235 | | Broken local inline Markdown targets in the original scan | 157, across 39 files | | Distinct embedded legacy URLs inventoried | 1,758 | The sets contain 114, 111, 143 and 143 content files respectively. Work 3 and Work 4 have identical content sets. Within the original archive, the same basename did not represent independently changed content. This made exact consolidation possible without choosing between different factual revisions hidden behind the same filename. The release uses Work 4's hierarchy where available and preserves the few historical only items from earlier sets. All 146 unique originals remain byte for byte intact in `99-Originals/`; the inventory records all 511 original paths. Consolidation removes repeated working copies, not unique historical content. The input ZIP is not overwritten. The old master index asserted a much smaller library than the actual archive. It has been rebuilt from the release catalog. The empty original `Schema.org` directory now contains four explicitly fictional examples rather than implying that deployable schema assets were already present. ## 2\. Audit and research method The structural pass enumerated archive entries, ignored directory and macOS resource fork noise for content counts, calculated exact hashes, grouped duplicate contents, counted approximate words and scanned local Markdown targets. These are reproducible file observations, not search engine measurements. The source inventory and migration map let another reviewer trace a current file back to its preserved original. A second pass located candidate problems: guarantees, universal thresholds, crawler names, structured data features, research attributions, rendering claims and destructive implementation instructions. Automated flagging was used for triage, not to decide that a statement was false. Selected passages were read in context and compared with primary documentation or the named research where available. The research register contains 52 primary sources. Fifty concern search, analytics, web platforms, research or agent protocols; two cover official usage of the proposed GitHub Actions components. Each record identifies the publisher, location, observation date, inspected scope and an actual document date only when available. Official documentation supports product behavior and stated policies. It does not certify every agency workflow proposed here. When sources disagreed because of timing, the release records the conflict rather than combining contradictory passages. Older Google AI guidance remains useful for eligibility while newer reporting documentation controls current reporting claims. The older FAQ announcement is not used to preserve eligibility after the final 2026 retirement. Version pinned protocol material is labeled as pinned, not silently called latest. [S01, S03 to S05, S21, S48] ## 3\. High impact research findings ### Current AI reporting needs a different measurement model Google announced dedicated generative AI performance reports on June 3, 2026 and updated the announcement to describe worldwide rollout on August 31. The documented Search report provides AI Overviews and AI Mode impressions with page, country, device and date views. This replaces both an incorrect older rollout claim and the blanket assumption that dedicated Google AI reporting cannot exist. Actual property availability and sufficient data still need inspection. [S04, S05] The new reporting modules deliberately avoid inventing dedicated clicks, CTR, raw prompts or a separate AI Overview-versus-AI Mode breakdown. They also prevent double counting AI impressions already represented in overall reporting. A report impression is not a website session, and neither is automatically a qualified lead. These boundaries are reflected in the metric contract template. GA4's current default channel documentation includes an AI Assistant channel; Google AI Overviews and AI Mode remain within Organic Search. A custom grouping may still serve a specific analysis, but it is no longer presented as universally required merely to identify the documented assistant category. Session, event and first user attribution scopes must be named rather than mixed in a single performance claim. [S36] Bing's newer preview reporting adds useful citation oriented dimensions. Its Citation Share is tied to citations for a grounding query, not general market share, ranking position or a share of all AI traffic. The library now has a dedicated Bing workflow rather than forcing Google, Bing and referral analytics into one “AI score.” [S06, S07] ### Technical eligibility is not a secret optimization formula Google's current guide does not require a special AI text file or special schema for its generative Search features. It also explicitly gives `llms.txt` no special positive or negative role in Google Search visibility. The release keeps room for an identified external consumer that actually uses an auxiliary file, but removes the assumption that creating such a file makes every engine consume or trust the site. [S02] The original material included universal rendering claims and confident quantitative assertions. Those selected claims have been corrected, narrowed or marked unverified. A benchmark from a research paper is not automatically a production rule for a current search product. A proprietary score, patent or third party multiplier cannot be treated as a disclosed ranking algorithm without evidence that supports that exact interpretation. The GEO paper is used within its research scope, not as a guarantee of present day citation gains. [S29] The useful engineering question becomes specific: which consumer needs which content, through which request and rendering path, under which access policy? The answer is tested on the actual route. That is more actionable than a broad promise about all models. ### Crawler permissions need purpose specific controls The updated engine matrix separates discovery/search, training and user requested retrieval. OpenAI's OAI-SearchBot, GPTBot and ChatGPT-User do not have interchangeable roles. Anthropic and Perplexity likewise document purpose specific agents and different behavior boundaries. Google-Extended is a policy token for specified non-Search uses, not a substitute for Googlebot access. [S08 to S13] The template therefore requires an explicit client policy rather than automatically enabling or blocking everything with “AI” in its name. The examples are not a complete opt out from every unlisted crawler. They also do not treat `robots.txt` as authentication, or a claimed user agent string as proof of identity. The observability module records how a request was verified and what the request actually establishes. This distinction matters to business reporting: an allowed request can establish attempted or successful retrieval, depending on the log evidence. It does not establish that a page was indexed, cited, recommended or responsible for revenue. The library now provides separate observation and attribution records instead of collapsing those steps. ### Structured data eligibility must have a lifecycle Google stopped showing FAQ rich results on May 7, 2026; its documentation was removed in June. HowTo rich results had already been retired. Useful FAQ content and the existence of a Schema.org vocabulary type are separate from eligibility for a Google visual feature. The current guide now distinguishes vocabulary validity, implementation syntax, visible factual agreement and feature support. [S01, S21] Review guidance also requires attention to current policy and whether the review concerns the publishing entity itself. The release does not include fabricated stars, review counts or guaranteed rich result outcomes. Merchant examples require consistency between visible offers, structured data and any relevant feed rather than treating markup as an independent place to invent sales information. [S20, S22, S23] The four example assets illustrate organization/site/breadcrumb relationships, an article and author, a product offer, and a real storefront only business case. Their data is fictional. Local JSON parsing verifies syntax only; it does not prove that a particular business qualifies for any feature or that the sample has passed a live rich result test. ### Route and rendering instructions needed safety boundaries Targeted inline edits replace universal instructions to lowercase routes, change established WordPress permalinks or remove thin/orphaned content without diagnosis. The revised approach is to define the actual route inventory, document the intended outcome, identify dependencies and approve a migration or retirement only when justified. Site moves need mappings, checks and rollback ownership. [S15, S38] The library also stops calling client rendering categorically invisible or malpractice. Google documents JavaScript rendering. Rendering choices should be based on the route, consumer, content, failure modes and application constraints. The updated React related patches and content delivery guide replace an absolute judgment with explicit checks. [S14, S24] The Next.js revision is version aware. In particular, a custom `htmlLimitedBots` expression replaces the default list rather than safely appending to it. The release warns against judging a streamed response solely from its first chunk or modifying this setting without testing the relevant bot and browser behavior. [S25 to S27] ## 4\. What was actually changed The active library contains 169 Markdown documents. Twenty seven are newly written researched modules. Nine original core guides were replaced with current scoped guidance: content delivery, Google AI visibility, AI citations, schema types, ChatGPT Search, spam policy, Search Console, GA4 and Next.js. The master index was regenerated separately. Five additional legacy documents received 14 exact inline safety edits. Their remaining content is still labeled legacy. Another 127 active original documents were retained with explicit review boundaries and links to current guidance. Four historical audit artifacts were preserved outside the active edition. No statement that every legacy paragraph has been corrected is implied by these labels. The 27 additions form practical groups: evidence and source governance; per engine access; Google and Bing AI reporting; observation and referral attribution; route and release contracts; location and regional eligibility; structured data and commerce consistency; Next.js metadata validation; verified crawler observability; crawl payload and field performance checks; agent access; social/video reporting; migration rollback; maintenance; client scope; faceted navigation; publisher preferences; title/description guidance; and the previously missing build/reference entry points. The 157 original broken local targets were repaired. Some were simply wrong relative paths; others named documents that were absent. Where a full specialist document remains absent, the replacement link says that it points to a related broader reference. A repaired link is not presented as a newly completed specialist chapter. The link repair log preserves the old target and reason. ## 5\. Operating assets and acceptance The 12 JSON templates cover intake, claims, engine policy, URL behavior, metric definitions, observations, migrations, locations, release acceptance, research maintenance, source facts and client scope. They use example only flags, placeholders or unavailable values rather than fictional completed client results. They are proposed records for a workflow, not integrations that have already been installed. Four new standard library Python utilities are included. The HTML checker inspects a saved complete HTML document for selected metadata and indexability expectations; it does not crawl a live site or run JavaScript. The robots generator turns an explicit policy into text and requires an approval declaration outside example mode; that declaration is not itself proof of human authorization. The JSON-LD embedder safely serializes example data into a script context but cannot establish its truth. The library audit checks declared local file targets, JSON syntax, catalog references and preserved hashes. Twenty four local unit tests cover both valid cases and deliberate failures, including canonical conflicts, noindex expectations, malformed JSON, policy input injection and script breakout escaping. These tests are evidence about the utilities' implemented checks. They do not certify the original million word corpus, every code sample, platform compliance or production SEO outcomes. The supplied CI workflow is proposed only; no GitHub execution was performed. [S51, S52] The release includes machine readable inventories, a migration map, catalog, source register, exact finding records, change log and checksum manifest. The offline browser defaults to current material while keeping legacy documents searchable with their status visible. This makes the research usable without asking an assistant to read every file before each task. ## 6\. How to apply the updated library to real work Start with project facts, not with a tier checklist. Identify the domain and canonical host, existing routes, application version, target markets, actual services or products, account ownership, publication rights, conversion definition and restrictions on crawler use. Record unavailable information rather than silently filling it with a plausible guess. Next, choose only the applicable modules. A local service area business should not inherit a fictional storefront schema. An established site should not change URL conventions solely because a general checklist prefers a different style. A store with facets needs explicit indexable state rules; a publisher needs rights, provenance and its own content distribution choices. Tier numbering remains useful for commercial organization, but not as a universal technical dependency graph. Establish a baseline before changing behavior. The baseline should separate access and rendering, indexing or reported appearances, site referrals and qualified business outcomes. Write acceptance criteria that can be observed on staging and after release. A release can pass technical checks without immediately increasing rankings; a visibility increase can occur without creating a qualified lead. Neither result should be mislabeled. Deploy only approved changes with a rollback route. Capture the version, affected URLs, before/after artifacts, tool output and accountable owner. Then evaluate the defined reporting period and cohort, retaining scope and denominator information. Improvements should be attributed cautiously when multiple changes, seasonality or reporting differences could explain them. These operating practices are recommendations, not claims about hidden platform algorithms. ## 7\. What remains unverified The largest remaining work item is the retained legacy corpus, including many industry and stack specific chapters. They remain available because preserving useful original material is preferable to deleting it without a full review. Their status is not a certificate. The review queue prioritizes high stakes advice, unsupported numbers, outdated product instructions and code intended for production. The 1,758 embedded legacy URLs were not all checked for availability or claim support. The local audit does not validate Markdown fragment anchors or every possible HTML link form. Existing server configurations and framework examples were not all executed. No benchmark was independently replicated, no client property was connected, and no real website's rankings, crawl permissions, leads or revenue were measured. Future maintenance should be triggered by an actual source change, stack upgrade, feature retirement or project decision, not merely a new date on a cover page. Assign an owner and preserve the old record when promoting a guide. The release supplies a maintenance ledger and proposed cadence; it does not start a background monitor. ## Conclusion The most important update is a change in authority: the library is no longer organized as though every confident paragraph deserves equal trust. New current guidance has explicit scope, source support and operational boundaries; older work is preserved and discoverable without pretending it was all revalidated. Use the current build reference and evidence rules as the entry point, the tier map for applicability, and the legacy documents as reviewable background. The package supplies concrete additions and tested offline tools while leaving live implementation and client acceptance where they belong: in the actual project's facts, permissions and measured results. ## Supporting records [Primary sources](https://library.feedthejoe.com/reference/source-register/) · [28 findings](https://library.feedthejoe.com/reference/findings/) · [Coverage matrix](https://library.feedthejoe.com/reference/coverage-matrix/) · [Tier applicability](https://library.feedthejoe.com/reference/tier-applicability-map/) · [Remaining review queue](https://library.feedthejoe.com/reference/remaining-review-queue/) · [Change log](https://library.feedthejoe.com/operating-model/changelog/) · [Tool boundaries](https://library.feedthejoe.com/reference/tools/) * * * # Coverage matrix _Every unique original_ Source: https://library.feedthejoe.com/reference/coverage-matrix/ Shelf: Reference modules · Status: Reference · Published 2026-09-09 · Release 2026.09.12-g40 This is a coverage disclosure, not a pass/fail score. Complete structural inventory and hash preservation apply to all 146 unique originals. Factual review was targeted, not exhaustive. Nine guides were rewritten; one index regenerated; five additional guides received targeted inline safety patches. The remaining 127 active legacy files are explicitly labeled as not fully fact checked. Four historical audit artifacts remain outside the active library. | Original unique file | Current treatment | Active document | Preserved original | | --- | --- | --- | --- | | `EO-COPY-PASTE-PLAYBOOK.md` | LEGACY · not fully verified | Open | Original | | `LOCATION-PAGE-FRAMEWORK.md` | PATCHED · legacy remainder | Open | Original | | `SEO-Search-Appearance.md` | LEGACY · not fully verified | Open | Original | | `SERP-Optimization.md` | LEGACY · not fully verified | Open | Original | | `audit-baseline-manifest.txt` | HISTORY · not active | Historical only | Original | | `build-log.md` | LEGACY · not fully verified | Open | Original | | `framework-11ty.md` | LEGACY · not fully verified | Open | Original | | `framework-accessibility.md` | LEGACY · not fully verified | Open | Original | | `framework-agenticaisearch.md` | LEGACY · not fully verified | Open | Original | | `framework-ai-content-workflow.md` | LEGACY · not fully verified | Open | Original | | `framework-aicitations.md` | REWRITTEN · researched | [Open](https://library.feedthejoe.com/reference/framework-aicitations/) | Original | | `framework-aioverviews.md` | REWRITTEN · researched | [Open](https://library.feedthejoe.com/reference/framework-aioverviews/) | Original | | `framework-aioverviews.outline.md` | LEGACY · not fully verified | Open | Original | | `framework-aso.md` | LEGACY · not fully verified | Open | Original | | `framework-astro.md` | LEGACY · not fully verified | Open | Original | | `framework-astrohugo.md` | LEGACY · not fully verified | Open | Original | | `framework-attribution.md` | LEGACY · not fully verified | Open | Original | | `framework-bigcommerce.md` | LEGACY · not fully verified | Open | Original | | `framework-boundaries.md` | LEGACY · not fully verified | Open | Original | | `framework-brandvoice.md` | LEGACY · not fully verified | Open | Original | | `framework-clientonboarding.md` | LEGACY · not fully verified | Open | Original | | `framework-competitoraudit.md` | LEGACY · not fully verified | Open | Original | | `framework-contentaudit.md` | LEGACY · not fully verified | Open | Original | | `framework-contentbriefs.md` | LEGACY · not fully verified | Open | Original | | `framework-contentfirst.md` | REWRITTEN · researched | [Open](https://library.feedthejoe.com/reference/framework-contentfirst/) | Original | | `framework-contentrefresh.md` | LEGACY · not fully verified | Open | Original | | `framework-coreupdates.md` | LEGACY · not fully verified | Open | Original | | `framework-cro.md` | LEGACY · not fully verified | Open | Original | | `framework-cross-stack-implementation.md` | LEGACY · not fully verified | Open | Original | | `framework-digitalpr.md` | LEGACY · not fully verified | Open | Original | | `framework-drupal.md` | LEGACY · not fully verified | Open | Original | | `framework-ecommerceseo.md` | LEGACY · not fully verified | Open | Original | | `framework-eeat.md` | LEGACY · not fully verified | Open | Original | | `framework-entitysalience.md` | LEGACY · not fully verified | Open | Original | | `framework-featuredsnippets.md` | LEGACY · not fully verified | Open | Original | | `framework-finance-seo.md` | LEGACY · not fully verified | Open | Original | | `framework-formoptimization.md` | LEGACY · not fully verified | Open | Original | | `framework-ga4.md` | REWRITTEN · researched | [Open](https://library.feedthejoe.com/reference/framework-ga4/) | Original | | `framework-gscanalysis.md` | REWRITTEN · researched | [Open](https://library.feedthejoe.com/reference/framework-gscanalysis/) | Original | | `framework-hcs.md` | LEGACY · not fully verified | Open | Original | | `framework-headless.md` | LEGACY · not fully verified | Open | Original | | `framework-healthcare-seo.md` | LEGACY · not fully verified | Open | Original | | `framework-hreflang.md` | LEGACY · not fully verified | Open | Original | | `framework-html-app-pwa-meta.md` | LEGACY · not fully verified | Open | Original | | `framework-html-canonical-alternate.md` | LEGACY · not fully verified | Open | Original | | `framework-html-favicon-icons.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-author.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-charset.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-color-scheme.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-content-language.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-copyright.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-generator.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-keywords.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-referrer.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-refresh.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-robots.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-theme-color.md` | LEGACY · not fully verified | Open | Original | | `framework-html-meta-viewport.md` | LEGACY · not fully verified | Open | Original | | `framework-html-open-graph.md` | LEGACY · not fully verified | Open | Original | | `framework-html-search-engine-verification.md` | LEGACY · not fully verified | Open | Original | | `framework-html-twitter-cards.md` | LEGACY · not fully verified | Open | Original | | `framework-http-2xx-status-codes.md` | LEGACY · not fully verified | Open | Original | | `framework-http-3xx-status-codes.md` | LEGACY · not fully verified | Open | Original | | `framework-http-4xx-status-codes.md` | LEGACY · not fully verified | Open | Original | | `framework-http-5xx-status-codes.md` | LEGACY · not fully verified | Open | Original | | `framework-http-caching-headers.md` | LEGACY · not fully verified | Open | Original | | `framework-http-content-headers.md` | LEGACY · not fully verified | Open | Original | | `framework-http-cors-headers.md` | LEGACY · not fully verified | Open | Original | | `framework-http-performance-headers.md` | LEGACY · not fully verified | Open | Original | | `framework-http-rate-control-headers.md` | LEGACY · not fully verified | Open | Original | | `framework-http-request-headers.md` | LEGACY · not fully verified | Open | Original | | `framework-http-security-headers.md` | LEGACY · not fully verified | Open | Original | | `framework-http-seo-headers.md` | LEGACY · not fully verified | Open | Original | | `framework-hugo.md` | LEGACY · not fully verified | Open | Original | | `framework-hydrogen.md` | LEGACY · not fully verified | Open | Original | | `framework-imageseo.md` | LEGACY · not fully verified | Open | Original | | `framework-infogain.md` | LEGACY · not fully verified | Open | Original | | `framework-initialaudit.md` | LEGACY · not fully verified | Open | Original | | `framework-internallinking.md` | LEGACY · not fully verified | Open | Original | | `framework-international.md` | LEGACY · not fully verified | Open | Original | | `framework-jekyll.md` | LEGACY · not fully verified | Open | Original | | `framework-keywordresearch.md` | LEGACY · not fully verified | Open | Original | | `framework-knowledgegraph.md` | LEGACY · not fully verified | Open | Original | | `framework-legal-seo.md` | LEGACY · not fully verified | Open | Original | | `framework-linkbuilding.md` | LEGACY · not fully verified | Open | Original | | `framework-localseo.md` | LEGACY · not fully verified | Open | Original | | `framework-magento.md` | LEGACY · not fully verified | Open | Original | | `framework-masterindex.md` | REBUILT · navigation | [Open](https://library.feedthejoe.com/reference/framework-masterindex/) | Original | | `framework-mcp.md` | LEGACY · not fully verified | Open | Original | | `framework-migration.md` | LEGACY · not fully verified | Open | Original | | `framework-mobileseo.md` | LEGACY · not fully verified | Open | Original | | `framework-multiengine-tradeoffs.md` | LEGACY · not fully verified | Open | Original | | `framework-multimodalsearch.md` | LEGACY · not fully verified | Open | Original | | `framework-newsseo.md` | LEGACY · not fully verified | Open | Original | | `framework-nextjs.md` | REWRITTEN · researched | [Open](https://library.feedthejoe.com/reference/framework-nextjs/) | Original | | `framework-nuxt.md` | LEGACY · not fully verified | Open | Original | | `framework-ongoingaudit.md` | LEGACY · not fully verified | Open | Original | | `framework-pageexperience.md` | LEGACY · not fully verified | Open | Original | | `framework-performance.md` | LEGACY · not fully verified | Open | Original | | `framework-perplexityspaces.md` | LEGACY · not fully verified | Open | Original | | `framework-ppc-seo-coordination.md` | LEGACY · not fully verified | Open | Original | | `framework-pricing.md` | LEGACY · not fully verified | Open | Original | | `framework-react.md` | PATCHED · legacy remainder | Open | Original | | `framework-realestate-seo.md` | LEGACY · not fully verified | Open | Original | | `framework-remix.md` | LEGACY · not fully verified | Open | Original | | `framework-reporting.md` | LEGACY · not fully verified | Open | Original | | `framework-robotstxt-crawlbudget.md` | LEGACY · not fully verified | Open | Original | | `framework-saas-seo.md` | LEGACY · not fully verified | Open | Original | | `framework-saas-website-builders.md` | LEGACY · not fully verified | Open | Original | | `framework-schema-types-2026.md` | REWRITTEN · researched | [Open](https://library.feedthejoe.com/reference/framework-schema-types-2026/) | Original | | `framework-schema.md` | LEGACY · not fully verified | Open | Original | | `framework-searchgpt.md` | REWRITTEN · researched | [Open](https://library.feedthejoe.com/reference/framework-searchgpt/) | Original | | `framework-security.md` | LEGACY · not fully verified | Open | Original | | `framework-shopify.md` | LEGACY · not fully verified | Open | Original | | `framework-spampolicies.md` | REWRITTEN · researched | [Open](https://library.feedthejoe.com/reference/framework-spampolicies/) | Original | | `framework-sqrg.md` | LEGACY · not fully verified | Open | Original | | `framework-sveltekit.md` | LEGACY · not fully verified | Open | Original | | `framework-tailwind.md` | LEGACY · not fully verified | Open | Original | | `framework-technicalseo.md` | PATCHED · legacy remainder | Open | Original | | `framework-topicalauthority.md` | LEGACY · not fully verified | Open | Original | | `framework-trustsignals.md` | LEGACY · not fully verified | Open | Original | | `framework-uxseo.md` | LEGACY · not fully verified | Open | Original | | `framework-videoseo.md` | LEGACY · not fully verified | Open | Original | | `framework-visualsearch.md` | LEGACY · not fully verified | Open | Original | | `framework-voicesearch.md` | LEGACY · not fully verified | Open | Original | | `framework-webflow.md` | LEGACY · not fully verified | Open | Original | | `framework-wordpress.md` | LEGACY · not fully verified | Open | Original | | `framework-ymyl.md` | LEGACY · not fully verified | Open | Original | | `growing-search-console-impressions-2026 (1).md` | LEGACY · not fully verified | Open | Original | | `jaccard-ruthless-check-data.json` | HISTORY · not active | Historical only | Original | | `jaccard-ruthless-check-report.md` | HISTORY · not active | Historical only | Original | | `jaccard-ruthless-check.py` | HISTORY · not active | Historical only | Original | | `tier-eight.md` | LEGACY · not fully verified | Open | Original | | `tier-eleven.md` | LEGACY · not fully verified | Open | Original | | `tier-five.md` | LEGACY · not fully verified | Open | Original | | `tier-four.md` | LEGACY · not fully verified | Open | Original | | `tier-fourteen.md` | LEGACY · not fully verified | Open | Original | | `tier-nine.md` | LEGACY · not fully verified | Open | Original | | `tier-one.md` | PATCHED · legacy remainder | Open | Original | | `tier-seven.md` | LEGACY · not fully verified | Open | Original | | `tier-six.md` | LEGACY · not fully verified | Open | Original | | `tier-ten.md` | LEGACY · not fully verified | Open | Original | | `tier-thirteen.md` | LEGACY · not fully verified | Open | Original | | `tier-three.md` | PATCHED · legacy remainder | Open | Original | | `tier-twelve.md` | LEGACY · not fully verified | Open | Original | | `tier-two.md` | LEGACY · not fully verified | Open | Original | * * * # Findings and dispositions Source: https://library.feedthejoe.com/reference/findings/ Shelf: Reference modules · Status: Reference · Published 2026-09-09 · Release 2026.09.12-g40 28 selected finding records. Classifications distinguish confirmed errors, outdated features, unsafe universal instructions, unsupported generalizations, unverified numerical claims and audit method limits. “Unverified” does not mean proved false. Original line numbers refer to the preserved source before banners and patches, not the revised active file. A resolution in current guidance does not certify every other occurrence in retained legacy prose. Sources are identified in the [primary source register](https://library.feedthejoe.com/reference/source-register/). Exact machine readable records are in findings.json. ## F01 · confirmed inventory error **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-masterindex.md`, line 13. Inspect preserved source **Located wording:** ``` The library currently contains **56 framework documents** plus this master index. Categorized below. ``` **Why it matters:** The entry point understates the archive and asserts unreliable navigation. **Disposition:** Regenerate the index from the current filesystem and status catalog. **Evidence:** Direct archive inspection / reproducible inventory ## F02 · unsafe universal instruction **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-one.md`, line 27. Inspect preserved source **Located wording:** ``` - Force lowercase URLs in `.htaccess` or `nginx.conf` to prevent case-duplicate indexing ``` **Why it matters:** Can break case sensitive routes, assets and signed links. **Disposition:** Require a project specific URL mapping and tests; no global rewrite by default. **Evidence:** S15, S38 ## F03 · unsafe universal instruction **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-one.md`, line 29. Inspect preserved source **Located wording:** ``` - 301-redirect or 410 all thin, duplicate, or orphan pages flagged in GSC ``` **Why it matters:** Can remove useful pages and destroy user paths without diagnosis. **Disposition:** Use per-URL keep, improve, merge, exclude or retire decisions with approval. **Evidence:** S15, S16, S38 ## F04 · unsafe universal instruction **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-one.md`, line 24. Inspect preserved source **Located wording:** ``` - Set WordPress permalinks to `/%postname%/`; in Next.js use file-based routing with consistent trailing-slash policy (pick one, stick to it sitewide) ``` **Why it matters:** Changing established URL structure solely for style creates migration risk. **Disposition:** Preserve established URLs unless an approved migration justifies changes. **Evidence:** S38 ## F05 · heuristic mislabeled as requirement **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-one.md`, line 44. Inspect preserved source **Located wording:** ``` - Write unique `` tag per page, 50–60 characters, primary keyword near the front ``` **Why it matters:** Editorial guidance is presented as a fixed implementation gate. **Disposition:** Treat length as review guidance, not an official limit. **Evidence:** S34 ## F06 · heuristic mislabeled as requirement **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-one.md`, line 45. Inspect preserved source **Located wording:** ``` - Write unique `<meta name="description">` per page, 140–160 characters, with active voice and CTA ``` **Why it matters:** A fixed count does not guarantee snippet selection or display. **Disposition:** Use truthful concise copy and flexible preview review. **Evidence:** S35 ## F07 · incorrect bot role for goal **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-three.md`, line 182. Inspect preserved source **Located wording:** ``` - **Claude (Anthropic)**: Nuanced, well-reasoned content with clear caveats and sourcing; ensure ClaudeBot is allowed ``` **Why it matters:** Training permission is conflated with search/citation discovery. **Disposition:** Use Claude-SearchBot for the documented search role; review Claude-User and training independently. **Evidence:** S10 ## F08 · outdated mixed bot list **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-three.md`, line 170. Inspect preserved source **Located wording:** ``` - Add explicit rules for: GPTBot, ClaudeBot, Claude-Web, PerplexityBot, Google-Extended, OAI-SearchBot, anthropic-ai, ChatGPT-User, Applebot-Extended ``` **Why it matters:** Legacy and current tokens are grouped without purpose or current support. **Disposition:** Use the engine role matrix and owner approved policy. **Evidence:** S08, S10, S11, S12 ## F09 · unsupported absolute **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-contentfirst.md`, line 17. Inspect preserved source **Located wording:** ``` The frameworks library cannot defend itself against this failure mode without an explicit doctrine. Individual frameworks contain technical guidance against client side rendering. None of them name the inversion as the build philosophy. Without a doctrine document, a builder (developer or AI assistant) can follow the dependency graph, install every framework in the prescribed order, and ship a beautifully styled React SPA that delivers an empty `<div id="root">` to GPTBot. Every framework was implemented. Zero citations result. ``` **Why it matters:** Architecture alone does not establish a universal zero citation outcome. **Disposition:** Replace with route/consumer specific delivery and measurement contracts. **Evidence:** S14, S24 ## F10 · unverified quantitative claim **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-contentfirst.md`, line 258. Inspect preserved source **Located wording:** ``` > Pages scoring G ≥ 0.70 with ≥ 12 of the 16 pillars active achieved a **78% cross engine citation rate** (cited by two or more of the three engines studied). ``` **Why it matters:** A proprietary score and broad outcome are presented without reproduced evidence. **Disposition:** Remove from authoritative guidance; retain in historical review queue. **Evidence:** S02, S29 ## F11 · contradicted blanket rendering claim **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-aioverviews.md`, line 210. Inspect preserved source **Located wording:** ``` Three implications: server rendered substrate is non negotiable, heading hierarchy carries citation weight (reading mode parses by structure not rendered layout), and JavaScript injected schema is invisible. The deeper tactical treatment of reading mode optimization across all AI engines lives in [framework-aicitations.md](framework-aicitations.md). For AIO, pass the `curl -A "GPTBot"` substrate test (see [framework-contentfirst.md](framework-contentfirst.md) Section 9.1) and reading mode is largely handled. ``` **Why it matters:** Conflates all consumers and conflicts with Google JavaScript guidance. **Disposition:** Validate actual rendering; do not equate GPTBot simulation with Google AI testing. **Evidence:** S14, S03 ## F12 · unverified quantitative claim **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-aioverviews.md`, line 250. Inspect preserved source **Located wording:** ``` Heading hierarchy (one H1, logical H2 to H6), descriptive anchor text, semantic sectioning elements (`<article>`, `<section>`, `<main>`, `<nav>`, `<aside>`), and lists where appropriate signal extractability. kime.ai 2026 found 4.2x citation rate for HTML `<table>` over equivalent prose, 2.7x for `<ol>` for sequential content, 1.8x for `<ul>` over prose. ``` **Why it matters:** An attributed multiplier is promoted as generally reproducible without verified methods. **Disposition:** Do not use in forecasts or acceptance tests; formatting follows information structure. **Evidence:** S29 ## F13 · unverified research attribution **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-aioverviews.md`, line 258. Inspect preserved source **Located wording:** ``` Princeton GEO study (SIGKDD 2024) found pages with at least three inbound internal links from topically related pages earn higher AIO citation rates than orphan or single linked pages. Internal linking signals topical centrality to the synthesis engine. See [framework-internallinking.md](framework-internallinking.md). ``` **Why it matters:** A specific internal link/AIO claim is not established by the inspected primary study. **Disposition:** Retain as unverified historical attribution, not a proven rule. **Evidence:** S29 ## F14 · overgeneralized research result **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-aioverviews.md`, line 462. Inspect preserved source **Located wording:** ``` Inline outbound citations to authoritative sources boost AIO citation probability by approximately 30 percent per Princeton GEO study (SIGKDD 2024). The pattern: descriptive anchor text linking to .gov, .edu, peer reviewed journals, standards bodies, primary sources. The link itself is the citation. The destination is authoritative. ``` **Why it matters:** Benchmark metrics are converted to current Google citation probability. **Disposition:** Scope research to its engine/model/dataset/outcome. **Evidence:** S29 ## F15 · incorrect reporting timeline **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-gscanalysis.md`, line 17. Inspect preserved source **Located wording:** ``` The 2026 reality: AI Overviews (AIO) appear on roughly 48 percent of all Google searches. The AIO tab in Performance, rolled out Q4 2025, separates AIO impression data for the first time. CWV thresholds moved to INP from FID in March 2024. Bulk Data Export to BigQuery (BDE), generally available since February 2024, removes the 1000 row cap and exposes URL level impression schema the UI never showed. ``` **Why it matters:** The library claims an old rollout and report structure not supported by current official sources. **Disposition:** Use June 3 announcement and August 31, 2026 rollout note and current help page. **Evidence:** S04, S05 ## F16 · obsolete feature list **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-gscanalysis.md`, line 198. Inspect preserved source **Located wording:** ``` Reports valid, warning, error counts per schema type Google detected. Types in 2026: Breadcrumbs, Logos, Sitelinks searchbox, FAQ, HowTo, Product, Review snippet, Video, Job posting, Event, Recipe, Practice problem, Math solver, Dataset, Course, Movie, Software application, Special announcement. A type appears only after Google detects matching schema. ``` **Why it matters:** Retired features are listed as current report appearances. **Disposition:** Use available report fields and current feature lifecycle. **Evidence:** S01, S21 ## F17 · superseded workflow requirement **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-ga4.md`, line 557. Inspect preserved source **Located wording:** ``` ### 11.4 Strategy 3: The AI Assistants Custom Channel Grouping ``` **Why it matters:** Custom grouping is treated as necessary while GA4 now documents an AI Assistant channel. **Disposition:** Use current default definitions; custom grouping remains optional for a declared purpose. **Evidence:** S36 ## F18 · version specific claim not revalidated **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-ga4.md`, line 531. Inspect preserved source **Located wording:** ``` GA4 attributes sessions to source / medium at session start. The combination persists for session duration even if the user navigates within the site. New session on session timeout (default 30 min), midnight crossover, or new campaign source. Internal navigation does not start new sessions. The granularity unlocks per channel landing analysis: filter Landing Page by Session Source / Medium for `google / organic`, `bing / organic`, `chatgpt.com / referral`, `perplexity.ai / referral`. ``` **Why it matters:** Old session semantics are stated as GA4 behavior. **Disposition:** Do not carry forward unsupported session reset assertions; verify actual GA4 scope. **Evidence:** S36 ## F19 · outdated safe harbor implication **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-spampolicies.md`, line 542. Inspect preserved source **Located wording:** ``` **What it is**: Third-party content published on a host site primarily to take advantage of the host's existing ranking signals, where the third-party content has little oversight from the host site. ``` **Why it matters:** Oversight is treated as a defining protection against reputation abuse. **Disposition:** Use current policy; review purpose and regional treatment rather than an oversight shortcut. **Evidence:** S18, S42 ## F20 · unsupported architecture absolute **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-react.md`, line 117. Inspect preserved source **Located wording:** ``` Verdict for 2026: pure CSR for any public content surface is malpractice. The only acceptable use cases are dashboards behind authentication, internal tools, and admin panels. ``` **Why it matters:** A single rendering pattern is categorically condemned regardless of route/consumer requirements. **Disposition:** Use route specific engineering evidence and official rendering documentation. **Evidence:** S14, S24 ## F21 · unsupported redirect absolute **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-technicalseo.md`, line 273. Inspect preserved source **Located wording:** ``` | 302 Found | Temporary redirect. Use only for actual temporary moves (A/B tests, seasonal pages). Misused 302s leak link equity. | ``` **Why it matters:** Temporary/permanent semantics are confused with a guaranteed signal loss mechanism. **Disposition:** Choose the correct move semantics and validate redirects without claiming automatic leakage. **Evidence:** S15, S38 ## F22 · unsupported schema page requirement **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/LOCATION-PAGE-FRAMEWORK.md`, line 78. Inspect preserved source **Located wording:** ``` - Schema graph requires distinct entities (State, AdministrativeArea, City) with `containedInPlace` and `containsPlace` cross references that only work when each tier is its own page. ``` **Why it matters:** A graph relationship is used to justify mandatory indexed geographic page proliferation. **Disposition:** Model real places without requiring every geography to have its own indexed page. **Evidence:** S18, S20 ## F23 · unsupported universal file requirement **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-aicitations.md`, line 34. Inspect preserved source **Located wording:** ``` 4. **Install Sections 5-9** — content patterns, technical infrastructure, llms.txt, RAG-friendly structure ``` **Why it matters:** Auxiliary AI file advice lacks an engine specific authority boundary. **Disposition:** Treat optional files as consumer specific; no special Google Search requirement. **Evidence:** S02 ## F24 · deprecated feature risk **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-schema-types-2026.md`, line 5. Inspect preserved source **Located wording:** ``` Companion to [framework-schema.md](framework-schema.md). This document inventories the schema types that move citation needles in 2026. The parent framework covers JSON-LD installation, the @id graph pattern, and the foundation schemas every site needs. This framework drills into the type-specific patterns for SoftwareApplication, Course, Event, JobPosting, Recipe, HowTo, FAQPage, QAPage, Review, Product, LocalBusiness subtypes, Person, ProfilePage, ClaimReview, and the broader CreativeWork hierarchy. ``` **Why it matters:** Legacy schema guidance predates final FAQ rich result retirement. **Disposition:** Separate vocabulary validity from feature lifecycle; Google FAQ rich results ended May 7, 2026. **Evidence:** S01, S20 ## F25 · unverified quantitative claim **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-schema-types-2026.md`, line 646. Inspect preserved source **Located wording:** ``` The full Product schema stack (Product plus Offer plus AggregateRating plus shippingDetails plus hasMerchantReturnPolicy) is the baseline for Merchant Listings, Shopping graph, and AI shopping citation. Pages with the full stack earn approximately 3.2 times the AI shopping citation rate of pages with Product schema alone (Schema App ecommerce study, October 2025, 6,800 product pages). Cross reference [framework-ecommerceseo.md](framework-ecommerceseo.md) for variant strategy, Merchant Center feed, and Shopping graph optimization. ``` **Why it matters:** Product schema completeness is linked to a claimed AI citation multiplier. **Disposition:** Replace with truth, applicable properties and feature validation. **Evidence:** S20, S23 ## F26 · overbroad hidden content rule **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-contentfirst.md`, line 349. Inspect preserved source **Located wording:** ``` > **Forbidden**: `display: none` on content meant to be indexed. Off screen positioning (`position: absolute; left: -9999px`) to hide content visually while keeping it in DOM (treated as cloaking by Google). Tabs and accordions that require JavaScript to reveal content. Carousels where slides 2 through N are not in the DOM until JS rotates them in. Modal overlays that contain primary content only revealed by click. ``` **Why it matters:** CSS hiding can be confused with manipulative hidden content regardless of legitimate UX. **Disposition:** Distinguish deceptive intent from accordions, accessibility and normal UI behavior. **Evidence:** S18 ## F27 · unverified cross surface equivalence **Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-searchgpt.md`, line 5. Inspect preserved source **Located wording:** ``` A comprehensive installation and audit reference for winning citation and brand mention on OpenAI's search surface family. ChatGPT Search (browsing inside ChatGPT, launched October 31, 2024 per OpenAI's announcement), the SearchGPT prototype (July 25, 2024 per OpenAI), the ChatGPT agent (integrated July 17, 2025, replacing the Operator preview that shut down August 31, 2025), and ChatGPT Atlas (the OpenAI Chromium based browser, October 21, 2025) share a bot family, an index dependency, and a retrieval pattern, but each surface produces distinct citation behavior. This framework specifies the structural, schema, freshness, entity, and access signals that drive citation on those surfaces, the bot family and how each member behaves, the audit rubric, and the maintenance cadence. Dual purpose: installation manual and audit document. ``` **Why it matters:** The entry point generalizes shared mechanics across ChatGPT product surfaces. **Disposition:** Use only documented provider roles and product specific scope. **Evidence:** S08, S09 ## F28 · audit method boundary **Original:** `SEO Tiers Version Sets/SEO Tiers For Work/jaccard-ruthless-check-report.md`, line 9. Inspect preserved source **Located wording:** ``` Ruthless threshold: 0.1000 ``` **Why it matters:** Lexical dissimilarity is not source verification, semantic uniqueness or compliance. **Disposition:** Keep the report historical; do not treat it as a quality certificate. **Evidence:** Direct archive inspection / reproducible inventory * * * # Remaining review queue and explicit limits Source: https://library.feedthejoe.com/reference/remaining-review-queue/ Shelf: Reference modules · Status: Reference · Published 2026-09-09 · Release 2026.09.12-g40 This release is a completed structural audit and targeted research update, not a line by line factual certification of approximately one million original words. ## Highest priority remaining reviews **Legacy claims and numerical promises.** There are 127 retained active documents without full factual review, plus legacy remainders in five patched guides. The automatic candidate list is a triage aid, not a list of established defects. Revisit named studies, percentages, benchmarks, guarantees, exact thresholds and claims about unpublished systems before use. **Industry specific advice.** Existing medical, legal, financial and other high stakes industry chapters remain legacy reference. A library banner does not establish professional or jurisdiction specific compliance. Have an appropriately qualified reviewer check intended use, place and current authority before client deployment. **Stack specific code.** Old examples for React, Next.js, Remix, WordPress, Shopify, Webflow, server configuration and other platforms were not all installed or runtime tested. Pin the actual project version, inspect dependencies and test on staging. The nine researched rewrites are guidance, not a fully implemented client application. **Missing specialist chapters.** Some historical links named absent specialist files, including security headers/CSP, TLS, FastAPI sidecars, fail2ban, compression and HTTP/3. Repairs point to labeled related references where appropriate. They do not pretend that a complete missing specialist treatment now exists. ## Scope not covered by local validation The 1,758 distinct embedded legacy URLs were inventoried, not all retrieved and checked. The link audit tests local Markdown file targets in its declared folders, not external availability, fragment anchors, every HTML link or source entailment. JSON parsing is not Schema.org vocabulary validation or rich result testing. Python unit tests cover the four new utilities, not the preserved original Jaccard script or every legacy code block. No client website was crawled as part of this release. No Search Console, Analytics, Bing Webmaster Tools, hosting, CRM or repository account was connected. No live rankings, real user performance metrics, consent setup, bot identity, revenue attribution or client result was verified. No research benchmark was independently replicated. ## Release promotion rule To promote a legacy guide, give it a named scope, current sources, corrected wording, explicit exceptions, representative implementation tests where applicable and a review date. Update the document catalog and migration map; do not silently relabel a file as reviewed. Maintain the original checksum record. A proposed review cadence is not an active scheduled monitor. * * * # Primary source register Source: https://library.feedthejoe.com/reference/source-register/ Shelf: Reference modules · Status: Reference · Published 2026-09-09 · Reviewed 2026-09-09 · Release 2026.09.12-g40 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. A source supports only its stated claim, not every recommendation in the library. Operational workflows and acceptance gates are proposed agency practices, not undisclosed ranking rules. Older live documentation can lag a dated update. In particular S04/S05 supersede S03 on dedicated AI reporting; S01 supersedes S21 on FAQ eligibility. S48 is intentionally version pinned, not represented as the latest MCP security contract. No source publication date is invented when unavailable. ## S01 · Google Search documentation updates **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-09-08 FAQ retirement; 2026 policy, feature and documentation changes. Changelog dates distinguish documentation changes from feature launches. [Open primary source](https://developers.google.com/search/updates) ## S02 · AI optimization guide **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned No special AI file or schema requirement for Google Search; llms.txt has no special Search role. [Open primary source](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) ## S03 · AI features and your website **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** 2025-12-10 Search eligibility and snippet controls. Its older reporting paragraph is superseded by S04/S05 for dedicated AI reporting. [Open primary source](https://developers.google.com/search/docs/appearance/ai-features) ## S04 · Introducing Search Generative AI performance reports **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-06-03 Announcement updated with worldwide rollout on 2026-08-31; dedicated reports coexist with overall performance data. [Open primary source](https://developers.google.com/search/blog/2026/06/gen-ai-performance-reports) ## S05 · Generative AI performance report (Search) **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned AI Overviews/AI Mode impressions; page, country, device and date dimensions. Availability requires sufficient data. No dedicated clicks or prompt dimension asserted. [Open primary source](https://support.google.com/webmasters/answer/16984139) ## S06 · Introducing AI Performance in Bing Webmaster Tools **Publisher:** Microsoft Bing · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-02-10 Public preview AI citation reporting. [Open primary source](https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview) ## S07 · New AI visibility insights: Intents, Topics, Citation Share and Compare **Publisher:** Microsoft Bing · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-06-16 Citation Share is relative to all cited sites for a grounding query; topic/intent classifications and period comparisons. [Open primary source](https://blogs.bing.com/search/June-2026/New-AI-Visibility-Insights-in-Bing-Webmaster-Tools-Intents-Topics-Citation-Share-Compare) ## S08 · Overview of OpenAI crawlers **Publisher:** OpenAI · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Separate OAI-SearchBot, GPTBot, ChatGPT-User and OAI-AdsBot roles; published verification feeds and user fetch caveat. [Open primary source](https://developers.openai.com/api/docs/bots) ## S09 · Publishers and Developers FAQ **Publisher:** OpenAI · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned ChatGPT referral UTM convention; search access guidance. [Open primary source](https://help.openai.com/en/articles/12627856-publishers-and-developers-faq) ## S10 · Does Anthropic crawl data from the web? **Publisher:** Anthropic · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-04-07 ClaudeBot training, Claude-SearchBot search and Claude-User retrieval; published robots behavior and IP information link. [Open primary source](https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler) ## S11 · Perplexity crawlers **Publisher:** Perplexity · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned PerplexityBot search and Perplexity-User user directed fetch; IP feeds and robots caveat. [Open primary source](https://docs.perplexity.ai/docs/resources/perplexity-crawlers) ## S12 · Google common crawlers **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-07-14 Google-Extended is a robots product token, not a separate HTTP user agent; Gemini training/grounding scope, not Google Search. [Open primary source](https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers) ## S13 · Verify requests from Google crawlers and fetchers **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Published IP ranges and reverse/forward DNS verification procedures. [Open primary source](https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests) ## S14 · JavaScript SEO basics **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Google can render JavaScript; rendering, HTTP, canonical and initial noindex considerations. [Open primary source](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics) ## S15 · How to specify a canonical URL **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Canonicalization methods are signals with different strengths, not a universal mandate or a guarantee. [Open primary source](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) ## S16 · Robots meta tag, data-nosnippet and X-Robots-Tag **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Page level indexing and snippet controls; crawl access is needed to read directives. [Open primary source](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag) ## S17 · How Google interprets robots.txt **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Robots group matching and crawl directives; robots is not authentication. [Open primary source](https://developers.google.com/crawling/docs/robots-txt/robots-txt-spec) ## S18 · Spam policies for Google web search **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Doorway, scaled content, hidden content and reputation abuse; policies also cover manipulation of generative Search responses. [Open primary source](https://developers.google.com/search/docs/essentials/spam-policies) ## S19 · Creating helpful, reliable, people first content **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned People first evaluation and quality questions, not an engine exposed numeric E-E-A-T score. [Open primary source](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) ## S20 · General structured data guidelines **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Visible content accuracy, feature eligibility, validation and no guaranteed rich result. [Open primary source](https://developers.google.com/search/docs/appearance/structured-data/sd-policies) ## S21 · Changes to HowTo and FAQ rich results **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** 2023-08-08 Updated 2023-09-14: HowTo retirement effective 2023-09-13. Old FAQ eligibility is superseded by 2026 retirement in S01. [Open primary source](https://developers.google.com/search/blog/2023/08/howto-faq-changes) ## S22 · Review snippet structured data **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Authentic visible reviews; no fake or undisclosed incentivized reviews; self serving LocalBusiness/Organization review star restriction. [Open primary source](https://developers.google.com/search/docs/appearance/structured-data/review-snippet) ## S23 · Merchant listing structured data **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Product/Offer eligibility, sale duration fields and truthful commercial data. Not a promise of AI citations. [Open primary source](https://developers.google.com/search/docs/appearance/structured-data/merchant-listing) ## S24 · Creating a React app **Publisher:** React · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Frameworks can support client rendering, prerendering and server rendering according to route needs. [Open primary source](https://react.dev/learn/creating-a-react-app) ## S25 · generateMetadata **Publisher:** Next.js / Vercel · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-08-25 Metadata API, streaming behavior and framework version specific usage. [Open primary source](https://nextjs.org/docs/app/api-reference/functions/generate-metadata) ## S26 · Metadata and OG images **Publisher:** Next.js / Vercel · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-08-25 App Router metadata and social image implementation. [Open primary source](https://nextjs.org/docs/app/getting-started/metadata-and-og-images) ## S27 · htmlLimitedBots configuration **Publisher:** Next.js / Vercel · **Observed:** 2026-09-09 · **Document/announcement date:** 2025-10-03 Option introduced in 15.2; custom regex replaces default list; all bot blocking changes streaming behavior. [Open primary source](https://nextjs.org/docs/app/api-reference/config/next-config-js/htmlLimitedBots) ## S28 · Web Vitals **Publisher:** Google web.dev · **Observed:** 2026-09-09 · **Document/announcement date:** 2024-10-31 Current LCP, INP, CLS thresholds and 75th-percentile field methodology; lab is not field evidence. [Open primary source](https://web.dev/articles/vitals) ## S29 · GEO: Generative Engine Optimization **Publisher:** Aggarwal et al. / arXiv · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Benchmark and deployed engine experiments; findings depend on setup, domain, metric and model. Not a 2026 Google production ranking specification. [Open primary source](https://arxiv.org/html/2311.09735v3) ## S30 · IndexNow documentation **Publisher:** IndexNow · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Changed-URL submission, ownership verification, batches up to 10000; success acknowledges receipt, not indexing. [Open primary source](https://www.indexnow.org/documentation) ## S31 · Indexing API quickstart **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Restricted to JobPosting or BroadcastEvent embedded in VideoObject, not a universal website indexing endpoint. [Open primary source](https://developers.google.com/search/apis/indexing-api/v3/quickstart) ## S32 · Guidelines for representing your business on Google **Publisher:** Google Business Profile · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Real business representation, address/service area eligibility and location restrictions. [Open primary source](https://support.google.com/business/answer/3038177?hl=en) ## S33 · Manage service areas for service area and hybrid businesses **Publisher:** Google Business Profile · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Service areas versus customer facing addresses; avoid invented storefronts. [Open primary source](https://support.google.com/business/answer/9157481?hl=en) ## S34 · Influencing title links **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Descriptive titles, automated selection and display truncation; no fixed character count requirement. [Open primary source](https://developers.google.com/search/docs/appearance/title-link) ## S35 · Control snippets in search results **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Meta description selection and truncation; no fixed character count requirement. [Open primary source](https://developers.google.com/search/docs/appearance/snippet) ## S36 · Default channel group **Publisher:** Google Analytics · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Current AI Assistant channel; Google AI Overviews/AI Mode remain Organic Search; event/session/first user scopes differ. [Open primary source](https://support.google.com/analytics/answer/9756891?hl=en) ## S37 · Avoid sending personally identifiable information **Publisher:** Google Analytics · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned PII exclusion from URLs, titles, user inputs and campaign/event fields. Legacy UA code on this page is not adopted. [Open primary source](https://support.google.com/analytics/answer/6366371?hl=en) ## S38 · Site moves and migrations **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned URL mapping, redirects, monitoring and move sequencing. [Open primary source](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) ## S39 · Managing faceted navigation crawling **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Control unnecessary filter URL crawling; decide which facets need search visibility. [Open primary source](https://developers.google.com/crawling/docs/faceted-navigation) ## S40 · Tell Google about localized versions **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Hreflang implementation alternatives and reciprocal alternate relationships. [Open primary source](https://developers.google.com/search/docs/specialty/international/localized-versions) ## S41 · Regional differences in Google Search **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Region-, query- and feature specific eligibility; documented on 2026-09-08. [Open primary source](https://developers.google.com/search/docs/appearance/aggregator-features) ## S42 · Update to the site reputation abuse policy **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-08-28 Changes beginning 2026-08-30 distinguish EEA treatment; not permission to pursue abuse. [Open primary source](https://developers.google.com/search/blog/2026/08/update-site-reputation-policy) ## S43 · Search Console platform properties and social/video guide **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-07-29 Global platform properties for supported social/video platforms; Search visibility differs from native platform analytics. [Open primary source](https://developers.google.com/search/blog/2026/07/platform-properties-social-video-guide) ## S44 · Analyze social and video content performance **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Connected/verified platform property workflows and Search performance interpretation. [Open primary source](https://developers.google.com/search/docs/monitor-debug/analyze-social-video-content) ## S45 · Preferred Sources guide for web publishers **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned User driven publisher preferences and button implementation; not a universal ranking guarantee. [Open primary source](https://developers.google.com/search/docs/appearance/preferred-sources) ## S46 · Googlebot crawling size clarification **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-03-31 Googlebot fetch size guidance: 2 MB for supported files except PDF, with headers included; separate resources fetched separately. [Open primary source](https://developers.google.com/search/blog/2026/03/crawler-blog-post) ## S47 · Model Context Protocol specification 2026-07-28 **Publisher:** Model Context Protocol · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-07-28 Versioned agent integration protocol; implementation must negotiate supported version and enforce security. [Open primary source](https://modelcontextprotocol.io/specification/2026-07-28) ## S48 · MCP security best practices, 2025-11-25 **Publisher:** Model Context Protocol · **Observed:** 2026-09-09 · **Document/announcement date:** 2025-11-25 Version pinned threat guidance: authorization, untrusted servers, SSRF and token/session risks; not the latest protocol contract. [Open primary source](https://modelcontextprotocol.io/docs/2025-11-25/tutorials/security/security_best_practices) ## S49 · MCP tools, 2026-07-28 **Publisher:** Model Context Protocol · **Observed:** 2026-09-09 · **Document/announcement date:** 2026-07-28 Tool interface metadata and human control; older examples can need migration. [Open primary source](https://modelcontextprotocol.io/specification/2026-07-28/server/tools) ## S50 · Video SEO best practices **Publisher:** Google · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Watch page eligibility, stable media resources and differences between video and ordinary web indexing. [Open primary source](https://developers.google.com/search/docs/appearance/video) ## S51 · actions/checkout official README **Publisher:** GitHub Actions · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Current checkout@v7 example and read only repository permissions; proposed workflow only, not executed on GitHub. [Open primary source](https://github.com/actions/checkout) ## S52 · actions/setup-python official README **Publisher:** GitHub Actions · **Observed:** 2026-09-09 · **Document/announcement date:** not assigned Current setup-python@v7 usage and Python version selection; proposed workflow only, not executed on GitHub. [Open primary source](https://github.com/actions/setup-python) * * * # Tier applicability and deliverable map Source: https://library.feedthejoe.com/reference/tier-applicability-map/ Shelf: Reference modules · Status: Reference · Published 2026-09-09 · Release 2026.09.12-g40 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. No prices, quotas or contractual terms were changed. Modules are selected by applicability; they are not an instruction to sell every task to every client. | Tier | Research additions to consult | Required inputs | Completion evidence | | --- | --- | --- | --- | | 01: FOUNDATION | URL lifecycle; release contracts; content delivery; crawler identity; field performance | Route inventory, existing URLs, stack, access policy | Approved route behavior and captured pre/post release checks | | 02: SEARCH VISIBILITY | Canonicalization; metadata; schema lifecycle; Search Console analysis | Target pages, consumer, country, eligible features | Indexability evidence and applicable metadata/schema validation | | 03: AI DOMINATION | Engine control matrix; Google/Bing AI performance; AI observation and attribution | Client permission policy and actual reporting availability | Separate crawl, impression, citation, referral and lead evidence; no visibility guarantee | | 04: ENTITY & AUTHORITY | Source provenance; evidence governance; fact register; organization schema | Verified business facts and source ownership | Consistent entity references and traceable claims; no fabricated authority | | 05: LOCAL DOMINATION | Location evidence; regional eligibility; real storefront schema boundary | Real staffed locations, service areas and original local evidence | Only justified location pages and eligible business representations | | 06: CONTENT & MULTIMEDIA AUTHORITY | Source provenance; social/video property reporting; publisher preferences | Editorial ownership, original evidence, image/video rights | Attributable content and platform specific measurement | | 07: SOCIAL & COMMUNITY | Social/video properties; AI referrals; client scope acceptance | Verified accounts, publication rights and attribution constraints | Measurable platform work without guaranteed backlinks or engagement | | 08: DATA, ANALYTICS & CONVERSION | GA4; metric contracts; AI attribution; observation protocol | Property access, event definitions, consent requirements | Documented denominators, attribution scope and qualified lead events | | 09: MONITORING & INTELLIGENCE | Research maintenance; crawler observability; source date conflict handling | Owner, review triggers, permitted logs and retention | Review ledger and alerts defined; scheduling is separate implementation | | 10: WORKFLOW & OPERATIONS | Release contracts; rollback; client scope; agent security; offline tools | Approvals, deployment path, owners and rollback authority | A reproducible release evidence packet and scoped acceptance | | 11: MARKETPLACE & RETAIL | Commerce consistency; merchant schema; URL lifecycle; faceted URLs | SKU/offer facts, feeds, platform and country eligibility | Agreement between visible prices, feeds and structured data | | 12: INTERNATIONAL | Regional Search eligibility; localized URL contracts | Target markets, languages, page equivalence, local expertise | Validated locale mappings and market specific acceptance | | 13: RETIRED | No reactivation or replacement invented | Existing retirement decision | Retirement preserved | | 14: ADVANCED & IMMERSIVE | Agent access security; client scope; release contracts; performance | Actual audience need, capability, threat model and budget | Bounded prototypes and tested access, not novelty based ranking claims | ## Scope rule Choose a tier only after the project intake and baseline. An existing WordPress business site, a Next.js application, a physical storefront, a service area business and a multiregional store do not share the same route, schema or account obligations. Deliverable acceptance belongs in the project contract; ranking and citation outcomes belong in a separately defined measurement plan. Use the [client scope module](https://library.feedthejoe.com/reference/framework-client-scope-acceptance/), project intake example and release acceptance example. The older item counts were not recertified as universally necessary or sufficient. * * * # Schema examples _Fictional, not deployable as supplied_ Source: https://library.feedthejoe.com/reference/schema-org/ Shelf: Reference modules · Status: Reference · Published 2026-09-09 · Release 2026.09.12-g40 These four files illustrate graph structure, not real businesses, credentials, offers, addresses or ratings. They pass local JSON syntax tests only. No live Rich Results Test, vocabulary validator, feature approval or client factual validation has been performed. Replace every `example.com`, fictional name, address, date, price and image with approved current facts. Do not publish a customer facing address for a service area business that has no genuine eligible storefront. No `AggregateRating` is included merely to make an example look complete. The product example is not a complete merchant feed or a guarantee of all shopping features. Before publication, validate the current intended feature, required fields, visible page consistency, resource URLs, permissions and safe HTML embedding. Use `Tools/seo_html_check.py` for limited saved-HTML checks and `Tools/jsonld_embed.py` for safe script serialization; neither certifies factual accuracy or rich result eligibility. See [schema lifecycle](https://library.feedthejoe.com/reference/framework-schema-lifecycle/), [current type reference](https://library.feedthejoe.com/reference/framework-schema-types-2026/) and [primary sources](https://library.feedthejoe.com/reference/source-register/), especially S20 to S23. * * * # Implementation templates Source: https://library.feedthejoe.com/reference/templates/ Shelf: Reference modules · Status: Reference · Published 2026-09-09 · Release 2026.09.12-g40 The 12 JSON files in this folder are working data contracts and fictional examples, not populated client reports. `null` means unknown or not yet measured; it must not be converted to zero. A draft or unapproved record is not authorization to publish, delete URLs or alter accounts. Start with `project-intake.example.json`, then complete the applicable source fact, URL, engine policy and metric records. Use the claim register for evidence, the release acceptance record for actual test output and the maintenance ledger for future changes. Keep Tier 13 retired in the client scope record. The example engine policy allows named search bots while denying selected training/product use tokens. It intentionally leaves unlisted consumers to the wildcard rule and is NOT a comprehensive opt out from all training. Google-Extended has additional grounding consequences. Review the [engine control matrix](https://library.feedthejoe.com/reference/framework-engine-control-matrix/) before generating any policy. No production key, private user record or live account configuration is included. The robots generator requires an approved policy unless explicitly run in example mode. * * * # Offline tools and test scope Source: https://library.feedthejoe.com/reference/tools/ Shelf: Reference modules · Status: Reference · Published 2026-09-09 · Release 2026.09.12-g40 Python 3.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. Run from the release root: ``` python3 -m unittest discover -s Tools/tests -v python3 Tools/library_audit.py . --output Reports/library-audit.json python3 Tools/seo_html_check.py saved-complete-page.html --expect index python3 Tools/seo_html_check.py saved-complete-page.html --canonical https://example.com/service/ python3 Tools/robots_policy.py Templates/engine-policy.example.json --allow-example --output Templates/robots.EXAMPLE.txt python3 Tools/jsonld_embed.py Schema.org/article-person.example.json --output article-example.html ``` `seo_html_check.py` evaluates a saved complete document, including title presence, duplicate canonicals, an explicit canonical contract, general/Googlebot meta noindex and JSON-LD syntax. It does not fetch headers, execute JavaScript, check real bot identity, determine CSS visibility or certify structured data eligibility. Header only noindex needs a separate live response test. Length outliers and missing canonical markup are not treated as universal Google errors. `robots_policy.py` rejects unapproved policies unless example mode is explicit. Marking a JSON field approved does not obtain real owner authorization. The generator repeats private path crawl exclusions in specific allowing groups, validates tokens and requires a same host sitemap in this implementation. It is not a complete robots parser or comprehensive opt out from every unlisted consumer. Authentication must protect private resources. `jsonld_embed.py` serializes JSON safely for a script element, including script breakout protection. It does not check that the facts are true, that a feature supports the graph or that fictional example values have been replaced. `library_audit.py` checks scoped local Markdown file targets, release JSON syntax, registered source IDs and the 146 preserved original hashes. It does not validate fragments, arbitrary HTML links, external URL availability, source truth or code embedded in legacy documents. The test suite uses synthetic fixtures. Passing results are evidence for those implemented checks, not end to end production validation. The original Jaccard script is preserved under `99-Originals` and was not run. ## 26 discipline extension See [Discipline utilities](https://library.feedthejoe.com/operating-model/disciplines-readme/) for the advisory router and strict evidence record checker, their CLI usage, test scope and limitations. These additions do not execute projects or authorize releases.