Summary — The 9 Foundational Crawler Categories
| Category | Core Question It Answers | Example Type |
|---|---|---|
| Purpose | Why is it crawling? | Scraping crawler |
| Crawl Strategy | How does it traverse pages? | BFS, DFS, Focused |
| Scheduling Behavior | When does it crawl? | Incremental, Continuous |
| Architecture | How is it organized? | Distributed crawler |
| Scope | How wide does it crawl? | Site-wide crawler |
| Data Access Method | Where does it get data from? | API crawler |
| Ethical Behavior | How does it treat site rules? | Polite crawler |
| Intelligence Level | How does it make decisions? | LLM-guided crawler |
| Integration Role | How does it fit into a pipeline? | Modular crawler |
By Purpose (Goal or Intent)
Defines why the crawler exists — what it aims to achieve.
Type Description
- Discovery Crawler - Finds and collects URLs or metadata; builds an index or frontier.
- Scraping Crawler - Extracts structured data from pages (e.g., tables, text, entities).
- Monitoring Crawler - Tracks updates or changes in content over time.
- Archival Crawler - Saves full page copies for preservation or offline analysis.
- Testing / Auditing Crawler - Used for SEO, broken-link checking, or site compliance validation.
By Crawl Strategy (Traversal Logic)
Defines how pages are selected or ordered during crawling.
Type Description
- Breadth-First (BFS) - Crawl all pages at one depth before moving deeper.
- Depth-First (DFS) - Crawl one path as deep as possible before backtracking.
- Priority-Based - Assign numerical priority scores to URLs.
- Adaptive Adjust - strategy dynamically based on feedback or results.
- Context-Aware - Use HTML structure and semantics to guide crawling decisions.
By Scheduling Behavior (Temporal Logic)
Defines when and how often the crawler operates.
Type Description
- One-Shot - Runs once and stops after completion.
- Incremental - Re-crawls known pages periodically to detect updates.
- Continuous - Never stops constantly cycles through crawl/revisit loops.
- Event-Driven - Triggered by signals such as webhooks or detected changes.
By Scope (Coverage Target)
Defines how broadly the crawler explores the web.
Type Description
- Focused - only relevant pages based on topic or keyword.
- Site-Wide - Restricted to one domain or subdomain.
- Multi-Domain - Crawls a fixed list of domains.
- Vertical / Domain-Specific - Focused on one industry (e.g., sports, jobs, e-commerce).
- Web-Scale - Crawls the entire public web; search-engine level.
By Architecture (System Design)
Defines how the crawler is built and organized internally.
Type-Description
- Centralized Single control node managing all crawl tasks.
- Distributed Multiple coordinated nodes sharing workload and URL queues.
- Peer-to-Peer Decentralized — nodes share discovered URLs without a central coordinator.
- Cloud / Serverless Uses scalable, ephemeral functions to perform crawl tasks.
By Data Access Method
Defines where and how data is retrieved.
Type Description
- HTML / Page Crawler Fetches and parses HTML pages.
- API Crawler Pulls structured data through APIs.
- Headless / Rendered Crawler Uses browsers or headless engines to handle JavaScript.
- Hybrid Crawler Combines HTML, API, and headless methods adaptively.
By Ethical or Policy Behavior
Defines how the crawler interacts with site policies.
Type Description
- Polite Crawler Obeys robots.txt, rate limits, and crawl delays.
- Aggressive Crawler Ignores some restrictions (not recommended).
- Authenticated Crawler Operates within login-required environments.
By Intelligence Level
Defines how much decision-making or AI the crawler uses.
Type Description
- Rule-Based Follows fixed rules or regex filters.
- Heuristic-Based Uses handcrafted scoring or relevance functions.
- ML-Guided Uses machine learning for link scoring or prioritization.
- LLM-Guided Uses large language models to interpret pages and guide navigation.
By Integration Role (System Position)
Defines how the crawler fits into the larger data pipeline.
Type Description
- Standalone Crawler - Operates independently, outputs raw pages or URLs.
- Coupled Crawler - Integrates scraping logic directly inside the crawl loop.
- Modular Crawler - Works with separate scraper, parser, and storage components.
- Streaming Crawler - Feeds data continuously into real-time pipelines (Kafka, etc.).
Metadata
Release files for SmartSpider 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| smartspider-0.0.3.tar.gz | 11.1 kB | Without provenance | Details for smartspider-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| smartspider-0.0.3-py3-none-any.whl | Python 3 | none | any | Details for smartspider-0.0.3-py3-none-any.whl |
Total release size: 22.6 kB
Release files / smartspider-0.0.3.tar.gz
| Download URL | smartspider-0.0.3.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bfaa3b50cbe41556007ac3a6f98d669a82a9871d581111e39ffc10327af1022
|
|
BLAKE2b-256 checksum How to use checksums |
1c3a7d66ae5a5495f6fd2a5ae0d1f07b37d7237cb5b9968a9a5600f734f8541f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / smartspider-0.0.3-py3-none-any.whl
| Download URL | smartspider-0.0.3-py3-none-any.whl |
|---|---|
| Size | 11.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ecd69aa982c76d8131ef4ac524e9546af24ad4b1acf08bd9fd7de498e271ec6
|
|
BLAKE2b-256 checksum How to use checksums |
87f519a2c09787b4abc2efa6cd10df4df3bbaa6f1d0e12fcd8979189f81058cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for SmartSpider 0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.