Home / Guides / How to find keywords in a website's source code

Guide · Source search

How to find keywords in a website's source code

By SearchWebCode · Updated November 21, 2026 · Source search · 3 min read

A magnifying glass over one highlighted word in source.
Use View Page Source for the original HTML, Elements for the current DOM and DevTools Search for loaded files. Network has a separate search for response text and headers.

Choose the scope before searching. The text shown on the page, the HTML returned by the server and the files loaded by the browser can contain different strings. A failed search in one place says nothing conclusive about the others.

Search the original HTML

Open View Page Source, then use Find for your keyword. This can reveal a meta tag, inline code, a comment or a script URL that the normal page does not display.

Keep the tag around the match. For example, a plugin path in a stylesheet link and the same path inside a tutorial paragraph are different evidence. The WordPress plugin walkthrough shows how to interpret that distinction.

Search the current DOM

Open DevTools → Elements and use its search bar. This searches the document as it currently exists after browser processing and JavaScript changes. Try the interaction that creates the content, then search again.

A browser's normal Find command searches the rendered page rather than offering a complete search of HTML attributes and loaded scripts. Use the source or developer tools when those are the material you need.

Search loaded files

Open DevTools → More tools → Search. Chrome's Search panel looks through loaded resources and supports case and regular-expression options. Open a match in Sources to read its context.

A marker inside an external JavaScript file may be missing from the original HTML. It must be in a resource available to the tool before that resource search can find it. Chrome documents a separate Network search for response bodies and headers.

A three-marker example

Our small local example uses these deliberately different locations:

MarkerWhere the example puts itWhere to inspect
alpha-sourceA meta attribute in the original HTML.Page source or the DOM element.
beta-domA node added by an external script after a button click.The DOM after the click; also the loaded script that defines the text.
gamma-resourceA comment in the external script.The loaded file's source or network response.

The initial HTML contains the script URL, not its entire body. This is why searching that HTML for the other two strings does not find them. The example illustrates scope, not a guarantee about how an arbitrary website renders its content.

Refine the search without changing the question accidentally

Start with a distinctive literal. Check capitalization and escaping if it fails. A regular expression can handle variable digits or whitespace, but it also changes the matching rule. The regex guide explains literal anchors and pattern checks.

For a framework clue such as __NEXT_DATA__ or a vendor hostname, inspect the surrounding element before assigning a technology. A copied example can contain the same keyword.

Move from one page to many websites

These browser tools inspect the page and resources you loaded. They do not automatically crawl every page on a domain. SearchWebCode instead searches stored homepages across its index.

Use a confirmed marker such as wp-content/plugins/elementor/ with the cross-site source-search workflow. Keep index capture dates separate from the date of your live browser check.

References

Chrome documents loaded-resource search, Network response search and DOM inspection.

Source counts checked 2026-10-14. They describe stored homepages, not live installations. How the counts are measured.

Frequently asked questions

Why can I see a word on the page but not in View Page Source?

The browser may have added or fetched it after the initial HTML response. Inspect the DOM and the relevant loaded resources after the interaction.

Does DevTools Search search every page on a website?

No. It works with resources available in the current debugging context. A broader crawl or source index has a different scope.