GEO Lab #05: Methods and Source Notes

Methods and source notes for the fifth learning record. This is a summary of technical observations, not an archive of new AI answers.

Publication boundary. The public JSON reproduces the visible aggregate tables. It is not a raw Search Console or Bing export. Private raw responses, screenshots, account/verification identifiers, secrets and private workflow links are not published.

Initial design and units

  • Google: 10 important editorial/navigation/appendix URLs, checked with the official indexed-version URL Inspection API.
  • Bing: 70 canonical content URLs, plus read-only site and Sitemap queries. A successful batch therefore has 72 API reads, not 72 indexed pages.
  • OpenAI eligibility: 70 public URLs checked for observable configuration/access conditions and fetched using a declared crawler user agent.
  • IndexNow: 70 deployed content fingerprints in the initial ledger. Only a verified real content addition, material update or deletion is eligible for a notification.

Lab #05 is not the postponed AI-search experiment. No ChatGPT/Grok prompt, recommendation rate, brand mention uplift or citation effect was measured here. The earlier AI-answer evidence library remains at 60 selected answers across Labs #01–#04.

Separate observations in time

ObservationSource time (UTC)Recorded result
Google indexed-version snapshot2026-11-06T11:45:46.842406+00:005 INDEXED; 5 NOT_INDEXED.
Bing successful information-query batch2026-11-06T09:26:16.359455+00:0070/70 URL queries succeeded; 70 index-membership and crawl-lifecycle states UNKNOWN.
Later combined monitor: Bing phase2026-11-06T11:46:50.389048+00:0011 successes; 1 ThrottleHost fault; 58 unqueried quota-blocked positions.
OpenAI configuration and declared-UA simulation2026-11-06T11:47:55.531296+00:0070 configuration-allowed and 70 simulated fetch successes; real crawler/index UNKNOWN.
IndexNow ledger/key observation2026-11-06T11:48:03.007423+00:0070 unchanged URLs; key file matched; 0 POSTs.

Times describe their source observations, not this page publication. Collection windows, engine outcomes and later interpretation remain separate. Default or absent date values are not turned into crawl evidence.

Sitemap submission is not indexing

EngineSeparate recorded statusLimit
GoogleOne official submission accepted with HTTP 204 on November 4. Initial API read: isPending=true; lastDownloaded absent.No confirmed download/processing completion at this snapshot. Missing download time is not itself a diagnosed crawl failure.
BingExisting imported feed confirmed as registered / Success, reporting 10 URLs in the successful read.A later quota stop skipped the feed read. It does not revoke the earlier Success observation or prove per-URL indexing.

The public Sitemap is generated from recorded canonical routes and real editorial revision dates. This edition adds the Lab #05 reader and methods page. Its new routes are not retroactively included in the earlier ten-URL feed observation or seventy-URL batch results.

Later verified observations

These dated follow-ups extend the record. They do not overwrite the earlier snapshots or establish an AI recommendation effect.

Time (UTC)ObservationVerified resultBoundary
2026-11-06T11:59:17.427043+00:00The Google Search Console Sitemaps screen reported "Could not read this sitemap", with a displayed last-read date of November 4 and zero discovered pages.This is an independently recorded owner-console observation, separate from the API isPending=true response. No corrective resubmission had been made at this observation.The screen did not expose a specific HTTP or XML error. A successful API submission and a browser HTTP 200 do not establish a successful Google fetch.
2026-11-06T12:57:21.739ZOne corrective Google Sitemap submission was accepted in the owner console after the genuine Lab #05 publication changed the verified Sitemap from 10 to 12 canonical URLs.The success confirmation followed the submission started at 12:56:01 UTC. This was a separate corrective UI action, not a second initial API PUT or a recurring duplicate submission.Acceptance does not establish that Google downloaded, processed or indexed the new pages. The earlier could-not-read observation remains in the record.
2026-11-06T13:03:44.549018+00:00The expanded Google indexed-version snapshot covered 12 important canonical URLs.5 URLs were INDEXED and 7 were NOT_INDEXED. The two new editorial pages are part of this later twelve-URL scope, not the earlier ten-URL baseline.These are official Google indexed-version observations at this time, not live tests, Bing outcomes or evidence of AI recommendations.
2026-11-06T13:03:44.221335+00:00The Google Sitemap API was read after the corrective UI submission.isPending remained true, lastDownloaded was absent, and the returned error and warning counts were zero.A successful submission is not confirmed processing. No new download time is inferred from the missing field.
2026-11-06T13:05:02.774161+00:00The later combined monitor queried all 72 current canonical content URLs in Bing with ten-second spacing.72/72 URL queries succeeded; site access and the Sitemap read also succeeded. The feed remained registered with processing status Success.All 72 Bing index-membership states remain UNKNOWN. This later success does not erase the earlier five-second throttled run or prove that spacing alone caused recovery.
2026-11-06T13:17:48.178440+00:00OpenAI search crawl-eligibility checks expanded to the 72 current canonical content URLs.72 configuration-allowed results and 72 successful declared-user-agent simulated fetches were recorded.Real OAI-SearchBot access and OpenAI index membership remain UNKNOWN; simulated access is not a verified crawler visit.
2026-11-06T13:18:13.900470+00:00The full combined monitoring workflow completed successfully and made one real IndexNow notification for 11 genuinely new or updated URLs.The response was HTTP 202 / KEY_VALIDATION_PENDING. The notification, expanded snapshots and history were saved; no ChatGPT/Grok answer experiment was run.HTTP 202 means key validation remains pending. Receipt acceptance is not crawling, indexing or AI recommendation evidence; unchanged URLs are not repeatedly submitted merely to obtain another status.
2026-11-06T13:33:18.073ZBetween 2026-11-06T13:19:02.659Z and 2026-11-06T13:33:18.073Z, an owner-authorized assistant used the official Google Search Console interface to request indexing for seven pages.A fresh indexed-version inspection before each request showed NOT_INDEXED. All seven requests received the interface acknowledgement that the URL had been accepted into the priority crawl queue.Accepted indexing requests are not evidence that the pages were indexed. The 13:03 UTC snapshot of 5 INDEXED and 7 NOT_INDEXED predates these requests and is not backfilled; this follow-up claims no new post-request indexing result.

Rules that protect the record

  • Retain original fields and immutable snapshots. Keep derived summaries separate from source observations.
  • Query success and HTTP status never override a missing indexed-version verdict.
  • Keep each planned URL, including failures and zero-attempt skipped positions.
  • Use a fixed property and approved read operations. Google readonly authorization and Bing's account-wide API key are different permission models; the program limits Bing calls to the approved site.
  • Keep credentials in protected storage and private encrypted workflow Secrets, never public content or state.
  • Preserve uncertain delivery state. A received IndexNow request or a confirmed notification is not a crawl/index confirmation.
  • Compare source times and execution environments. One local or manually dispatched success cannot prove every recurring scheduled run will pass.

Official references

  • Google URL Inspection API

    Queries the indexed version; it is not a live test or an indexing request.

  • Google Sitemap fields

    Submission, processing and download observations are separate fields.

  • Bing GetUrlInfo

    The returned URL fields do not supply an unambiguous membership verdict.

  • Bing API fault codes

    ThrottleHost is code 5; the observed response used HTTP 400.

  • Bing URL Inspection

    Index details and a live URL check answer different questions.

  • IndexNow protocol

    A project-subfolder key requires an explicit keyLocation; a receipt does not establish crawling or indexing.

  • OpenAI crawlers

    A declared user agent is different from a request whose source identity can be checked.

  • GitHub Pages API

    Pages management/build interfaces are not a per-request crawler log.

Public data and reproduction

Reviewed aggregate observations · Publication scope · Download the public summary

Build this edition offline with python3 scripts/build_stage5_report.py; rebuild the full site with python3 scripts/build_site.py --preserve-evidence. These commands do not call search engines or submit URLs.

The public monitoring code can be adapted to another verified site using its owner's authorization. The private raw responses are not in the download, so the aggregate checks cannot independently audit every source field.

Author: Helen Bird · Observation period: 2026-11-04 to 2026-11-06 (technical observations; no AI-answer experiment) · First published: 2026-11-06 · Last revised: 2026-11-06 · Version: v1.1

Added dated follow-ups: expanded 12/72 URL monitoring, successful combined run, genuine IndexNow receipt with key validation pending, corrective Sitemap submission, and seven acknowledged indexing requests. Initial observations and failures remain unchanged; private raw data remains excluded.

Version metadata · Revision history · Cross-report review decisions · Stage 4 review decisions · Technical maintenance