Screaming Frog Custom Search lets you scan crawled pages for words, phrases, HTML elements, response text, or patterns that a normal crawl summary may miss. For SEO audits, it is useful when you need to find a specific implementation detail across many URLs instead of opening pages one by one.
How do you use Screaming Frog Custom Search for an SEO audit? Open Configuration, use Custom Search, define what you want to find, crawl the site, and review the matching URLs. The strongest use cases are focused checks such as finding analytics snippets, legal wording, old brand names, internal-link patterns, or implementation text that needs review.
What Screaming Frog Custom Search does
Custom Search extends a standard crawl with a question that is specific to your site. Instead of asking only whether a page returns 200, you can ask whether pages contain a particular script, phrase, heading pattern, class, identifier, or piece of text. That makes the feature useful for audits where the same issue may appear across many templates.
When Custom Search is better than a normal crawl filter
Standard crawl data is excellent for titles, canonicals, status codes, headings, links, and other common fields. Custom Search helps when the information you need is buried inside page HTML or page text and is not represented by a standard column.
How to set up a Custom Search audit
- Define the exact question you want the crawl to answer.
- Choose the search type that matches the evidence you need.
- Write a narrow pattern rather than starting with a broad phrase.
- Run the crawl and inspect matching URLs.
- Open representative pages before acting on the result.
Use Custom Search to find analytics and tracking code
A practical audit is checking whether important templates contain the expected analytics or tag-manager snippet. Search for a distinctive part of the implementation, then sample both matches and non-matches so you can separate a real implementation gap from a template difference.
Use it to find outdated brand or product references
Site migrations and rebrands often leave old names inside body copy, footer text, schema, or template content. A Custom Search pass can surface those remnants quickly. This is especially useful when the old wording appears on many pages but is not visible in a standard crawl export.
Use regex when the pattern can vary
Regex is useful when the content changes slightly from page to page but follows a predictable structure. Keep the expression small, test a known match and a known non-match, and document what the pattern is intended to detect before using it across a large crawl.
How to avoid false positives
A match does not automatically mean an SEO problem. The same phrase may appear in navigation, structured data, examples, comments, or a template element that is expected. Review the context of representative matches and compare them with pages that should not match.
Useful Custom Search checks for SEO teams
- Find old company or product names after a rebrand.
- Check that required tracking snippets exist on key templates.
- Locate pages containing a deprecated widget or embed.
- Find a recurring legal or compliance phrase before updating it.
- Identify pages that contain an outdated canonical or internal-link pattern.
How Custom Search fits with other crawl checks
Custom Search works best as a focused layer on top of normal technical SEO checks. For example, use a standard crawl for status codes and canonicals, then use Custom Search to investigate a template-level implementation issue. This prevents one tool feature from becoming a replacement for the broader audit.
Build a repeatable Custom Search checklist
Save the questions your team checks regularly and keep each one tied to a clear expected result. A useful audit record includes the pattern, the purpose, the date checked, the number of matches, and the action taken. That turns an ad hoc crawl into a repeatable QA process.
Use ToolBoxKart tools alongside the audit
After the crawl identifies page-level SEO issues, use the ToolBoxKart SEO Meta Extractor to inspect individual URLs and the Search Console Regex Generator when you need matching patterns for Search Console reporting. These tools support the audit rather than replace the crawl.
Related ToolBoxKart guides
For structured-data extraction, read Screaming Frog JSON-LD Custom Extraction. For orphan discovery, use the guide to finding orphan pages with crawls and sitemaps. For redirect problems, see how to check redirect chains for SEO. For Search Console filtering, read how to use Google Search Console regex.
Frequently asked questions
What can Screaming Frog Custom Search find?
It can search crawled page content for specific text, patterns, or HTML details so you can locate implementation elements that are not covered by standard crawl fields.
Should every Custom Search rule use regex?
No. Use the simplest search method that answers the audit question. Regex is useful when the value varies in a predictable way, but a plain phrase is easier to understand and maintain when it is enough.
How do I know a Custom Search match is a real SEO issue?
Review the surrounding page context and compare several matching URLs with pages that should not match. A match is evidence to investigate, not proof that a page is broken.
Sources
- Screaming Frog SEO Spider — Custom Search
- Screaming Frog SEO Spider
- Google Search Central — Crawling and indexing overview