Capture dates: The exhibits cover February 12–October 8, 2026. The latest captures document partial domain visibility and zero results for the targeted Hawaii Courts query.
Bing’s own tools reported inconsistent states for gtcode.com depending on the page inspected: blocked, not discovered, invisible in public search, or indexed successfully. Public Bing visibility has fluctuated between complete absence and limited results. On October 8, 2026, Bing displayed two gtcode.com URLs on the captured first page—a technical article and an archived government-source document—while returning zero results for the Hawaii Courts directory. On February 15, Bing Webmaster Tools had explicitly marked The Nod, a known Hawaii Courts investigation URL, as “Blocked.” The documented blocking and public-search absence are established observations; their cause remains unresolved.
On May 17, a public Bing search for site:nshkr.com returned visible results for that lower-traffic domain, which uses the same general publication stack. Cloudflare analytics captured that day showed materially more measured traffic for gtcode.com than for nshkr.com over the previous 30 days. Bing still returned no visible site:gtcode.com results.
This article documents Bing Webmaster diagnostic differences and public-search behavior over time. Ordinary technical explanations are considered first: crawler scheduling, stale diagnostics, site-scan bugs, CDN/crawler mismatch, canonicalization, transient HTTP behavior, quality classifiers, policy systems, duplicate handling, index freshness, and public-result rendering differences. The exhibits test those explanations against Bing’s own screenshots. The current evidence does not identify any human actor inside or outside Microsoft.
The evidence shows inconsistent diagnostics and repeated public searches with no visible gtcode.com results. It does not show what caused those results, whether a complaint or policy decision was involved, or whether a particular article played a role. Bing records, crawler logs, policy notices, support responses, complaint records, or other technical evidence would be needed to answer those questions.
On February 12, 2026, a routine check of Bing Webmaster Tools and public search showed that gtcode.com returned zero visible public results on Microsoft’s search engine.
The evidence comes from Microsoft’s own tools.
Exhibit A: The February 12 Disappearance
On February 12, 2026, a site:gtcode.com search on Bing returned no visible results.
“There are no results for site:gtcode.com.”
The domain has published investigative journalism and open-source software documentation since 2025. It has a valid sitemap, a robots.txt that explicitly welcomes all crawlers, valid structured data, and no crawl barrier identified in the checks described here.
Exhibit B: The Investigation Page
URL Inspection of the most recent investigation — “The Nod: Visual Allegation, Audio Sequence, and Review Gap” — returns “Not discovered.”
“URL cannot appear on Bing. The inspected URL is not known to Bing.”
This status could reflect a page awaiting discovery or an out-of-date diagnostic. Later exhibits show a broader site-level diagnostic anomaly. The “Request indexing” control exists. The unresolved question is why URL Inspection labeled the page not known despite a valid sitemap and no identified crawl barrier, while other URLs on the same domain showed different statuses.
Exhibit C: The Control Case
This is the exhibit that first indicated the diagnostic pattern was not limited to one article.
“The inspected URL is known to Bing but has some issues which are preventing us from serving it to our users. We recommend you to follow Bing Webmaster Guidelines.”
The inspected URL points to documentation for an open-source Elixir library — agent_session_manager — a technical package for managing AI agent sessions. It contains:
- API documentation
- Installation instructions
- Code examples
- A link to the Hex.pm package registry
The page contains ordinary software documentation. Its reported status shows that the diagnostic pattern extended beyond the investigation page.
Note the distinction. Exhibit B says “Not discovered” — the tool labels the URL as not known. Exhibit C says the URL “is known to Bing”. Bing’s tools marked the URL as known and blocked. The screenshot establishes that Bing reported the URL as known and unable to be served. It does not identify a crawl event, human review, policy decision, or the cause of that status.
The two pages share a domain, but these captures alone do not establish a domain-wide action.
Technical Pattern
The process question here is technical: what mechanism reduced public visibility, what ordinary explanation applies, and what record would test the cause?
The exhibits document site-level and page-level diagnostic differences inside Bing’s own webmaster tools. Any explanation involving a policy system, third-party report, technical bug, or intent would require Bing support responses, policy notices, crawl logs, server logs, Lumen entries, reproducible crawler audits, or subsequent public-search behavior.
What The Evidence Leaves Open
The current evidence does not identify any human actor inside or outside Microsoft.
Captured public-search behavior includes zero visible site:gtcode.com results on February 12, partial visibility on May 12, zero visible results again on May 17, and two visible first-page domain URLs on October 8 alongside zero targeted Hawaii Courts results. In the May 17 control capture, nshkr.com appeared in Bing while gtcode.com did not, despite gtcode.com having more traffic in the captured Cloudflare window.
Search engines use automated policy systems, quality classifiers, crawler queues, site diagnostics, spam and malware classifiers, complaint-review channels, and public-result rendering layers. Any of those mechanisms could explain reduced or uneven visibility. So could benign internal explanations: stale diagnostic state, unsupported status propagation, false-positive filters, canonicalization defects, or index-serving bugs.
It is still unknown whether anyone filed a complaint, whether Bing applied a policy rule, whether a technical bug is involved, or whether Bing has placed gtcode.com in a site-level diagnostic or policy state.
The Open Questions
What requests and responses underlie the reported statuses? Bingbot and CDN logs could test request-specific errors, crawler access, and transient conditions.
What is the specific “issue” preventing the agent_session_manager page from being served? Bing’s message does not identify whether the status reflects a technical error, an indexing classification, or another mechanism.
Are the same pages visible on other search engines? Repeated exact-URL, exact-title, and site queries could help characterize whether the observed visibility problem is Bing-specific.
When did the visibility problem begin relative to publication dates and site changes? Timeline comparison can test technical explanations against the observed changes.
Is there a policy notice or removal-request record affecting the domain? The captured Webmaster Tools views do not establish whether one exists. A Bing response or public record, such as a Lumen entry, would be needed.
The Evidence Standard
The initial exhibits are screenshots from Microsoft’s own Bing Webmaster Tools and public search results, taken on February 12, 2026, by the verified site owner. They are primary-source outputs showing that:
- The captured
site:gtcode.comsearch returned no visible results on February 12, 2026 - Investigation pages are “Not discovered”
- Bing’s tools reported an open-source software page as known to Bing and unable to be served to users
The screenshots are the primary sources. On May 12, one gtcode.com result appeared in the captured Bing page. On May 17, no visible site:gtcode.com results appeared, while the same-day control domain site:nshkr.com remained visible and Cloudflare showed materially higher traffic for gtcode.com than for the control domain. On October 8, two domain URLs appeared on the captured first page, while the targeted Hawaii Courts search returned no results. The February 15 URL Inspection had already marked a known investigation URL as blocked.
This article documents Bing’s treatment of gtcode.com as reflected in Bing Webmaster Tools and search results. Bing has not explained why. The current record shows a visibility anomaly and diagnostic differences. Proving that any specific article, person, complaint, or policy rule caused the result would require additional technical or platform records.
Update: February 15, 2026
Exhibit D: “Not Discovered” Becomes “Blocked”
Two days after this article was published, the same investigation page from Exhibit B — “The Nod: Visual Allegation, Audio Sequence, and Review Gap” — was re-inspected using Bing Webmaster Tools.
The status has changed.
On February 12, URL Inspection labeled this page “Not discovered”. On February 15, the status reads “Blocked”:
“URL cannot appear on Bing. The inspected URL is known to Bing but has some issues which are preventing us from serving it to our users. We recommend you to follow Bing Webmaster Guidelines.”
This is the same message, word for word, that appeared on the open-source Elixir software page in Exhibit C. Both inspected pages now carry the same reported status.
Between the two captures, URL Inspection changed from “Not discovered” to “Blocked” and represented the page as known. The screenshots establish that status change; they do not establish when or how Bing discovered or evaluated the URL.
Bing’s tools marked the URL as known and blocked in the later capture.
Update: February 18, 2026
Exhibit E: A 4xx Finding Not Reproduced in External Tests
Six days after the initial documentation, and three days after Exhibit D showed the page’s status change from “Not discovered” to “Blocked”, a standard diagnostic step was taken: a Site Scan was initiated through Bing Webmaster Tools. This is Microsoft’s own tool for webmasters — designed to identify technical problems that might prevent a site from appearing in search results. The purpose is to help site owners fix their sites.
The scan completed. An email confirmation arrived from Bing Webmaster Tools ([email protected]):
“Scan initiated in Bing Webmaster with name test is now available.”
The scan report contained a single finding: “ERROR: Http 400-499 errors” — on the homepage.
The scan reported page depth 0 and an HTTP 4xx finding for https://gtcode.com/. The screenshot does not include the underlying request, response headers, or server log needed to establish what that scan received.
There is one problem with this finding: the reported error fails external reproduction.
The homepage returns HTTP 200 — the standard success response — to every user agent tested, including a user-agent string identifying as Bingbot (Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)). It returns 200 over HTTP/1.1 and HTTP/2. It returns 200 with no user agent at all. The page loads. The content renders. The tests showed no server-side rejection.
This was tested independently on February 18, 2026, using multiple user agents and protocol versions against the live site. Every request in those tests succeeded. The 4xx finding could not be reproduced in those tests. Requests using a Bingbot user-agent string do not reproduce Bing’s source IP, request path, timing, or network conditions.
A URL Inspection was then run on the homepage itself — the same URL the Site Scan claimed was returning 4xx errors:
The result: “Discovered but not crawled. URL cannot appear on Bing.” The crawl section states: “The inspected URL is known to Bing but has some issues which are preventing indexation.” The tool supplied a vague advisory to “follow Bing Webmaster Guidelines” without a specific actionable explanation.
URL Inspection displayed a discovery date of 14 November 2017 alongside “Discovered but not crawled.” That status is not a complete request history and does not establish that Bing made no crawl attempt in eight years.
Microsoft describes URL Inspection as providing crawl and indexing information, and Site Scan as a separate, on-demand site audit. A Site Scan request and a search-crawler status can refer to different processes or times. The two outputs therefore need an explanation, but they do not prove that an impossible internal state occurred.
Page Diagnostics and Public Search
On the same day, a URL Inspection was run on a different page: https://gtcode.com/consulting/ — a services page.
The result: “Indexed successfully. URL can appear on Bing.” Green checkmarks. No SEO issues. No problems found.
Compare this to the other URL Inspections documented in this investigation:
| Page | Content | Bing Status |
|---|---|---|
/ | Homepage | Discovered but not crawled |
/hawaii-courts/the-nod-visual-allegation/ | Judicial-accountability investigation | Blocked |
| /consulting/ | Services page | Indexed successfully |
Bing’s own URL Inspection tool reported that a consulting page on gtcode.com was indexed and could appear in search results. But Exhibit A showed that, on February 12, 2026, a site:gtcode.com search on Bing returned zero visible results.
The captured outputs differed:
- URL Inspection labeled the homepage “Discovered but not crawled”; Site Scan reported a 4xx finding.
- URL Inspection displayed the 2017 discovery date without supplying a complete crawl history.
- The consulting page was labeled indexed and eligible, while the February 12 public site-search capture returned no visible results.
- The investigation and software pages carried “Blocked” statuses.
- The 4xx finding was not reproduced in the external tests.
As of the February 18 check, the consulting page still did not surface in public site: search. These captures document a difference between an eligibility diagnostic and observed search results. They do not identify an internal override or establish that the outputs describe the same processing state or time.
The Control Domain
There is a second domain on the same general publication stack: nshkr.com. Same static site generator (Hugo). Same hosting platform (GitHub Pages). Same CDN and DNS provider (Cloudflare). Same domain registrar. Same deployment pipeline.
nshkr.com appeared normally in the captured Bing checks, with no comparable 4xx finding or visibility anomaly observed.
What This Exhibit Weighs Against
The external HTTP 200 tests weigh against a persistent error affecting every request to the homepage. The visible control domain weighs against a failure common to every site using Hugo, GitHub Pages, and Cloudflare. The indexed consulting page and blocked software documentation show that Bing’s displayed statuses varied across different kinds of content.
Those controls do not exclude domain-specific configuration, request-path differences, Bing-specific crawler treatment, transient conditions, or other technical causes. Sharing a publication stack does not establish identical behavior for every crawler request. Ordinary software content also does not exclude quality or indexing classifications.
Microsoft’s tools produced materially different diagnostic states across the same domain, some difficult to reconcile with external tests and public search. The available evidence does not identify which Bing subsystem or process produced those differences. Request logs, response details, status histories, and a support explanation could distinguish among the possible causes.
Update: May 12, 2026 — One Visible Result Appears
A later public Bing search for site:gtcode.com shifted away from the clean zero-result page documented in Exhibit A. Bing displayed “About 50 results” while visibly showing only one result from gtcode.com:
Harness Engineering: The Discipline of Building Systems
https://gtcode.com/articles/harness-engineering
The visible URL points to a technical article about harness engineering. The screenshot captures only the first-page result set.
Exhibit F: Bing public search for site:gtcode.com, showing “About 50 results” but visibly surfacing only one gtcode.com result on the captured first page, the technical article /articles/harness-engineering/.
The February 12 screenshot documented zero visible results in that site-search capture. The later result shows partial visibility: one URL surfaced on the captured first page. Bing has not explained why.
The captured dates show this:
- Bing previously returned zero visible results for
site:gtcode.com. - Bing Webmaster Tools reported different states across the same domain: “Not discovered,” “Blocked,” “Discovered but not crawled,” and “Indexed successfully.”
- A later public
site:search reported “About 50 results.” - The visible result set surfaced only one gtcode.com page.
Bing can report a larger result count than the captured first-page result set reflects. The records needed to evaluate that gap are crawler logs, index-status histories, policy notices, support responses, and reproducible control queries.
Update: May 17, 2026 — Public Bing Search Returns to Zero Visible Results
On May 17, 2026, public Bing search for site:gtcode.com again returned no visible results.
This is a material update to the May 12 record. The May 12 screenshot showed incomplete partial visibility: Bing reported about 50 results, while the captured first page visibly surfaced only one gtcode.com URL, a technical article. The May 17 screenshot returns the public-search condition to the February 12 state: zero visible domain results for gtcode.com.
Same-day control: nshkr.com remains visible
The same day, a public Bing search for site:nshkr.com returned ordinary visible results and reported about 50 results.
The control matters because nshkr.com runs on the same general publication stack: static Hugo output, GitHub Pages hosting, Cloudflare in front, and the same site-owner operating environment. The observed difference is not that Bing could not render or serve that class of site. Bing served the control domain in public site-search while returning no visible public site-search results for gtcode.com.
Same-day traffic comparison
Cloudflare analytics captured on May 17 showed gtcode.com had substantial measured traffic over the previous 30 days: 53.05k unique visitors, with a maximum of 5.26k unique visitors in a day and a minimum of 1.63k.
The same Cloudflare view for nshkr.com showed 6.63k unique visitors over the previous 30 days, with a maximum of 662 unique visitors in a day and a minimum of 391.
In the captured window, gtcode.com had roughly eight times the unique visitors of the control domain. Bing public search exposed ordinary site:nshkr.com results while returning no visible site:gtcode.com results. The traffic comparison documents the scale of visits, not Bing crawl eligibility: Cloudflare visitor counts and Bing indexing measure different things, and sharing a publication stack does not control for domain-specific crawler responses or index-quality signals.
The May 17 capture documents zero visible gtcode.com results in that public Bing site: search on May 17, 2026. It does not establish the site’s search visibility on dates not captured here, or identify any actor or intent. Explaining why requires Bing-side records, crawler logs, policy notices, complaint records, or support responses.
Exhibit H: October 8, 2026 — Partial Domain Visibility, Zero Hawaii Courts Results
On October 8, 2026, a public Bing search for site:gtcode.com displayed “About 57 results” but returned only two visible gtcode.com URLs on the captured first page:
/articles/harness-engineering/— a technical article./sources/the-ledger/DCCA_Search_HFBA.html— an archived Hawaii business-registration source page, titled “Hawaii Business Express | BREG DCCA.”
Exhibit H1: October 8 domain search. Bing reports an estimated count of about 57 but displays only two URLs on page one. The capture does not establish what appears on pages two and three.
A separate public Bing search targeting the Hawaii Courts directory, site:gtcode.com/hawaii-courts/, returned:
“There are no results for site:gtcode.com/hawaii-courts/”
Exhibit H2: October 8 Hawaii Courts search. Bing returns no results for the targeted investigation directory.
This is a material addition to the search-visibility record. Bing visibly returned a technical article and archived source material from gtcode.com while returning zero results for the Hawaii Courts investigation directory in the captured search.
The February 15 URL Inspection in Exhibit D explicitly marked The Nod, a Hawaii Courts investigation, as known to Bing but “Blocked”, with issues preventing Bing from serving it to users. The October 8 screenshots do not establish that article’s current URL Inspection status, but they document the continued public-search absence of the Hawaii Courts portfolio in the targeted query.
Bing’s estimated domain result count does not establish how many URLs are actually indexed or publicly retrievable. The captures establish a portfolio-specific public-search visibility disparity. They do not identify its cause or intent, or reveal which pages Bing retains internally.
| Capture date | Bing’s reported domain count | Visible domain results in the capture | Targeted Hawaii Courts search |
|---|---|---|---|
| February 12, 2026 | No results | None | Not captured |
| May 12, 2026 | About 50 | One technical article on page one | Not captured |
| May 17, 2026 | No results | None | Not captured |
| October 8, 2026 | About 57 | Two URLs on page one: a technical article and an archived source document | No results |
The unresolved question is what accounts for the limited domain results and the zero-result directory query.
What The Evidence Leaves Open
Public Bing results and Bing Webmaster Tools show a search-index diagnostics problem. The current record identifies no human actor. It does not show whether a technical bug, a stale diagnostic state, a policy system, a third-party complaint, or some combination caused the result. On May 12, at least one technical article surfaced. The May 12 capture leaves a gap between Bing’s estimated result count and the single visible first-page result; the May 17 capture shows no visible results. The October 8 capture shows partial domain visibility again, with two visible first-page URLs, but the targeted Hawaii Courts query returns zero results. Exhibit D establishes that Bing previously reported a known investigation URL as blocked from being served. The search captures document public visibility; they do not reveal Bing’s internal index coverage or identify the mechanism causing the disparity.
What Would Resolve This
The fastest way to resolve the diagnostics issue would be one of the following:
- a Bing support response identifying the technical or policy basis;
- crawl logs showing whether Bingbot received a reproducible server-side error;
- a policy notice, URL-removal notice, or webmaster action message;
- a Lumen record or other public removal-request record;
- a reproducible third-party crawl audit showing the same problem outside Bing;
- a subsequent ordinary
site:gtcode.comresult set showing navigable coverage of the domain, including investigation pages.
What Would Falsify This
The article’s characterization of ongoing visibility would need revision if Bing reliably returned a representative set of gtcode.com results in public site: search, if Bing provided a specific technical explanation for the different Webmaster Tools states, or if server-side evidence showed a previously missed crawl barrier affecting Bingbot. The dated historical screenshots would remain observations from their capture dates.
It would also need revision if the same-stack control domain began showing the same disappearance pattern, because that would make a stack-level explanation more plausible. As of the May 17 capture, the opposite pattern is present: the control domain appears in Bing public site-search while gtcode.com does not.
The May 17 evidence documents a return to full public-search disappearance after the May 12 partial-visibility capture. The October 8 evidence updates the latest observed state to partial domain visibility with zero targeted Hawaii Courts results. Neither establishes a human actor, complaint source, policy reason, or intent.
What Happens Next
The next record-building steps are straightforward:
- Repeat same-session public Bing checks for
site:gtcode.com,site:gtcode.com/hawaii-courts/,site:nshkr.com, exact-title queries, and exact-URL queries. - Preserve same-day Cloudflare traffic captures around each search screenshot.
- Compare Bing behavior against Google, DuckDuckGo, and direct sitemap fetches.
- Request Bing-side clarification for the different states: blocked, not discovered, indexed successfully, site-scan 4xx, partial visibility, and zero-result public search.
- Treat cause as unresolved unless Bing records, crawler logs, complaint records, or policy notices identify the mechanism.
— Ekewaka Lono, 13 February 2026 (updated 10 October 2026)