Build a clean crawl list
Normalize copied URLs, expose invalid entries, and export one stable list before a crawler touches it.
- 1Extract URLs
- 2Choose rules
- 3Review exceptions
- 4Export the list
Paste the source
The workbench extracts URLs from lists, tables, Markdown links, or pasted sitemap XML.
Reading the pasted source…
Choose normalization rules
Parameters may change page content. Remove only what the next crawl does not need.
Review hosts and exceptions
Invalid entries and suspicious variants stay visible instead of disappearing silently.
| Host | URLs |
|---|
Suspicious variants
Invalid entries
Export the crawl input
Lines are best for a simple queue. CSV and JSON retain the review fields.
This output has not been crawled. Status, canonical, robots, and content still need a live request.
Ready
Use this workflow when…
- A crawl export contains the same page in several URL forms.
- You copied URLs from a spreadsheet, sitemap, Markdown file, or issue.
- You need to separate invalid text before a crawl or import.
What changes, exactly?
Every normalization choice is visible. The workflow cannot decide whether two parameter variants contain different content.
https://EXAMPLE.com/ https://example.com example.com/page/#top example.com/page?utm_source=news example.com/about/
- Unique URLs
- 3
- Duplicates
- 2
- Invalid
- 0
https://example.com/ https://example.com/page https://example.com/about
A normalized URL is not proof that the page exists, returns 200, redirects correctly, or should be canonical. Those checks require a live request.
Check these edge cases
Do not remove information simply because it looks untidy.
?page=2Keep unless proven redundant?utm_source=emailRemove in tracking mode/guide#setupRemove for an HTTP crawl targetexample.comAdd HTTPS only when intendedWhere the result can go
Download the result first. It stays useful without another product.
Where the result can go
Download the result first. It stays useful without another product.