Bot traffic: austinmayor.com

all sites · all domains · last 15 days

All sites · All Domains · Visit austinmayor.com

Who is really visiting austinmayor.com?

Between Oct 23 and Nov 6, austinmayor.com received 61,462 requests. About 98% came from automated software and about 1.7% look like real people.

That works out to about 240 human visitors, roughly 16 a day, who opened 340 pages between them. 69 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
240human visitors (estimate)
340pages opened by people
61,462total requests, 15 days

Where the requests came from

People 1.7%Named bots 16%Disguised bots 10%Scanners 71%Unclear 0.9%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
02,5005,0007,50010,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.

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

The breakdown

SourceRequestsΣ 61,462ShareData sentBlockedby the serverWhat this means
Break-in scanners35,95358%40 MB22,623Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers7,93413%37 MB70Other requests from an address also caught probing for weak spots.
Disguised scrapers4,5877.5%59 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 engines4,2586.9%33 MB6Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots3,0314.9%27 MB36Any other software that identifies itself as a bot.
AI crawlers1,9383.2%6 MB95AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools1,5822.6%23 MB2Programs such as curl or Python, or anything with an unrecognizable name.
Likely people8871.4%114 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
SEO and marketing tools6181.0%3 MB85Commercial tools that sell data about websites.
Unclear5360.9%18 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Possibly people1330.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 browsers50.0%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines1,639
QlyzeBotOther named bots873
ApplebotSearch engines663
ClaudeBotAI crawlers602
bingbotSearch engines518
Amzn-SearchBotSearch engines505
GooglebotSearch engines348
ElevenlabsCrawlerOther named bots273
SERankingBacklinksBotSEO and marketing tools255
DataForSeoBotSEO and marketing tools231
OAI-SearchBotAI crawlers224
DuckDuckBotSearch engines214
ExaSearchBotOther named bots212
ChatGPT-UserAI crawlers152
meta-webindexerOther named bots151

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/107
/mayor/15
/council/15
/mayor/race/12
/news/2026-06-04-austin-police-escorts-this-week-what-to-know.html10
/news/2026-06-03-kirk-watson-wins-austin-mayoral-runoff-returns-city-hall.html7
/council09/7
/council/district-7/6
/issues/6
/council/district-5/4
/katie-kam/3
/datacenters/3

How people arrived

Referring siteHuman visitors
www.google.com47
duckduckgo.com44
austintweet.com23
m.baidu.com21
www.bing.com15
search.brave.com4
search.yahoo.com4
www.baidu.com3
www.ecosia.org1
us.search.yahoo.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
77.90.0.0/162052
192.42.0.0/1617132
158.69.0.0/161471
183.207.0.0/161313
66.249.0.0/161083
185.220.0.0/168616
92.62.0.0/16661
87.81.0.0/166361

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2326345487313,482194,88198%
Oct 2420235874972,364263,55797%
Oct 2510138413135,064296,27499.1%
Oct 2621317904901,031392,40896%
Oct 2715214545515,676266,75399%
Oct 2817185612822,427353,38397%
Oct 2916213974572,435373,36098%
Oct 3013357052867,315488,48998%
Oct 3118243394681,431512,36195%
Nov 117221,6675423,672486,01698%
Nov 211134753292,674433,55298%
Nov 319255893011,999292,99197%
Nov 420297982071,956243,10695%
Nov 514168523231,059332,29797%
Nov 612152423971,302492,03495%

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.