
To add an ingredient checker to your esthetics website, choose a page, decide between free self-hosted ChekIt Core and a hosted plan, and have your website person connect the checker. Add a clear consultation or contact link, then test input, matching, results, next steps and errors on a phone and desktop. The free software still needs hosting and someone responsible for updates.
A client spots a moisturizer online and wants to know whether it fits their routine. A checker on your studio website gives them somewhere to start, with a clear route back to you when they need help.
To add an ingredient checker to your website, choose where it will live, pick a self-hosted or hosted setup, and have your website person connect and test it. You do not need to rebuild your whole site or switch booking systems.
ChekIt offers free Core software you can run with technical help, plus hosted plans for studios that want hosting handled. This guide walks through the setup decisions and gives you a brief to hand to whoever manages your website.
If you are still deciding what a checker does, start with our pore-clogging ingredient checker guide. Here, we will focus on getting the website experience ready for clients.
Start with a dedicated page rather than squeezing a form into an already crowded homepage. "Check your products" is a useful page name. Put a short explanation above the input field so visitors know to paste the full ingredient list.
A simple page needs:
Ask clients to use a current ingredient list from the packaging or manufacturer. The tool cannot correct a formula copied from an outdated product page.
You can keep your existing website and booking software. If you are weighing a broader software change, our standalone-versus-bundled guide covers that separately.
Choose Core when you want control and have technical helpChekIt Core is the free source project behind a small ingredient-matching service. Its public repository includes ingredient data, synonym matching, a website connection example, and deployment instructions.
That transparency is useful: your developer can inspect the data and matching behavior rather than guess what a result means.
Core is not the same purchase as a hosted subscription. Someone still needs to deploy it, connect the website experience, and maintain that setup. Server costs and installation help can cost money even when the software is free. Review the repository's license before modifying or deploying it.
Next step: Read the free Core setup guide, then give the launch brief below to whoever handles your website.
Hosted plans are for operators who prefer a managed setup. The current pricing page starts with Starter at $49/month. Professional and Business list additional features and different usage limits.
Choose from the features you actually need. The pricing page places image scans in Professional and Business, and Shopify integration in Business. Do not assume those are included in the free Core project or every paid tier.
Next step: Compare the current hosted plans. If your website setup needs clarification, ask us about it before choosing a plan.
For ChekIt Core, the website form and the ingredient-matching service need to be connected. Giving someone the repository link is the start, not the finished installation.
Ask your developer to:
The repository includes a documented test list: Water, Cocos Nucifera, Isopropyl Myristate. Its expected matches include "Cocos Nucifera" through the "Coconut Oil" synonym and "Isopropyl Myristate" through "Myristate". Your developer can use that example to check the connection before trying your own labels.
For a hosted plan, confirm the installation instructions for your website platform and account with ChekIt. Have your website person check where the tool will appear and whether your site permits the required custom code. Confirm the plan includes the features you need before paying for it.
The exact clicks depend on your website platform and editor permissions. Use the current Core setup guide or ask about your hosted setup; this article is the owner checklist, not a universal paste-in code snippet.
Put a consultation or contact link beside the results. "Want help reviewing your routine? Book a consultation" tells visitors what they can do next.
Keep the explanation short. For example:
"Here is what the checker found in the ingredient list. If you want help reviewing it alongside your routine, book a consultation with us."
Ingredient matching can identify concerns worth discussing. It cannot guarantee how a finished product will affect an individual client's skin. State that once in plain language; do not turn the whole page into a disclaimer.
For the fuller conversation after someone books, read how acne-focused estheticians can use ingredient checkers.
Use real product labels. Start with one list containing a name you know is in the tool's database, one documented synonym, and one label that is hard to format. This is an installation check, not a clinical validation study.
Record anything that fails before adding the checker to your main navigation. If a request fails, the page should stop loading, explain the problem, and give the visitor a way to try again or contact you.
For a self-hosted setup, name the person responsible for hosting, service availability and ingredient-data updates. Ask what happens when that person is unavailable. Free software still needs an owner.
For a hosted setup, check your support route and usage limits. Keep a few representative labels so you can repeat the launch tests after a website or data update.
If a name seems missing, check the current label and spelling first. Then report the exact wording through the project's contribution route or your hosted support channel.
That brief also works if you are evaluating another checker. The point is to get a tool your studio can actually use.
The Core software is free. Hosting, installation help, and ongoing technical work may have separate costs. The free setup page links to the public repository and instructions.
No. The public Core project documents ingredient matching and synonym handling. Hosted plans list additional features by tier. Check the current plan details rather than assuming Core includes image scanning or Shopify integration.
Yes, but choose the setup route first. Core needs a deployed service and a connection to your website. For hosted ChekIt, confirm the installation requirements for your platform and chosen plan.
The page should explain that no matching flagged ingredients were found in the submitted list. It should not promise that the product cannot cause a reaction or a breakout. Keep a clear next step for clients who want your guidance.
Check the current label and the spelling first. For Core, the public repository and free setup page invite reports of missing names or synonyms. Include the exact ingredient wording when you report it.
Ready to choose? Get free ChekIt Core if you have technical help, or compare hosted plans if you want hosting handled.
