The preview edition
HelpKit growth preview
See what the highest-leverage change could unlock, why the opportunity matters, and the first measurable move before opening the Full Report.
Growth readiness map
Your strengths and gaps at a glanceSelect a dimension below. Unconfirmed dimensions are not plotted.
Inspect a dimension
AI Search Readiness88/100
What this means
Source and limits of generalization let readers verify the conclusions beyond promotional assertions
Observed evidence
No independent outcome evidence supports broad productivity generalization.
32 public sources observed
Website readiness
Your growth snapshot
Public evidence · Five equally weighted dimensions · Search samples, not measured AI citations
Positioning and offer
20 conditions assessed
Conversion and trust
20 conditions assessed
Search discovery
20 conditions assessed
AI content readiness
16 conditions assessed
External recognition
12 conditions assessed
Explore score evidence 22 checks · 5 dimensions
Website readiness
Your growth snapshot
Public evidence · Five equally weighted dimensions · Search samples, not measured AI citations
How scoring works
Target: one-to-three-person SaaS support teams using Notion. Conversion: seven-day trial, first useful output, then subscription. Checked: homepage, SaaS, pricing, MCP, AI, comparison, support, legal, Academy, signup, robots, sitemap, llms, changelog. Frozen questions: setup; MCP draft workflow; trial/plan/renewal commitments. Frozen queries: “best Notion knowledge base software”; “turn Notion docs into help center”; “HelpKit alternatives GitBook”; “HelpKit pricing reviews”. Search date 2026-09-19; English; engine, region, count, locale, and ranks unknown. First successful samples remain src_020–src_023.
Evidence-backed conditions determine each score. Unknowns remain unscored. This measures readiness, not traffic, revenue or search ranking.
Positioning and offer
20 conditions assessed
Score evidence
Audience and use case · 4/4
- Specific target user rather than everyone · Supported: Names one-to-three-person support teams. helpkit.so · Use Case Page
- Concrete trigger for using the product · Supported: Names recurring questions as trigger. helpkit.so · Use Case Page
- Specific difficulty at that trigger is clear · Supported: Describes developer bottleneck and answer need. helpkit.so · Use Case Page
- Shown use case matches the identified user and trigger · Supported: Use case matches cohort and trigger. helpkit.so · Use Case Page
Input and deliverable · 4/4
- Task actually performed by the product is clear · Supported: Notion-to-help-center task is clear. helpkit.so · Homepagehelpkit.so · Use Case Page
- Required input, account or other prerequisites are identifiable · Supported: Notion, account, public page, and MCP approval are stated. helpkit.so · Homepagehelpkit.so · Product Pagehelpkit.so · Signup Page
- Actual output and its format are identifiable · Supported: Hosted site, widget, and draft outputs are identifiable. helpkit.so · Homepagehelpkit.so · Product Page
- Product execution is distinguished from remaining user work · Supported: Publishing is distinguished from customer writing and review. helpkit.so · Homepagehelpkit.so · Use Case Pagehelpkit.so · Product Page
Value mechanism · 4/4
- Specific work outcome expected to change is clear · Supported: Self-service and reduced repetitive support are stated. helpkit.so · Homepagehelpkit.so · Use Case Page
- A capability is connected to how that change happens · Supported: Capabilities connect to that outcome. helpkit.so · Use Case Pagehelpkit.so · Product Page
- Workflow explains the capability in the primary use case · Supported: Workflows are shown. helpkit.so · Use Case Pagehelpkit.so · Product Page
- Core value is understandable without unexplained jargon · Supported: Core value is operationally explained. helpkit.so · Homepagehelpkit.so · Use Case Page
Reason to choose · 4/4
- Existing alternative way of doing the work is identifiable · Supported: Git-based docs are identified alternative. helpkit.so · Comparison Page
- A material difference beyond generic superiority is explained · Supported: Notion ownership is differentiated. helpkit.so · Comparison Page
- Difference maps to an inspectable capability, workflow or deliverable · Supported: Difference maps to inspectable workflow. helpkit.so · Comparison Pagehelpkit.so · Product Page
- Suitable or unsuitable needs and constraints are explained · Supported: Suitable constraints are stated. helpkit.so · Comparison Page
Next action · 4/4
- Primary action is identifiable · Supported: Trial signup is identifiable. helpkit.so · Homepagehelpkit.so · Pricing Pagehelpkit.so · Use Case Page
- Label explains the next step · Supported: Labels explain action. helpkit.so · Homepagehelpkit.so · Use Case Page
- Observed public destination matches the promise · Supported: CTAs reach signup. helpkit.so · Homepagehelpkit.so · Use Case Pagehelpkit.so · Signup Page
- Multiple paths are distinguishable and consistent, or a single path has no conflicting instructions · Supported: Trial, demo, and MCP routes are consistent. helpkit.so · Homepagehelpkit.so · Use Case Pagehelpkit.so · Product Page
Conversion and trust
20 conditions assessed
Score evidence
Commitment and costs · 4/4
- Required money, time, account or data investment is clear · Supported: Yearly prices, limits, trial, and AI add-on are public. helpkit.so · Pricing Pagehelpkit.so · Public Browser Observation
- Deliverables and access scope are clear · Supported: Access scope is described. helpkit.so · Homepagehelpkit.so · Pricing Pagehelpkit.so · Product Pagehelpkit.so · Public Browser Observation
- Duration and usage limits are clear · Supported: Trial, yearly limits, and renewal mechanics are public. helpkit.so · Pricing Pagehelpkit.so · Termshelpkit.so · Public Browser Observation
- Relevant renewal, expiry or cost changes are explained, or evidence establishes they do not apply · Supported: Terms state renewal and cancellation. helpkit.so · Terms
Claim evidence · 3/4
- Central claim has an inspectable demonstration, example or original supporting material · Supported: Demos and setup are inspectable. helpkit.so · Homepage
- Subject and origin of supporting material are verifiable · Supported: Demos and testimonials are attributed. helpkit.so · Homepage
- Material lets a reader trace relevant inputs and process to actual outputs · Supported: Setup traces input to output. helpkit.so · Homepage
- Claim strength does not exceed what the material demonstrates · Needs improvement: Broad customer and reduction claims exceed individual demonstrations. helpkit.so · Homepagehelpkit.so · Use Case Page
Expectations and limits · 4/4
- Important outcomes that are not guaranteed are clear · Supported: AI accuracy is qualified. helpkit.so · Product Page
- Key prerequisites are clear · Supported: Prerequisites are stated. helpkit.so · Homepagehelpkit.so · Product Page
- Limitations relevant to the central promise are clear · Supported: Block and AI limits are disclosed. helpkit.so · Pricing Pagehelpkit.so · Product Page
- Limitations are reachable before commitment and consistent with the central promise · Supported: Limits are public pre-signup. helpkit.so · Pricing Pagehelpkit.so · Product Pagehelpkit.so · Product Page
Accountability and support · 4/4
- Responsible public entity is identifiable · Supported: Responsible entity is named. helpkit.so · Privacy Policyhelpkit.so · Terms
- Contact channel is accessible · Supported: Contacts are accessible. helpkit.so · Termssupport.helpkit.so · Support Center
- Appropriate problem handling guidance is available · Supported: Support and complaint routes exist. helpkit.so · Termssupport.helpkit.so · Support Center
- No observed identity conflict across website, support and responsible entity · Supported: No identity conflict observed. helpkit.so · Homepagehelpkit.so · Privacy Policyhelpkit.so · Termssupport.helpkit.so · Support Center
User rights and data · 4/4
- Data purpose is explained or public evidence establishes no submission is needed · Supported: Data purposes are described. helpkit.so · Privacy Policy
- Material money, account and content rights are clear · Supported: Rights and terms are described. helpkit.so · Terms
- Applicable exit, deletion or refund process is accessible · Supported: Deletion and cancellation routes exist. helpkit.so · Privacy Policyhelpkit.so · Terms
- Decision path reaches rights explanations consistent with public product rules · Supported: Legal links align with public rules. helpkit.so · Pricing Pagehelpkit.so · Privacy Policyhelpkit.so · Termshelpkit.so · Public Browser Observation
Search discovery
20 conditions assessed
Score evidence
Technical entry points · 4/4
- Homepage and identified decision pages return actual usable content · Supported: Checked pages returned usable public content. helpkit.so · Homepagehelpkit.so · Pricing Pagehelpkit.so · Use Case Pagesupport.helpkit.so · Support Centerhelpkit.so · Http Headershelpkit.so · Product Page
- Checked public pages have no conflicting crawl restrictions or noindex · Supported: No conflicting restrictions observed. helpkit.so · Robots Txthelpkit.so · Http Headershelpkit.so · Html Head Metadata
- Observed protocol and host redirects and canonicals are consistent · Supported: Redirects and self-canonicals are consistent. helpkit.so · Http Headershelpkit.so · Html Head Metadata
- Public navigation and key destinations have no errors blocking access · Supported: Key destinations were reachable. helpkit.so · Homepagehelpkit.so · Pricing Pagehelpkit.so · Use Case Pagesupport.helpkit.so · Support Centerhelpkit.so · Product Pagehelpkit.so · Signup Page
Buyer search intent · 4/4
- Primary entry topic matches the buyer intent fixed before search sampling · Supported: SaaS page matches buyer intent. helpkit.so · Use Case Page
- Actual body content addresses that intent beyond repeating keywords · Supported: Body addresses buyer problems. helpkit.so · Use Case Page
- Page provides decision information or task help required by that intent · Supported: Decision information is provided. helpkit.so · Use Case Pagehelpkit.so · Methodology Article
- Page promise and next step match the intent and actual product deliverable · Supported: CTA matches deliverable. helpkit.so · Use Case Pagehelpkit.so · Signup Page
Buyer question coverage · 4/4
- First predefined important buyer question has a substantive public answer · Supported: Setup answer is substantive. helpkit.so · Homepagehelpkit.so · Use Case Page
- Second predefined important buyer question has a substantive public answer · Supported: MCP answer is substantive. helpkit.so · Product Page
- Third predefined important buyer question has a substantive public answer · Supported: Commitment answer is substantive. helpkit.so · Pricing Pagehelpkit.so · Termshelpkit.so · Public Browser Observation
- All three answers are reachable from relevant public entry points; one page can suffice · Supported: Answers are publicly reachable. helpkit.so · Homepagehelpkit.so · Pricing Pagehelpkit.so · Use Case Pagehelpkit.so · Termshelpkit.so · Product Pagehelpkit.so · Public Browser Observation
Decision information value · 4/4
- Key explanation includes concrete steps, examples or supporting material · Supported: Steps and examples are available. helpkit.so · Use Case Pagehelpkit.so · Product Page
- Comparisons or recommendations explain selection criteria · Supported: Selection criteria are explained. helpkit.so · Comparison Page
- Information explains applicable conditions, limitations or tradeoffs · Supported: Limits and tradeoffs are disclosed. helpkit.so · Pricing Pagehelpkit.so · Product Pagehelpkit.so · Termshelpkit.so · Product Pagehelpkit.so · Public Browser Observation
- Information supports a concrete user decision beyond general promises · Supported: Supports workflow choice. helpkit.so · Comparison Pagehelpkit.so · Product Page
Non-brand discovery samples · 3/4
- Correct website appears in the actual returned sample for the frozen category-selection query · Supported: Website appears in category sample. · WebSearch
- Correct website appears in the actual returned sample for the frozen problem-solving query · Needs improvement: Finite problem sample has no helpkit.so URL. · WebSearch
- Correct website appears in the actual returned sample for the frozen alternatives-comparison query · Supported: Website appears in alternatives sample. · WebSearch
- Correct website appears in the actual returned sample for the frozen purchase-decision query · Supported: Website appears in purchase sample. · WebSearch
AI content readiness
16 conditions assessed
Score evidence
Standalone answers · 4/4
- A predefined core buyer question receives a direct answer · Supported: MCP directly answers drafting and publishing question. helpkit.so · Product Page
- Answer contains concrete information understandable without using the product · Supported: Concrete workflow information is public. helpkit.so · Product Page
- Necessary prerequisites and limitations accompany the answer · Supported: Prerequisites and safeguards accompany answer. helpkit.so · Product Page
- Answer can be read and understood publicly without signing in · Supported: Answer is public. helpkit.so · Product Page
Answer support · 3/4
- Key answer conclusions have locatable specific supporting material · Supported: Claims have locatable setup and guardrails. helpkit.so · Product Page
- Method or steps producing the conclusions are explained · Supported: Steps are explained. helpkit.so · Product Page
- Examples, data or demonstrations match the scope of the conclusions · Supported: Examples match workflow scope. helpkit.so · Product Page
- Source and limits of generalization let readers verify the conclusions beyond promotional assertions · Needs improvement: No independent outcome evidence supports broad productivity generalization. helpkit.so · Product Page
Citation context · 3/4
- Relevant answer passages identify the correct product or subject · Supported: Subject and output are identified. helpkit.so · Product Page
- Key facts are locatable at a public URL and a specific passage · Supported: Facts are locatable at public URL. helpkit.so · Product Page
- Numbers and examples retain units, scope and necessary conditions · Supported: Conditions remain with examples. helpkit.so · Product Page
- Changing product or method facts have relevant dates, versions or current applicability statements; unrelated legal dates do not qualify · Needs improvement: No current applicability statement for changing method facts. helpkit.so · Product Pagehelpkit.so · Changelog
Connected supporting material · 4/4
- Answer identifies the subject and meaning of any supporting material it refers to without requiring private context · Supported: Supporting material is identified in context. helpkit.so · Product Page
- Reader can follow explicit references from answer claims to the material supporting them · Supported: References connect claims and material. support.helpkit.so · Support Centerhelpkit.so · Product Page
- Referenced material is reachable from a relevant public answer or navigation path rather than an isolated page · Supported: Material is publicly linked and navigable. helpkit.so · Homepagesupport.helpkit.so · Support Centerhelpkit.so · Product Page
- Referenced examples, versions and limitations are consistent with the current answer · Supported: Observed examples retain draft, owner, role, and project limits; runtime behavior was not certified. helpkit.so · Product Page
External recognition
12 conditions assessed
Score evidence
Brand identification · 4/4
- Executed exact-domain query finds the correct product · Supported: Exact-domain query found HelpKit. · WebSearch
- Executed brand-plus-category query finds the correct product · Supported: Brand-category query found HelpKit. · WebSearch
- Located external material maps to the product through domain or explicit identity evidence · Supported: External sources identify the exact product. notis.ai · Tutorialdiscuss.logseq.com · Community Post
- Observed namesakes are distinguished and material is not attributed to the wrong entity · Supported: No namesake conflict observed. · WebSearch · WebSearchdiscuss.logseq.com · Community Post
Independent use evidence · 4/4
- At least one source has verifiable independent authorship or relationship evidence, not merely a different domain · Supported: Ramses is a named former Logseq community manager reporting customer-side paid HelpKit use; no HelpKit affiliation or sponsorship is observed. discuss.logseq.com · Community Postdiscuss.logseq.com · Author Profile
- Read source confirms the exact product rather than an ambiguous namesake · Supported: The post explicitly identifies paid HelpKit and Notion as CMS for Logseq’s Community Hub. discuss.logseq.com · Community Post
- Independent source contains specific use observations, results or comparison rather than a link repost · Supported: The author reports a specific use configuration and a migration from the Hub to Ghost, not a bare link or praise. discuss.logseq.com · Community Postdiscuss.logseq.com · Author Profile
- Those observations are traceable to a concrete use context or supporting material rather than unverifiable praise · Supported: The observation is traceable to the Logseq Community Hub context and includes a stated migration caveat; outcomes are not audited. discuss.logseq.com · Community Postdiscuss.logseq.com · Author Profile
Relevant distribution · 3/4
- Product content is observed in at least one public channel relevant to the target buyer · Supported: Notis tutorial reaches a relevant documentation audience. notis.ai · Tutorial
- Content responds to an observable need or question in that channel · Supported: It addresses documentation maintenance need. notis.ai · Tutorial
- Content provides usable information beyond a submitted link · Supported: It provides usable workflow guidance. notis.ai · Tutorial
- Observable relevant responses from people other than the creator discuss the content; likes alone do not qualify · Needs improvement: No non-creator discussion was observed on inspected tutorial. notis.ai · Tutorial
Google Search verification Public signals and owner checks
01
Public scanObservable without account access
Public search sampleVisible in sample
The brand appeared in sampled public search evidence. This is not a complete Google index check.
Sitemap on siteDetected
The sitemap was publicly reachable. This does not prove Google has processed it.
02
Owner-only verificationRequires Google Search Console access
Search Console propertyOwner verification required
A public scan cannot confirm whether a Google Search Console property exists or is verified.
Sitemap processingUnknown until connected
Check Submitted, Last read, Status, and Discovered pages inside Search Console.
Index and search performanceNo owner baseline
Use URL Inspection and Search performance data to verify indexing, queries, clicks, and Google AI visibility when available.
Evidence-backed Growth Preview
No public funnel bottleneck is established; the untested link is whether the SaaS audience recognizes the MCP workflow as a reason to start and can produce a reviewable Notion draft during trial.
A concrete first result can qualify relevant visitors and align trial effort with the repeat-value workflow.
The SaaS CTA reaches signup while MCP provides a specific permissioned first output; extracted signup content does not show outcome-specific onboarding.
- helpkit.so · Use Case Page · owned surface
- helpkit.so · Product Page · owned surface
First move ▸
Add an MCP first-value block and attributed CTA to /for/saas, then measure eligible entrants creating one unpublished draft from a real product change or repeated question.
Complete edition
2 more prioritized findings
See the evidence, fix, and experiment behind every finding.
One payment. Full access to this report.Sample Full Report · free