KB Search Query Tester

Store Positioning

Store title: KB Search Query Tester

Short description: Test public knowledge base search queries and evaluate whether expected articles, titles, keywords, or categories appear in the top results.

SEO title: KB Search Query Tester — technical SEO, web, and domain audit

SEO description: Test public knowledge base search queries and evaluate whether expected articles, titles, keywords, or categories appear in the top results. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.

Categories: DEVELOPER_TOOLS

Keywords: kb, search, query, tester, public data, web/domain audit

Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: W1 — Web/domain audit
• Primary event: page-audited at $0.00490 base
• Default max charge: $10.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. Kb Search Query Tester: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• page-audited: base $0.00490, GOLD $0.00392. Kb Search Query Tester: charged when page audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• record-extracted: base $0.00372, GOLD $0.00298. Kb Search Query Tester: charged when record extracted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• finding-emitted: base $0.00372, GOLD $0.00298. Kb Search Query Tester: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• audit-report-generated: base $0.05000, GOLD $0.04000. Kb Search Query Tester: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

The actor accepts actor-start before work, accepts the primary event before each dataset row, and accepts the configured report event before writing report files. If maxChargeUsd or the live PPE limit blocks a charge, the corresponding row or report is not written.

Public Task Concepts

• Audit KB Search Query Tester controls on a capped public sample
• Find high-priority KB Search Query Tester issues before release
• Validate KB Search Query Tester evidence from supplied pages
• Prioritize KB Search Query Tester fixes with severity and proof
• Export KB Search Query Tester QA rows for client review

Test public knowledge base search queries and evaluate whether expected articles, titles, keywords, or categories appear in the top results.

What it does

• Accept help center base URL, search endpoint URL, configured search query list, expected URLs/titles/keywords, and selectors.
• Run public search queries with polite rate limits.
• Extract result rank, URL, title, snippet, category hints, and match status.
• Score query coverage using expected result rules.
• Detect zero-result searches, weak top result matches, duplicate results, and result drift.
• Generate a search QA report for support teams.

What it does not do

• No private support search, login-required results, search ranking manipulation, automated search spam, or scraping personal support tickets.
• No guarantee that a query “should” rank without user-provided expectations.

Input fields

Primary inputs from the locked actor spec: helpCenterBaseUrl, searchUrlTemplate, queries, expectedResults, expectedKeywords, resultSelectors, locale, maxResultsPerQuery, requestDelayMs, includeSnippets, failOnMissingExpected, timeoutMs. maxChargeUsd keeps runs capped during production use.

Output fields

Dataset rows include: query, locale, searchUrl, resultRank, resultUrl, resultTitle, resultSnippet, categoryHint, matchedExpected, expectedUrl, expectedKeywordMatches, score, issueCode, warning.

Starter example

Use examples/input.tiny.json as a small starter input. Keep the first run capped and review the dataset before increasing limits.

Public task examples

• Run KB Search Query Tester on supplied sample data: Run KB Search Query Tester on supplied sample data using a small bounded input.
• Generate a KB Search Query Tester QA report: Generate a KB Search Query Tester QA report using a small bounded input.
• Find invalid rows with KB Search Query Tester: Find invalid rows with KB Search Query Tester using a small bounded input.
• Create a capped local endpoint readiness check for KB Search Query Tester: Create a capped local endpoint readiness check for KB Search Query Tester using a small bounded input.
• Prepare KB Search Query Tester output for downstream automation: Prepare KB Search Query Tester output for downstream automation using a small bounded input.

Public source provenance

The starter input tests Zendesk's public help-center search for getting started and checks for the public article at https://support.zendesk.com/hc/en-us/articles/4408884056346-Introduction-Getting-started-with-Zendesk-Support.

Reports

• kb-search-query-test-report.md
• query-result-matrix.csv
• missing-expected-results.json
• zero-result-queries.csv
• search-quality-summary.json

Limitations and safe use

Start with supplied-input runs, then enable live endpoints only with tight caps, domain allowlists, and no secrets in public examples.