Traffic from Lanzhou and Singapore: how to investigate it
Unusual city traffic is not proof of AI crawlers. Check analytics, hosting logs, engagement and enquiry quality before drawing conclusions.
Unusual city traffic is not proof of AI crawlers. Check analytics, hosting logs, engagement and enquiry quality before drawing conclusions.
Published by TERAMOK · Real estate and building-industry marketing.
Does traffic from Lanzhou or Singapore mean AI crawlers are visiting?
Not by itself. A city label and low engagement cannot identify who generated a visit. Investigate unusual traffic before calling it a security incident, a real customer audience or a positive AI-search signal. The same caution applies to traffic from any unfamiliar location.
What Google Analytics can and cannot establish
Google says known bot and spider traffic is excluded automatically. That does not make every remaining event human or trustworthy. Engagement time describes recorded foreground activity; a missing or very small value is not a crawler identity test. A request that never triggers your analytics collection may not appear as a session at all.
A practical investigation workflow
Compare the affected dates, landing pages, hostname, source/medium, device and engagement with your normal baseline. Note tracking or consent changes in the same period.
Where hosting or CDN logs are available, compare timestamps, request paths, response codes, request volume and user-agent strings. Check the provider’s published verification method; bot names can be imitated.
Look for normal enquiry progression and verified CRM records. Keep suspicious traffic out of commercial conclusions until it is understood.
Check error rates, server load and security alerts. Stable conversion totals alone do not rule out abuse. Use proportionate hosting controls when evidence supports them.
Document what is known, what is suspected and what remains unresolved. Preserve a clean reporting view before changing filters or blocking rules.
Example: a sudden spike with no enquiries
If a developer sees a city-specific spike and no corresponding tour requests, first compare landing paths and event patterns with normal traffic. Then reconcile with hosting logs if available. Without that evidence, label it unexplained traffic. Do not describe it as AI demand, add it to a qualified-lead count or conclude that search visibility improved.
How to assess actual AI-search visibility
Use dated answer captures, the pages actually cited and separately identified referral traffic. OpenAI documents different agents for search, training and user-triggered visits. Those functions should not be combined into one success metric. Useful content and crawl access matter, but a request from a crawler does not prove ranking, recommendation or commercial intent.
How TERAMOK can help
We can review tracking implementation, traffic quality, content access and the relationship between website enquiries and CRM outcomes. Start with an AI visibility review if your question is what assistants say about your brand, or discuss the traffic pattern if the issue is analytics accuracy.
Sources and scope
Sources checked October 27, 2026. Practical recommendations are TERAMOK’s editorial guidance; they are not a published ranking formula or a promise of commercial results.
Published by TERAMOK · Real estate and building-industry marketing.
Does traffic from Lanzhou or Singapore mean AI crawlers are visiting?
Not by itself. A city label and low engagement cannot identify who generated a visit. Investigate unusual traffic before calling it a security incident, a real customer audience or a positive AI-search signal. The same caution applies to traffic from any unfamiliar location.
What Google Analytics can and cannot establish
Google says known bot and spider traffic is excluded automatically. That does not make every remaining event human or trustworthy. Engagement time describes recorded foreground activity; a missing or very small value is not a crawler identity test. A request that never triggers your analytics collection may not appear as a session at all.
A practical investigation workflow
Compare the affected dates, landing pages, hostname, source/medium, device and engagement with your normal baseline. Note tracking or consent changes in the same period.
Where hosting or CDN logs are available, compare timestamps, request paths, response codes, request volume and user-agent strings. Check the provider’s published verification method; bot names can be imitated.
Look for normal enquiry progression and verified CRM records. Keep suspicious traffic out of commercial conclusions until it is understood.
Check error rates, server load and security alerts. Stable conversion totals alone do not rule out abuse. Use proportionate hosting controls when evidence supports them.
Document what is known, what is suspected and what remains unresolved. Preserve a clean reporting view before changing filters or blocking rules.
Example: a sudden spike with no enquiries
If a developer sees a city-specific spike and no corresponding tour requests, first compare landing paths and event patterns with normal traffic. Then reconcile with hosting logs if available. Without that evidence, label it unexplained traffic. Do not describe it as AI demand, add it to a qualified-lead count or conclude that search visibility improved.
How to assess actual AI-search visibility
Use dated answer captures, the pages actually cited and separately identified referral traffic. OpenAI documents different agents for search, training and user-triggered visits. Those functions should not be combined into one success metric. Useful content and crawl access matter, but a request from a crawler does not prove ranking, recommendation or commercial intent.
How TERAMOK can help
We can review tracking implementation, traffic quality, content access and the relationship between website enquiries and CRM outcomes. Start with an AI visibility review if your question is what assistants say about your brand, or discuss the traffic pattern if the issue is analytics accuracy.
Sources and scope
Sources checked October 27, 2026. Practical recommendations are TERAMOK’s editorial guidance; they are not a published ranking formula or a promise of commercial results.
Editorial standards
Written by TERAMOK’s strategy team from direct work with real estate developers, architecture firms, construction companies, and operators. Claims are tied to published project evidence or identified as general guidance.
Get started
Chicago's in-house production and marketing team for real estate.
Book a free 30-minute strategy call. Tell us about your project, your firm, or your launch — and we'll show you exactly how TERAMOK plugs into your operation with cinema-grade production, campaign strategy, and senior creative.
Get started
Chicago's in-house production and marketing team for real estate.
Book a free 30-minute strategy call. Tell us about your project, your firm, or your launch — and we'll show you exactly how TERAMOK plugs into your operation with cinema-grade production, campaign strategy, and senior creative.
Get started
Chicago's in-house production and marketing team for real estate.
Book a free 30-minute strategy call. Tell us about your project, your firm, or your launch — and we'll show you exactly how TERAMOK plugs into your operation with cinema-grade production, campaign strategy, and senior creative.