SEO automation, from proposal to completed work.

Choose whether the initial focus is Google visibility, being mentioned in AI answers, investigating competitors or a balanced approach. The Growth Engine weighs that focus alongside your services, customers and existing website. Your priority is context for the work, not permission to make every possible change.

The recurring cycle is to observe, choose, do and measure. Research runs on its own schedule; your plan determines the rhythm of suitable completed website improvements. A new page is not automatically the best answer.

An instruction such as “improve your homepage” leaves the difficult work with you. A prepared proposal should identify the page and issue, show the existing and proposed content, explain the reason and state who can implement it.

1. Understand the reason

Read the customer question, relevant finding, source and period. An average position or a saved focus keyword is context; it does not by itself prove which edit will help.

2. Review the proposal

Compare current and proposed text and its intended placement. Keep what is already useful. New content needs a distinct purpose rather than repeating the page.

3. Choose the changes

Select the changes you want. For a supported edit, review any required approval. Otherwise prepare a complete developer brief.

4. Follow implementation

Saved, sent, implemented and confirmed live remain distinct. You can return to saved work and its status. No website change is implied merely by saving a proposal.

A large search volume does not make a question valuable to every business. Klusio considers the customer need, relevance to your offer, existing coverage and whether a useful change can actually be made. The selected proposal should explain why it comes first.

The following invented accountancy example illustrates that comparison. The numbers are illustrative priority scores, not percentages, search volumes or predicted conversion rates.

First check whether the question is already answered on the website. Then look for a genuinely different angle or a specific weakness in an existing explanation. Finally check whether there is enough relevant business knowledge to produce a useful answer.

The result can be a new page, an existing-page improvement, a prepared external-mention request or a LinkedIn draft. If the existing content already answers the question well, leaving it alone can be the right decision. Technical or unsupported work needs a clear task for the person who can carry it out.

The decision uses the evidence available for your connected account. Missing measurement is not treated as proof that something is absent or performing badly.

Google

Search Console impressions, clicks and queries, tracked positions and, when connected and permitted, relevant Ads data.

AI answers

Your selected customer questions, dated platform responses, brand mentions and cited sources.

Competitors

The competitors you have chosen, their visible coverage and relevant gaps. A competitor’s decline does not guarantee your rise.

Your existing content

The current page text, recent work, overlapping topics and internal links. Existing relevant pages can be strengthened instead of creating competing pages.

Reviews and external mentions

Available customer evidence, reviews and places where your business is mentioned, within the relevant permissions.

Your knowledge and priorities

Services, working area, approved claims, product facts and practical experience. Business relevance comes before producing another article.

The route depends on your CMS, permissions and the actual page structure. Connecting a website does not make every element editable.

Through your website connection

Klusio reads the supported content and prepares the change. After any required approval, it applies the selected change and checks the result. Elementor and Bricks editing is a beta route with an additional plugin and compatibility checks. Shared templates and unsupported widgets need separate handling.

Through your web developer

Create a PDF brief containing the selected changes, current and new text, exact placement, rationale and checks. Saving it does not send it. Agree implementation, publication and any developer costs separately.

Keep recent manual work

Compare the current live version before applying an earlier proposal. A change made by your developer since the analysis must not be silently overwritten.

• Check the supported integrations →

Mark work as completed once it has been carried out. The live check and later impact measurements have their own status. Reopen a completed task if more work is needed.

Return to the saved brief

Follow the saved brief and associated work instead of generating a replacement. It records what was requested and what still needs checking.

Undo completion

Removing a completion tick reopens the task. It does not reverse the content on your website. Restoring website text is a separate action requiring a supported restore route and a suitable backup.

Measure after implementation

Follow the affected URL and available search measurements from the implementation date. Changes in impressions, clicks or AI mentions are observations; other changes and seasonality may also contribute.

A useful next step may concern the business information people find elsewhere. Each destination has its own connection, permissions and approval rules.

External mentions

Klusio can research a relevant publication and draft an approach. You review and send it. Placement or a backlink cannot be promised.

Customer reviews

Use relevant, attributable reviews to support the subject being discussed. A review must not be stretched into proof of an unrelated technical claim.

LinkedIn

LinkedIn Basic prepares article-related drafts. Porthos is a separate LinkedIn planning and publishing workflow with its own scope. Approval and connection settings still apply.

Google Business Profile

Connected profile work can include posts derived from published content, subject to permissions and configured publication limits. A draft is kept separate from a published post.

• Explore mentions and supporting evidence →
• Use reviews and project experience →
• Explore SEO and AI visibility features →
• Explore deeper market research with AMI →

Illustrative example: an employer asks an AI assistant for a sales-recruitment agency. AMI shows which agency is named and which customer case is cited. Your team can then investigate whether your own service page explains the selection process and relevant experience clearly enough.

AMI is a separate module. With an active, connected Growth Engine, a suitable AMI finding can be weighed alongside other work. Execution still depends on your settings, business knowledge, quality checks and website connection.

Follow a relevant question

Choose a question that matches the service and audience you want to reach.

Read the answer and source

Inspect what was actually said and whether the source reveals a meaningful gap.

Choose a suitable improvement

Review a brief or supported execution proposal, then measure again later. A finding is not itself an instruction to publish.

• Explore AMI separately →
• From an AI observation to a next step →

Klusio can ask a focused question through WhatsApp when practical knowledge would improve an article. Reply by typing or voice, or skip a question. Available approved knowledge can be reused where it is relevant; missing facts must not be invented.

A small, relevant question

For example, an accountant might be asked which document clients most often forget before a quarterly VAT return. This is an illustrative topic, not a claim about your customers.

A chance to correct the text

You can review how your answer is used and correct it. A question for general company knowledge must be distinguished from a question about a specific article.

A bounded conversation

The workflow limits proactive knowledge questions to at most four per working week. The number depends on what is needed; you do not have to supply a new story for every action.

You can type an answer or send a voice message between appointments. Klusio can show the paragraph it derives from your answer so you can correct the meaning. Relevant approved knowledge can support later articles too; it should not be copied indiscriminately into every subject.

Illustrative conversation with a bicycle retailer—not a real customer testimonial or a technical diagnosis:

Klusio asks

“I’m preparing an article about replacing an e-bike battery. What change do customers most often notice first? You can send a voice message.”

The retailer replies

“In winter, some customers can no longer complete their usual route. We check the battery, but also the temperature, settings and other possible causes.”

Klusio proposes a paragraph

“If your usual route suddenly feels out of reach in winter, have the bike and battery checked. In our shop we consider battery condition alongside temperature, settings and other possible causes.”

The retailer checks it

Confirm that the paragraph reflects your actual experience, or explain what needs changing before the text is used.

The conversation also gives you a way to ask about the available figures or share a topic from your working day. The assistant should distinguish measured data from a planned action and should ask for clarification when a necessary detail is missing.

Illustrative examples: you ask which pages received more Google clicks in the latest complete period, or mention that several clients asked about a late VAT return. A useful answer identifies the measurement period or checks whether an existing article already covers the question. Sharing an idea is not a promise that a new article will be live the following day.

Illustrative example for an accountancy firm using Groei Pro. The sequence depends on the evidence, permissions and preparation. It is not a promise that every account follows these exact days.

Monday: review the evidence

Klusio compares available search questions and existing pages. This research does not itself count as a website improvement.

Tuesday: select the next step

An existing explanation may need a concrete example, or a distinct question may warrant an article.

Wednesday: add practical knowledge

The firm answers a short question if the existing knowledge is insufficient.

Thursday: implement supported work

Content proceeds within the chosen approval workflow and website connection. A prepared draft is not counted as confirmed publication.

Friday: prepare relevant follow-up

An external-mention draft or a later measurement can inform the next step. Preparing an outreach draft is separate from the plan’s website-improvement rhythm.

The recordings below demonstrate the Dutch account. Use the English explanation above to follow the purpose of each screen, or ask Sicco to show your intended workflow in an English demo.

A saved draft or a publication request does not count as a confirmed live page. Klusio checks the resulting URL and expected content where the connection supports it. Later follow-ups can use 14-, 30-, 60- and 90-day windows, depending on the action and available data.

Follow impressions, clicks and relevant AI mentions separately, with their source and period. Search data can arrive late and visibility can change for other reasons too. The available evidence informs the next choice; it does not establish that one edit alone caused the difference.

• Read how results are measured →

Choose a working mode during setup and change it when your needs change. External or major actions keep their own safeguards. Your settings do not authorise arbitrary changes to third-party websites.

Let supported routine work proceed

Klusio works within the agreed settings and you review what happened afterwards.

Ask before major steps

Routine work continues, while actions such as merging, deleting or contacting an outside party require the appropriate decision.

Review each proposed website change

Use prior approval when you want to read the proposal before publication, including while getting familiar with the workflow.

• See the responsibilities during setup →

All three approaches can be suitable. Compare responsibilities, evidence and the work you retain. An agency’s service depends on its contract; the table describes questions to discuss rather than claiming every agency operates the same way.

These cases cover different businesses and measurement periods. Read the full case before comparing figures. Google clicks are not unique visitors, AI mentions are not enquiries, and a historical position is not a permanent ranking.

Hagman: customer questions about carpentry and maintenance

The case records +364% Google impressions in March–May 2026 compared with the preceding period (Google Search Console). Klusio prepared explanations around the relevant questions and followed the results.

Ebbers: appearances in measured AI answers

48 mentions were recorded in the first 90 days of the case’s tracked AI measurements. The count describes that question set and period, not all answers on those platforms.

NieuwHuis: questions about buying and selling in Almere

NieuwHuis recorded 455 Google clicks from 5 July 2026 to 2 October 2026, compared with 136 in the period 5 July 2025 to 2 October 2025 (Google Search Console). One article about when to use a buying agent recorded 26 clicks in the current period. These are clicks, not a count of new customers or a guaranteed result. The older January–April 2026 case also recorded a first-place Google observation for “makelaar Almere Duin”; it is historical, not a claim about today’s position.

Prak: questions about moisture, pointing and costs

1,068 Google clicks went to Klusio articles from 5 July to 2 October 2026. The whole website recorded 1,487 clicks versus 273 in the same period of 2025 (Google Search Console). The content and measurements belong to the business’s own website.

• Read Hagman’s case →
• Read Ebbers’s case →
• Read NieuwHuis’s case →
• Read Prak’s case →

Groei Start has one website improvement per week, Groei Pro two per week, and Groei Marktleider one each working day. Klusio Partner adds personal direction to the Marktleider rhythm. The chosen work may be new content, an existing-page improvement or a corrected issue. Access, required approval and sufficient knowledge remain necessary.

• Compare plans, limits and guidance →

An accessible website, real customer questions and reliable business knowledge are the starting point. A business with no relevant search demand, a very large product catalogue requiring bespoke work or an expectation of guaranteed results within two weeks needs a specific discussion before starting.

A good starting point

You have a website that may be updated through a supported connection, customers who research your work online, and someone willing to provide practical knowledge. You want a sustainable rhythm of useful changes.

Discuss the limitations first

You cannot grant website access, most work arrives through closed tenders or fixed relationships, or you need bespoke optimisation of thousands of products. A fixed result within two weeks is not promised.

• Discuss the fit for your website →
• Read measured customer examples →

The growth guarantee is available only on Groei Marktleider and Klusio Partner with Klusio running fully on autopilot. It does not apply to Groei Start, Groei Pro, self-managed execution or a workflow requiring approval before publication.

Day one is the date of the first successful Klusio publication on your website. We compare 30 complete days with the 30 days immediately before day one, using organic impressions and clicks in Google Search Console. If neither figure is higher and the conditions are met, the subscription fee for the first paid month is refundable. The final assessment normally follows within 3 days of the measurement window because Google reports with a delay. This is not a guarantee of rankings, indexing, AI mentions, enquiries or revenue.

• Read the full growth-guarantee conditions →