Janady13/thatstupidcomputer / private/standards/SEO-AIO-Library.txt · Lines 9001–10500

9001- [D10 — Defining the Core Web Vitals thresholds](https://web.dev/articles/defining-core-web-vitals-thresholds): Good thresholds and 75th-percentile aggregation; not a universal conversion or ranking guarantee. 9002 9003============================================================================== 9004DOCUMENT 090 OF 135 9005Title: R07 public-content brief — What must an accessibility audit test beyond an automated score? 9006Path: Publishing/Briefs/R07-accessibility.md 9007Group: briefs 9008Label: PUBLIC WORKBENCH · not approved 9009Review status: scope_stated_in_document 9010============================================================================== 9011 9012# R07 public-content brief — What must an accessibility audit test beyond an automated score? 9013 9014**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R07. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9015 9016## Reader and purpose 9017 9018A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **What must an accessibility audit test beyond an automated score?** 9019 9020**Distinct contribution:** A complete contact-process walkthrough tied to WCAG criteria, including keyboard and screen-reader evidence. 9021 9022## Candidate search questions — hypotheses, not measured demand 9023 9024- WCAG 2.2 AA manual accessibility audit 9025- accessible contact form testing 9026- website keyboard screen reader audit 9027 9028No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9029 9030## Proposed outline 9031 90321. Define complete processes 90332. Use automation as detection 90343. Test human interaction 90354. Retest and disclose limitations 9036 9037Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9038 9039## Evidence needed before making an expertise or results claim 9040 9041- Criterion-to-finding record 9042- Manual keyboard/screen-reader process results 9043- Retest log and scope/limitations statement 9044 9045These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9046 9047## Proposed public route and internal relationships 9048 9049Suggested route, pending canonical-host approval: `/expertise/accessibility/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9050 9051Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9052 9053## Conversion and measurement contract 9054 9055Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9056 9057Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9058 9059## Publication gate 9060 9061R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9062 9063No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9064 9065## Research references 9066 9067- [D07 — HTML forms](https://html.spec.whatwg.org/multipage/forms.html): Native form submission, constraints, labels and submit controls; client validation is not server validation. 9068- [D11 — Web Content Accessibility Guidelines 2.2](https://www.w3.org/TR/WCAG22/): WCAG 2.2 success criteria and conformance requirements; AA is the project target, not a legal certification. 9069- [D12 — Understanding conformance](https://www.w3.org/WAI/WCAG22/Understanding/conformance): Whole pages, complete processes and human evaluation; no automated-only full-conformance claim. 9070 9071============================================================================== 9072DOCUMENT 091 OF 135 9073Title: R08 public-content brief — How do you distinguish a crawlability problem from an indexing or relevance problem? 9074Path: Publishing/Briefs/R08-technical-seo.md 9075Group: briefs 9076Label: PUBLIC WORKBENCH · not approved 9077Review status: scope_stated_in_document 9078============================================================================== 9079 9080# R08 public-content brief — How do you distinguish a crawlability problem from an indexing or relevance problem? 9081 9082**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R08. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9083 9084## Reader and purpose 9085 9086A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you distinguish a crawlability problem from an indexing or relevance problem?** 9087 9088**Distinct contribution:** An evidence-led URL contract that separates HTTP behavior, crawler access, engine observations and content selection. 9089 9090## Candidate search questions — hypotheses, not measured demand 9091 9092- website crawlable but not indexed 9093- canonical robots sitemap audit 9094- technical SEO URL status diagnosis 9095 9096No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9097 9098## Proposed outline 9099 91001. Define intended URL states 91012. Inspect response and directives 91023. Use engine observations 91034. Route nontechnical problems correctly 9104 9105Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9106 9107## Evidence needed before making an expertise or results claim 9108 9109- Per-URL expected/observed contract 9110- Response/redirect/canonical test captures 9111- Engine inspection record or access limitation 9112 9113These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9114 9115## Proposed public route and internal relationships 9116 9117Suggested route, pending canonical-host approval: `/expertise/technical-seo/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9118 9119Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9120 9121## Conversion and measurement contract 9122 9123Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9124 9125Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9126 9127## Publication gate 9128 9129R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9130 9131No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9132 9133## Research references 9134 9135- [D13 — Google Search technical requirements](https://developers.google.com/search/docs/essentials/technical): Minimum eligibility conditions; eligibility does not guarantee indexing or ranking. 9136- [D14 — Make your links crawlable](https://developers.google.com/search/docs/crawling-indexing/links-crawlable): Crawlable links and descriptive anchors; no prescribed universal link count. 9137- [D20 — AI optimization guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide): Google AI Search retains core SEO foundations; no special llms.txt or schema requirement or ranking guarantee. 9138- [D49 — Overview of Google crawlers and fetchers](https://developers.google.com/crawling/docs/crawlers-fetchers/overview-google-crawlers): Crawler/fetcher purposes and verification references; user-agent strings alone are not identity proof. 9139 9140============================================================================== 9141DOCUMENT 092 OF 135 9142Title: R09 public-content brief — How do you organize a service website without creating duplicate or orphan pages? 9143Path: Publishing/Briefs/R09-information-architecture.md 9144Group: briefs 9145Label: PUBLIC WORKBENCH · not approved 9146Review status: scope_stated_in_document 9147============================================================================== 9148 9149# R09 public-content brief — How do you organize a service website without creating duplicate or orphan pages? 9150 9151**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R09. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9152 9153## Reader and purpose 9154 9155A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you organize a service website without creating duplicate or orphan pages?** 9156 9157**Distinct contribution:** A page-purpose register and navigable service-to-proof-to-contact architecture, with concrete merge decisions. 9158 9159## Candidate search questions — hypotheses, not measured demand 9160 9161- service website information architecture 9162- orphan pages internal linking 9163- website page purpose mapping 9164 9165No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9166 9167## Proposed outline 9168 91691. Inventory purposes 91702. Group real decisions 91713. Connect useful pages 91724. Govern publication and consolidation 9173 9174Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9175 9176## Evidence needed before making an expertise or results claim 9177 9178- Page-purpose and parent map 9179- Incoming/contextual link inventory 9180- Findability task results with method label 9181 9182These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9183 9184## Proposed public route and internal relationships 9185 9186Suggested route, pending canonical-host approval: `/expertise/information-architecture/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9187 9188Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9189 9190## Conversion and measurement contract 9191 9192Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9193 9194Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9195 9196## Publication gate 9197 9198R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9199 9200No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9201 9202## Research references 9203 9204- [D14 — Make your links crawlable](https://developers.google.com/search/docs/crawling-indexing/links-crawlable): Crawlable links and descriptive anchors; no prescribed universal link count. 9205- [D21 — Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content): Original value, sources, authorship and first-hand expertise; not a points-based ranking formula. 9206- [D40 — Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies): Link spam, doorway and scaled-content abuse boundaries; public authority cannot be manufactured with false signals. 9207 9208============================================================================== 9209DOCUMENT 093 OF 135 9210Title: R10 public-content brief — What makes a page relevant to a customer question rather than merely keyword-rich? 9211Path: Publishing/Briefs/R10-search-relevance-ir.md 9212Group: briefs 9213Label: PUBLIC WORKBENCH · not approved 9214Review status: scope_stated_in_document 9215============================================================================== 9216 9217# R10 public-content brief — What makes a page relevant to a customer question rather than merely keyword-rich? 9218 9219**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R10. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9220 9221## Reader and purpose 9222 9223A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **What makes a page relevant to a customer question rather than merely keyword-rich?** 9224 9225**Distinct contribution:** A transparent relevance rubric and judged query examples, with evidence gaps and task completion instead of opaque SEO scores. 9226 9227## Candidate search questions — hypotheses, not measured demand 9228 9229- search intent page relevance audit 9230- information gain useful website content 9231- site search relevance evaluation 9232 9233No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9234 9235## Proposed outline 9236 92371. Separate owned retrieval from Google 92382. Judge actual questions 92393. Identify missing information 92404. Evaluate without claiming hidden weights 9241 9242Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9243 9244## Evidence needed before making an expertise or results claim 9245 9246- Query set with observed versus hypothesis labels 9247- Relevance rubric and judged examples 9248- Baseline/candidate failure analysis for owned retrieval 9249 9250These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9251 9252## Proposed public route and internal relationships 9253 9254Suggested route, pending canonical-host approval: `/expertise/search-relevance-ir/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9255 9256Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9257 9258## Conversion and measurement contract 9259 9260Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9261 9262Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9263 9264## Publication gate 9265 9266R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9267 9268No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9269 9270## Research references 9271 9272- [D15 — Evaluation in information retrieval](https://nlp.stanford.edu/IR-book/html/htmledition/evaluation-in-information-retrieval-1.html): Relevance judgments and retrieval evaluation; not disclosure of a commercial engine ranking algorithm. 9273- [D20 — AI optimization guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide): Google AI Search retains core SEO foundations; no special llms.txt or schema requirement or ranking guarantee. 9274- [D21 — Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content): Original value, sources, authorship and first-hand expertise; not a points-based ranking formula. 9275 9276============================================================================== 9277DOCUMENT 094 OF 135 9278Title: R11 public-content brief — How do you connect an author, business and technical article without inventing authority? 9279Path: Publishing/Briefs/R11-structured-data-knowledge-graph.md 9280Group: briefs 9281Label: PUBLIC WORKBENCH · not approved 9282Review status: scope_stated_in_document 9283============================================================================== 9284 9285# R11 public-content brief — How do you connect an author, business and technical article without inventing authority? 9286 9287**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R11. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9288 9289## Reader and purpose 9290 9291A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you connect an author, business and technical article without inventing authority?** 9292 9293**Distinct contribution:** A provenance-backed entity model with exact identity links and explicit examples of relationships that must not be asserted. 9294 9295## Candidate search questions — hypotheses, not measured demand 9296 9297- Person Organization TechArticle schema author 9298- sameAs identity schema mistakes 9299- knowledge graph entity consistency website 9300 9301No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9302 9303## Proposed outline 9304 93051. Separate real entities 93062. Choose stable IDs 93073. Verify identity links 93084. Check visible facts and eligibility separately 9309 9310Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9311 9312## Evidence needed before making an expertise or results claim 9313 9314- Entity/ID registry and claim provenance 9315- Syntax and graph-consistency results 9316- Visible-content and feature-policy review 9317 9318These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9319 9320## Proposed public route and internal relationships 9321 9322Suggested route, pending canonical-host approval: `/expertise/structured-data-knowledge-graph/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9323 9324Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9325 9326## Conversion and measurement contract 9327 9328Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9329 9330Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9331 9332## Publication gate 9333 9334R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9335 9336No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9337 9338## Research references 9339 9340- [D16 — Person](https://schema.org/Person): Vocabulary for a real person; use truthful properties and exact identity links. 9341- [D17 — Organization](https://schema.org/Organization): Organization identity vocabulary; do not convert internal roles into fictional employees. 9342- [D18 — TechArticle](https://schema.org/TechArticle): Technical-article vocabulary; vocabulary support does not establish a Google rich-result feature. 9343- [D19 — Structured data general guidelines](https://developers.google.com/search/docs/appearance/structured-data/sd-policies): Accurate visible content and feature-specific eligibility; valid JSON alone is insufficient. 9344 9345============================================================================== 9346DOCUMENT 095 OF 135 9347Title: R12 public-content brief — How can a business measure AI search visibility without confusing crawler visits with customers? 9348Path: Publishing/Briefs/R12-aeo-aio-geo.md 9349Group: briefs 9350Label: PUBLIC WORKBENCH · not approved 9351Review status: scope_stated_in_document 9352============================================================================== 9353 9354# R12 public-content brief — How can a business measure AI search visibility without confusing crawler visits with customers? 9355 9356**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R12. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9357 9358## Reader and purpose 9359 9360A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How can a business measure AI search visibility without confusing crawler visits with customers?** 9361 9362**Distinct contribution:** A six-stage evidence ladder and reproducible engine-specific observation protocol, with negative results and uncertainty preserved. 9363 9364## Candidate search questions — hypotheses, not measured demand 9365 9366- measure AI search citations and leads 9367- ChatGPT crawler versus GPTBot 9368- AIO SEO visibility measurement 9369 9370No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9371 9372## Proposed outline 9373 93741. Name the engine and surface 93752. Check access and useful sources 93763. Record citations reproducibly 93774. Connect referrals to qualified outcomes carefully 9378 9379Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9380 9381## Evidence needed before making an expertise or results claim 9382 9383- Engine-control and access matrix 9384- Timestamped answer/citation observation records 9385- Source-to-referral-to-qualified-outcome measurement map 9386 9387These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9388 9389## Proposed public route and internal relationships 9390 9391Suggested route, pending canonical-host approval: `/expertise/aeo-aio-geo/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9392 9393Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9394 9395## Conversion and measurement contract 9396 9397Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9398 9399Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9400 9401## Publication gate 9402 9403R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9404 9405No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9406 9407## Research references 9408 9409- [D20 — AI optimization guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide): Google AI Search retains core SEO foundations; no special llms.txt or schema requirement or ranking guarantee. 9410- [D22 — OpenAI crawlers](https://developers.openai.com/api/docs/bots): OAI-SearchBot, GPTBot and user-triggered fetching have distinct purposes and controls. 9411- [D23 — Does Anthropic crawl data from the web?](https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler): Engine-specific crawl policies; inspect current agent-specific controls rather than inherit Google assumptions. 9412- [D24 — Perplexity crawlers](https://docs.perplexity.ai/docs/resources/perplexity-crawlers): Engine-specific crawler and user-fetch documentation; access is not proof of selection. 9413- [D29 — Default channel group](https://support.google.com/analytics/answer/9756891?hl=en): AI Assistant channel; Google AI Overviews and AI Mode classified in Organic Search in current documentation. 9414- [D31 — New AI visibility insights in Bing Webmaster Tools](https://blogs.bing.com/search/June-2026/New-AI-Visibility-Insights-in-Bing-Webmaster-Tools-Intents-Topics-Citation-Share-Compare): June 2026 reporting expansion; citation measurements are not website conversions or revenue. 9415 9416============================================================================== 9417DOCUMENT 096 OF 135 9418Title: R13 public-content brief — How do you turn technical troubleshooting into useful evidence-led content? 9419Path: Publishing/Briefs/R13-content-strategy-seo-editor.md 9420Group: briefs 9421Label: PUBLIC WORKBENCH · not approved 9422Review status: scope_stated_in_document 9423============================================================================== 9424 9425# R13 public-content brief — How do you turn technical troubleshooting into useful evidence-led content? 9426 9427**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R13. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9428 9429## Reader and purpose 9430 9431A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you turn technical troubleshooting into useful evidence-led content?** 9432 9433**Distinct contribution:** A worked editorial method that turns a bounded diagnosis into a helpful article without inventing results or duplicating every keyword. 9434 9435## Candidate search questions — hypotheses, not measured demand 9436 9437- technical case study evidence writing 9438- SEO content from real troubleshooting 9439- buyer focused technical content 9440 9441No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9442 9443## Proposed outline 9444 94451. Start from a customer decision 94462. Collect authorized proof 94473. Draft with limits and sources 94484. Consolidate and review before publishing 9449 9450Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9451 9452## Evidence needed before making an expertise or results claim 9453 9454- Purpose/differentiation brief 9455- Claim-to-source annotated draft 9456- Author/editor approval and consolidation decisions 9457 9458These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9459 9460## Proposed public route and internal relationships 9461 9462Suggested route, pending canonical-host approval: `/expertise/content-strategy-seo-editor/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9463 9464Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9465 9466## Conversion and measurement contract 9467 9468Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9469 9470Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9471 9472## Publication gate 9473 9474R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9475 9476No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9477 9478## Research references 9479 9480- [D21 — Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content): Original value, sources, authorship and first-hand expertise; not a points-based ranking formula. 9481- [D25 — Advertising FAQs: A guide for small business](https://www.ftc.gov/business-guidance/resources/advertising-faqs-guide-small-business): US advertising substantiation principles; context-specific legal review may still be needed. 9482- [D40 — Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies): Link spam, doorway and scaled-content abuse boundaries; public authority cannot be manufactured with false signals. 9483 9484============================================================================== 9485DOCUMENT 097 OF 135 9486Title: R14 public-content brief — What evidence should support a website performance or marketing claim? 9487Path: Publishing/Briefs/R14-claims-auditor.md 9488Group: briefs 9489Label: PUBLIC WORKBENCH · not approved 9490Review status: scope_stated_in_document 9491============================================================================== 9492 9493# R14 public-content brief — What evidence should support a website performance or marketing claim? 9494 9495**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R14. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9496 9497## Reader and purpose 9498 9499A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **What evidence should support a website performance or marketing claim?** 9500 9501**Distinct contribution:** A publishable claims ledger example with denominators, date windows, allowed wording and rejected overclaims. 9502 9503## Candidate search questions — hypotheses, not measured demand 9504 9505- verify website performance claims 9506- marketing case study evidence 9507- technical claims audit 9508 9509No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9510 9511## Proposed outline 9512 95131. Classify exact claims 95142. Trace primary evidence 95153. Check numbers and credentials 95164. Approve bounded wording 9517 9518Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9519 9520## Evidence needed before making an expertise or results claim 9521 9522- Claim ledger with exact allowed wording 9523- Source provenance and recalculation record 9524- Approval/rejection reason and review date 9525 9526These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9527 9528## Proposed public route and internal relationships 9529 9530Suggested route, pending canonical-host approval: `/expertise/claims-auditor/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9531 9532Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9533 9534## Conversion and measurement contract 9535 9536Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9537 9538Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9539 9540## Publication gate 9541 9542R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9543 9544No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9545 9546## Research references 9547 9548- [D21 — Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content): Original value, sources, authorship and first-hand expertise; not a points-based ranking formula. 9549- [D25 — Advertising FAQs: A guide for small business](https://www.ftc.gov/business-guidance/resources/advertising-faqs-guide-small-business): US advertising substantiation principles; context-specific legal review may still be needed. 9550- [D26 — Endorsements, influencers and reviews](https://www.ftc.gov/business-guidance/advertising-marketing/endorsements-influencers-reviews): Truthful endorsements and relevant disclosures; no invented testimonials or review provenance. 9551 9552============================================================================== 9553DOCUMENT 098 OF 135 9554Title: R15 public-content brief — How do you improve a service inquiry path without mistaking clicks for leads? 9555Path: Publishing/Briefs/R15-conversion-rate-optimization.md 9556Group: briefs 9557Label: PUBLIC WORKBENCH · not approved 9558Review status: scope_stated_in_document 9559============================================================================== 9560 9561# R15 public-content brief — How do you improve a service inquiry path without mistaking clicks for leads? 9562 9563**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R15. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9564 9565## Reader and purpose 9566 9567A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you improve a service inquiry path without mistaking clicks for leads?** 9568 9569**Distinct contribution:** A traceable friction hypothesis and qualification-aware measurement plan, with low-traffic limits stated honestly. 9570 9571## Candidate search questions — hypotheses, not measured demand 9572 9573- service website conversion audit 9574- qualified leads versus form clicks 9575- CRO low traffic website 9576 9577No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9578 9579## Proposed outline 9580 95811. Fix broken journeys first 95822. Observe friction 95833. Predefine outcome and guardrails 95844. Report effects without false causality 9585 9586Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9587 9588## Evidence needed before making an expertise or results claim 9589 9590- Journey/friction record tied to observation 9591- Predeclared hypothesis and evaluation design 9592- Outcome/guardrail report with uncertainty 9593 9594These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9595 9596## Proposed public route and internal relationships 9597 9598Suggested route, pending canonical-host approval: `/expertise/conversion-rate-optimization/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9599 9600Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9601 9602## Conversion and measurement contract 9603 9604Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9605 9606Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9607 9608## Publication gate 9609 9610R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9611 9612No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9613 9614## Research references 9615 9616- [D25 — Advertising FAQs: A guide for small business](https://www.ftc.gov/business-guidance/resources/advertising-faqs-guide-small-business): US advertising substantiation principles; context-specific legal review may still be needed. 9617- [D27 — Patterns of trustworthy experimentation: pre-experiment stage](https://www.microsoft.com/en-us/research/articles/patterns-of-trustworthy-experimentation-pre-experiment-stage/): Define trustworthy experiment design before interpreting results; no universal sample size or uplift claim. 9618- [D28 — Set up events](https://developers.google.com/analytics/devguides/collection/ga4/events): Event implementation and verification; emitting an event does not prove a qualified lead. 9619 9620============================================================================== 9621DOCUMENT 099 OF 135 9622Title: R16 public-content brief — How do you reconcile search visibility, AI referrals and qualified website inquiries? 9623Path: Publishing/Briefs/R16-analytics-measurement.md 9624Group: briefs 9625Label: PUBLIC WORKBENCH · not approved 9626Review status: scope_stated_in_document 9627============================================================================== 9628 9629# R16 public-content brief — How do you reconcile search visibility, AI referrals and qualified website inquiries? 9630 9631**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R16. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9632 9633## Reader and purpose 9634 9635A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you reconcile search visibility, AI referrals and qualified website inquiries?** 9636 9637**Distinct contribution:** A metric dictionary and synthetic-journey reconciliation that never merges incompatible denominators into a vanity score. 9638 9639## Candidate search questions — hypotheses, not measured demand 9640 9641- GA4 AI Assistant attribution 9642- GSC Bing citations versus website leads 9643- website inquiry event tracking audit 9644 9645No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9646 9647## Proposed outline 9648 96491. Define sources and scopes 96502. Validate an event against reality 96513. Separate channels and outcomes 96524. Disclose attribution limits 9653 9654Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9655 9656## Evidence needed before making an expertise or results claim 9657 9658- Metric/event contracts 9659- Synthetic journey collection and business-state reconciliation 9660- Data-quality, consent and attribution limitations report 9661 9662These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9663 9664## Proposed public route and internal relationships 9665 9666Suggested route, pending canonical-host approval: `/expertise/analytics-measurement/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9667 9668Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9669 9670## Conversion and measurement contract 9671 9672Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9673 9674Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9675 9676## Publication gate 9677 9678R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9679 9680No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9681 9682## Research references 9683 9684- [D28 — Set up events](https://developers.google.com/analytics/devguides/collection/ga4/events): Event implementation and verification; emitting an event does not prove a qualified lead. 9685- [D29 — Default channel group](https://support.google.com/analytics/answer/9756891?hl=en): AI Assistant channel; Google AI Overviews and AI Mode classified in Organic Search in current documentation. 9686- [D30 — Set up consent mode](https://developers.google.com/tag-platform/security/guides/consent): Technical consent signaling; configuration alone does not establish legal permission. 9687- [D31 — New AI visibility insights in Bing Webmaster Tools](https://blogs.bing.com/search/June-2026/New-AI-Visibility-Insights-in-Bing-Webmaster-Tools-Intents-Topics-Citation-Share-Compare): June 2026 reporting expansion; citation measurements are not website conversions or revenue. 9688 9689============================================================================== 9690DOCUMENT 100 OF 135 9691Title: R17 public-content brief — How do you prove that a website inquiry reached your mailbox? 9692Path: Publishing/Briefs/R17-email-deliverability.md 9693Group: briefs 9694Label: PUBLIC WORKBENCH · not approved 9695Review status: scope_stated_in_document 9696============================================================================== 9697 9698# R17 public-content brief — How do you prove that a website inquiry reached your mailbox? 9699 9700**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R17. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9701 9702## Reader and purpose 9703 9704A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you prove that a website inquiry reached your mailbox?** 9705 9706**Distinct contribution:** A controlled message trace and redacted header walkthrough, including the 2026 DMARC specification update and bounded receipt claims. 9707 9708## Candidate search questions — hypotheses, not measured demand 9709 9710- contact form email deliverability audit 9711- SPF DKIM DMARC website forms 9712- prove website inquiry mailbox delivery 9713 9714No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9715 9716## Proposed outline 9717 97181. Inventory sending paths 97192. Trace one synthetic message 97203. Inspect authentication and actual receipt 97214. Change policy carefully and retest 9722 9723Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9724 9725## Evidence needed before making an expertise or results claim 9726 9727- Sender-stream and authentication inventory 9728- Redacted received headers and controlled-mailbox observation 9729- DNS policy diff, monitoring and rollback plan 9730 9731These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9732 9733## Proposed public route and internal relationships 9734 9735Suggested route, pending canonical-host approval: `/expertise/email-deliverability/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9736 9737Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9738 9739## Conversion and measurement contract 9740 9741Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9742 9743Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9744 9745## Publication gate 9746 9747R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9748 9749No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9750 9751## Research references 9752 9753- [D32 — Email sender guidelines](https://support.google.com/a/answer/81126?hl=en): Provider authentication and sending requirements vary by sending class; no guaranteed inbox placement. 9754- [D33 — Simple Mail Transfer Protocol (RFC 5321)](https://www.rfc-editor.org/rfc/rfc5321.html): SMTP acceptance, relaying and failures; acceptance is distinct from final mailbox observation. 9755- [D34 — Sender Policy Framework (RFC 7208)](https://www.rfc-editor.org/rfc/rfc7208.html): SPF authorization and evaluation; inventory legitimate senders before altering DNS. 9756- [D35 — DomainKeys Identified Mail (RFC 6376)](https://www.rfc-editor.org/rfc/rfc6376.html): DKIM signatures and domain authentication; inspect results on received mail. 9757- [D36 — DMARC (RFC 9989)](https://www.rfc-editor.org/rfc/rfc9989.html): May 2026 core DMARC specification, obsoletes RFCs 7489 and 9091. A pass does not guarantee inbox desirability. 9758- [D37 — DMARC aggregate reporting (RFC 9990)](https://www.rfc-editor.org/info/rfc9990/): May 2026 aggregate reporting specification; data sensitivity and provider compatibility still require review. 9759- [D38 — DMARC failure reporting (RFC 9991)](https://www.rfc-editor.org/info/rfc9991/): May 2026 failure reporting specification; do not expose message data in public evidence. 9760 9761============================================================================== 9762DOCUMENT 101 OF 135 9763Title: R18 public-content brief — How do you improve local visibility without inventing locations or duplicating city pages? 9764Path: Publishing/Briefs/R18-local-seo-gbp.md 9765Group: briefs 9766Label: PUBLIC WORKBENCH · not approved 9767Review status: scope_stated_in_document 9768============================================================================== 9769 9770# R18 public-content brief — How do you improve local visibility without inventing locations or duplicating city pages? 9771 9772**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R18. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9773 9774## Reader and purpose 9775 9776A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you improve local visibility without inventing locations or duplicating city pages?** 9777 9778**Distinct contribution:** An eligibility-first local evidence map that connects actual service coverage, profile facts and useful regional content. 9779 9780## Candidate search questions — hypotheses, not measured demand 9781 9782- Google Business Profile service area eligibility 9783- local SEO real service area pages 9784- NAP consistency audit 9785 9786No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9787 9788## Proposed outline 9789 97901. Verify real business eligibility 97912. Align profile and website facts 97923. Support regional pages with evidence 97934. Measure location-specific results 9794 9795Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9796 9797## Evidence needed before making an expertise or results claim 9798 9799- Eligibility and business-fact register 9800- Approved profile changes and website consistency check 9801- Regional observation panel with context 9802 9803These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9804 9805## Proposed public route and internal relationships 9806 9807Suggested route, pending canonical-host approval: `/expertise/local-seo-gbp/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9808 9809Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9810 9811## Conversion and measurement contract 9812 9813Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9814 9815Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9816 9817## Publication gate 9818 9819R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9820 9821No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9822 9823## Research references 9824 9825- [D26 — Endorsements, influencers and reviews](https://www.ftc.gov/business-guidance/advertising-marketing/endorsements-influencers-reviews): Truthful endorsements and relevant disclosures; no invented testimonials or review provenance. 9826- [D39 — Guidelines for representing your business on Google](https://support.google.com/business/answer/3038177?hl=en): Real-world representation, eligible businesses and locations; no fabricated offices or credentials. 9827- [D40 — Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies): Link spam, doorway and scaled-content abuse boundaries; public authority cannot be manufactured with false signals. 9828 9829============================================================================== 9830DOCUMENT 102 OF 135 9831Title: R19 public-content brief — What makes a backlink or publication mention meaningful evidence of expertise? 9832Path: Publishing/Briefs/R19-digital-pr-authority.md 9833Group: briefs 9834Label: PUBLIC WORKBENCH · not approved 9835Review status: scope_stated_in_document 9836============================================================================== 9837 9838# R19 public-content brief — What makes a backlink or publication mention meaningful evidence of expertise? 9839 9840**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R19. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9841 9842## Reader and purpose 9843 9844A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **What makes a backlink or publication mention meaningful evidence of expertise?** 9845 9846**Distinct contribution:** A clear distinction between original useful work, independent coverage, owned profiles and sponsorship. 9847 9848## Candidate search questions — hypotheses, not measured demand 9849 9850- evidence based digital PR technical business 9851- earned authority versus paid backlinks 9852- technical case study publication outreach 9853 9854No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9855 9856## Proposed outline 9857 98581. Build something worth citing 98592. Select relevant audiences 98603. Disclose relationships 98614. Measure corroboration and useful referrals 9862 9863Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9864 9865## Evidence needed before making an expertise or results claim 9866 9867- Evidence-backed asset and outreach rationale 9868- Relationship/disclosure register 9869- Published references with context and independence label 9870 9871These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9872 9873## Proposed public route and internal relationships 9874 9875Suggested route, pending canonical-host approval: `/expertise/digital-pr-authority/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9876 9877Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9878 9879## Conversion and measurement contract 9880 9881Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9882 9883Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9884 9885## Publication gate 9886 9887R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9888 9889No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9890 9891## Research references 9892 9893- [D21 — Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content): Original value, sources, authorship and first-hand expertise; not a points-based ranking formula. 9894- [D25 — Advertising FAQs: A guide for small business](https://www.ftc.gov/business-guidance/resources/advertising-faqs-guide-small-business): US advertising substantiation principles; context-specific legal review may still be needed. 9895- [D26 — Endorsements, influencers and reviews](https://www.ftc.gov/business-guidance/advertising-marketing/endorsements-influencers-reviews): Truthful endorsements and relevant disclosures; no invented testimonials or review provenance. 9896- [D40 — Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies): Link spam, doorway and scaled-content abuse boundaries; public authority cannot be manufactured with false signals. 9897 9898============================================================================== 9899DOCUMENT 103 OF 135 9900Title: R20 public-content brief — How do you harden a business website without breaking its forms or tracking? 9901Path: Publishing/Briefs/R20-application-security-privacy.md 9902Group: briefs 9903Label: PUBLIC WORKBENCH · not approved 9904Review status: scope_stated_in_document 9905============================================================================== 9906 9907# R20 public-content brief — How do you harden a business website without breaking its forms or tracking? 9908 9909**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R20. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9910 9911## Reader and purpose 9912 9913A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you harden a business website without breaking its forms or tracking?** 9914 9915**Distinct contribution:** A scoped security/data-flow review with enforcement-mode tests, redacted artifacts and functional regression safeguards. 9916 9917## Candidate search questions — hypotheses, not measured demand 9918 9919- CSP website forms security audit 9920- website exposed files privacy logs 9921- secure contact form analytics 9922 9923No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9924 9925## Proposed outline 9926 99271. Map data and trust boundaries 99282. Prioritize exposure 99293. Test controls and integrations 99304. Publish only sanitized proof 9931 9932Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 9933 9934## Evidence needed before making an expertise or results claim 9935 9936- Data-flow/threat model and scoped findings 9937- Header/control behavior tests 9938- Redaction, secret handling and consent/retention review 9939 9940These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 9941 9942## Proposed public route and internal relationships 9943 9944Suggested route, pending canonical-host approval: `/expertise/application-security-privacy/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 9945 9946Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 9947 9948## Conversion and measurement contract 9949 9950Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 9951 9952Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 9953 9954## Publication gate 9955 9956R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 9957 9958No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 9959 9960## Research references 9961 9962- [D30 — Set up consent mode](https://developers.google.com/tag-platform/security/guides/consent): Technical consent signaling; configuration alone does not establish legal permission. 9963- [D41 — Application Security Verification Standard](https://owasp.org/www-project-application-security-verification-standard/): Application security verification requirements; tailor version and assurance scope before adopting controls. 9964- [D42 — Web Security Testing Guide](https://owasp.org/www-project-web-security-testing-guide/): Authorized security testing methodology; not permission to test third-party production systems. 9965- [D43 — Content Security Policy Level 3](https://www.w3.org/TR/CSP3/): Working-draft specification: report-only and enforcement differ; test against actual browser support. 9966- [D44 — Secure Software Development Framework 1.1](https://csrc.nist.gov/pubs/sp/800/218/final): Final SP 800-218 v1.1; the v1.2 public draft is not substituted as a final standard. 9967 9968============================================================================== 9969DOCUMENT 104 OF 135 9970Title: R21 public-content brief — What should a website regression suite prove before deployment? 9971Path: Publishing/Briefs/R21-qa-sdet.md 9972Group: briefs 9973Label: PUBLIC WORKBENCH · not approved 9974Review status: scope_stated_in_document 9975============================================================================== 9976 9977# R21 public-content brief — What should a website regression suite prove before deployment? 9978 9979**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R21. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 9980 9981## Reader and purpose 9982 9983A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **What should a website regression suite prove before deployment?** 9984 9985**Distinct contribution:** A risk-to-assertion map covering inquiry handling, URL policy and user interactions, with mocked versus live boundaries disclosed. 9986 9987## Candidate search questions — hypotheses, not measured demand 9988 9989- website regression test release checklist 9990- QA contact form failure paths 9991- automated crawl integration testing 9992 9993No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 9994 9995## Proposed outline 9996 99971. Start with risks and contracts 99982. Build safe fixtures 99993. Exercise failures 100004. Report what the green build does not cover 10001 10002Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 10003 10004## Evidence needed before making an expertise or results claim 10005 10006- Risk-to-test coverage map 10007- Versioned fixtures/assertions and execution report 10008- Reproduction artifacts and explicit coverage gaps 10009 10010These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 10011 10012## Proposed public route and internal relationships 10013 10014Suggested route, pending canonical-host approval: `/expertise/qa-sdet/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 10015 10016Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 10017 10018## Conversion and measurement contract 10019 10020Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 10021 10022Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 10023 10024## Publication gate 10025 10026R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 10027 10028No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 10029 10030## Research references 10031 10032- [D08 — Browsers](https://playwright.dev/docs/browsers): Supported engines and branded channels; WebKit automation is not a real Safari or iOS test. 10033- [D44 — Secure Software Development Framework 1.1](https://csrc.nist.gov/pubs/sp/800/218/final): Final SP 800-218 v1.1; the v1.2 public draft is not substituted as a final standard. 10034- [D45 — Release engineering](https://sre.google/sre-book/release-engineering/): Controlled, repeatable releases and rollback; actual release authorization is project-specific. 10035 10036============================================================================== 10037DOCUMENT 105 OF 135 10038Title: R22 public-content brief — How does an adversarial website review challenge a clean audit report? 10039Path: Publishing/Briefs/R22-adversarial-red-team.md 10040Group: briefs 10041Label: PUBLIC WORKBENCH · not approved 10042Review status: scope_stated_in_document 10043============================================================================== 10044 10045# R22 public-content brief — How does an adversarial website review challenge a clean audit report? 10046 10047**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R22. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 10048 10049## Reader and purpose 10050 10051A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How does an adversarial website review challenge a clean audit report?** 10052 10053**Distinct contribution:** A safe falsification checklist that tests claims, not just expected paths, while documenting authority and stop conditions. 10054 10055## Candidate search questions — hypotheses, not measured demand 10056 10057- adversarial website QA review 10058- website release negative testing 10059- AI agent prompt injection evidence review 10060 10061No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 10062 10063## Proposed outline 10064 100651. Name a claim to challenge 100662. Define safe scope 100673. Preserve counterexamples 100684. Retest and disclose residual risk 10069 10070Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 10071 10072## Evidence needed before making an expertise or results claim 10073 10074- Authorized scope and stop conditions 10075- Claim-to-counterexample test log 10076- Redacted findings and repair verification 10077 10078These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 10079 10080## Proposed public route and internal relationships 10081 10082Suggested route, pending canonical-host approval: `/expertise/adversarial-red-team/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 10083 10084Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 10085 10086## Conversion and measurement contract 10087 10088Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 10089 10090Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 10091 10092## Publication gate 10093 10094R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 10095 10096No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 10097 10098## Research references 10099 10100- [D41 — Application Security Verification Standard](https://owasp.org/www-project-application-security-verification-standard/): Application security verification requirements; tailor version and assurance scope before adopting controls. 10101- [D42 — Web Security Testing Guide](https://owasp.org/www-project-web-security-testing-guide/): Authorized security testing methodology; not permission to test third-party production systems. 10102- [D44 — Secure Software Development Framework 1.1](https://csrc.nist.gov/pubs/sp/800/218/final): Final SP 800-218 v1.1; the v1.2 public draft is not substituted as a final standard. 10103 10104============================================================================== 10105DOCUMENT 106 OF 135 10106Title: R23 public-content brief — How do you choose technical website topics that attract the right service inquiries? 10107Path: Publishing/Briefs/R23-product-marketing-research.md 10108Group: briefs 10109Label: PUBLIC WORKBENCH · not approved 10110Review status: scope_stated_in_document 10111============================================================================== 10112 10113# R23 public-content brief — How do you choose technical website topics that attract the right service inquiries? 10114 10115**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R23. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 10116 10117## Reader and purpose 10118 10119A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you choose technical website topics that attract the right service inquiries?** 10120 10121**Distinct contribution:** A buyer-problem map linking demand evidence, actual capability, proof and an appropriate service action. 10122 10123## Candidate search questions — hypotheses, not measured demand 10124 10125- technical service website positioning 10126- buyer intent website content strategy 10127- website troubleshooting service demand 10128 10129No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 10130 10131## Proposed outline 10132 101331. Define the buyer problem 101342. Separate evidence from assumptions 101353. Match offer to capacity 101364. Prioritize useful proof-led topics 10137 10138Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 10139 10140## Evidence needed before making an expertise or results claim 10141 10142- Audience/problem/alternative map 10143- Observed-language and demand evidence register 10144- Positioning hypothesis with disconfirmation conditions 10145 10146These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 10147 10148## Proposed public route and internal relationships 10149 10150Suggested route, pending canonical-host approval: `/expertise/product-marketing-research/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 10151 10152Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 10153 10154## Conversion and measurement contract 10155 10156Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 10157 10158Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 10159 10160## Publication gate 10161 10162R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 10163 10164No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 10165 10166## Research references 10167 10168- [D21 — Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content): Original value, sources, authorship and first-hand expertise; not a points-based ranking formula. 10169- [D25 — Advertising FAQs: A guide for small business](https://www.ftc.gov/business-guidance/resources/advertising-faqs-guide-small-business): US advertising substantiation principles; context-specific legal review may still be needed. 10170- [D47 — Plan your business](https://www.sba.gov/counseling/plan-your-business/): Market/business planning overview; query demand and commercial fit require local evidence. 10171 10172============================================================================== 10173DOCUMENT 107 OF 135 10174Title: R24 public-content brief — Who resolves conflicting fixes when SEO, performance and security disagree? 10175Path: Publishing/Briefs/R24-solutions-architecture.md 10176Group: briefs 10177Label: PUBLIC WORKBENCH · not approved 10178Review status: scope_stated_in_document 10179============================================================================== 10180 10181# R24 public-content brief — Who resolves conflicting fixes when SEO, performance and security disagree? 10182 10183**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R24. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 10184 10185## Reader and purpose 10186 10187A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **Who resolves conflicting fixes when SEO, performance and security disagree?** 10188 10189**Distinct contribution:** A decision record showing named owners, interface contracts, competing options and a reversible integrated solution. 10190 10191## Candidate search questions — hypotheses, not measured demand 10192 10193- website solutions architect technical SEO security 10194- conflicting website fixes integration 10195- website engineering ownership matrix 10196 10197No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 10198 10199## Proposed outline 10200 102011. Map decisions not job titles 102022. Identify interfaces 102033. Compare evidence and alternatives 102044. Release one coherent change set 10205 10206Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 10207 10208## Evidence needed before making an expertise or results claim 10209 10210- Task/decision ownership map 10211- Architecture decision and conflict register 10212- Integrated change and verification dependency plan 10213 10214These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 10215 10216## Proposed public route and internal relationships 10217 10218Suggested route, pending canonical-host approval: `/expertise/solutions-architecture/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 10219 10220Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 10221 10222## Conversion and measurement contract 10223 10224Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 10225 10226Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 10227 10228## Publication gate 10229 10230R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 10231 10232No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 10233 10234## Research references 10235 10236- [D44 — Secure Software Development Framework 1.1](https://csrc.nist.gov/pubs/sp/800/218/final): Final SP 800-218 v1.1; the v1.2 public draft is not substituted as a final standard. 10237- [D45 — Release engineering](https://sre.google/sre-book/release-engineering/): Controlled, repeatable releases and rollback; actual release authorization is project-specific. 10238- [D46 — Evolving SRE engagement model](https://sre.google/sre-book/evolving-sre-engagement-model/): Production readiness review and operational ownership; custom role organization is an agency design. 10239 10240============================================================================== 10241DOCUMENT 108 OF 135 10242Title: R25 public-content brief — What should a website release plan include beyond clicking deploy? 10243Path: Publishing/Briefs/R25-release-change-management.md 10244Group: briefs 10245Label: PUBLIC WORKBENCH · not approved 10246Review status: scope_stated_in_document 10247============================================================================== 10248 10249# R25 public-content brief — What should a website release plan include beyond clicking deploy? 10250 10251**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R25. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 10252 10253## Reader and purpose 10254 10255A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **What should a website release plan include beyond clicking deploy?** 10256 10257**Distinct contribution:** A controlled change record with exact scope, preflight, rollback ownership and independent postchange journey checks. 10258 10259## Candidate search questions — hypotheses, not measured demand 10260 10261- website deployment rollback plan 10262- technical SEO release management 10263- website production acceptance checklist 10264 10265No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 10266 10267## Proposed outline 10268 102691. Freeze scope and authority 102702. Verify recovery and dependencies 102713. Define stop conditions 102724. Accept the customer journey after deployment 10273 10274Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 10275 10276## Evidence needed before making an expertise or results claim 10277 10278- Authorized change/build and sequencing record 10279- Preflight/backup/rollback readiness evidence 10280- Deployment and postchange acceptance record 10281 10282These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 10283 10284## Proposed public route and internal relationships 10285 10286Suggested route, pending canonical-host approval: `/expertise/release-change-management/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 10287 10288Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 10289 10290## Conversion and measurement contract 10291 10292Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 10293 10294Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 10295 10296## Publication gate 10297 10298R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 10299 10300No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 10301 10302## Research references 10303 10304- [D44 — Secure Software Development Framework 1.1](https://csrc.nist.gov/pubs/sp/800/218/final): Final SP 800-218 v1.1; the v1.2 public draft is not substituted as a final standard. 10305- [D45 — Release engineering](https://sre.google/sre-book/release-engineering/): Controlled, repeatable releases and rollback; actual release authorization is project-specific. 10306- [D46 — Evolving SRE engagement model](https://sre.google/sre-book/evolving-sre-engagement-model/): Production readiness review and operational ownership; custom role organization is an agency design. 10307 10308============================================================================== 10309DOCUMENT 109 OF 135 10310Title: R26 public-content brief — What makes website acceptance testing genuinely independent? 10311Path: Publishing/Briefs/R26-independent-acceptance.md 10312Group: briefs 10313Label: PUBLIC WORKBENCH · not approved 10314Review status: scope_stated_in_document 10315============================================================================== 10316 10317# R26 public-content brief — What makes website acceptance testing genuinely independent? 10318 10319**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R26. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 10320 10321## Reader and purpose 10322 10323A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **What makes website acceptance testing genuinely independent?** 10324 10325**Distinct contribution:** A fresh-execution acceptance record with explicit reviewer relationship, build identity and evidence limitations—not AI persona theater. 10326 10327## Candidate search questions — hypotheses, not measured demand 10328 10329- independent website acceptance testing 10330- verify website builders tests 10331- website final acceptance evidence 10332 10333No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 10334 10335## Proposed outline 10336 103371. Set the contract before testing 103382. Declare actual independence 103393. Execute fresh critical journeys 103404. Report evidence and unresolved blocks 10341 10342Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 10343 10344## Evidence needed before making an expertise or results claim 10345 10346- Independence declaration and fresh run identity 10347- Requirement-to-observation record with raw artifacts 10348- Final bounded verdict and unresolved risks 10349 10350These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 10351 10352## Proposed public route and internal relationships 10353 10354Suggested route, pending canonical-host approval: `/expertise/independent-acceptance/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 10355 10356Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 10357 10358## Conversion and measurement contract 10359 10360Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 10361 10362Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 10363 10364## Publication gate 10365 10366R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 10367 10368No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 10369 10370## Research references 10371 10372- [D44 — Secure Software Development Framework 1.1](https://csrc.nist.gov/pubs/sp/800/218/final): Final SP 800-218 v1.1; the v1.2 public draft is not substituted as a final standard. 10373- [D45 — Release engineering](https://sre.google/sre-book/release-engineering/): Controlled, repeatable releases and rollback; actual release authorization is project-specific. 10374- [D46 — Evolving SRE engagement model](https://sre.google/sre-book/evolving-sre-engagement-model/): Production readiness review and operational ownership; custom role organization is an agency design. 10375 10376============================================================================== 10377DOCUMENT 110 OF 135 10378Title: Why SEO cannot repair a broken inquiry pipeline 10379Path: Publishing/Drafts/01-SEO-CANNOT-FIX-BROKEN-INQUIRIES.md 10380Group: drafts 10381Label: PUBLIC WORKBENCH · not approved 10382Review status: scope_stated_in_document 10383============================================================================== 10384 10385# Why SEO cannot repair a broken inquiry pipeline 10386 10387*A website needs separate evidence for discovery, usability, application handling, email delivery and qualified business outcomes.* 10388 10389> 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. 10390 10391A website can be discoverable and still fail the business. A customer may find the service page, understand the offer, complete the form and see a success message—yet the inquiry may not reach the person responsible for responding. 10392 10393The correct response is not automatically another SEO adjustment. It is to establish which part of the customer journey failed and assign that decision to the right specialist. 10394 10395## Start with the outcome, not the tool 10396 10397“More traffic” is a different objective from “every accepted inquiry is handled according to the service contract.” A search report can help explain discovery. It cannot, by itself, establish what an application persisted or which mailbox received a message. Likewise, a backend success response does not establish search visibility. 10398 10399A useful first question is: **What observable event would prove that the business outcome happened?** For an inquiry journey, that might involve a durable application record, a controlled mailbox observation and a later qualification decision. Those are different states and should remain different measurements. 10400 10401## Separate the layers before changing them 10402 10403Reliability and networking establish whether the intended public journey is reachable. Frontend and browser work establish whether the customer can operate the page. Accessibility assessment examines whether the complete task can be understood and completed with the agreed assistive workflows. Backend engineering verifies authoritative validation, persistence and error handling. Email delivery work traces the mail handoff and actual recipient evidence. 10404 10405Search engineering then has a defensible foundation on which to work: an accessible, useful public source and a functioning business process behind it. Google’s minimum technical requirements concern eligibility for Search; they do not certify the application’s inquiry handling or guarantee indexing. [Technical requirements](https://developers.google.com/search/docs/essentials/technical). 10406 10407## A hypothetical failure, traced properly 10408 10409Consider a hypothetical contact form that displays “Message sent” immediately after the customer clicks Submit. The browser later receives a provider timeout, but the interface never changes its message. An analytics event also fires when the thank-you panel appears. 10410 10411In that example, three observations can disagree: the visible message, the application outcome and the analytics count. The useful investigation follows one synthetic request through each state. The frontend engineer checks when success is displayed; the backend engineer inspects the actual request and durable handling; the measurement engineer checks whether the event corresponds to a genuine state transition. The email specialist becomes the lead for downstream delivery only after the application-to-provider handoff is established. 10412 10413This is an illustration of a diagnostic method, not a report of a completed engagement or a claim about any particular website. 10414 10415## Evidence makes the handoffs work 10416 10417Each specialist should receive the same task identifier, timestamps, relevant build/environment and a safe correlation reference. The handoff should say what was observed and which decision remains unresolved. It should not turn “provider accepted” into “customer inquiry delivered.” SMTP defines transport responsibilities, but its acceptance states are not a universal inbox-placement guarantee. [SMTP specification](https://www.rfc-editor.org/rfc/rfc5321.html). 10418 10419The final check should repeat the agreed critical journey with fresh synthetic input. The report must say which browsers, environments and delivery observations were actually tested, and which were unavailable. 10420 10421## Where SEO and AI visibility fit 10422 10423The goal is not to replace SEO with an engineering taxonomy. It is to stop asking one discipline to prove another discipline’s outcome. Search visibility, AI citations, referral sessions and qualified inquiries are different measurements. Google’s AI guidance also places optimization for its generative Search on core SEO foundations rather than a special-file shortcut. [AI optimization guidance](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide). 10424 10425A business can improve each stage without pretending that one metric certifies the entire system. That produces a more useful audit—and a more honest explanation of what the work achieved. 10426 10427--- 10428 10429## Editorial handoff — not public article copy 10430 10431R13: 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. 10432 10433============================================================================== 10434DOCUMENT 111 OF 135 10435Title: A public website needs a public test 10436Path: Publishing/Drafts/02-PUBLIC-REACHABILITY.md 10437Group: drafts 10438Label: PUBLIC WORKBENCH · not approved 10439Review status: scope_stated_in_document 10440============================================================================== 10441 10442# A public website needs a public test 10443 10444*Why private-network success, a running process and a valid-looking DNS record are not sufficient evidence of customer reachability.* 10445 10446> 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. 10447 10448A website that works from one computer has passed one connectivity test. Whether that test represents customers depends on where it was run and which path it used. 10449 10450This matters when a development or hosting environment uses a private network such as Tailscale. A tailnet connects authorized devices within its configured network. Successful access there does not, by itself, establish that an unaffiliated visitor or search crawler can reach the intended public hostname. [Tailscale tailnet concepts](https://tailscale.com/docs/concepts/tailnet). 10451 10452## Name the intended audience and path 10453 10454Before changing DNS or a firewall, distinguish the public website from private administration, monitoring and development services. A service that is intentionally private should not be exposed merely to make an external test green. 10455 10456For the public journey, record the hostname, the expected application and a genuinely external vantage point. Keep the private result as useful comparison evidence rather than relabeling it as an external test. 10457 10458## Examine DNS authority, not just one cached answer 10459 10460DNS has authoritative and recursive roles. A resolver may return cached information, while the authoritative nameservers describe the zone’s configured data. Comparing the two helps distinguish a configuration issue from a particular resolver’s cached view. Record timestamps and relevant TTL context; do not promise that a DNS change reaches every client at an exact universal time. [DNS concepts](https://www.rfc-editor.org/rfc/rfc1034.html). 10461 10462The question is not simply whether the domain has a record. It is whether the intended public name resolves to the authorized serving path and whether that path works. 10463 10464## Separate address families and hostname behavior 10465 10466When a hostname publishes both IPv4 and IPv6 addresses, test the advertised paths independently. A working IPv4 result should not conceal a broken IPv6 path. Similarly, a connection to an address is not enough when the application relies on the requested hostname and TLS configuration. 10467 10468An evidence matrix can identify each hostname, address family, test vantage, timestamp, expected result and observed result. Unavailable tests should remain clearly untested. The appropriate repair depends on the actual cause and intended configuration, not a generic instruction to remove records. 10469 10470## Follow the request to the application 10471 10472Once transport reaches the server, inspect the serving chain. Nginx may be receiving requests while the upstream application is unavailable. A service-manager process can be alive while a specific route is failing. Nginx’s documentation describes the proxy and process concepts, but the actual configuration paths and upstreams must be discovered in the authorized environment. [NGINX guide](https://nginx.org/en/docs/beginners_guide.html). 10473 10474Correlated timestamps and request references help the network and reliability specialists compare their observations. Bounded redacted logs are preferable to indiscriminate dumps of visitor data or credentials. 10475 10476## Change the smallest supported part 10477 10478A justified repair might involve a DNS answer, an ingress rule, a certificate configuration, a proxy target or an application dependency. Those changes have different owners and risks. Mail records, private services and canonical hostname decisions may be affected by a seemingly simple zone edit. 10479 10480Preserve the prior configuration, agree the exact change and rollback, and test the customer journey again from outside the private network. Recovery should be demonstrated through the same path that originally failed. 10481 10482A useful final report is specific: which public hostname worked, from which vantage, over which advertised paths, on which build and at what time. “It works on my machine” can remain one observation; it should not become the whole acceptance test. 10483 10484--- 10485 10486## Editorial handoff — not public article copy 10487 10488R13: 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. 10489 10490============================================================================== 10491DOCUMENT 112 OF 135 10492Title: Sent is not the same as received 10493Path: Publishing/Drafts/03-INQUIRY-DELIVERY-PROOF.md 10494Group: drafts 10495Label: PUBLIC WORKBENCH · not approved 10496Review status: scope_stated_in_document 10497============================================================================== 10498 10499# Sent is not the same as received 10500