Source Code Search: Find Text in Page HTML

You already know how to open View Source. The problem is doing that on forty template variants after a tag manager migration, or proving that noindex is gone from every landing page in a launch batch. Tab fatigue is real. You need search across HTML, not memory. This guide covers a simple workflow: build a URL list, pick plain text or regex, choose found vs not-found mode, then export CSV for tickets. The tool is Source Code Search on Scrawl: up to 25 URLs per run, raw HTML only, safe regex limits, and three snippets per page. When browser search beats a full crawl Use a URL-list search when: You have a known set of URLs from analytics, sitemaps, or a recent deploy log You need a single string (GTM container ID, old jQuery path, rel="canonical" variant) You want a quick negative check ("this pixel should be gone everywhere") Open Screaming Frog when you need source code search across an entire crawl under its paid licence. Scrawl's tool does not spider your domain. It only fetches what you paste. What gets searched Each URL fetch: Follows redirects with the usual safety checks Caps HTML at 1.5MB per page Searches the raw response (no JavaScript execution) That means client-rendered tags may be missing from results. If your analytics only appears after React mounts, this search will not see it unless the tag is also in the initial HTML or you paste saved HTML from a rendered capture. For structured data specifically, pair this with the Schema Checker on sample URLs. JSON-LD lives in script tags; plain text search can find the script block even when you do not parse it. Plain text vs regex Plain text is the default. Search for googletagmanager.com/gtm.js , a affiliate network domain, or a retired CDN…