Feature guide · 3 minute read
Sort crawl results
Bring a useful group of results to the top without losing the surrounding crawl. Sort by Status Code to review response groups, then return to URL order when you need to scan page addresses.
Best for scanning a completed crawl while keeping every visible result
15-second workflow
Bring the 404 into view.
A completed public fixture crawl with 14 results. The 404 is intentional. Only the order and cell selection change; the demo does not run another crawl or apply a filter.
What happens in the demo
Sort Status Code ascending
Click the Status Code heading, not its filter icon. The ascending arrow appears and the 200 responses move ahead of the 302 and 404 responses.
Reverse the direction
Click the same heading again. The descending order puts this fixture's 404 first, followed by redirects and successful responses. All 14 rows remain.
Select the affected URL
Select the broken-target URL cell beside 404 - Not Found. Sorting has brought the result into view without changing its response.
Return to URL order
Click URL to restore ascending URL order. The selection clears and the same crawl results remain available.
Choose the order for the question.
- Open Pages after the crawl completes and find the column you want to review.
- Click its heading to sort. A newly selected column starts in ascending order.
- Click the same heading again to reverse the direction. Read the arrow beside the heading to confirm the active order.
- Click URL when you want to return to ascending address order.
For Status Code, ascending groups lower response codes first. Descending reverses those groups. URL sorting orders the addresses alphabetically; it is not a ranking of their importance.
Sorting changes order. Filtering changes the set.
Click the heading text to sort. The nearby funnel opens a filter instead. An issue selection or column filter can hide nonmatching rows; sorting simply rearranges the results that are currently visible.
If rows appear to be missing, check active filters before changing the sort direction. Sorting does not clear an issue selection or restore rows hidden by a filter.
Use Pages table filters when you want only a specific response group. Use sorting when you want that group together while keeping the other responses for comparison.
Position is not priority.
This fixture has 200, 302, and 404 responses, so 404 comes first in descending order. A crawl containing higher response codes would put those ahead of it. Descending order does not guarantee that a 404 is always the first result.
Read the URL and response together, then investigate the finding. A 302 may be intentional, and a 200 does not prove a page is indexable. The sort direction changes neither the recorded response nor the issue counts.
Changing the Pages sort clears the current cell selection. Re-select the intended URL before copying it or taking another action.