The mem0ai/dolphinbench website has been changed to output the Google Analytics tag directly in the head of the page's first response. The 2026-09-23 commit (#7, 81cb6f8) replaced the gtag script, which had been injected after hydration using next/script's afterInteractive strategy, with a plain script tag, so that the complete tag containing the measurement ID G-DS880BMQ34 is included in the initial HTML head. The changed files are four under website/, with 51 insertions and 13 deletions.
This adjustment is intended for search engine support. Google Search Console, which indexes the site, verifies ownership through the Analytics tag, but when the script was inserted after hydration it did not remain in the head, making verification impossible. With layout.tsx explicitly opening the head element and placing the Analytics component inside it, the tag on public pages will now be loaded starting with the very first HTML. The measurement ID is a public identifier, and the README states that it is fixed in lib/site.ts, so the tag cannot quietly go missing at deploy time.
There is one exception that was left in place. The fragment of the submission receipt link contains a non-public capability token, so because gtag transmits the entire URL, the tag is not placed on that path. Analytics.tsx re-attaches the tag via the afterInteractive approach only when it starts on the receipt path and then moves to another page. The seo.spec.ts test checks whether the measurement ID and gtag('config') are present in the initial head of public pages, whether the Google Tag Manager string and config call are absent from the receipt-side head, and whether the tag is not inserted twice during navigation so that the number of dataLayer entries stays at 2.
The scope of the change is limited to the website directory. Only the four files layout.tsx, components/Analytics.tsx, tests/browser/seo.spec.ts, and README.md were touched, and neither the code that runs the benchmark nor the agent memory metric values changed in this commit. Performance figures and dataset counts are likewise not presented in this commit. Therefore this change concerns site indexing and ownership verification, and should not be read as a change in the results of the memory benchmark.