Bot traffic: jane.austen.com

all sites · all domains · last 15 days

All sites · All Domains · Visit jane.austen.com

Who is really visiting jane.austen.com?

Between Oct 23 and Nov 6, jane.austen.com received 14,285 requests. About 82% came from automated software and about 14% look like real people.

That works out to about 241 human visitors, roughly 16 a day, who opened 463 pages between them. 94 of them read more than one page.

The biggest source is bots that say who they are. Most of those are normal and some, like search engines, help people find the site.

82%of requests from bots
241human visitors (estimate)
463pages opened by people
14,285total requests, 15 days

Where the requests came from

People 14%Named bots 55%Disguised bots 20%Scanners 7.9%Unclear 3.2%

Requests per day

PeopleNamed botsDisguised botsScannersUnclear
03757501,1251,500Oct 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Σ 14,285ShareData sentBlockedby the serverWhat this means
Search engines2,67119%18 MB0Crawlers that say who they are, such as Google, Bing, Apple and Amazon. Usually welcome: this is how people find the site.
Disguised scrapers2,50118%15 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.
AI crawlers2,48117%20 MB2AI companies gathering pages or answering a user's question, and saying so.
Other named bots2,47217%18 MB21Any other software that identifies itself as a bot.
Likely people2,05814%7 MB0Opened a page and also fetched its images or icons, at a human pace, from a non-cloud address.
Scanners posing as browsers6604.6%4 MB0Other requests from an address also caught probing for weak spots.
Break-in scanners4723.3%1 MB121Probing for WordPress logins, password files and other common weak spots.
Unclear4513.2%1 MB0Browser name, but fetched only an image or data file and no page. Could be either.
Scripts and tools3152.2%2 MB0Programs such as curl or Python, or anything with an unrecognizable name.
SEO and marketing tools1901.3%1 MB39Commercial tools that sell data about websites.
Possibly people120.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.
No name given20.0%<1 MB0Requests that give no software name at all.

Named bots

Botas it names itselfTypeRequests
ChatGPT-UserAI crawlers1,496
ExaSearchBotOther named bots1,012
Amzn-SearchBotSearch engines683
ClaudeBotAI crawlers624
PetalBotSearch engines542
bingbotSearch engines415
Baiduspider-renderSearch engines371
ElevenlabsCrawlerOther named bots330
OAI-SearchBotAI crawlers286
ApplebotSearch engines250
meta-webindexerOther named bots176
SofyaBotOther named bots154
BaiduspiderSearch engines142
ibou-searchOther named bots134
BarkrowlerSEO and marketing tools123

What people opened

Pages opened by at least two different human visitors.

PageHuman visitors
/pride/111
/59
/pride/vol1ch01.htm47
/pride/vol1ch02.htm16
/pride/vol1ch03.htm14
/pride/vol1ch06.htm6
/sense/ss_ch08.htm6
/sense/5
/emma/vol2ch13.htm5
/emma/5
/pride/vol1ch05.htm5
/pride/vol1ch04.htm5

How people arrived

Referring siteHuman visitors
www.bing.com54
duckduckgo.com24
cn.bing.com10
www.google.com8
www.ecosia.org7
search.yahoo.com5
in.search.yahoo.com2
r.search.yahoo.com2
uk.search.yahoo.com1
m.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
204.8.0.0/165511
141.94.0.0/164311
43.130.0.0/163925
5.102.0.0/16391
43.157.0.0/163721
43.134.0.0/162813
129.45.0.0/16281
170.106.0.0/162721

Day by day

DayHuman visitorsHuman pagesNamed botsrequestsDisguisedrequestsScannersrequestsUnclearrequestsAllrequestsBot share
Oct 23204070530551201,25185%
Oct 24172340411622765779%
Oct 25123754311722782181%
Oct 261421444120132772779%
Oct 271622416108471468983%
Oct 2828471,0431317291,45081%
Oct 291227526123162683280%
Oct 30917468151484151,17894%
Oct 31143445118615282477%
Nov 12122566154186471,02788%
Nov 2182853310762882478%
Nov 32241464235221341,12182%
Nov 4223352831275381,09284%
Nov 5185250243415431,22278%
Nov 6111922121962457078%

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:42 UTC from 15 log files.