Top Requested URLs Extractor

Your endpoints, ranked by popularity. Top Requested URLs Extractor pulls the path out of each request line in an access log — from the standard combined-log format "GET /api/orders HTTP/1.1" down to a bare path sitting on its own — and ranks every distinct path by hit count with a percentage share of total traffic.

Path extraction happens in two stages. First it looks for the classic quoted request line (an HTTP method followed by a path, inside quotes) and pulls the path out of that. If a line doesn’t have that structure — say you’ve already trimmed the log down to bare paths, or you’re working from an application log rather than a web-server access log — it falls back to matching a bare path-like token (a slash followed by word characters) anywhere in the line, so both raw and pre-processed logs work without switching modes.

By default the query string is stripped, so /api/users?id=5 and /api/users?id=9 both roll up into one entry for /api/users — which is almost always what you want when the question is "which endpoint gets hit the most", since query parameters usually vary per request and would otherwise fragment every URL into hundreds of one-off entries. Flip the "keep query strings" toggle when you specifically need to see which parameter values are driving traffic, for example distinguishing /search?q=shoes from /search?q=boots.

• Smart path extraction — parses quoted HTTP request lines, and falls back to bare-path matching for pre-processed logs.
• Query-string control — strip ?params by default to group by endpoint, or keep them to see individual parameterized requests.
• Ranked output — every path with its hit count and percentage share of total requests.
• Top-N selector — show the top 10, 25 or 50 paths.
• Copyable, chart-ready output — plain text ranking ready to paste into a spreadsheet or ticket.

1. Paste access log lines containing HTTP request lines (or already-extracted bare paths).
2. Decide whether query strings matter for your question — leave the checkbox off to group by endpoint, or check it to keep exact query values.
3. Pick how many top paths to display.
4. Click Extract top URLs. The ranked list, with counts and percentages, appears instantly.

Example 1 — Hot endpoint. If /api/orders dominates at 60% of all traffic, that is exactly where a caching layer or query optimization pays off the most — the ranking tells you where to spend the engineering time before you spend it.

Example 2 — Abuse check. A sudden spike of /wp-login.php or /admin near the top of the ranking, especially on a site that doesn’t run WordPress, is a clear signal of a credential-stuffing or path-scanning attempt.

Example 3 — Cache tuning. The ranked-by-hit-count list is a direct proxy for which responses are worth caching aggressively — the paths at the top of the list benefit the most from every millisecond you shave off.

Example 4 — Query-aware debugging. Toggle "keep query strings" on to see whether a specific parameter value (like a particular search term or filter) is responsible for a disproportionate share of load on an otherwise reasonable-looking endpoint.

• Immediate ranking — no manual log diving to find your busiest endpoints.
• Traffic-aware — percentages show real share of load, not just raw counts.
• Clean or detailed paths — choose endpoint-level grouping or full query-string detail.
• Works on raw or pre-processed logs — quoted request lines and bare paths both parse correctly.
• Private — extraction and ranking run entirely in your browser.