Feature guide · 5 minute read
Filter the Pages table
A crawl can answer several questions at once. That does not mean every question belongs in the same review. Combine filters in the table to isolate one section, one technical condition, and one useful handoff without rebuilding the crawl in a spreadsheet.
16-second workflow
Turn a full crawl into a two-page review queue.
Recorded in the installed SEO Crawler 0.1.8 app using deliberate public fixtures. The matching light or dark recording loads with the viewer's theme; the other file is not fetched.
What happens in the demo
Start with the completed crawl
The Pages table contains the full fixture crawl. The Issues panel stays open for context, but no issue group controls this review.
Remove columns that do not answer the question
Open Filter and hide H1 and H2. The crawl data remains available; only the working view becomes quieter.
Keep successful pages
Open the Status Code menu, clear the existing choices, and select 200 OK. The table now excludes redirects and errors.
Limit the review to the services section
Enter /services/ in URL Incl. The final queue contains two matching service URLs, ready for a focused page review or handoff.
Less scanning, better decisions
Keep the evidence. Remove the rows you do not need yet.
Exporting every URL too early creates another sorting job. In-table filters preserve the relationship between the page and its response, directives, metadata, headings, and discovery source while reducing the visible result to the decision in front of you.
Choose the filter that matches the data.
Text fields are useful for paths and fragments. Value menus are safer for classified data such as response codes and indexability. Use the Filter menu at the top of the app to show the columns needed for the review.
| Control | Available on | Use it to |
|---|---|---|
| Incl. and Excl. | URL, title, description, canonical, and H1-H6 fields | Include rows containing a value or remove rows containing noise such as archives, tags, or parameters. |
| Column filter menu | Status Code, Content Type, Indexability, Indexing Reason, and Discovery Source | Keep one or more known values without having to remember their exact spelling. |
| Audit field filter | Robots directives, rendered robots values, X-Robots-Tag, and Redirect Type | Review technical directives directly when those columns are visible in the table. |
Combine alternatives within a column, then narrow across columns.
Selecting several values in one column keeps rows matching any selected value. A row can be 301 or 302, for example. Adding a filter in another column narrows the result further: the row must also match that URL, content type, or indexability condition.
Review one site section
URL Incl. /services/ and URL Excl. /archive/
Keeps the active service URLs while removing a known legacy branch.
Build a migration response queue
URL Incl. /new-section/ plus selected 3xx and 4xx status codes
Shows redirecting and broken URLs only inside the migrated section.
Trace an old hostname
Canonical Incl. old.example.com
Finds pages whose canonical field still references the previous host.
Review indexable HTML only
Content Type text/html plus Indexability Indexable
Removes resources, redirects, errors, and intentionally excluded pages from content QA.
Build a review queue in five passes.
- 1.
Choose the smallest useful set of columns
Open Filter and hide columns that do not answer the current question. Column visibility changes presentation, not which rows qualify.
- 2.
Constrain the site section first
Use URL Incl. for the directory, hostname, or pattern you own. Add URL Excl. only for a specific source of noise.
- 3.
Add one technical condition
Use a column filter for status, content type, indexability, indexing reason, or discovery source. Start broad enough to avoid hiding related symptoms.
- 4.
Read several rows before narrowing again
Confirm the remaining rows describe the problem you intended to isolate. Add another filter only when it removes a clearly irrelevant group.
- 5.
Sort the column that drives the decision
Sort after filtering so repeated values, outliers, and adjacent URL patterns become easier to compare.
Start literal. Reach for patterns only when they save work.
Incl. and Excl. use case-insensitive substring matching by default and compare both encoded and decoded text. That makes a path fragment such as /products/ the safest starting point.
| Input | Meaning |
|---|---|
| blog|guides | Match either term in the same text field. |
| regex:^https://example.com/(en|fr)/ | Use an explicit regular expression for a precise structural pattern. |
Invalid regular expressions fall back to literal matching. Keep patterns short enough that another reviewer can understand why each row remains.
Reset the review, not your column layout.
When filters, sorting, or the frozen URL state have changed, Actions shows Reset pages table. It clears text and value filters, restores the default sort, and unfreezes URL. The columns you chose in Filter remain visible or hidden, so a useful review layout can be reused for the next question.
Once the filtered rows describe a real unit of work, export them with the evidence columns still visible. Name the site section and filter logic in the handoff so the recipient knows both what is included and what was intentionally left out.
Turn the filtered crawl into a fix list