Frequent Questions and Answers

Seekdown creates website AI chatbots and smart help centers from approved content sources. The assistant answers questions with source links, guides visitors to the right next step, and stays aligned as your content changes.

Traditional search returns links. Generic chatbots can drift off-source. Seekdown answers from approved sources, can show citations, and gives teams controls for tone, behavior, branding, source boundaries, and fallback handling.

The main building blocks are memory datasets, data capture jobs, AI assistants, analytics, and keys for embeds or integrations.

Datasets can contain uploaded files, website content captured by crawlers, content created through APIs, and form submissions collected by assistants. Supported uploads include PDFs, Word documents, spreadsheets, PowerPoint files, text, rich text, Markdown where enabled, and ZIP archives.

Crawler settings include initial URLs, allowed hostnames, included paths, excluded paths, sitemap URL, depth, max contents, schedules, and crawler keys. Use these controls to avoid login pages, checkout flows, or unrelated site sections.

Yes. Data capture jobs can be rerun and scheduled. Teams can monitor progress, review captured content, adjust crawler scope, clean results, and re-index datasets when needed.

An assistant needs a name, a connected dataset, optional behavior instructions, optional security settings, and enough reviewed content to answer well.

Yes. Assistant settings include behavior instructions, search controls, security, appearance, hints, translations, forms, keys, and backup or restore options.

Yes. Assistants can use forms to collect visitor information, and teams can review lead and usage data in the workspace.

Configure allowed origins, generate an assistant key if your security mode requires one, add the Seekdown assistant script and container, then initialize the assistant with its ID. See embed an assistant on a website.

Yes. WordPress can use the Seekdown plugin with all-pages mode or a shortcode. Shopify can use the theme code path with the script, container, assistant ID, and token if required.

Public endpoints support dataset file upload, dataset content create and update, OData content reads, crawler triggers, assistant queries, and health checks. See the API documentation.

Custom GPT actions and other API integrations use generated keys and the public API surfaces configured for your workspace.

Seekdown uses dataset keys for dataset APIs and OData, assistant keys for embeds and assistant query APIs, and crawler keys for public crawler triggers.

Allowed origins define which website domains can load an embedded assistant. Add production, staging, custom Shopify domains, and .myshopify.com domains when those domains are part of the launch.

Rotate the key immediately, update every integration that used the old key, and avoid sending secrets in support messages or committing them to code repositories.

Analytics include sessions, total queries, average queries per session, unique users, last accessed time, sessions with or without interaction, conversations, and positive or negative reactions.

Yes. Visitor questions reveal missing articles, unclear policies, repeated ticket drivers, and conversion friction. Use those patterns to update source content, then refresh the dataset.

Dashboard preview traffic is excluded from analytics. The current docs describe analytics windows around the last 30 days.

The pricing page lists Seekdown Basic, Seekdown PRO, and Enterprise Pay-As-You-Go. Basic and Pro include fixed monthly allowances. Enterprise pay-as-you-go uses metered dimensions from the first unit consumed.

The current dimensions are storage, LLM tokens, standard proxy bandwidth, and residential proxy bandwidth. The pricing calculator estimates these dimensions before taxes.

Some features are available to everyone, while others depend on plan, subscription status, generated keys, or workspace permissions.