Updated on 20 October 2026.
Semly combines monitoring a brand in AI answers with source analysis and content work. Leon is Semly's agent for analysis and preparing actions. It can help turn an identified issue into material for review, but a recommendation, a draft and a publication are separate stages.
Define the result of each stage
Name the deliverable before requesting work. “Improve visibility” does not specify whether you need a diagnosis, a finished article or an update to a live page. Use this matrix to agree the scope.
| Task | Deliverable | Acceptance condition |
|---|---|---|
| Analyze answers, competitors and sources | A specific need or fact to investigate | Evidence and context support the interpretation |
| Recommend an action | A proposed content or technical change | The change and its destination are clear |
| Generate or revise content | An article, FAQ or other working material | Facts, language and offer accuracy have been checked |
| Publish to the knowledge base | Content in the configured subdomain knowledge base | Publication and the accessible address are confirmed |
| Send to WordPress | A post sent through a connected integration | The correct site, post and status are confirmed |
Availability depends on plan and configuration
Semly's public pricing distinguishes monitoring allowances, content generation and access to Leon. A platform-wide description does not establish that every subscription includes every function. Check the available features and destination before assigning work. CMS connections, permissions and the selected workflow affect which changes can be performed.
What the business still contributes
The business confirms offer facts, service limits and commercial terms. An editor decides whether the material meets a reader need and duplicates an existing page. Some technical solutions need implementation outside Semly, such as DNS or website configuration changes. A prepared instruction does not establish that implementation occurred.
Agree the task before starting
- Identify the public fact or reader need and an existing page if it already covers the subject.
- Specify the deliverable: analysis, proposed revision, draft or authorized publication. Name the approver.
- Choose the correct brand, language and destination. Do not supply confidential client information as article examples.
- Accept the deliverable and check its facts. Confirm publication separately; the existence of a draft is insufficient.
A scoped assignment
Example data: a furniture installer serves a defined area and needs a clearer existing service page. The assignment covers checking its public offer and preparing a revision for the owner's approval. It does not include inventing additional locations or publishing automatically.
Semly and Leon support visibility work. Saving or publishing content does not guarantee that an external AI system will cite it. Integration documentation explains the publishing procedure; this reference defines the deliverable and responsibility.
Judge Leon by the deliverable
“Expand this page” is advice. A replacement paragraph with an identified location is an editorial proposal. A saved article is a draft. An accessible document at its intended destination is a publication. Each is useful, but they require different permissions and should not be grouped into a single promise of automation.
Analysis should support a decision
For an analytical task, ask what needs attention and why. A usable result identifies the reader's problem, the relevant part of the offer or website, and the limits of the evidence. It need not end in a new article. If the answer already exists, clarifying it, resolving contradictory information or checking page access may be more appropriate.
Leon cannot replace the offer owner's knowledge. Compatibility, delivery conditions and service boundaries need confirmation when public documentation is incomplete. The right response is to identify the missing fact and its owner. A plausible completion from an AI assistant is insufficient evidence for a product claim.
Content needs a destination and a purpose
Leon's public description covers formats including articles, FAQs, descriptions and comparisons. This is a product capability description, rather than proof that every connected interface exposes every format. Establish whether the intended output is a new page, a replacement section, or material an editor will use later.
Assess the draft against that purpose. A comparison should explain selection criteria and meaningful trade-offs. An FAQ should resolve a genuine uncertainty. A product description should follow the correct specification. Headings, fluent sentences and repeated keywords do not establish that the reader can make the intended decision.
A refresh needs an explicit replacement boundary
When updating a document, identify what the proposed copy replaces. Without this, an editor receives competing versions and must reconstruct the intended change. Supply the existing page address, the section to improve and any facts or contractual language that must be preserved.
Review the complete proposed version alongside the original. Check the headline and search description as well as the body: an accurate paragraph does not correct a title that still promises an unavailable feature. Preserve historical publication metadata. A visible update note can explain substantive changes without pretending that the original publication is new.
A request an editor can actually accept
Example data prepared only to explain the method: an equipment rental business needs to clarify booking conditions. “Write an SEO article” leaves the audience and outcome undefined. A more useful request is: “Draft a section for the current offer page explaining how an availability confirmation differs from a confirmed booking. Use the public rental terms, flag anything requiring confirmation, and save the result as a draft.”
This creates clear acceptance criteria. The owner can check agreement with the terms, completeness of the explanation and placement on the page. No customer success story or visibility forecast is necessary. The contribution is a resolved customer question supported by verifiable information.
What to check before handing content over
Confirm product facts, source freshness, link destinations and confidentiality. Then check the intended destination, status and connection permissions. Permission to generate is distinct from permission to publish. A working CMS integration is a route for an authorised action, rather than a reason to send every revision live.
If work belongs outside Semly, identify its owner and provide an implementable specification. Store templates, domain configuration and site files can require separate technical work. A recommendation alone does not confirm those changes. Once publication is authorised and completed, inspect the resulting page and address. Saving a draft cannot verify the public presentation.
Keep the division of work visible: the assistant can prepare and check material against accessible sources; a responsible business owner confirms claims about the offer and decides whether the content should be released. Do not label assistant verification as a human expert review.
Related guide on the blog
Semly vs Peec AI: compare the workflow
Check whether the article is already public before saving
Permission to prepare a draft does not authorize changing a live page. In the Semly connection, editing an article already published through Semly changes its public content immediately. Omitting a separate publication request does not keep that revision private.
A short editorial check
- Read the intended article and verify brand, language, URL and status.
- Keep new material as a draft when requested. Obtain authorization for a change to an existing public article.
- Prepare a complete replacement body for an update and preserve the current URL unless its change was agreed.
- Read the saved article again. After a public change, inspect the public page too.
- Check the separate sources panel and metadata. A corrected body does not establish that every page element changed.
Actions depend on the interface and permissions. If the connection does not support unpublishing, redirects or source-panel editing, hand the exact correction to the administrator. Do not mark it as implemented. Sending to WordPress or another CMS is separate from saving in Semly.
