Turing internal reporting example for 17 October 2026

This is evidence from Turing's own reporting system, not a client case study.
The collection is scheduled. Turing prepared this interpretation and extract.
These figures do not establish leads, revenue or time saved.

Collection and reporting period

All 39 configured Search Console and GA4 reports refreshed successfully on
17 October, between 03:30:08 and 03:32:59 UTC.

This extract covers 1 to 14 October 2026. Each of the 39 source reports has
14 verified dates, totalling 546 report-days. Verification includes earlier
successful requests: the control sheet records the oldest and latest checks.
A verified empty response is distinguished from a missed or unverified date.

The stored API-verified Search Console final frontier is 14 October.
GA4 was requested through 15 October; this extract uses the common fortnight.

Source inputs

Per site: seven Search Console web-search reports and six GA4 reports.
Search Console property totals are held separately from diagnostic breakdowns.
The accompanying report-checks.csv lists all 39 report grains and date coverage.

Output for 1 to 14 October

Search Console property totals, web search:

Site                    Clicks    Impressions
Turing BI                    2          2,084
Turing Websites              2            259
Turing Automate              0            627

These are discovery measures. Query and page breakdowns use different
aggregation or privacy filtering and must not replace property headlines.

The verified GA4 traffic responses contain four recorded sessions for BI.
BI has rows on two dates and verified empty responses on twelve dates.
Websites and Automate have verified empty traffic responses on all 14 dates.
Consent-gated analytics does not establish the full number of visits or
commercial enquiries. No enquiry or paid-work total is inferred here.

Checks and decisions

1. Use the verified Search Console frontier for the reporting cutoff.
2. Retain API-empty responses separately from failed or unverified dates.
3. Keep GA4 sessions, search clicks and genuine enquiries as separate measures.
4. Keep indexing checks dated: the latest stored sitemap inspection is 4 October.
5. Leave historical GA4 growth comparisons out where older coverage is incomplete.

Outstanding work

Reconcile current genuine enquiries independently of analytics.
Validate a controlled consented visit in each live GA4 stream.
Refresh the URL Inspection census and investigate accountant-query exposure.
Backfill and revalidate the older dates before using complete historical comparisons.

Scope

This example covers Google reporting collection and its verification controls.
It does not demonstrate a client's paid-media integration, automated commentary,
client-report delivery or an n8n workflow. No client data or credentials are included.
The stored evidence was reviewed on 17 October; no fresh manual URL inspection
or historical backfill was performed during that review.