Bot traffic: changeaustin.com

all sites · all domains · last 15 days

All sites · All Domains · Visit changeaustin.com

Who is really visiting changeaustin.com?

Between Oct 23 and Nov 6, changeaustin.com received 68,245 requests. About 99% came from automated software and about 0.5% look like real people.

That works out to about 147 human visitors, roughly 10 a day, who opened 188 pages between them. 38 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.

99%of requests from bots
147human visitors (estimate)
188pages opened by people
68,245total requests, 15 days

Where the requests came from

People 0.5%Named bots 9.2%Disguised bots 6.6%Scanners 83%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.

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

The breakdown

SourceRequestsΣ 68,245ShareData sentBlockedby the serverWhat this means
Break-in scanners49,21572%79 MB29,830Probing for WordPress logins, password files and other common weak spots.
Scanners posing as browsers7,54611%30 MB154Other requests from an address also caught probing for weak spots.
Disguised scrapers3,7475.5%33 MB2Claims 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 engines2,3333.4%16 MB8Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Other named bots1,9562.9%13 MB23Any other software that identifies itself as a bot.
AI crawlers1,5922.3%4 MB75AI companies gathering pages or answering a user's question, and saying so.
Scripts and tools6190.9%16 MB4Programs such as curl or Python, or anything with an unrecognizable name.
SEO and marketing tools3730.5%1 MB75Commercial tools that sell data about websites.
Unclear3530.5%6 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Likely people2750.4%20 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Automated browsers1470.2%<1 MB0Loads images like a browser, but too fast for a person or with a faked browser name.
Possibly people890.1%<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.

Named bots

Botas it names itselfTypeRequests
PetalBotSearch engines692
bingbotSearch engines438
ClaudeBotAI crawlers410
Amzn-SearchBotSearch engines407
QlyzeBotOther named bots392
GooglebotSearch engines315
ElevenlabsCrawlerOther named bots224
SERankingBacklinksBotSEO and marketing tools209
OAI-SearchBotAI crawlers160
ISPDomainVerifierOther named bots119
ApplebotSearch engines105
PerplexityBotAI crawlers101
GPTBotAI crawlers97
BaiduspiderSearch engines90
BarkrowlerSEO and marketing tools87

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/73
/news/2026-06-04-police-escorts-austin-what-to-know-and-what-to-do34
/live/4
/news/2026-05-18-austin-mayor-residency-requirements-who-can-run3
/news/2026-05-19-austin-investors-300-million-ponzi-scheme-what-to-know.html2
/news/2026-05-07-musk-terafab-college-station-texas-what-it-means2
/sitemap/2
/about/2
/faq/2
/news/2
/news/2026-05-21-meta-layoffs-austin-tech-workers-ai-cuts-impact.html2

How people arrived

Referring siteHuman visitors
duckduckgo.com29
m.baidu.com19
austintweet.com18
www.google.com13
www.bing.com11
search.yahoo.com8
noai.duckduckgo.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
104.164.0.0/162456
192.42.0.0/1617532
47.82.0.0/16161152
158.69.0.0/161471
102.129.0.0/161215
185.220.0.0/169316
93.123.0.0/16851
45.138.0.0/16713

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 2316213033013,867194,53299%
Oct 2410131652753,580114,05099.3%
Oct 2514142062463,298103,78699.0%
Oct 2616203482776,262146,92899.4%
Oct 27792883363,606174,25799.4%
Oct 288122562864,293294,88599%
Oct 299123733552,827193,59599%
Oct 30665142213,433154,19199.5%
Oct 31683822716,105196,78899.6%
Nov 119247317304,784566,37398%
Nov 2457473003,681194,75499.5%
Nov 39113401985,532226,10999.4%
Nov 4683912951,897272,62598%
Nov 511131,0472382,251183,57899%
Nov 611121631841,345581,79494%

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.