TinyPingTinyPing

Keyword Checker

Check whether a word or phrase appears on a web page. You see if it was found, how many times, and the page's status code. Enter a URL such as https://example.com and the text to look for.

Common keyword check problems

The text is visible in the browser but not found

The page builds that part with JavaScript after loading, so the text is not in the HTML the server sends. This check reads the raw HTML, like the keyword monitor. Pick text that is in the server response: a heading, the title, or a footer line.

Case does not match

The check is case-sensitive: "In stock" does not match "In Stock". Copy the text from the page source (view-source) rather than from what you see on screen, since CSS can change how text looks.

HTML entities and tags split the text

On screen you see Tom & Jerry, but the HTML contains Tom &amp; Jerry, or a word is wrapped in a <strong> tag halfway through a phrase. Search for a shorter piece that appears unbroken in the source.

You got a different page than expected

The URL redirected to a login page, a cookie banner wall or a country version. Check the status code and final URL, and point the check at the page that really holds the text.

A bot protection page answered

Cloudflare, a WAF or a security plugin may serve a challenge page to automated requests. The status is often 403 or 503 and the text is missing. Allow the checker or use a page that is not challenged.

How to check for a keyword on a page

  1. Enter the page URL, for example https://example.com/pricing.
  2. Enter the exact text to look for, with the right capitalisation.
  3. Click Check page.
  4. Read whether the text was found, how many times, and the status code.

What is a keyword check?

A keyword check fetches a page and searches its HTML for a piece of text. It answers a question a status code cannot: is the page showing the right content?

A site can return 200 OK and still be broken. A database error printed inside the normal template, an empty product list, a "maintenance" notice or a hacked page full of spam all return 200. Looking for text that should be there, or text that should not, catches those cases.

This checker reads the raw HTML from the server after following redirects. It does not run JavaScript, and the match is case-sensitive. That is exactly how TinyPing's keyword monitor works, so a text that is found here will be found by the monitor.

Looking for: "Add to cart"

HTTP/1.1 200 OK
...
<button class="buy">Add to cart</button>

Found: 1 match

When to use a keyword checker

Checking a Shopify or WooCommerce product page

Confirm "Add to cart" is on the page, or that "Sold out" is not, before a campaign sends traffic there.

Catching error text behind a 200

Search for phrases like "Error establishing a database connection" on WordPress, or your framework's error message, which some setups return with status 200.

Verifying a deploy

Look for a version string, a new headline or a footer line to confirm the new release is the one being served, not a cached copy.

Watching a third-party page

Check a supplier's status page or a public listing for a word that tells you something changed.

Check something else

Frequently asked questions

Is the keyword check case-sensitive?

Yes. "Login" and "login" are different. Copy the text from the page source to get it exactly right.

Does it run JavaScript?

No. It reads the HTML the server sends, after following redirects. Text added by JavaScript in the browser will not be found.

Does it search hidden text and HTML attributes?

Yes. It searches the whole HTML source, so text in hidden elements, attributes, scripts and comments counts as a match.

Can I check that a word is not on the page?

Here you see whether it was found and how many times. A TinyPing keyword monitor can alert you either when the text disappears or when it appears.

What happens if the page returns an error?

You see the status code alongside the result. The search still runs on whatever the server returned, so an error page will usually not contain your text.

A 200 status is not the whole story

Pages break while still returning 200 OK. A keyword monitor checks the content every 5, 15 or 30 minutes and alerts you when:

  • text that should be there disappears
  • text that should not be there appears
  • the page errors or times out
Start monitoring free for 7 days

US$6.99 a month or US$47 a year per 50 monitors, team members free. 7-day free trial, no card needed.

Want alerts in team chat? Follow the guide for Slack or Google Chat.