Bot traffic: austinhomesearches.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austinhomesearches.com

Who is really visiting austinhomesearches.com?

Between Oct 23 and Nov 6, austinhomesearches.com received 71,198 requests. About 98% came from automated software and about 0.8% look like real people.

That works out to about 211 human visitors, roughly 14 a day, who opened 272 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
211human visitors (estimate)
272pages opened by people
71,198total requests, 15 days

Where the requests came from

People 0.8%Named bots 9.8%Disguised bots 7.9%Scanners 81%Unclear 0.7%

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.

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

The breakdown

SourceRequestsΣ 71,198ShareData sentBlockedby the serverWhat this means
Break-in scanners50,29571%59 MB28,216Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers7,26710%27 MB12Other requests from an address also caught probing for weak spots.
Disguised scrapers3,8235.4%30 MB1Claims 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.
Other named bots2,4173.4%13 MB30Any other software that identifies itself as a bot.
Search engines2,0942.9%10 MB11Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
AI crawlers2,0512.9%6 MB129AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools1,6022.3%16 MB4Programs such as curl or Python, or anything with an unrecognizable name.
Unclear5110.7%3 MB0Browser name, but fetched only an image or data file and no page. Could be either.
SEO and marketing tools4370.6%2 MB98Commercial tools that sell data about websites.
Likely people3690.5%14 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Possibly people1660.2%<1 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.
Automated browsers1640.2%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
No name given20.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines981
QlyzeBotOther named bots789
ClaudeBotAI crawlers575
bingbotSearch engines325
GooglebotSearch engines272
OAI-SearchBotAI crawlers252
ElevenlabsCrawlerOther named bots228
SERankingBacklinksBotSEO and marketing tools220
Amzn-SearchBotSearch engines127
GPTBotAI crawlers122
BytespiderAI crawlers119
BarkrowlerSEO and marketing tools119
ChatGPT-UserAI crawlers99
Perplexity-UserAI crawlers92
SemrushBotSEO and marketing tools88

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/74
/videos/7
/social/4
/about/4
/condo/4
/east-7th/4
/faq/3
/market-2026/2
/comps/2

How people arrived

Referring siteHuman visitors
www.google.com107
m.baidu.com19
austinhangout.com6
austintweet.com2
dataindex.pro1
claudefieldguide.com1
duckduckgo.com1
www.bing.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
192.42.0.0/1620546
158.69.0.0/161641
47.82.0.0/16137132
102.129.0.0/16942
173.46.0.0/16872
158.173.0.0/16703
154.28.0.0/16682
43.157.0.0/165725

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2310135446103,218134,42399%
Oct 247121332723,08153,52299%
Oct 25445301965,218456,00699%
Oct 2618234003104,906205,68999%
Oct 276105783356,285317,24199.4%
Oct 28662762933,488234,09499.1%
Oct 2912172044105,267205,93699.1%
Oct 3011133442316,206456,87999%
Oct 31352282192,889213,36399.2%
Nov 110141,0791,4323,842246,41599.0%
Nov 2448132684,221665,37999%
Nov 38102222433,044773,61597%
Nov 418204443391,292752,17795%
Nov 579967392482,611173,75996%
Nov 621254651851,994292,70098%

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.