What you’ll need
CSV with a query or URL column, or a line-separated list. Enter a pattern or build one from a list of literal values.
Build RE2 expressions and test them against real query or URL exports. Keep the full rows and metrics you need.
Runs on your device · Files stay privateCSV with a query or URL column, or a line-separated list. Enter a pattern or build one from a list of literal values. New here? Start with “Try an example”.
Or paste your data below. You can edit it before running the tool.
Or paste your data below. You can edit it before running the tool.
CSV with a query or URL column, or a line-separated list. Enter a pattern or build one from a list of literal values.
The RE2 engine evaluates partial matches by default. Include/exclude, case and anchor settings are explicit. Other CSV columns survive export.
50,000 rows and 8 MB text. RE2 rejects lookaround and backreferences. GSC uses partial matching; other platforms may behave differently.
A small regex mistake can hide useful queries or pull unrelated pages into a report. This SEO regex tester shows which supplied rows match before you use the pattern elsewhere. It supports literal-list building as well as direct RE2 expressions, making it useful for branded query groups, URL families or recurring reporting filters where a long manual include list becomes hard to maintain.
Paste a line list or upload a CSV with the query or URL column you want to test. Keep any metrics you need in the same rows.
Enter an expression or build one from literal values. Choose case sensitivity, include/exclude behavior and anchors to match the task.
Run the filter and inspect both expected matches and unexpected exclusions. Export the retained rows with their original metrics.
RE2 uses its own supported syntax. A pattern that works in another regex engine may fail here. Partial matching can include more than you intended, so anchors and literal escaping should be deliberate. A correct filter cannot repair missing or inconsistent input rows.
Use GSC Cannibalization Tracker when the filtered query/page history needs a leadership comparison across periods.
50,000 rows and 8 MB text. RE2 rejects lookaround and backreferences. GSC uses partial matching; other platforms may behave differently.
They are not supported by RE2. Rewrite the expression using supported alternatives instead of assuming a JavaScript or PCRE pattern will behave identically.
Use the literal-list builder or escape regex metacharacters correctly. Otherwise a plus sign can act as an operator rather than the character in the name you wanted to match.