Site search
Search CiteKit
Find tools, guides, sample reports, official source notes, and policy pages across the CiteKit library.
Type a topic to search the static CiteKit index. Queries stay in your browser.
How to search the CiteKit library
Search works best when the query names the task you need to complete. Use terms such as schema, crawler, prompt log, alternatives, scorecard, sources, saved reports, or ChatGPT citation. The index covers tools, guides, templates, resources, examples, reports, and trust pages so a reviewer can move from a question to a working artifact without guessing which section of the site contains it.
- Search for the blocker first, such as crawler access, answer snippet, or comparison proof.
- Open the result type that matches your next action: tool for generation, guide for process, template for handoff, or report for example format.
- Save or copy the artifact created by the linked tool so the search session ends with a reviewable output.
Search result types
| Type | Use it for | Expected next step |
|---|---|---|
| Tool | Generate prompts, schema, snippets, crawler notes, briefs, or scores. | Copy, download, or save the generated report. |
| Guide | Understand a workflow before editing a SaaS page. | Pair the advice with a prompt log, source list, or page-change note. |
| Template | Turn evidence into a structured outline, audit report, or schema brief. | Fill the draft with public sources before publishing. |
| Resource | Check rubrics, crawler references, prompt packs, and terminology. | Use the reference to make a tool result easier to review. |
| Report or example | Compare your output with a fictional but complete audit artifact. | Copy the structure, not the fictional product facts. |
Common starting points
Most visitors begin with a tool, then use the method page or sample report to understand how to review the output.
How search supports the site
Search is local and browser-based. It helps users and reviewers find method notes, source references, saved-report guidance, role-based use cases, and individual tools without sending queries to a server. This keeps the static implementation simple while making the library easier to audit and navigate.
Search privacy and limits
Queries run against a static JSON index in the browser. CiteKit does not receive search terms in the current implementation, and the results are meant for navigation rather than ranking claims. If a query returns weak results, use the contact page to suggest a better resource or workflow.
When search results are weak
Weak search results usually mean the query is too broad or the site needs a better resource. Try a more specific task query before assuming the site has no answer. For example, search "SoftwareApplication schema" instead of "SEO", "Perplexity citation" instead of "AI", or "saved report" instead of "audit". If a real user query still has no useful result, that query belongs in the content backlog rather than being covered by a thin placeholder page.
- Use Search Console impressions later to identify queries that deserve a new guide, resource, or template.
- Do not create bulk pages for every zero-result query; require a workflow, example, table, or downloadable artifact.
- Keep search labels plain so results cannot be confused with ads or navigation tricks.
Navigation quality checks
This page supports clear navigation, which is part of AdSense readiness and a good user experience. The primary nav exposes Start, Tools, Workflow, Use cases, Resources, Guides, Templates, Search, Method, Updates, and About. Footer links add Privacy, Terms, Contact, Checklist, Examples, Sources, and Saved Reports. Search is a supplement to those links, not a replacement for a clear menu.