
The second step of creating a data service is to select trigger and test URLs. This step determines which pages your data service extracts data from, and provides up to ten URLs to test your extraction code.
Trigger URL Pattern — Specifies a URL pattern to match against search results and trigger your data service. Since a data service is built to extract data from web pages with a particular structure, you must scope your data service to trigger only against those pages.
Multiple wildcards are supported—you may begin and end your
pattern with a wildcard, "*", which matches any string. For example,
*.wikipedia.org/wiki/* or
*.wikipedia.com/wiki/* trigger your data service for all
Wikipedia pages, while en.wikipedia.org/wiki/* triggers
only for Wikipedia pages in English. http:// is
optional.
![]() |
Note |
|---|---|
"*pedia.com/wiki/q=*" is NOT supported. The prefixed wildcard much match the host and domain names and the appended wildcard must match paths. |
Add Test URLs — Specifies up to ten URLs to test your data service against. You can use these URLs in later steps to verify that your data service is extracting data correctly. Be sure to provide URLs that match your specified Trigger URL Pattern.
As you select or tab to the next field, SearchMonkey verifies
that the URL you specified is reachable. If the test URL is
reachable, SearchMonkey displays "Reachable URL" in
green, or possibly a 301 HTTP code. If the test URL is
unreachable, SearchMonkey might display a timeout message,
"Unreachable URL - Operation timed out after 5000 milliseconds
with 0 bytes received" or an error message "Non 200
HTTP code - Recieved: ,
where http_code" is typically
a http_code404 or a 50x. If you receive an error
code or timeout, check the test URL in your own browser, and select
a different URL if necessary
— Retrieves ten random URLs that match the specified Trigger URL Pattern, overriding any test URLs specified manually. SearchMonkey verifies that all ten URLs are reachable, as above.
— Saves your changes and continues to “Step 3: Data Extraction”.
— Saves your changes and returns to “Step 1: Basic Info”.
— Returns to the Application Dashboard.