Bot traffic: austinlifestyles.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austinlifestyles.com

Who is really visiting austinlifestyles.com?

Between Oct 23 and Nov 6, austinlifestyles.com received 73,009 requests. About 98% came from automated software and about 1.3% look like real people.

That works out to about 589 human visitors, roughly 39 a day, who opened 671 pages between them. 51 of them read more than one page.

The biggest source is scanners hunting for security holes. They try the same list of common weak spots on every site they find.

Bottom line: the hit counts on the All Domains worksheet are almost entirely bots. Use the human visitor figure here to judge this site's real audience.

98%of requests from bots
589human visitors (estimate)
671pages opened by people
73,009total requests, 15 days

Where the requests came from

People 1.3%Named bots 9.7%Disguised bots 8.4%Scanners 80%Unclear 0.5%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
02,0004,0006,0008,000Oct 23Oct 25Oct 27Oct 29Oct 31Nov 2Nov 4Nov 6

Human visitors per day

Same days, people only, on their own scale so they are visible.

050100150200Oct 23Oct 25Oct 27Oct 29Oct 31Nov 2Nov 4Nov 6

The breakdown

SourceRequestsΣ 73,009ShareData sentBlockedby the serverWhat this means
Break-in scanners39,94255%3 MB23,910Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers18,54525%44 MB8Other requests from an address also caught probing for weak spots.
Disguised scrapers4,4136.0%26 MB0Claims to be a normal browser but only downloads pages, never the images or icons a real browser fetches, reads many pages without ever clicking a link, or runs from a cloud provider.
Search engines3,8615.3%21 MB5Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Scripts and tools1,6092.2%5 MB5Programs such as curl or Python, or anything with an unrecognizable name.
AI crawlers1,6072.2%2 MB79AI companies gathering pages or answering a user's question, and saying so.
Other named bots1,4572.0%4 MB15Any other software that identifies itself as a bot.
Likely people5430.7%2 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people3830.5%2 MB0Read 1 to 3 pages, arrived from a search engine or social link, no icons fetched. Referrers can be faked, so treat these as maybe.
Unclear3300.5%<1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools1780.2%<1 MB137Commercial tools that sell data about websites.
Automated browsers1340.2%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
No name given50.0%<1 MB0Requests that give no software name at all.
App link sweepers20.0%<1 MB0Touches only login, app or embed links and no actual content.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines2,250
GooglebotSearch engines696
ClaudeBotAI crawlers380
bingbotSearch engines357
OAI-SearchBotAI crawlers187
BaiduspiderSearch engines179
pathscanOther named bots173
ApplebotSearch engines152
SemrushBotSEO and marketing tools134
BytespiderAI crawlers85
cohere-aiAI crawlers85
Kimi-SearchBotOther named bots84
GPTBotAI crawlers82
KimiBotOther named bots81
Perplexity-UserAI crawlers81

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/346
/live/70
/about/3
/events/2

How people arrived

Referring siteHuman visitors
olevigsveg26.blogspot.com322
m.baidu.com17
google.com, http:13
austinhangout.com11
austintweet.com8
www.google.com5
www.bing.com1
m.facebook.com1
austen.com1
www.baidu.com1

Where disguised bots operate from

Address blocks, not individual addresses. A heavily used block with many addresses suggests one operator rotating through them.

Address blockRequestsAddresses used
47.82.0.0/16320156
45.138.0.0/161363
192.42.0.0/1613538
172.190.0.0/16881
47.79.0.0/168840
183.207.0.0/16823
185.220.0.0/164412
43.157.0.0/164120

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2317217323144,751215,85599.0%
Oct 241861882903272,448113,27094%
Oct 251591597022466,668137,79798%
Oct 2621237633986,253167,47599.2%
Oct 2712143116425,957216,95399.4%
Oct 2811124492282,648193,36699%
Oct 2919224045933,803184,85099%
Oct 3016184783066,059276,90599.1%
Oct 319102322401,602172,11098%
Nov 134727581,1332,522284,55197%
Nov 229334532963,292284,13198%
Nov 328355003332,671353,60197%
Nov 427294815281,491192,57397%
Nov 514153063831,970102,69699%
Nov 617202441966,352476,87699%

How this was measured

Every request in the server log was sorted by what it did, not only what it claimed to be. Bots that name themselves are counted as named. Anything claiming to be a browser had to act like one: open a page, fetch its images or icons, move at human speed, and come from outside the big cloud providers. These are estimates. A careful bot can pass the test, and a person with images blocked or a cached icon can fail it, so read the human figures as a good approximation, not an exact count. One person using two devices counts as two visitors. Google Analytics-style tools would show different numbers because most bots never run their script. Logs are kept for 15 days.

Built 2026-11-06 22:43 UTC from 15 log files.