Janady13/thatstupidcomputer / private/standards/SEO-AIO-Library.txt · Lines 10501–12000

10501*A practical evidence chain for testing website inquiries, SMTP handling and controlled mailbox receipt.* 10502 10503> Editorial workbench: this is an unpublished methodology draft. No client results, credentials, real site test outcomes or owner approval are asserted. Remove this editorial note only after the actual publication review; do not publish the private library. 10504 10505A contact form’s success message is a statement made by the website. To interpret it, first determine which event causes the application to display it. 10506 10507It might mean that the browser accepted the fields, that the server received the request, that a record was persisted, or that a mail provider accepted a message. Those events are not interchangeable. A reliable inquiry process defines them explicitly and avoids promising a later outcome before it has evidence. 10508 10509## Start with one controlled message 10510 10511Use authorized synthetic data and a controlled destination mailbox. Assign a correlation reference that can connect the form request, application record, queue entry and provider response without exposing a real customer’s message. 10512 10513Record the relevant environment, deployed build and timestamps. A production test and a provider mock in a development test suite answer different questions; both can be useful, but they must be labeled accurately. 10514 10515## Verify the application contract 10516 10517The backend check should establish authoritative validation, handling of invalid input, durable acceptance where promised, retry behavior and errors. A browser’s client-side validation does not replace server-side controls. A timeout should not be silently converted into “delivered.” 10518 10519The user interface should describe the state the system actually knows. Depending on the application contract, “Your inquiry has been received for processing” may be more accurate than asserting final email delivery. That wording still needs to match actual durable handling; it is not a substitute for fixing a dropped request. 10520 10521## Trace the provider handoff 10522 10523After the application hands a message to a provider, preserve the provider/message identifier and inspect the subsequent evidence. SMTP specifies transport behavior and responses; a successful handoff does not by itself establish the final folder placement in every recipient’s mailbox. [SMTP specification](https://www.rfc-editor.org/rfc/rfc5321.html). 10524 10525A delivery specialist should distinguish provider acceptance, queue or bounce observations, authentication results and an actual controlled-mailbox observation. The absence of a visible bounce is not a direct observation of receipt. 10526 10527## Check authentication without damaging legitimate mail 10528 10529Inventory all legitimate sending streams before changing SPF, DKIM or DMARC policy. The website may not be the only authorized sender for the domain. Enforcement that fixes one path while blocking another is not a successful integrated repair. 10530 10531The core DMARC specification changed in May 2026: RFC 9989 obsoletes RFCs 7489 and 9091, with aggregate and failure reporting addressed separately by RFCs 9990 and 9991. This is a documentation update to account for, not an instruction to change production DNS blindly. [Current DMARC specification](https://www.rfc-editor.org/rfc/rfc9989.html), [aggregate reporting](https://www.rfc-editor.org/info/rfc9990/), [failure reporting](https://www.rfc-editor.org/info/rfc9991/). 10532 10533Provider requirements and actual received headers still matter. An authentication pass is not a promise that every message will be desirable to a receiver or placed in the inbox. [Gmail sender guidelines](https://support.google.com/a/answer/81126?hl=en). 10534 10535## Observe the mailbox and report the boundary 10536 10537For the tested destination, inspect authorized mailbox evidence and identify whether the synthetic message arrived and where it appeared. Redact sensitive header details before publication. If the reviewer lacks mailbox access or owner-supplied evidence, the receipt check remains blocked. 10538 10539Finally, reconcile analytics with the real application state. Counting a thank-you panel is not the same as counting a qualified inquiry. A second operator should repeat the agreed critical path when independent acceptance is required. 10540 10541The strongest defensible conclusion is bounded: this synthetic inquiry, on this build, through this sending path, reached this controlled destination at this time. That is more useful than an unsupported claim of universal “100% deliverability.” 10542 10543--- 10544 10545## Editorial handoff — not public article copy 10546 10547R13: confirm distinct usefulness and the actual audience. R14: verify current sources and every added result/credential claim. R20: approve any screenshots or proof artifacts for publication. Joseph: substantively review the final article and approve the exact author/byline. R08/R11: approve the actual canonical URL and truthful entity representation. R16: define measurement without implying guaranteed citations or inquiries. The suggested service action is appropriate only if the service is actually offered and its contact path works. 10548 10549============================================================================== 10550DOCUMENT 113 OF 135 10551Title: Browser coverage without overclaiming 10552Path: Publishing/Drafts/04-REAL-BROWSER-EVIDENCE.md 10553Group: drafts 10554Label: PUBLIC WORKBENCH · not approved 10555Review status: scope_stated_in_document 10556============================================================================== 10557 10558# Browser coverage without overclaiming 10559 10560*How to distinguish browser engines, branded products, device emulation and actual mobile testing.* 10561 10562> Editorial workbench: this is an unpublished methodology draft. No client results, credentials, real site test outcomes or owner approval are asserted. Remove this editorial note only after the actual publication review; do not publish the private library. 10563 10564“Tested in all browsers” is not a useful technical statement unless the report says which products, versions, platforms and interactions were actually tested. 10565 10566A browser engine test, a branded-browser test and an actual mobile-device test can expose different classes of problem. A responsible coverage report keeps those categories visible instead of collapsing them into a single green badge. 10567 10568## Name exactly what ran 10569 10570Playwright supports browser engines and specific branded-browser channels, but its WebKit build is not the same as launching the Safari application on a real iPhone. Its browser documentation also distinguishes the environments and binaries it uses. [Playwright browser documentation](https://playwright.dev/docs/browsers). 10571 10572A coverage row should identify the OS, browser name and version, engine/channel where relevant, device, input mode and test type. An emulated device setting may be useful for viewport and input assumptions, but it does not establish that the corresponding physical device was tested. 10573 10574## Test a task, not only a screenshot 10575 10576A page can look correct while its controls fail. Include the actual business journey: navigating to a service, opening contact, entering information, encountering an error, recovering from it and receiving an accurate confirmation. 10577 10578Native controls, focus, scrolling, viewport changes, file selection and back/forward behavior may matter depending on the application. Record what the user did and what happened. A screenshot is helpful evidence of appearance; it cannot prove that the server persisted a submission. 10579 10580## Keep accessibility coverage explicit 10581 10582Accessibility is not identical to visual browser compatibility. Keyboard sequence, focus visibility, names and relationships, error messages and assistive-technology behavior require their own evaluation. 10583 10584WCAG conformance considers whole pages and complete processes, with criteria that are not all established by automated tooling. A browser regression suite can detect some failures, but an automated score is not a full WCAG 2.2 AA verdict. [W3C conformance guidance](https://www.w3.org/WAI/WCAG22/Understanding/conformance), [WCAG 2.2](https://www.w3.org/TR/WCAG22/). 10585 10586The agreed matrix should therefore identify actual browser/screen-reader combinations and the manual processes evaluated. If a required combination is unavailable, report that gap rather than inferring a pass from another environment. 10587 10588## Use automation where it provides repeatability 10589 10590Automation is valuable for reproducing the same steps after a change, protecting known failures and checking many routes consistently. Its assertions must still match the requirement. “HTTP status is 200” does not prove that a form works or that a dialog can be operated with a keyboard. 10591 10592Keep provider mocks, synthetic fixtures and real integrations distinct. A reliable test report includes the build identity and enough safe evidence to reproduce failures. Broad automatic retries should not conceal a defect simply because one run eventually passed. 10593 10594## Accept the original failing case 10595 10596After the repair, repeat the specific environment and interaction that failed. Then run the relevant regression set to check that the change did not break other supported conditions. 10597 10598The final statement should describe actual coverage: the named environments passed the named journeys on the recorded build; other rows were not tested or remain blocked. That does not sound as sweeping as “works everywhere,” but it gives a business owner a clear basis for deciding whether the remaining risk is acceptable. 10599 10600--- 10601 10602## Editorial handoff — not public article copy 10603 10604R13: confirm distinct usefulness and the actual audience. R14: verify current sources and every added result/credential claim. R20: approve any screenshots or proof artifacts for publication. Joseph: substantively review the final article and approve the exact author/byline. R08/R11: approve the actual canonical URL and truthful entity representation. R16: define measurement without implying guaranteed citations or inquiries. The suggested service action is appropriate only if the service is actually offered and its contact path works. 10605 10606============================================================================== 10607DOCUMENT 114 OF 135 10608Title: Measure AI visibility without inventing attribution 10609Path: Publishing/Drafts/05-AI-VISIBILITY-EVIDENCE.md 10610Group: drafts 10611Label: PUBLIC WORKBENCH · not approved 10612Review status: scope_stated_in_document 10613============================================================================== 10614 10615# Measure AI visibility without inventing attribution 10616 10617*A clear separation between crawler access, search presence, citations, referrals and qualified inquiries.* 10618 10619> Editorial workbench: this is an unpublished methodology draft. No client results, credentials, real site test outcomes or owner approval are asserted. Remove this editorial note only after the actual publication review; do not publish the private library. 10620 10621AI visibility is not a single event. A crawler can request a page without the page becoming a cited source. An answer can cite a source without a reader visiting it. A referral visit can occur without a qualified inquiry. 10622 10623A useful measurement system keeps those observations separate and explains how each was obtained. 10624 10625## Name the engine and surface 10626 10627Start with the actual product being evaluated. A Google AI Search result, a Bing Webmaster Tools citation report and a ChatGPT search answer are not automatically interchangeable datasets. Record the query or prompt, surface, date, locale and any model or account context that the product exposes. 10628 10629When a field is not exposed, say so. Do not invent a model version or assume that one account’s answer represents every user. 10630 10631## Distinguish crawler purposes 10632 10633Providers document different bots and fetching mechanisms. OpenAI, for example, distinguishes OAI-SearchBot, GPTBot and ChatGPT-User; search crawling, training and user-triggered fetching are not the same function. Policies must be chosen for the intended consumer rather than copied universally. [OpenAI crawler documentation](https://developers.openai.com/api/docs/bots). 10634 10635A log entry should also be interpreted carefully: a claimed user-agent string alone is not sufficient identity proof. Access evidence supports an access claim. It does not establish a recommendation, model memory or lead. 10636 10637## Make the source useful before optimizing its packaging 10638 10639Google’s AI guidance places its generative Search on core SEO foundations and does not require a special AI file or special schema. The practical content goal is a useful supported answer that can be understood in context—not a collection of artificial pages designed only to trigger prompts. [Google AI optimization guidance](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide). 10640 10641For a technical service business, that may mean a documented troubleshooting method, a safe original example or an authorized case study with clear limits. A truthful author and a defensible source trail help readers assess the work. They do not guarantee selection by any engine. 10642 10643## Use an evidence ladder 10644 10645Keep at least these categories distinct: public delivery/access; observed indexing or search exposure; observed answer citation; referral session; qualified inquiry; and attributed revenue where the data supports it. 10646 10647Each category needs a source, date window, unit and scope. An observation of one answer should preserve the actual cited URL and enough context to reproduce the query. Counterexamples and missing citations belong in the record, too. Repeating only favorable prompts would distort the report. 10648 10649## Reconcile analytics carefully 10650 10651GA4’s current default-channel documentation includes an AI Assistant channel. Google AI Overviews and AI Mode remain classified under Organic Search. That distinction should be checked before building a custom reporting category and should not be mistaken for complete attribution of every AI-influenced visit. [GA4 channel definitions](https://support.google.com/analytics/answer/9756891?hl=en). 10652 10653Bing’s AI visibility reporting also has its own documented measures and surfaces. Citation measurements are useful visibility evidence, not a substitute for website or CRM outcomes. [Bing reporting documentation](https://blogs.bing.com/search/June-2026/New-AI-Visibility-Insights-in-Bing-Webmaster-Tools-Intents-Topics-Citation-Share-Compare). 10654 10655## Report observations, not inevitability 10656 10657The right conclusion identifies what improved, where it was observed and what remains uncertain. Public source quality, technical eligibility and clear measurement can all be improved without claiming that every model must recommend the business. 10658 10659For a business owner, the important question is not simply whether an AI mentioned the company. It is whether the work created useful discoverability and, when measurable, relevant opportunities—without confusing visibility with revenue. 10660 10661--- 10662 10663## Editorial handoff — not public article copy 10664 10665R13: confirm distinct usefulness and the actual audience. R14: verify current sources and every added result/credential claim. R20: approve any screenshots or proof artifacts for publication. Joseph: substantively review the final article and approve the exact author/byline. R08/R11: approve the actual canonical URL and truthful entity representation. R16: define measurement without implying guaranteed citations or inquiries. The suggested service action is appropriate only if the service is actually offered and its contact path works. 10666 10667============================================================================== 10668DOCUMENT 115 OF 135 10669Title: Independent acceptance is more than another green check 10670Path: Publishing/Drafts/06-INDEPENDENT-ACCEPTANCE.md 10671Group: drafts 10672Label: PUBLIC WORKBENCH · not approved 10673Review status: scope_stated_in_document 10674============================================================================== 10675 10676# Independent acceptance is more than another green check 10677 10678*Why fresh execution, a fixed contract and an honest reviewer relationship matter before declaring a website finished.* 10679 10680> Editorial workbench: this is an unpublished methodology draft. No client results, credentials, real site test outcomes or owner approval are asserted. Remove this editorial note only after the actual publication review; do not publish the private library. 10681 10682A builder’s tests are valuable. They are also bounded by the builder’s assumptions, fixtures and chosen assertions. Final acceptance asks a different question: does the delivered system satisfy the agreed requirement when someone verifies the actual result? 10683 10684That distinction becomes especially important when AI assistants perform several tasks. Asking the same assistant to “act as an independent reviewer” may provide a useful second pass, but the role label does not create a separate person, fresh access or genuine independence. 10685 10686## Freeze what success means 10687 10688Write the acceptance contract before interpreting the result. Identify the project, build, environment, required journeys, allowed exceptions and evidence needed. A requirement should not be silently weakened because a test failed. 10689 10690A legitimate scope change can happen, but it needs a recorded reason and renewed approval. The acceptance report should still make the difference visible. 10691 10692## Declare the review arrangement 10693 10694A self-review, a separately run AI review, another operator’s test and an external independent assessment are different arrangements. Describe the actual one and any relevant relationship or conflict. 10695 10696A separate execution run can reduce some kinds of dependence, but different names in a JSON file do not prove different people. Neither do they prove that the reviewer exercised judgment or inspected the evidence. The responsible owner must verify the arrangement rather than treating labels as credentials. 10697 10698## Re-execute critical outcomes 10699 10700For a website inquiry journey, fresh acceptance may include an independent public connection, a new synthetic submission, the promised application handling and an authorized controlled-mailbox observation. The exact checks depend on the approved scope. 10701 10702The verifier should inspect the declared build and environment, not an older local version that happened to pass. Raw artifacts, timestamps and negative-path outcomes matter more than a builder’s summary saying “all fixed.” Production readiness and release engineering practices emphasize controlled requirements and reliable operational transitions; the particular independence policy here is a deliberate operating design. [Production readiness](https://sre.google/sre-book/evolving-sre-engagement-model/), [release engineering](https://sre.google/sre-book/release-engineering/). 10703 10704## Know what automated evidence checks can prove 10705 10706A structural gate can detect a missing requirement, an inconsistent build identifier, an artifact that does not exist, a hash mismatch or a timestamp that contradicts the sequence. Those are useful checks. 10707 10708It cannot prove that the artifact tells the truth, that a mailbox was inspected, that a real iPhone was used, or that a reviewer is independent. A hash establishes byte identity, not the correctness of the statement inside the file. The evidence must still be evaluated by the responsible verifier. 10709 10710This is why a structural pass should never grant production or publication permission by itself. 10711 10712## Preserve blocked results 10713 10714Use a clear distinction between pass, fail, blocked and an explicitly permitted not-applicable result. If the required browser is unavailable or mailbox access has not been provided, that check is blocked. Calling it “probably fine” does not complete it. 10715 10716The release manager receives the bounded verdict and the unresolved risks. Actual deployment authority and recovery readiness remain separate decisions. If a material required condition is not met, the report should state that the release has not been accepted. 10717 10718## Make the final claim match the work 10719 10720A credible completion statement names the tested scope, actual reviewer arrangement, build, environment and limitations. It does not promise the absence of all defects or claim an external audit that never occurred. 10721 10722For the business owner, this is a practical safeguard: the final “done” corresponds to the customer journey and the approved contract, not merely to a confident builder or another green icon. 10723 10724--- 10725 10726## Editorial handoff — not public article copy 10727 10728R13: confirm distinct usefulness and the actual audience. R14: verify current sources and every added result/credential claim. R20: approve any screenshots or proof artifacts for publication. Joseph: substantively review the final article and approve the exact author/byline. R08/R11: approve the actual canonical URL and truthful entity representation. R16: define measurement without implying guaranteed citations or inquiries. The suggested service action is appropriate only if the service is actually offered and its contact path works. 10729 10730============================================================================== 10731DOCUMENT 116 OF 135 10732Title: Author, business and publication identity plan 10733Path: Publishing/ENTITY-AND-PUBLICATION-PLAN.md 10734Group: publishing 10735Label: PUBLIC WORKBENCH · not approved 10736Review status: scope_stated_in_document 10737============================================================================== 10738 10739# Author, business and publication identity plan 10740 10741## Verified inputs versus open decisions 10742 10743The user identifies as Joseph, a software developer and graphic designer, and supplies ThatDevPro.com and ThatDeveloperGuy.com as owned brands/domains. This package has not verified current legal business names, addresses, credentials, social profiles, certifications, staffing, live site ownership records, analytics or existing canonical architecture. Leave those fields unknown until authorized review supplies evidence. 10744 10745**Do not market the role library as 26 employees, 26 certifications or an external accreditation.** A supported description can explain that the workflow assigns specialist responsibilities and independent acceptance requirements. Publish an actual capability statement only after the owner confirms the offered work and evidence. 10746 10747## Proposed architecture, subject to approval 10748 10749A provisional option is a service-facing ThatDeveloperGuy site linked to original research/tools on ThatDevPro. This is not a migration recommendation. Inspect existing traffic, backlinks, branded demand, pages and business strategy before selecting a canonical publication home. One original article should have one approved public canonical location; sister-site links should be contextual, not automatic duplicate copies. 10750 10751Possible content structure: an expertise-methodology hub; distinct problem-solving articles; real service pages; genuine case studies with permission; source/methodology notes; an accurate author page; and a working contact path. Avoid thousands of synthetic role/city/keyword combinations. [Google people-first guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content), [spam policies](https://developers.google.com/search/docs/essentials/spam-policies). 10752 10753## Entity model 10754 10755Represent Joseph as a Person only with approved factual properties. Represent each actual business/organization distinctly; do not guess whether a domain is a legal entity, brand or trading name. Model each technical article as a document with real headline, author, publisher where appropriate, canonical page and actual dates. `TechArticle` is a vocabulary option, not a promise of a special search feature. [Schema.org Person](https://schema.org/Person), [Organization](https://schema.org/Organization), [TechArticle](https://schema.org/TechArticle). 10756 10757Stable proposed patterns, **not production IDs**, are `{approved_origin}/about/joseph/#person`, `{approved_origin}/#organization` and `{canonical_article_url}#article`. Do not deploy braces or placeholders. An organization ID may belong on a different approved canonical domain from the person or article; the relationship must reflect the actual publication arrangement. 10758 10759Only add `sameAs` for verified profiles of that exact entity. Do not use role reference pages, general Wikipedia subjects, programming-language pages or a made-up Wikidata identifier as identity links. Do not mark internal AI personas as authors or employees. Validate visible facts and graph consistency in addition to JSON syntax. [Google structured-data policies](https://developers.google.com/search/docs/appearance/structured-data/sd-policies). 10760 10761## Review record 10762 10763For each public artifact record owner approval, approved author name, exact bio/credential wording, canonical origin/path, distinct page purpose, evidence/source register, private-data review, actual publication date, modification date reason, schema decision, contact destination and measurement scope. The publication contract is blocked until those decisions are made. 10764 10765Independent corroboration can be a real editorial citation, a truthful authorized testimonial, an original contribution others reference or a verified professional profile. Label owned, paid and earned mentions separately; never fabricate them to complete a graph. 10766 10767============================================================================== 10768DOCUMENT 117 OF 135 10769Title: Public expertise layer — briefs and reviewable drafts 10770Path: Publishing/README.md 10771Group: publishing 10772Label: PUBLIC WORKBENCH · not approved 10773Review status: scope_stated_in_document 10774============================================================================== 10775 10776# Public expertise layer — briefs and reviewable drafts 10777 10778This folder is a **publication workbench**, not a ready-to-upload website. It contains 26 distinct role-linked briefs, six substantial methodology drafts and an identity/content plan. None is approved for publication or evidence that a client engagement happened. Do not publish the private library or its site-fact/log templates. 10779 10780## Use the material 10781 10782Choose a real buyer problem and an actually demonstrated capability. Review the relevant brief, add safe original evidence where the article makes experience/results claims, obtain Joseph's substantive review and approve a truthful byline. Run claims/privacy and technical publication checks. Choose one canonical host and an actual route before publishing. 10783 10784Methods articles can explain documented principles without claiming client results. Hypothetical examples must remain labeled. Candidate queries are ideas, not measured search volume. The aim is useful attributable work that may earn discovery and citations, not a guarantee of rankings or recognition. 10785 10786## Six methodology drafts 10787 10788- [Why SEO cannot repair a broken inquiry pipeline](Drafts/01-SEO-CANNOT-FIX-BROKEN-INQUIRIES.md) 10789- [A public website needs a public test](Drafts/02-PUBLIC-REACHABILITY.md) 10790- [Sent is not the same as received](Drafts/03-INQUIRY-DELIVERY-PROOF.md) 10791- [Browser coverage without overclaiming](Drafts/04-REAL-BROWSER-EVIDENCE.md) 10792- [Measure AI visibility without inventing attribution](Drafts/05-AI-VISIBILITY-EVIDENCE.md) 10793- [Independent acceptance is more than another green check](Drafts/06-INDEPENDENT-ACCEPTANCE.md) 10794 10795Read the [public identity plan](ENTITY-AND-PUBLICATION-PLAN.md), [discipline directory](../Library/Disciplines/README.md) and [publishing operating model](../Library/Disciplines/04-SEARCH-EXPERTISE-PUBLISHING.md). The 26 brief paths are also listed in `Research/discipline-role-registry.json`. 10796 10797============================================================================== 10798DOCUMENT 118 OF 135 10799Title: SEO / AIO Library — 26-Discipline Edition 10800Path: README.md 10801Group: expansion 10802Label: EXPANSION · source-linked operating design 10803Review status: scope_stated_in_document 10804============================================================================== 10805 10806# SEO / AIO Library — 26-Discipline Edition 10807 10808**Release:** 2026.09.09-d26 · **Prepared for:** Joseph · **Date:** 9 September 2026. 10809 10810Open **START-HERE.html** for the integrated offline browser. It now includes all 26 professional role charters, their operating model, cross-discipline playbooks, public-content workbench and the prior current/legacy library. Keep the extracted folder intact for links to JSON, prompts, code and historical originals. 10811 10812## What to use first 10813 10814Read [the expansion report](Research/DISCIPLINE-EXPANSION-REPORT.md), then [the discipline directory](Library/Disciplines/README.md). `CODEX-START-HERE.txt` provides a copy-and-paste starting instruction. The [integration guide](Library/Disciplines/05-INTEGRATION-GUIDE.md) explains actual project placement; downloading this package does not install it into another repository. 10815 10816**Private operating layer:** 26 source-linked charters and 26 standalone prompts; advisory task routing; evidence and handoff contracts; scope/ownership/conflict rules; eight critical-path playbooks; and honest acceptance/independence checks. 10817 10818**Public expertise layer:** 26 distinct problem-led publication briefs and six methodology drafts, with proof requirements, truthful author/entity planning, canonical-home review and measurement boundaries. They are unapproved workbench material, not fabricated case studies or evidence of 26 employees/credentials. Do not publish internal configuration or raw evidence. 10819 10820## Tools and validation 10821 10822The two new Python utilities are offline and standard-library-only: `Tools/discipline_router.py` proposes task context; `Tools/evidence_gate.py` validates records and artifact hashes. Neither performs the task, establishes evidence truth, authenticates independent reviewers nor authorizes a release. The template records intentionally fail until completed with actual approved scope and evidence. 10823 10824Read the [tools guide](Tools/DISCIPLINES-README.md) and [current validation report](Reports/DISCIPLINE-VALIDATION.md). Prior validation reports remain historical records of the baseline edition and are not new production tests. 10825 10826## Compatibility and boundaries 10827 10828All 146 unique original files in `99-Originals/` remain byte-for-byte intact. Existing tier numbering, names, pricing and promises were not changed; commercial Tier 13 remains retired. Source-linked new work does not make the retained legacy corpus fully verified. 10829 10830The source supplement contains 49 primary-source records, some overlapping the baseline's 52 records; do not add them together as unique sources. The 26-role taxonomy and routing/acceptance policies are a custom operating design, not a universal regulated job classification. 10831 10832No live website, Bubbles configuration, DNS, mailbox, repository, account or public profile was inspected or changed by the local build/validation work. Provider documentation was researched separately. Publishing and genuine project evidence remain subject to actual owner approval and access. 10833 10834============================================================================== 10835DOCUMENT 119 OF 135 10836Title: 26-discipline validation — actual local results 10837Path: Reports/DISCIPLINE-VALIDATION.md 10838Group: expansion 10839Label: EXPANSION · local delivery record 10840Review status: scope_stated_in_document 10841============================================================================== 10842 10843# 26-discipline validation — actual local results 10844 10845**Release:** 2026.09.09-d26. These are artifact/tool validation results, not production-site acceptance or an independent external audit. 10846 10847## Executed results 10848 10849| Check family | Result | Boundary | 10850| --- | --- | --- | 10851| Utility unit tests | **84 passed**: 24 baseline + 60 new | Local synthetic fixtures; no real website/account | 10852| CLI smoke tests | **6 passed** | Actual local invocation, overwrite rejection, template blocking and malformed-input handling | 10853| Browser interaction checks | **23 passed** | Generated HTML rendered in headless Chromium 144.0.7559.96 through `set_content` | 10854| Role coverage | **26 exact IDs** with charter, prompt, brief, sources and handoffs | Presence/linkage, not 26 executed specialist audits | 10855| Preserved originals | **146 hashes verified** | Original bytes preserved, not all legacy facts validated | 10856| Local Markdown file targets | **3892 checked; zero missing/outside targets** | No Markdown-fragment or external-URL completeness claim | 10857| Markdown files audited | **267** | Active Library, Publishing, Templates, Tools, Research, Reports and root | 10858| JSON files parsed | **60** | Historical originals excluded; parsing is not semantic truth | 10859 10860The unit tests exercise routing for forms, DNS/tailnet, outages, AI citations, mail policy, explicit overrides and unknown tasks; bounded context packs; gate rejection of missing/blocked/failing checks, absent or changed files, path traversal, symlink escapes, contract/hash/build/run mismatches, reused identities, weak independence declarations, unauthorized exceptions, duplicate IDs/keys, future/naive timestamps, placeholders and publication-review gaps. Synthetic structurally valid fixtures are explicitly not client evidence. 10861 10862## Browser review 10863 10864Verified report load, document counts, all 26 role charters, role/full-text search, current DMARC references, internal brief navigation, history restoration, prompt companion paths, legacy boundaries, six draft entries, sanitized article DOM, keyboard-scrollable table regions, no horizontal overflow at a simulated 390-pixel viewport and no automatic external requests or JavaScript runtime errors. Desktop and narrow screenshots were visually inspected for legibility and layout. 10865 10866Local HTTP navigation was blocked by the environment with `ERR_BLOCKED_BY_ADMINISTRATOR`. The generated HTML was therefore rendered using Chromium `set_content`, not through a hosted live site or a successfully navigated local HTTP origin. Actual Safari, Firefox, branded Chrome, physical iPhone/Android and assistive-technology combinations were **not tested**. These checks do not establish full WCAG 2.2 AA conformance. 10867 10868## Gate truth boundary 10869 10870The evidence checker can detect inconsistent records and verify local bytes. It cannot authenticate an approval, a human identity, reviewer independence or the truth of a captured statement. Every structural pass retains `authorization_granted: false`, `external_truth_verified: false` and `identity_or_independence_authenticated: false`. Template acceptance records intentionally fail; no production acceptance record has been fabricated. 10871 10872## Reports and reproducibility 10873 10874- [Unit output](discipline-unit-tests.txt) 10875- [CLI smoke results](discipline-cli-smoke-tests.json) 10876- [Browser results and limits](discipline-browser-qa.json) 10877- [Library integrity result](discipline-library-audit.json) 10878- [Desktop screenshot](browser-desktop.png) and [simulated narrow screenshot](browser-mobile.png) 10879 10880Run `python3 -m unittest discover -s Tools/tests -v` and `python3 Tools/library_audit.py .` from the extracted library root. The original legacy reports remain historical baseline snapshots. No external site, Bubbles service, DNS record, mailbox, analytics account, repository or persistent Library folder was changed. 10881 10882============================================================================== 10883DOCUMENT 120 OF 135 10884Title: Executed validation — 2026.09.09 10885Path: Reports/VALIDATION.md 10886Group: baseline 10887Label: BASELINE · historical report 10888Review status: scope_stated_in_document 10889============================================================================== 10890 10891# Executed validation — 2026.09.09 10892 10893## New utility tests 10894 10895All 24 unit tests passed locally. Exact output is in [unit-tests.txt](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. 10896 10897## Release integrity 10898 10899The [library audit result](library-audit.json) 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. 10900 10901The check does not test external URL availability, Markdown fragment anchors, factual entailment, live indexing, application execution or rich-result eligibility. 10902 10903## Browser behavior 10904 10905The [browser QA result](browser-qa.json) 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. 10906 10907The 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. 10908 10909## Manifest scope 10910 10911`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. 10912 10913============================================================================== 10914DOCUMENT 121 OF 135 10915Title: SEO library audit and research update 10916Path: Research/AUDIT-REPORT.md 10917Group: baseline 10918Label: BASELINE · historical report 10919Review status: scope_stated_in_document 10920============================================================================== 10921 10922# SEO library audit and research update 10923 10924**Prepared for Joseph · Research snapshot: 9 September 2026 · Release: 2026.09.09** 10925 10926## Executive assessment 10927 10928The 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. 10929 10930This 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. 10931 10932The 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](COVERAGE-MATRIX.md) discloses the treatment of every unique original. 10933 10934## 1. What the archive actually contained 10935 10936| Measure | Observed result | 10937| --- | --- | 10938| ZIP entries, including directories and macOS metadata | 812 | 10939| Content files across the four sets | 511 | 10940| Unique file contents, by SHA-256 | 146 | 10941| Redundant content copies | 365 | 10942| Unique Markdown files | 143 | 10943| Other unique files | One Python, one JSON, one TXT | 10944| Approximate unique original word count | 1,047,235 | 10945| Broken local inline Markdown targets in the original scan | 157, across 39 files | 10946| Distinct embedded legacy URLs inventoried | 1,758 | 10947 10948The 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. 10949 10950The 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. 10951 10952The 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. 10953 10954## 2. Audit and research method 10955 10956The 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. 10957 10958A 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. 10959 10960The 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. 10961 10962When 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–S05, S21, S48] 10963 10964## 3. High-impact research findings 10965 10966### Current AI reporting needs a different measurement model 10967 10968Google 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] 10969 10970The 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. 10971 10972GA4'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] 10973 10974Bing'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] 10975 10976### Technical eligibility is not a secret optimization formula 10977 10978Google'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] 10979 10980The 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] 10981 10982The 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. 10983 10984### Crawler permissions need purpose-specific controls 10985 10986The 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–S13] 10987 10988The 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. 10989 10990This 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. 10991 10992### Structured-data eligibility must have a lifecycle 10993 10994Google 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] 10995 10996Review 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] 10997 10998The 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. 10999 11000### Route and rendering instructions needed safety boundaries 11001 11002Targeted 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] 11003 11004The 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] 11005 11006The 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–S27] 11007 11008## 4. What was actually changed 11009 11010The 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. 11011 11012Five 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. 11013 11014The 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. 11015 11016The 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. 11017 11018## 5. Operating assets and acceptance 11019 11020The 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. 11021 11022Four 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. 11023 11024Twenty-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] 11025 11026The 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. 11027 11028## 6. How to apply the updated library to real work 11029 11030Start 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. 11031 11032Next, 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. 11033 11034Establish 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. 11035 11036Deploy 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. 11037 11038## 7. What remains unverified 11039 11040The 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. 11041 11042The 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. 11043 11044Future 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. 11045 11046## Conclusion 11047 11048The 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. 11049 11050Use 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. 11051 11052## Supporting records 11053 11054[Primary sources](SOURCE-REGISTER.md) · [28 findings](FINDINGS.md) · [Coverage matrix](COVERAGE-MATRIX.md) · [Tier applicability](TIER-APPLICABILITY-MAP.md) · [Remaining review queue](REMAINING-REVIEW-QUEUE.md) · [Change log](../CHANGELOG.md) · [Tool boundaries](../Tools/README.md) 11055 11056============================================================================== 11057DOCUMENT 122 OF 135 11058Title: Coverage matrix — every unique original 11059Path: Research/COVERAGE-MATRIX.md 11060Group: baseline 11061Label: REFERENCE · scope stated in document 11062Review status: scope_stated_in_document 11063============================================================================== 11064 11065# Coverage matrix — every unique original 11066 11067This 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. 11068 11069| Original unique file | Current treatment | Active document | Preserved original | 11070| --- | --- | --- | --- | 11071| `EO-COPY-PASTE-PLAYBOOK.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/EO-COPY-PASTE-PLAYBOOK.md) | [Original](../99-Originals/Production%20Customer%20Tiers/EO-COPY-PASTE-PLAYBOOK.md) | 11072| `LOCATION-PAGE-FRAMEWORK.md` | PATCHED · legacy remainder | [Open](../Library/LOCATION-PAGE-FRAMEWORK.md) | [Original](../99-Originals/LOCATION-PAGE-FRAMEWORK.md) | 11073| `SEO-Search-Appearance.md` | LEGACY · not fully verified | [Open](../Library/Framework/SEO-Search-Appearance.md) | [Original](../99-Originals/Framework/SEO-Search-Appearance.md) | 11074| `SERP-Optimization.md` | LEGACY · not fully verified | [Open](../Library/Framework/SERP-Optimization.md) | [Original](../99-Originals/Framework/SERP-Optimization.md) | 11075| `audit-baseline-manifest.txt` | HISTORY · not active | Historical only | [Original](../99-Originals/Framework/audit-baseline-manifest.txt) | 11076| `build-log.md` | LEGACY · not fully verified | [Open](../Library/Framework/build-log.md) | [Original](../99-Originals/Framework/build-log.md) | 11077| `framework-11ty.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-11ty.md) | [Original](../99-Originals/Framework/framework-11ty.md) | 11078| `framework-accessibility.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-accessibility.md) | [Original](../99-Originals/Framework/framework-accessibility.md) | 11079| `framework-agenticaisearch.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-agenticaisearch.md) | [Original](../99-Originals/Framework/framework-agenticaisearch.md) | 11080| `framework-ai-content-workflow.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-ai-content-workflow.md) | [Original](../99-Originals/Framework/framework-ai-content-workflow.md) | 11081| `framework-aicitations.md` | REWRITTEN · researched | [Open](../Library/Framework/framework-aicitations.md) | [Original](../99-Originals/Framework/framework-aicitations.md) | 11082| `framework-aioverviews.md` | REWRITTEN · researched | [Open](../Library/Framework/framework-aioverviews.md) | [Original](../99-Originals/Framework/framework-aioverviews.md) | 11083| `framework-aioverviews.outline.md` | LEGACY · not fully verified | [Open](../Library/Framework/outlines/framework-aioverviews.outline.md) | [Original](../99-Originals/Framework/outlines/framework-aioverviews.outline.md) | 11084| `framework-aso.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-aso.md) | [Original](../99-Originals/Framework/framework-aso.md) | 11085| `framework-astro.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-astro.md) | [Original](../99-Originals/Framework/framework-astro.md) | 11086| `framework-astrohugo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-astrohugo.md) | [Original](../99-Originals/Framework/framework-astrohugo.md) | 11087| `framework-attribution.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-attribution.md) | [Original](../99-Originals/Framework/framework-attribution.md) | 11088| `framework-bigcommerce.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-bigcommerce.md) | [Original](../99-Originals/Framework/framework-bigcommerce.md) | 11089| `framework-boundaries.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-boundaries.md) | [Original](../99-Originals/Framework/framework-boundaries.md) | 11090| `framework-brandvoice.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-brandvoice.md) | [Original](../99-Originals/Framework/framework-brandvoice.md) | 11091| `framework-clientonboarding.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-clientonboarding.md) | [Original](../99-Originals/Framework/framework-clientonboarding.md) | 11092| `framework-competitoraudit.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-competitoraudit.md) | [Original](../99-Originals/Framework/framework-competitoraudit.md) | 11093| `framework-contentaudit.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-contentaudit.md) | [Original](../99-Originals/Framework/framework-contentaudit.md) | 11094| `framework-contentbriefs.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-contentbriefs.md) | [Original](../99-Originals/Framework/framework-contentbriefs.md) | 11095| `framework-contentfirst.md` | REWRITTEN · researched | [Open](../Library/Framework/framework-contentfirst.md) | [Original](../99-Originals/Framework/framework-contentfirst.md) | 11096| `framework-contentrefresh.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-contentrefresh.md) | [Original](../99-Originals/Framework/framework-contentrefresh.md) | 11097| `framework-coreupdates.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-coreupdates.md) | [Original](../99-Originals/Framework/framework-coreupdates.md) | 11098| `framework-cro.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-cro.md) | [Original](../99-Originals/Framework/framework-cro.md) | 11099| `framework-cross-stack-implementation.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-cross-stack-implementation.md) | [Original](../99-Originals/Framework/framework-cross-stack-implementation.md) | 11100| `framework-digitalpr.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-digitalpr.md) | [Original](../99-Originals/Framework/framework-digitalpr.md) | 11101| `framework-drupal.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-drupal.md) | [Original](../99-Originals/Framework/framework-drupal.md) | 11102| `framework-ecommerceseo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-ecommerceseo.md) | [Original](../99-Originals/Framework/framework-ecommerceseo.md) | 11103| `framework-eeat.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-eeat.md) | [Original](../99-Originals/Framework/framework-eeat.md) | 11104| `framework-entitysalience.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-entitysalience.md) | [Original](../99-Originals/Framework/framework-entitysalience.md) | 11105| `framework-featuredsnippets.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-featuredsnippets.md) | [Original](../99-Originals/Framework/framework-featuredsnippets.md) | 11106| `framework-finance-seo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-finance-seo.md) | [Original](../99-Originals/Framework/framework-finance-seo.md) | 11107| `framework-formoptimization.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-formoptimization.md) | [Original](../99-Originals/Framework/framework-formoptimization.md) | 11108| `framework-ga4.md` | REWRITTEN · researched | [Open](../Library/Framework/framework-ga4.md) | [Original](../99-Originals/Framework/framework-ga4.md) | 11109| `framework-gscanalysis.md` | REWRITTEN · researched | [Open](../Library/Framework/framework-gscanalysis.md) | [Original](../99-Originals/Framework/framework-gscanalysis.md) | 11110| `framework-hcs.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-hcs.md) | [Original](../99-Originals/Framework/framework-hcs.md) | 11111| `framework-headless.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-headless.md) | [Original](../99-Originals/Framework/framework-headless.md) | 11112| `framework-healthcare-seo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-healthcare-seo.md) | [Original](../99-Originals/Framework/framework-healthcare-seo.md) | 11113| `framework-hreflang.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-hreflang.md) | [Original](../99-Originals/Framework/framework-hreflang.md) | 11114| `framework-html-app-pwa-meta.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-app-pwa-meta.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-app-pwa-meta.md) | 11115| `framework-html-canonical-alternate.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-canonical-alternate.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-canonical-alternate.md) | 11116| `framework-html-favicon-icons.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-favicon-icons.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-favicon-icons.md) | 11117| `framework-html-meta-author.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-author.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-author.md) | 11118| `framework-html-meta-charset.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-charset.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-charset.md) | 11119| `framework-html-meta-color-scheme.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-color-scheme.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-color-scheme.md) | 11120| `framework-html-meta-content-language.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-content-language.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-content-language.md) | 11121| `framework-html-meta-copyright.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-copyright.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-copyright.md) | 11122| `framework-html-meta-generator.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-generator.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-generator.md) | 11123| `framework-html-meta-keywords.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-keywords.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-keywords.md) | 11124| `framework-html-meta-referrer.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-referrer.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-referrer.md) | 11125| `framework-html-meta-refresh.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-refresh.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-refresh.md) | 11126| `framework-html-meta-robots.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-robots.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-robots.md) | 11127| `framework-html-meta-theme-color.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-theme-color.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-theme-color.md) | 11128| `framework-html-meta-viewport.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-viewport.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-meta-viewport.md) | 11129| `framework-html-open-graph.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-open-graph.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-open-graph.md) | 11130| `framework-html-search-engine-verification.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-search-engine-verification.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-search-engine-verification.md) | 11131| `framework-html-twitter-cards.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-twitter-cards.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-html-twitter-cards.md) | 11132| `framework-http-2xx-status-codes.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-2xx-status-codes.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-2xx-status-codes.md) | 11133| `framework-http-3xx-status-codes.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-3xx-status-codes.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-3xx-status-codes.md) | 11134| `framework-http-4xx-status-codes.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-4xx-status-codes.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-4xx-status-codes.md) | 11135| `framework-http-5xx-status-codes.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-5xx-status-codes.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-5xx-status-codes.md) | 11136| `framework-http-caching-headers.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-caching-headers.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-caching-headers.md) | 11137| `framework-http-content-headers.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-content-headers.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-content-headers.md) | 11138| `framework-http-cors-headers.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-cors-headers.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-cors-headers.md) | 11139| `framework-http-performance-headers.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-performance-headers.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-performance-headers.md) | 11140| `framework-http-rate-control-headers.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-rate-control-headers.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-rate-control-headers.md) | 11141| `framework-http-request-headers.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-request-headers.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-request-headers.md) | 11142| `framework-http-security-headers.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-security-headers.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-security-headers.md) | 11143| `framework-http-seo-headers.md` | LEGACY · not fully verified | [Open](../Library/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-seo-headers.md) | [Original](../99-Originals/Crawler%20Signal%20Refrence%20for%20troubleshooting/framework-http-seo-headers.md) | 11144| `framework-hugo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-hugo.md) | [Original](../99-Originals/Framework/framework-hugo.md) | 11145| `framework-hydrogen.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-hydrogen.md) | [Original](../99-Originals/Framework/framework-hydrogen.md) | 11146| `framework-imageseo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-imageseo.md) | [Original](../99-Originals/Framework/framework-imageseo.md) | 11147| `framework-infogain.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-infogain.md) | [Original](../99-Originals/Framework/framework-infogain.md) | 11148| `framework-initialaudit.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-initialaudit.md) | [Original](../99-Originals/Framework/framework-initialaudit.md) | 11149| `framework-internallinking.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-internallinking.md) | [Original](../99-Originals/Framework/framework-internallinking.md) | 11150| `framework-international.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-international.md) | [Original](../99-Originals/Framework/framework-international.md) | 11151| `framework-jekyll.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-jekyll.md) | [Original](../99-Originals/Framework/framework-jekyll.md) | 11152| `framework-keywordresearch.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-keywordresearch.md) | [Original](../99-Originals/Framework/framework-keywordresearch.md) | 11153| `framework-knowledgegraph.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-knowledgegraph.md) | [Original](../99-Originals/Framework/framework-knowledgegraph.md) | 11154| `framework-legal-seo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-legal-seo.md) | [Original](../99-Originals/Framework/framework-legal-seo.md) | 11155| `framework-linkbuilding.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-linkbuilding.md) | [Original](../99-Originals/Framework/framework-linkbuilding.md) | 11156| `framework-localseo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-localseo.md) | [Original](../99-Originals/Framework/framework-localseo.md) | 11157| `framework-magento.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-magento.md) | [Original](../99-Originals/Framework/framework-magento.md) | 11158| `framework-masterindex.md` | REBUILT · navigation | [Open](../Library/Framework/framework-masterindex.md) | [Original](../99-Originals/Framework/framework-masterindex.md) | 11159| `framework-mcp.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-mcp.md) | [Original](../99-Originals/Framework/framework-mcp.md) | 11160| `framework-migration.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-migration.md) | [Original](../99-Originals/Framework/framework-migration.md) | 11161| `framework-mobileseo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-mobileseo.md) | [Original](../99-Originals/Framework/framework-mobileseo.md) | 11162| `framework-multiengine-tradeoffs.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-multiengine-tradeoffs.md) | [Original](../99-Originals/Framework/framework-multiengine-tradeoffs.md) | 11163| `framework-multimodalsearch.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-multimodalsearch.md) | [Original](../99-Originals/Framework/framework-multimodalsearch.md) | 11164| `framework-newsseo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-newsseo.md) | [Original](../99-Originals/Framework/framework-newsseo.md) | 11165| `framework-nextjs.md` | REWRITTEN · researched | [Open](../Library/Framework/framework-nextjs.md) | [Original](../99-Originals/Framework/framework-nextjs.md) | 11166| `framework-nuxt.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-nuxt.md) | [Original](../99-Originals/Framework/framework-nuxt.md) | 11167| `framework-ongoingaudit.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-ongoingaudit.md) | [Original](../99-Originals/Framework/framework-ongoingaudit.md) | 11168| `framework-pageexperience.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-pageexperience.md) | [Original](../99-Originals/Framework/framework-pageexperience.md) | 11169| `framework-performance.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-performance.md) | [Original](../99-Originals/Framework/framework-performance.md) | 11170| `framework-perplexityspaces.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-perplexityspaces.md) | [Original](../99-Originals/Framework/framework-perplexityspaces.md) | 11171| `framework-ppc-seo-coordination.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-ppc-seo-coordination.md) | [Original](../99-Originals/Framework/framework-ppc-seo-coordination.md) | 11172| `framework-pricing.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-pricing.md) | [Original](../99-Originals/Framework/framework-pricing.md) | 11173| `framework-react.md` | PATCHED · legacy remainder | [Open](../Library/Framework/framework-react.md) | [Original](../99-Originals/Framework/framework-react.md) | 11174| `framework-realestate-seo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-realestate-seo.md) | [Original](../99-Originals/Framework/framework-realestate-seo.md) | 11175| `framework-remix.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-remix.md) | [Original](../99-Originals/Framework/framework-remix.md) | 11176| `framework-reporting.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-reporting.md) | [Original](../99-Originals/Framework/framework-reporting.md) | 11177| `framework-robotstxt-crawlbudget.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-robotstxt-crawlbudget.md) | [Original](../99-Originals/Framework/framework-robotstxt-crawlbudget.md) | 11178| `framework-saas-seo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-saas-seo.md) | [Original](../99-Originals/Framework/framework-saas-seo.md) | 11179| `framework-saas-website-builders.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-saas-website-builders.md) | [Original](../99-Originals/Framework/framework-saas-website-builders.md) | 11180| `framework-schema-types-2026.md` | REWRITTEN · researched | [Open](../Library/Framework/framework-schema-types-2026.md) | [Original](../99-Originals/Framework/framework-schema-types-2026.md) | 11181| `framework-schema.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-schema.md) | [Original](../99-Originals/Framework/framework-schema.md) | 11182| `framework-searchgpt.md` | REWRITTEN · researched | [Open](../Library/Framework/framework-searchgpt.md) | [Original](../99-Originals/Framework/framework-searchgpt.md) | 11183| `framework-security.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-security.md) | [Original](../99-Originals/Framework/framework-security.md) | 11184| `framework-shopify.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-shopify.md) | [Original](../99-Originals/Framework/framework-shopify.md) | 11185| `framework-spampolicies.md` | REWRITTEN · researched | [Open](../Library/Framework/framework-spampolicies.md) | [Original](../99-Originals/Framework/framework-spampolicies.md) | 11186| `framework-sqrg.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-sqrg.md) | [Original](../99-Originals/Framework/framework-sqrg.md) | 11187| `framework-sveltekit.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-sveltekit.md) | [Original](../99-Originals/Framework/framework-sveltekit.md) | 11188| `framework-tailwind.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-tailwind.md) | [Original](../99-Originals/Framework/framework-tailwind.md) | 11189| `framework-technicalseo.md` | PATCHED · legacy remainder | [Open](../Library/Framework/framework-technicalseo.md) | [Original](../99-Originals/Framework/framework-technicalseo.md) | 11190| `framework-topicalauthority.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-topicalauthority.md) | [Original](../99-Originals/Framework/framework-topicalauthority.md) | 11191| `framework-trustsignals.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-trustsignals.md) | [Original](../99-Originals/Framework/framework-trustsignals.md) | 11192| `framework-uxseo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-uxseo.md) | [Original](../99-Originals/Framework/framework-uxseo.md) | 11193| `framework-videoseo.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-videoseo.md) | [Original](../99-Originals/Framework/framework-videoseo.md) | 11194| `framework-visualsearch.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-visualsearch.md) | [Original](../99-Originals/Framework/framework-visualsearch.md) | 11195| `framework-voicesearch.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-voicesearch.md) | [Original](../99-Originals/Framework/framework-voicesearch.md) | 11196| `framework-webflow.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-webflow.md) | [Original](../99-Originals/Framework/framework-webflow.md) | 11197| `framework-wordpress.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-wordpress.md) | [Original](../99-Originals/Framework/framework-wordpress.md) | 11198| `framework-ymyl.md` | LEGACY · not fully verified | [Open](../Library/Framework/framework-ymyl.md) | [Original](../99-Originals/Framework/framework-ymyl.md) | 11199| `growing-search-console-impressions-2026 (1).md` | LEGACY · not fully verified | [Open](../Library/growing-search-console-impressions-2026%20%281%29.md) | [Original](../99-Originals/growing-search-console-impressions-2026%20%281%29.md) | 11200| `jaccard-ruthless-check-data.json` | HISTORY · not active | Historical only | [Original](../99-Originals/jaccard-ruthless-check-data.json) | 11201| `jaccard-ruthless-check-report.md` | HISTORY · not active | Historical only | [Original](../99-Originals/jaccard-ruthless-check-report.md) | 11202| `jaccard-ruthless-check.py` | HISTORY · not active | Historical only | [Original](../99-Originals/jaccard-ruthless-check.py) | 11203| `tier-eight.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-eight.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-eight.md) | 11204| `tier-eleven.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-eleven.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-eleven.md) | 11205| `tier-five.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-five.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-five.md) | 11206| `tier-four.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-four.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-four.md) | 11207| `tier-fourteen.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-fourteen.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-fourteen.md) | 11208| `tier-nine.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-nine.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-nine.md) | 11209| `tier-one.md` | PATCHED · legacy remainder | [Open](../Library/Production%20Customer%20Tiers/tier-one.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-one.md) | 11210| `tier-seven.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-seven.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-seven.md) | 11211| `tier-six.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-six.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-six.md) | 11212| `tier-ten.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-ten.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-ten.md) | 11213| `tier-thirteen.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-thirteen.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-thirteen.md) | 11214| `tier-three.md` | PATCHED · legacy remainder | [Open](../Library/Production%20Customer%20Tiers/tier-three.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-three.md) | 11215| `tier-twelve.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-twelve.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-twelve.md) | 11216| `tier-two.md` | LEGACY · not fully verified | [Open](../Library/Production%20Customer%20Tiers/tier-two.md) | [Original](../99-Originals/Production%20Customer%20Tiers/tier-two.md) | 11217 11218============================================================================== 11219DOCUMENT 123 OF 135 11220Title: 26-Discipline Expansion — Research and Delivery Report 11221Path: Research/DISCIPLINE-EXPANSION-REPORT.md 11222Group: expansion 11223Label: EXPANSION · local delivery record 11224Review status: scope_stated_in_document 11225============================================================================== 11226 11227# 26-Discipline Expansion — Research and Delivery Report 11228 11229**Release:** 2026.09.09-d26 · **Date:** 9 September 2026 · **Prepared for:** Joseph. 11230 11231## Delivered scope 11232 11233The updated SEO library now contains all **26 user-requested professional responsibilities**, with the original numbering preserved. Each role has a distinct accountable scope, exclusions, activation signals, minimum inputs, a practical diagnostic sequence, evidence requirements, acceptance conditions, failure modes, named handoffs, current source references, a standalone AI prompt and a public-content brief. 11234 11235The expansion separates two goals: making an AI assistant perform the right specialist workflow, and creating useful public evidence of actual expertise. A private prompt library cannot itself produce public search exposure. The role taxonomy is a custom operating design, not a claim of 26 employees, credentials or universally separate regulated professions. 11236 11237## Added assets 11238 11239| Asset | Count | Purpose | 11240| --- | --- | --- | 11241| Detailed role charters | 26 | Accountable specialist procedures and scope boundaries | 11242| Standalone specialist prompts | 26 | Explicit task assignment and evidence/permission rules | 11243| Cross-discipline playbooks | 8 | Critical-path ownership, evidence and acceptance | 11244| New active Library Markdown documents | 44 | Charters, operating model, navigation and playbooks | 11245| Evidence-led publication briefs | 26 | Distinct buyer questions, proof and review requirements | 11246| Methodology article drafts | 6 | Substantial sourced drafts; no invented client case studies | 11247| New discipline JSON templates | 13 | Private intake, facts, findings, handoffs, coverage and acceptance | 11248| Primary-source supplement records | 49 | Current standards and official product/engine documentation | 11249| New executable offline utilities | 2 | Advisory routing and evidence-record consistency | 11250| New utility unit tests | 60 | Positive and failure-path behavior | 11251| Total utility tests executed | 84 | Includes the previous edition's 24 tests | 11252 11253The six article bodies contain approximately **3,344 words**, excluding editorial handoff notes. They remain unpublished, unapproved methodology drafts. The 26 briefs are not instructions to mass-publish nearly identical role pages; each has a distinct reader problem and proof requirement. 11254 11255## Major ownership corrections 11256 11257**Inquiry handling:** R03 proves application validation/persistence/provider handoff; R17 investigates authentication and mailbox observation; R16 tests the truth of the event definition. R02 reviews supported DNS changes. Provider acceptance is not automatically mailbox receipt. 11258 11259**Public reachability:** R02 distinguishes authoritative DNS, address families, TLS and private/public test vantages; R01 handles serving processes and upstreams. Bubbles configuration is not assumed from its name. 11260 11261**Browser and accessibility evidence:** R05 labels engines, branded products, emulation and real devices accurately. R07 keeps manual complete-process assessment separate from automated checks. [Playwright](https://playwright.dev/docs/browsers), [W3C conformance](https://www.w3.org/WAI/WCAG22/Understanding/conformance). 11262 11263**Search/AI work:** R08 owns general URL/indexing contracts; R12 adds engine-specific discovery and citation observation; R10/R13 own relevance and useful answers; R16 owns attribution. Google describes its AI Search optimization on core SEO foundations rather than special-file requirements. [Google guidance](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide). 11264 11265**Independent acceptance:** R26 must disclose actual reviewer relationship and fresh execution. A model switching persona does not become an independent professional. The evidence gate validates metadata/artifact consistency, not identity, truth or production readiness. 11266 11267## Currentness findings incorporated 11268 11269The email charter uses **RFC 9989, May 2026**, which obsoletes core DMARC RFCs 7489 and 9091, and references separate reporting specifications RFCs 9990/9991. This does not justify blind production policy changes; legitimate senders, alignment and receiver behavior still require actual inspection. [Current DMARC](https://www.rfc-editor.org/rfc/rfc9989.html). 11270 11271The measurement charter uses current GA4 channel distinctions, including the documented AI Assistant channel and the separate classification of Google AI Overviews/AI Mode under Organic Search. Citation and referral measurements remain separate from qualified inquiries. [GA4 channel definitions](https://support.google.com/analytics/answer/9756891?hl=en). 11272 11273Security guidance distinguishes the final NIST SSDF 1.1 publication from draft revisions and CSP report-only observation from enforcement. Source register notes identify working-draft and foundational specifications rather than mislabeling every reference as a new final standard. [NIST SSDF](https://csrc.nist.gov/pubs/sp/800/218/final), [CSP](https://www.w3.org/TR/CSP3/). 11274 11275## AI integration and executable behavior 11276 11277The root [AGENTS.md](../AGENTS.md), [build reference](../Library/Framework/SEO-BUILD-REFERENCE.md), [master index](../Library/Framework/framework-masterindex.md) and document catalog include the expansion. `CODEX-START-HERE.txt` and an integration snippet explain how to merge instructions into the **actual** project without overwriting its existing rules. No external repository has been changed. [Official instruction discovery](https://developers.openai.com/codex/guides/agents-md). 11278 11279The router proposes a lead, consultees and bounded prompt pack using deterministic rules. It is not a semantic diagnosis or an agent runtime. The evidence gate checks a separately approved contract, hashes, paths, run/build consistency, timestamps, required checks and declared independence. A structural pass always states that authorization is not granted and external truth/identity have not been verified. 11280 11281## Public expertise path 11282 11283Use the [public workbench](../Publishing/README.md) to turn documented principles or actual authorized work into useful articles. Approve truthful authorship and any credentials; redact proof; choose a canonical publication home; check a working service/inquiry path; and measure outcomes. ThatDevPro as a research home and ThatDeveloperGuy as a service site is only a provisional option, not a domain migration decision. 11284 11285No biography, professional qualification, staff size, customer result, testimonial, traffic estimate, keyword volume, backlink placement or AI recommendation was invented to complete the framework. The publishing templates remain blocked until the required facts and owner review exist. 11286 11287## Compatibility and preservation 11288 11289All **146 unique original files** remain hash-identical. The previous edition's manifest is preserved as `Research/baseline-release-manifest.json`; prior reports remain historical records. Existing commercial tiers, names and pricing are unchanged; Tier 13 remains retired. Role R13 is the content/editorial responsibility. 11290 11291The prior corpus remains partly unverified. This extension is a source-linked operational expansion and structural integration, not a new sentence-by-sentence certification of the inherited library. Source supplement records overlap some baseline references; 49 + 52 is not a count of 101 unique sources. 11292 11293## Validation and limits 11294 11295The [current validation report](../Reports/DISCIPLINE-VALIDATION.md) contains the final local test, integrity and browser results. Unit fixtures are synthetic and run in temporary directories. No real Bubbles uptime, DNS, form, mailbox, Safari/iPhone, analytics property or live search performance was tested by these local utilities. No live site, account, public profile, repository or persistent Library folder was changed. 11296 11297See the [gap map](DISCIPLINE-GAP-MAP.md), [primary-source register](DISCIPLINE-SOURCE-REGISTER.md), [tools guide](../Tools/DISCIPLINES-README.md) and [discipline directory](../Library/Disciplines/README.md) for the exact procedures and boundaries. 11298 11299============================================================================== 11300DOCUMENT 124 OF 135 11301Title: Discipline gap map 11302Path: Research/DISCIPLINE-GAP-MAP.md 11303Group: expansion 11304Label: EXPANSION · source-linked operating design 11305Review status: scope_stated_in_document 11306============================================================================== 11307 11308# Discipline gap map 11309 11310This maps the operational coverage added in this edition. It does not claim that every related concept was absent from the million-word baseline or that every inherited assertion has been verified. Each role now has a formal owner, scope boundary, diagnostic procedure, evidence/acceptance rules, handoffs, a standalone prompt and a distinct public-content brief. 11311 11312| Role | Accountable domain | Project proof still required | 11313| --- | --- | --- | 11314| [R01](../Library/Disciplines/R01-site-reliability.md) | Site Reliability Engineer | Timestamped external/origin probe pair | 11315| [R02](../Library/Disciplines/R02-network-dns.md) | Network/DNS Engineer | Authoritative/recursive answer matrix with timestamps | 11316| [R03](../Library/Disciplines/R03-backend-web.md) | Backend Web Engineer | Request-to-persistence trace with synthetic identifier | 11317| [R04](../Library/Disciplines/R04-frontend-web.md) | Frontend Web Engineer | State-by-state UI contract | 11318| [R05](../Library/Disciplines/R05-browser-compatibility.md) | Browser Compatibility Engineer | Versioned environment matrix | 11319| [R06](../Library/Disciplines/R06-web-performance.md) | Web Performance Engineer | Field/lab separation and route-level baseline | 11320| [R07](../Library/Disciplines/R07-accessibility.md) | Accessibility Specialist | Criterion-to-finding record | 11321| [R08](../Library/Disciplines/R08-technical-seo.md) | Technical SEO Engineer | Per-URL expected/observed contract | 11322| [R09](../Library/Disciplines/R09-information-architecture.md) | Information Architect | Page-purpose and parent map | 11323| [R10](../Library/Disciplines/R10-search-relevance-ir.md) | Search Relevance/IR Engineer | Query set with observed versus hypothesis labels | 11324| [R11](../Library/Disciplines/R11-structured-data-knowledge-graph.md) | Structured Data/Knowledge Graph Engineer | Entity/ID registry and claim provenance | 11325| [R12](../Library/Disciplines/R12-aeo-aio-geo.md) | AEO/AIO/GEO Engineer | Engine-control and access matrix | 11326| [R13](../Library/Disciplines/R13-content-strategy-seo-editor.md) | Content Strategist/SEO Editor | Purpose/differentiation brief | 11327| [R14](../Library/Disciplines/R14-claims-auditor.md) | Fact-Checker/Claims Auditor | Claim ledger with exact allowed wording | 11328| [R15](../Library/Disciplines/R15-conversion-rate-optimization.md) | Conversion-Rate Optimization Specialist | Journey/friction record tied to observation | 11329| [R16](../Library/Disciplines/R16-analytics-measurement.md) | Analytics/Measurement Engineer | Metric/event contracts | 11330| [R17](../Library/Disciplines/R17-email-deliverability.md) | Email Deliverability Engineer | Sender-stream and authentication inventory | 11331| [R18](../Library/Disciplines/R18-local-seo-gbp.md) | Local SEO/GBP Specialist | Eligibility and business-fact register | 11332| [R19](../Library/Disciplines/R19-digital-pr-authority.md) | Digital PR/Authority Specialist | Evidence-backed asset and outreach rationale | 11333| [R20](../Library/Disciplines/R20-application-security-privacy.md) | Application Security/Privacy Engineer | Data-flow/threat model and scoped findings | 11334| [R21](../Library/Disciplines/R21-qa-sdet.md) | QA/SDET Engineer | Risk-to-test coverage map | 11335| [R22](../Library/Disciplines/R22-adversarial-red-team.md) | Adversarial/Red-Team Reviewer | Authorized scope and stop conditions | 11336| [R23](../Library/Disciplines/R23-product-marketing-research.md) | Product Marketing/Market Researcher | Audience/problem/alternative map | 11337| [R24](../Library/Disciplines/R24-solutions-architecture.md) | Solutions Architect/Integrator | Task/decision ownership map | 11338| [R25](../Library/Disciplines/R25-release-change-management.md) | Release/Change Manager | Authorized change/build and sequencing record | 11339| [R26](../Library/Disciplines/R26-independent-acceptance.md) | Independent Acceptance Engineer | Independence declaration and fresh run identity | 11340 11341Read the machine-readable `discipline-gap-map.json` for links to existing framework references and every new role asset. No role is represented as a completed audit of Bubbles or either live brand website. 11342 11343============================================================================== 11344DOCUMENT 125 OF 135 11345Title: Discipline expansion — primary-source register 11346Path: Research/DISCIPLINE-SOURCE-REGISTER.md 11347Group: expansion 11348Label: EXPANSION · source-linked operating design 11349Review status: scope_stated_in_document 11350============================================================================== 11351 11352# Discipline expansion — primary-source register 11353 11354Reviewed 9 September 2026. These 49 source records supplement, not replace, the baseline S01–S52 register. Some sources overlap intentionally so each expansion role has a self-contained authority trail. Do not call the sum 101 unique references. The custom 26-role division, workflow gates, suggested briefs and routing rules are agency operating design, not mandates issued by these publishers. 11355 11356## D01 — Monitoring distributed systems 11357 11358Publisher: Google SRE. [Primary source](https://sre.google/sre-book/monitoring-distributed-systems/). Observed: 2026-09-09. 11359 11360SLO-oriented monitoring and user-visible symptoms; no uptime assertion about Bubbles. 11361 11362## D02 — NGINX beginners guide 11363 11364Publisher: NGINX. [Primary source](https://nginx.org/en/docs/beginners_guide.html). Observed: 2026-09-09. 11365 11366Configuration checks, processes and reverse proxy concepts; deployment-specific paths must be discovered. 11367 11368## D03 — Automating recovery with systemd 11369 11370Publisher: Red Hat. [Primary source](https://www.redhat.com/en/blog/systemd-automate-recovery). Observed: 2026-09-09. 11371 11372Service-manager restart/recovery concepts; vendor tutorial, not proof of an installed unit. 11373 11374## D04 — Domain names: concepts and facilities (RFC 1034) 11375 11376Publisher: RFC Editor / IETF. [Primary source](https://www.rfc-editor.org/rfc/rfc1034.html). Observed: 2026-09-09. 11377 11378Authoritative and recursive DNS concepts; foundational specification with later updates. 11379 11380## D05 — HTTP semantics (RFC 9110) 11381 11382Publisher: RFC Editor / IETF. [Primary source](https://www.rfc-editor.org/rfc/rfc9110.html). Observed: 2026-09-09. 11383 11384HTTP method and response semantics; application response does not establish business delivery. 11385 11386## D06 — What is a tailnet? 11387 11388Publisher: Tailscale. [Primary source](https://tailscale.com/docs/concepts/tailnet). Observed: 2026-09-09. 11389 11390Private tailnet membership and connectivity; tailnet success is not a public-internet test. 11391 11392## D07 — HTML forms 11393 11394Publisher: WHATWG. [Primary source](https://html.spec.whatwg.org/multipage/forms.html). Observed: 2026-09-09. 11395 11396Native form submission, constraints, labels and submit controls; client validation is not server validation. 11397 11398## D08 — Browsers 11399 11400Publisher: Playwright. [Primary source](https://playwright.dev/docs/browsers). Observed: 2026-09-09. 11401 11402Supported engines and branded channels; WebKit automation is not a real Safari or iOS test. 11403 11404## D09 — Web Vitals 11405 11406Publisher: Google web.dev. [Primary source](https://web.dev/articles/vitals). Observed: 2026-09-09. 11407 11408LCP, INP and CLS; field assessment differs from lab diagnostics. 11409 11410## D10 — Defining the Core Web Vitals thresholds 11411 11412Publisher: Google web.dev. [Primary source](https://web.dev/articles/defining-core-web-vitals-thresholds). Observed: 2026-09-09. 11413 11414Good thresholds and 75th-percentile aggregation; not a universal conversion or ranking guarantee. 11415 11416## D11 — Web Content Accessibility Guidelines 2.2 11417 11418Publisher: W3C. [Primary source](https://www.w3.org/TR/WCAG22/). Observed: 2026-09-09. 11419 11420WCAG 2.2 success criteria and conformance requirements; AA is the project target, not a legal certification. 11421 11422## D12 — Understanding conformance 11423 11424Publisher: W3C WAI. [Primary source](https://www.w3.org/WAI/WCAG22/Understanding/conformance). Observed: 2026-09-09. 11425 11426Whole pages, complete processes and human evaluation; no automated-only full-conformance claim. 11427 11428## D13 — Google Search technical requirements 11429 11430Publisher: Google Search Central. [Primary source](https://developers.google.com/search/docs/essentials/technical). Observed: 2026-09-09. 11431 11432Minimum eligibility conditions; eligibility does not guarantee indexing or ranking. 11433 11434## D14 — Make your links crawlable 11435 11436Publisher: Google Search Central. [Primary source](https://developers.google.com/search/docs/crawling-indexing/links-crawlable). Observed: 2026-09-09. 11437 11438Crawlable links and descriptive anchors; no prescribed universal link count. 11439 11440## D15 — Evaluation in information retrieval 11441 11442Publisher: Manning, Raghavan and Schütze / Stanford. [Primary source](https://nlp.stanford.edu/IR-book/html/htmledition/evaluation-in-information-retrieval-1.html). Observed: 2026-09-09. 11443 11444Relevance judgments and retrieval evaluation; not disclosure of a commercial engine ranking algorithm. 11445 11446## D16 — Person 11447 11448Publisher: Schema.org. [Primary source](https://schema.org/Person). Observed: 2026-09-09. 11449 11450Vocabulary for a real person; use truthful properties and exact identity links. 11451 11452## D17 — Organization 11453 11454Publisher: Schema.org. [Primary source](https://schema.org/Organization). Observed: 2026-09-09. 11455 11456Organization identity vocabulary; do not convert internal roles into fictional employees. 11457 11458## D18 — TechArticle 11459 11460Publisher: Schema.org. [Primary source](https://schema.org/TechArticle). Observed: 2026-09-09. 11461 11462Technical-article vocabulary; vocabulary support does not establish a Google rich-result feature. 11463 11464## D19 — Structured data general guidelines 11465 11466Publisher: Google Search Central. [Primary source](https://developers.google.com/search/docs/appearance/structured-data/sd-policies). Observed: 2026-09-09. 11467 11468Accurate visible content and feature-specific eligibility; valid JSON alone is insufficient. 11469 11470## D20 — AI optimization guide 11471 11472Publisher: Google Search Central. [Primary source](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide). Observed: 2026-09-09. 11473 11474Google AI Search retains core SEO foundations; no special llms.txt or schema requirement or ranking guarantee. 11475 11476## D21 — Creating helpful, reliable, people-first content 11477 11478Publisher: Google Search Central. [Primary source](https://developers.google.com/search/docs/fundamentals/creating-helpful-content). Observed: 2026-09-09. 11479 11480Original value, sources, authorship and first-hand expertise; not a points-based ranking formula. 11481 11482## D22 — OpenAI crawlers 11483 11484Publisher: OpenAI. [Primary source](https://developers.openai.com/api/docs/bots). Observed: 2026-09-09. 11485 11486OAI-SearchBot, GPTBot and user-triggered fetching have distinct purposes and controls. 11487 11488## D23 — Does Anthropic crawl data from the web? 11489 11490Publisher: Anthropic. [Primary source](https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler). Observed: 2026-09-09. 11491 11492Engine-specific crawl policies; inspect current agent-specific controls rather than inherit Google assumptions. 11493 11494## D24 — Perplexity crawlers 11495 11496Publisher: Perplexity. [Primary source](https://docs.perplexity.ai/docs/resources/perplexity-crawlers). Observed: 2026-09-09. 11497 11498Engine-specific crawler and user-fetch documentation; access is not proof of selection. 11499 11500## D25 — Advertising FAQs: A guide for small business 11501 11502Publisher: US Federal Trade Commission. [Primary source](https://www.ftc.gov/business-guidance/resources/advertising-faqs-guide-small-business). Observed: 2026-09-09. 11503 11504US advertising substantiation principles; context-specific legal review may still be needed. 11505 11506## D26 — Endorsements, influencers and reviews 11507 11508Publisher: US Federal Trade Commission. [Primary source](https://www.ftc.gov/business-guidance/advertising-marketing/endorsements-influencers-reviews). Observed: 2026-09-09. 11509 11510Truthful endorsements and relevant disclosures; no invented testimonials or review provenance. 11511 11512## D27 — Patterns of trustworthy experimentation: pre-experiment stage 11513 11514Publisher: Microsoft Research. [Primary source](https://www.microsoft.com/en-us/research/articles/patterns-of-trustworthy-experimentation-pre-experiment-stage/). Observed: 2026-09-09. 11515 11516Define trustworthy experiment design before interpreting results; no universal sample size or uplift claim. 11517 11518## D28 — Set up events 11519 11520Publisher: Google Analytics Developers. [Primary source](https://developers.google.com/analytics/devguides/collection/ga4/events). Observed: 2026-09-09. 11521 11522Event implementation and verification; emitting an event does not prove a qualified lead. 11523 11524## D29 — Default channel group 11525 11526Publisher: Google Analytics Help. [Primary source](https://support.google.com/analytics/answer/9756891?hl=en). Observed: 2026-09-09. 11527 11528AI Assistant channel; Google AI Overviews and AI Mode classified in Organic Search in current documentation. 11529 11530## D30 — Set up consent mode 11531 11532Publisher: Google for Developers. [Primary source](https://developers.google.com/tag-platform/security/guides/consent). Observed: 2026-09-09. 11533 11534Technical consent signaling; configuration alone does not establish legal permission. 11535 11536## D31 — New AI visibility insights in Bing Webmaster Tools 11537 11538Publisher: Microsoft Bing. [Primary source](https://blogs.bing.com/search/June-2026/New-AI-Visibility-Insights-in-Bing-Webmaster-Tools-Intents-Topics-Citation-Share-Compare). Observed: 2026-09-09. 11539 11540June 2026 reporting expansion; citation measurements are not website conversions or revenue. 11541 11542## D32 — Email sender guidelines 11543 11544Publisher: Google Workspace / Gmail. [Primary source](https://support.google.com/a/answer/81126?hl=en). Observed: 2026-09-09. 11545 11546Provider authentication and sending requirements vary by sending class; no guaranteed inbox placement. 11547 11548## D33 — Simple Mail Transfer Protocol (RFC 5321) 11549 11550Publisher: RFC Editor / IETF. [Primary source](https://www.rfc-editor.org/rfc/rfc5321.html). Observed: 2026-09-09. 11551 11552SMTP acceptance, relaying and failures; acceptance is distinct from final mailbox observation. 11553 11554## D34 — Sender Policy Framework (RFC 7208) 11555 11556Publisher: RFC Editor / IETF. [Primary source](https://www.rfc-editor.org/rfc/rfc7208.html). Observed: 2026-09-09. 11557 11558SPF authorization and evaluation; inventory legitimate senders before altering DNS. 11559 11560## D35 — DomainKeys Identified Mail (RFC 6376) 11561 11562Publisher: RFC Editor / IETF. [Primary source](https://www.rfc-editor.org/rfc/rfc6376.html). Observed: 2026-09-09. 11563 11564DKIM signatures and domain authentication; inspect results on received mail. 11565 11566## D36 — DMARC (RFC 9989) 11567 11568Publisher: RFC Editor / IETF. [Primary source](https://www.rfc-editor.org/rfc/rfc9989.html). Observed: 2026-09-09. 11569 11570May 2026 core DMARC specification, obsoletes RFCs 7489 and 9091. A pass does not guarantee inbox desirability. 11571 11572## D37 — DMARC aggregate reporting (RFC 9990) 11573 11574Publisher: RFC Editor / IETF. [Primary source](https://www.rfc-editor.org/info/rfc9990/). Observed: 2026-09-09. 11575 11576May 2026 aggregate reporting specification; data sensitivity and provider compatibility still require review. 11577 11578## D38 — DMARC failure reporting (RFC 9991) 11579 11580Publisher: RFC Editor / IETF. [Primary source](https://www.rfc-editor.org/info/rfc9991/). Observed: 2026-09-09. 11581 11582May 2026 failure reporting specification; do not expose message data in public evidence. 11583 11584## D39 — Guidelines for representing your business on Google 11585 11586Publisher: Google Business Profile. [Primary source](https://support.google.com/business/answer/3038177?hl=en). Observed: 2026-09-09. 11587 11588Real-world representation, eligible businesses and locations; no fabricated offices or credentials. 11589 11590## D40 — Spam policies for Google web search 11591 11592Publisher: Google Search Central. [Primary source](https://developers.google.com/search/docs/essentials/spam-policies). Observed: 2026-09-09. 11593 11594Link spam, doorway and scaled-content abuse boundaries; public authority cannot be manufactured with false signals. 11595 11596## D41 — Application Security Verification Standard 11597 11598Publisher: OWASP. [Primary source](https://owasp.org/www-project-application-security-verification-standard/). Observed: 2026-09-09. 11599 11600Application security verification requirements; tailor version and assurance scope before adopting controls. 11601 11602## D42 — Web Security Testing Guide 11603 11604Publisher: OWASP. [Primary source](https://owasp.org/www-project-web-security-testing-guide/). Observed: 2026-09-09. 11605 11606Authorized security testing methodology; not permission to test third-party production systems. 11607 11608## D43 — Content Security Policy Level 3 11609 11610Publisher: W3C. [Primary source](https://www.w3.org/TR/CSP3/). Observed: 2026-09-09. 11611 11612Working-draft specification: report-only and enforcement differ; test against actual browser support. 11613 11614## D44 — Secure Software Development Framework 1.1 11615 11616Publisher: NIST. [Primary source](https://csrc.nist.gov/pubs/sp/800/218/final). Observed: 2026-09-09. 11617 11618Final SP 800-218 v1.1; the v1.2 public draft is not substituted as a final standard. 11619 11620## D45 — Release engineering 11621 11622Publisher: Google SRE. [Primary source](https://sre.google/sre-book/release-engineering/). Observed: 2026-09-09. 11623 11624Controlled, repeatable releases and rollback; actual release authorization is project-specific. 11625 11626## D46 — Evolving SRE engagement model 11627 11628Publisher: Google SRE. [Primary source](https://sre.google/sre-book/evolving-sre-engagement-model/). Observed: 2026-09-09. 11629 11630Production readiness review and operational ownership; custom role organization is an agency design. 11631 11632## D47 — Plan your business 11633 11634Publisher: US Small Business Administration. [Primary source](https://www.sba.gov/counseling/plan-your-business/). Observed: 2026-09-09. 11635 11636Market/business planning overview; query demand and commercial fit require local evidence. 11637 11638## D48 — Custom instructions with AGENTS.md 11639 11640Publisher: OpenAI. [Primary source](https://developers.openai.com/codex/guides/agents-md). Observed: 2026-09-09. 11641 11642Codex instruction discovery and hierarchy; a downloaded library does not install itself in another repository. 11643 11644## D49 — Overview of Google crawlers and fetchers 11645 11646Publisher: Google. [Primary source](https://developers.google.com/crawling/docs/crawlers-fetchers/overview-google-crawlers). Observed: 2026-09-09. 11647 11648Crawler/fetcher purposes and verification references; user-agent strings alone are not identity proof. 11649 11650============================================================================== 11651DOCUMENT 126 OF 135 11652Title: Findings and dispositions 11653Path: Research/FINDINGS.md 11654Group: baseline 11655Label: REFERENCE · scope stated in document 11656Review status: scope_stated_in_document 11657============================================================================== 11658 11659# Findings and dispositions 11660 1166128 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. 11662 11663Sources are identified in the [primary-source register](SOURCE-REGISTER.md). Exact machine-readable records are in [findings.json](findings.json). 11664 11665## F01 — confirmed inventory error 11666 11667**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-masterindex.md`, line 13. 11668 11669[Inspect preserved source](../99-Originals/Framework/framework-masterindex.md) 11670 11671**Located wording:** 11672 11673``` 11674The library currently contains **56 framework documents** plus this master index. Categorized below. 11675``` 11676 11677**Why it matters:** The entry point understates the archive and asserts unreliable navigation. 11678 11679**Disposition:** Regenerate the index from the current filesystem and status catalog. 11680 11681**Evidence:** Direct archive inspection / reproducible inventory 11682 11683## F02 — unsafe universal instruction 11684 11685**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-one.md`, line 27. 11686 11687[Inspect preserved source](../99-Originals/Production%20Customer%20Tiers/tier-one.md) 11688 11689**Located wording:** 11690 11691``` 11692- Force lowercase URLs in `.htaccess` or `nginx.conf` to prevent case-duplicate indexing 11693``` 11694 11695**Why it matters:** Can break case-sensitive routes, assets and signed links. 11696 11697**Disposition:** Require a project-specific URL mapping and tests; no global rewrite by default. 11698 11699**Evidence:** S15, S38 11700 11701## F03 — unsafe universal instruction 11702 11703**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-one.md`, line 29. 11704 11705[Inspect preserved source](../99-Originals/Production%20Customer%20Tiers/tier-one.md) 11706 11707**Located wording:** 11708 11709``` 11710- 301-redirect or 410 all thin, duplicate, or orphan pages flagged in GSC 11711``` 11712 11713**Why it matters:** Can remove useful pages and destroy user paths without diagnosis. 11714 11715**Disposition:** Use per-URL keep, improve, merge, exclude or retire decisions with approval. 11716 11717**Evidence:** S15, S16, S38 11718 11719## F04 — unsafe universal instruction 11720 11721**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-one.md`, line 24. 11722 11723[Inspect preserved source](../99-Originals/Production%20Customer%20Tiers/tier-one.md) 11724 11725**Located wording:** 11726 11727``` 11728- Set WordPress permalinks to `/%postname%/`; in Next.js use file-based routing with consistent trailing-slash policy (pick one, stick to it sitewide) 11729``` 11730 11731**Why it matters:** Changing established URL structure solely for style creates migration risk. 11732 11733**Disposition:** Preserve established URLs unless an approved migration justifies changes. 11734 11735**Evidence:** S38 11736 11737## F05 — heuristic mislabeled as requirement 11738 11739**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-one.md`, line 44. 11740 11741[Inspect preserved source](../99-Originals/Production%20Customer%20Tiers/tier-one.md) 11742 11743**Located wording:** 11744 11745``` 11746- Write unique `<title>` tag per page, 50–60 characters, primary keyword near the front 11747``` 11748 11749**Why it matters:** Editorial guidance is presented as a fixed implementation gate. 11750 11751**Disposition:** Treat length as review guidance, not an official limit. 11752 11753**Evidence:** S34 11754 11755## F06 — heuristic mislabeled as requirement 11756 11757**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-one.md`, line 45. 11758 11759[Inspect preserved source](../99-Originals/Production%20Customer%20Tiers/tier-one.md) 11760 11761**Located wording:** 11762 11763``` 11764- Write unique `<meta name="description">` per page, 140–160 characters, with active voice and CTA 11765``` 11766 11767**Why it matters:** A fixed count does not guarantee snippet selection or display. 11768 11769**Disposition:** Use truthful concise copy and flexible preview review. 11770 11771**Evidence:** S35 11772 11773## F07 — incorrect bot role for goal 11774 11775**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-three.md`, line 182. 11776 11777[Inspect preserved source](../99-Originals/Production%20Customer%20Tiers/tier-three.md) 11778 11779**Located wording:** 11780 11781``` 11782- **Claude (Anthropic)**: Nuanced, well-reasoned content with clear caveats and sourcing; ensure ClaudeBot is allowed 11783``` 11784 11785**Why it matters:** Training permission is conflated with search/citation discovery. 11786 11787**Disposition:** Use Claude-SearchBot for the documented search role; review Claude-User and training independently. 11788 11789**Evidence:** S10 11790 11791## F08 — outdated mixed bot list 11792 11793**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Production Customer Tiers/tier-three.md`, line 170. 11794 11795[Inspect preserved source](../99-Originals/Production%20Customer%20Tiers/tier-three.md) 11796 11797**Located wording:** 11798 11799``` 11800- Add explicit rules for: GPTBot, ClaudeBot, Claude-Web, PerplexityBot, Google-Extended, OAI-SearchBot, anthropic-ai, ChatGPT-User, Applebot-Extended 11801``` 11802 11803**Why it matters:** Legacy and current tokens are grouped without purpose or current support. 11804 11805**Disposition:** Use the engine role matrix and owner-approved policy. 11806 11807**Evidence:** S08, S10, S11, S12 11808 11809## F09 — unsupported absolute 11810 11811**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-contentfirst.md`, line 17. 11812 11813[Inspect preserved source](../99-Originals/Framework/framework-contentfirst.md) 11814 11815**Located wording:** 11816 11817``` 11818The 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. 11819``` 11820 11821**Why it matters:** Architecture alone does not establish a universal zero-citation outcome. 11822 11823**Disposition:** Replace with route/consumer-specific delivery and measurement contracts. 11824 11825**Evidence:** S14, S24 11826 11827## F10 — unverified quantitative claim 11828 11829**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-contentfirst.md`, line 258. 11830 11831[Inspect preserved source](../99-Originals/Framework/framework-contentfirst.md) 11832 11833**Located wording:** 11834 11835``` 11836> 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). 11837``` 11838 11839**Why it matters:** A proprietary score and broad outcome are presented without reproduced evidence. 11840 11841**Disposition:** Remove from authoritative guidance; retain in historical review queue. 11842 11843**Evidence:** S02, S29 11844 11845## F11 — contradicted blanket rendering claim 11846 11847**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-aioverviews.md`, line 210. 11848 11849[Inspect preserved source](../99-Originals/Framework/framework-aioverviews.md) 11850 11851**Located wording:** 11852 11853``` 11854Three 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. 11855``` 11856 11857**Why it matters:** Conflates all consumers and conflicts with Google JavaScript guidance. 11858 11859**Disposition:** Validate actual rendering; do not equate GPTBot simulation with Google AI testing. 11860 11861**Evidence:** S14, S03 11862 11863## F12 — unverified quantitative claim 11864 11865**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-aioverviews.md`, line 250. 11866 11867[Inspect preserved source](../99-Originals/Framework/framework-aioverviews.md) 11868 11869**Located wording:** 11870 11871``` 11872Heading 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. 11873``` 11874 11875**Why it matters:** An attributed multiplier is promoted as generally reproducible without verified methods. 11876 11877**Disposition:** Do not use in forecasts or acceptance tests; formatting follows information structure. 11878 11879**Evidence:** S29 11880 11881## F13 — unverified research attribution 11882 11883**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-aioverviews.md`, line 258. 11884 11885[Inspect preserved source](../99-Originals/Framework/framework-aioverviews.md) 11886 11887**Located wording:** 11888 11889``` 11890Princeton 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). 11891``` 11892 11893**Why it matters:** A specific internal-link/AIO claim is not established by the inspected primary study. 11894 11895**Disposition:** Retain as unverified historical attribution, not a proven rule. 11896 11897**Evidence:** S29 11898 11899## F14 — overgeneralized research result 11900 11901**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-aioverviews.md`, line 462. 11902 11903[Inspect preserved source](../99-Originals/Framework/framework-aioverviews.md) 11904 11905**Located wording:** 11906 11907``` 11908Inline 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. 11909``` 11910 11911**Why it matters:** Benchmark metrics are converted to current Google citation probability. 11912 11913**Disposition:** Scope research to its engine/model/dataset/outcome. 11914 11915**Evidence:** S29 11916 11917## F15 — incorrect reporting timeline 11918 11919**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-gscanalysis.md`, line 17. 11920 11921[Inspect preserved source](../99-Originals/Framework/framework-gscanalysis.md) 11922 11923**Located wording:** 11924 11925``` 11926The 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. 11927``` 11928 11929**Why it matters:** The library claims an old rollout and report structure not supported by current official sources. 11930 11931**Disposition:** Use June 3 announcement and August 31, 2026 rollout note and current help page. 11932 11933**Evidence:** S04, S05 11934 11935## F16 — obsolete feature list 11936 11937**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-gscanalysis.md`, line 198. 11938 11939[Inspect preserved source](../99-Originals/Framework/framework-gscanalysis.md) 11940 11941**Located wording:** 11942 11943``` 11944Reports 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. 11945``` 11946 11947**Why it matters:** Retired features are listed as current report appearances. 11948 11949**Disposition:** Use available report fields and current feature lifecycle. 11950 11951**Evidence:** S01, S21 11952 11953## F17 — superseded workflow requirement 11954 11955**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-ga4.md`, line 557. 11956 11957[Inspect preserved source](../99-Originals/Framework/framework-ga4.md) 11958 11959**Located wording:** 11960 11961``` 11962### 11.4 Strategy 3: The AI Assistants Custom Channel Grouping 11963``` 11964 11965**Why it matters:** Custom grouping is treated as necessary while GA4 now documents an AI Assistant channel. 11966 11967**Disposition:** Use current default definitions; custom grouping remains optional for a declared purpose. 11968 11969**Evidence:** S36 11970 11971## F18 — version specific claim not revalidated 11972 11973**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-ga4.md`, line 531. 11974 11975[Inspect preserved source](../99-Originals/Framework/framework-ga4.md) 11976 11977**Located wording:** 11978 11979``` 11980GA4 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`. 11981``` 11982 11983**Why it matters:** Old session semantics are stated as GA4 behavior. 11984 11985**Disposition:** Do not carry forward unsupported session reset assertions; verify actual GA4 scope. 11986 11987**Evidence:** S36 11988 11989## F19 — outdated safe harbor implication 11990 11991**Original:** `SEO Tiers Version Sets/SEO Tiers For Work 4/Framework/framework-spampolicies.md`, line 542. 11992 11993[Inspect preserved source](../99-Originals/Framework/framework-spampolicies.md) 11994 11995**Located wording:** 11996 11997``` 11998**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. 11999``` 12000