Your public website remains the source
The default onboarding path starts from approved public URLs and sitemaps without requesting customer database credentials or private-network access.
GONGJAK AX TOOL / COMPANY WEBSITE AGENT
Company Website Agent does not require a site rebuild or internal database access. It collects and structures approved public pages, then connects a visitor's natural-language question to grounded answers and relevant content.
01 / DEFINITION
Company Website Agent is an installable AX tool that turns public company, service, product, project, notice, and FAQ pages into searchable knowledge. It answers with retrieved website evidence and returns the source page, related content, follow-up questions, and an appropriate inquiry path.
One public website → one verified knowledge boundaryThe default onboarding path starts from approved public URLs and sitemaps without requesting customer database credentials or private-network access.
Only retrieved website knowledge and allowed content IDs reach the answer model, with insufficient evidence designed to return no answer.
The target integration connects a lightweight JavaScript plugin to an existing search input, button, or dedicated trigger.
02 / DIFFERENCE
It does not replay a scripted conversation or let a general model guess. It connects current public content to the visitor's actual question.
Operators register every answer manually
Approved web content is collected, chunked, and indexed
A fixed response follows a keyword or scenario
A constrained answer is generated from relevant evidence
The conversation ends inside a chat window
Answers include sources, related pages, and follow-ups
Every content change requires an answer rewrite
Changed pages trigger targeted knowledge refreshes
03 / PRODUCT FLOW
The product is not just a model. It is the complete flow that safely collects website content, publishes a verified index, and preserves visitor questions as signals for future content improvement.
Follow sitemaps, canonicals, and internal links, then approve inclusion and exclusion rules.
Preserve headings and content structure, create searchable chunks, and index them for lexical and semantic retrieval.
Send only sufficiently relevant evidence to the model and return answers, citations, content cards, and follow-up questions.
Compare content hashes and update changed documents before atomically publishing a verified index version.
04 / KNOWLEDGE SOURCE
The default scope is information a visitor can already access on the public website. Private data integrations require separate approval and security design.
About pages, history, organization, locations, contacts, and official policies
Service descriptions, product details, features, audiences, and official guidance
Approved projects, responsibilities, scope, and verifiable outcomes
Frequently asked questions, careers, news, notices, and frequently changing content
05 / AGENT × AEO
AEO helps search engines and AI answer services understand a site's entities and answers. Company Website Agent connects the same public knowledge to real visitor questions. Designing both together keeps human-facing answers aligned with externally discoverable evidence.
Explore GONGJAK AEOKeep company names, service names, canonical URLs, and scope consistent across copy, metadata, and structured data.
Publish actual visitor questions as definitions, comparisons, procedures, and accessible FAQ content.
Preserve canonical URLs and safe internal links so every Agent answer can lead back to its source.
Do not force answers when evidence is missing. Preserve those questions as signals for deciding what public content to add.
06 / INSTALLATION
This is not a full-site migration. We agree on the public information scope, create a verified search index, and connect an Agent entry point to the current interface.
Register the primary domain and public site, then verify ownership and allowed origins.
AI proposes URL types and fetch modes; an operator approves what is included and excluded.
Only a knowledge version that passes sample questions and quality checks becomes visitor-searchable.
Attach an installation key and trigger to an existing button or search input to open the Agent.
07 / TRUST BOUNDARY
A visitor Agent needs tenant isolation, source validation, and an explicit insufficient-evidence path—not just a convenient interface.
Search only within the customer, site, locale, and active index
CHECKVerify the allowed Origin and site installation key
CHECKReturn not_found without an LLM call below the relevance gate
CHECKRevalidate every citation ID and URL returned by the model
CHECKKeep the previous live index if a new version fails quality checks
CHECKTreat collected content and visitor questions as untrusted data
CHECK08 / FAQ
Direct answers to the questions a team asks before installing a website Agent.
It is a website AX tool that turns an existing public website into searchable knowledge and uses that evidence to answer visitor questions with relevant source pages.
It does not replay a fixed script or only list title-keyword matches. It retrieves relevant website evidence and, when evidence is sufficient, returns a constrained answer, sources, content cards, and follow-up questions.
A rebuild is not the default integration path. The platform uses the public site as the knowledge source and is designed to connect a JavaScript plugin to an existing search input, button, or dedicated trigger. Final scope depends on the site's architecture and security policy.
No customer database account, private-network access, or internal API key is required for the public-website onboarding path. Information not supported by public pages remains a content gap rather than an invented answer.
The target flow follows an approved refresh policy, compares page signals and content hashes, processes only changed documents and chunks, and publishes a verified index version.
No. The intended behavior applies relevance and minimum-evidence gates and returns not_found below the threshold. Citation IDs and URLs are revalidated by the server.
The Agent and AEO use the same company entities, answer-first copy, canonical URLs, and public evidence. Questions that lack evidence can also show where the website needs clearer public content.
The GONGJAK home page already provides an Agent grounded in GONGJAK's company, service, and project knowledge. The reusable platform version for external websites is in release preparation, and its final scope may change after validation.
Pricing and fixed delivery estimates are not published on the website. We first review the number of pages, content types, refresh policy, and required safety profile before providing a scoped proposal.
COMPANY WEBSITE → BUSINESS KNOWLEDGE