AI names your business. Someone visits the website. An enquiry arrives. These are three different events. Only by describing their connection and limits clearly can you decide which work helps your business.
1 — A question needs a suitable destination
SEO and GEO meet at the customer’s question. Someone learning a method needs an explanation. Someone comparing providers needs scope, fit and evidence. Someone ready to enquire needs a clear next step. Sending all three to the same generic homepage loses that context.
| Situation | Suitable content | Useful next step |
|---|---|---|
| Understand | Guide with definition, example and limitations | Relevant service page |
| Compare | Service scope, process and traceable evidence | Clarify open questions |
| Decide | Process, prerequisites and enquiry form | Communicate the actual need |
| Follow up | Clear confirmation and responsible person | Initial conversation or clarification |
2 — Current measurement: two different Google reports
As checked on 25 October 2026, GA4 documentation describes AI Assistant as a channel for visits from sources such as ChatGPT or Gemini. Google AI Overviews and AI Mode are explicitly excluded and included in Organic Search. A single “AI traffic” number without a channel definition would therefore be ambiguous. [1]
Google also documents a generative AI performance report in Search Console. Its help page states a worldwide rollout by 31 August 2026; it reports impressions for AI Overviews and AI Mode. The report may be absent when impressions are insufficient. These statements describe product documentation, not retrieved GlasBox account data. [2]
| Source | What it shows here | Important limit |
|---|---|---|
| Search Console generative report | Links shown in supported generative search features | An impression is not a visit or lead [2] |
| GA4 session channel | Assignment of recorded visits under channel rules | Not every origin is observable; check dimension [1] |
| Form / CRM | Accepted enquiry and later qualification | An enquiry may involve several touchpoints |
| Customer statement | Voluntarily recalled source information | Recollection is not a complete technical journey |
Search Console and GA4 measure different things and use different reporting contexts. Do not divide a month’s enquiries by arbitrary AI impressions and call it a conversion rate. First check period, time zone, landing page, consent state and attribution rules. An unknown origin remains unknown.
3 — A lead is not a button click
Google describes generate_lead as a recommended event for submitting a form or information request. Implementation must match the real workflow. Our recommendation: record successful acceptance, prevent duplicates and test failures. A click on an invalid form must not be counted as an accepted enquiry. [3]
Qualification follows: does the service fit, is the property within the service area and is the need sufficiently concrete? Define these rules before analysis. Spam, internal tests and duplicate submissions need separate statuses. Personal free-text content should not be placed in analytics event parameters.
4 — Worked example with a clear denominator
Wholly fictional example for a defined period: 100 recorded sessions produce 8 uniquely attributed accepted enquiries. Five meet the predefined qualification criteria. Every value uses the same defined scope. The teaching example assumes unambiguous attribution; real data requires verification.
| Calculation | Result | Meaning |
|---|---|---|
| 8 ÷ 100 | 8% | Accepted enquiries per recorded session |
| 5 ÷ 8 | 62.5% | Qualified share of accepted enquiries |
| 5 ÷ 100 | 5% | Qualified enquiries per recorded session |
The second rate has a different denominator from the first and third. None establishes improvement without a comparison. None proves that an AI mention caused the enquiry. Good reporting states those limits and then identifies the specific issue to investigate.
5 — Inspect the transition to an enquiry
| Observation | Next check |
|---|---|
| Visitors repeatedly ask about scope | Is the service boundary clear on the landing page? |
| Many started but few accepted forms | Check functionality, required fields and error messages |
| Enquiries fall outside the service area | Explain the area before the form |
| Confirmation does not arrive | Test acceptance, delivery and receipt separately |
| Many leads, few suitable conversations | Review qualification rules and offer claims |
Change one justified element at a time and record when. Small counts fluctuate substantially. One good month does not replace repeated observation. The task is to improve clarity and functionality, capture data correctly and assess business quality with the people handling enquiries.
Connections within the course
| Part | What you build on here |
|---|---|
| Part 5 · Sources | A citation is a possible touchpoint, not a lead. |
| Part 6 · Measurement | Separate answer observation from business metrics. |
| Part 7 · Improve pages | Turn a specific obstacle into a testable task. |
| Part 10 · Own data | Every rate needs a method and denominator. |
| Part 12 · Local GEO | Service area and actual need must fit. |
Clarify your next step.
SOURCE/01 connects specific findings with evidence and a prioritised task.
Explore SOURCE/01Sources and working method
Checked on 25 October 2026. The example of 100 sessions, 8 enquiries and 5 qualified enquiries is fictional. Product descriptions follow the linked documentation; no Analytics or CRM account data was retrieved.
No exact document date stated. · Checked: 25 October 2026.
No exact document date stated. · Checked: 25 October 2026.
No exact document date stated. · Checked: 25 October 2026.
Glossary: terms and connections
| Term / translation | Meaning | Connection |
|---|---|---|
| Customer journey / Kundenweg | Multiple touchpoints before a decision. | Part 2: organise questions by situation. |
| Landing page / Einstiegsseite | The first page of a website visit. | Part 7: provide the relevant answer. |
| Impression / Einblendung | A link displayed under a report’s rules. | Part 6: not proof of a visit. |
| AI Assistant / KI-Assistenten-Kanal | GA4 channel for certain AI-referred visits. | Here: excludes Google AI search. |
| Generate lead / Anfrage erfassen | Event for an actual form or information enquiry. | Here: verify successful acceptance. |
| Qualified lead / qualifizierte Anfrage | Enquiry meeting predefined fit criteria. | Part 12: service and area match. |
| Attribution / Zuordnung | Rule linking an outcome to a touchpoint. | Part 6: no automatic causation. |
| Conversion rate / Umwandlungsquote | Outcomes divided by a defined base. | Part 10: explicitly state the denominator. |