The engagement at a glance
A practical working plan for the first three months. We agree the page scope, responsibilities, and review dates with your team before kickoff, then use a shared scorecard to guide the work.
- Built for
- B2B SaaS and apps
- Planning horizon
- 90-day GEO program
- Focus
- Buyer questions, product evidence, and conversion paths
The starting point
Help the right buyer understand your product.
Buyers need to understand more than a feature list. They want to know which workflows fit, how integrations work, what a plan includes, and when your product is the right choice for their needs.
The program connects those questions to product evidence and a useful next step. For a sales-led SaaS company, that may be a qualified demo. For an app, it may be a trial or an agreed activation event.
The Sementa program
Research, publish, refine. Over 90 days.
Days 1–30
Find the questions that lead to a shortlist.
Start with your buyers, product, and target market. Map the questions people ask when comparing options, review the pages and sources in their answers, and agree on a stable measurement baseline. Product and sales teams help define the next action worth tracking.
The handoff
A question-to-page map, a baseline report, technical priorities, and an approved pilot brief.
The review
Confirm the priority audience, question set, conversion definition, and publishing owners.
Days 31–60
Give each buyer a useful next step.
Develop the agreed comparison, use-case, or feature content with clear decision criteria and approved product evidence. Your product team reviews the facts, your publishing owner releases the pages, and your web team implements the agreed technical recommendations.
The handoff
Reviewed content, a release register, and recommendations connecting useful answers to a trial or demo.
The review
Check each page against its brief, verify the product claims, and test the next action.
Days 61–90
Learn from the work. Set the next priorities.
Repeat the agreed question set and inspect the sources in the answers. Review released pages, correct unresolved questions, and examine observable referral and conversion signals. Use the findings to decide which topics deserve more attention and what needs another review.
The handoff
An updated answer-and-source log, a written progress review, and a prioritized plan for the next period.
The review
Compare like-for-like observations, record tracking limits, and agree the next delivery priorities.
A shared scorecard
Know what shipped. Understand what changed.
Each review connects the delivery record with visibility and business signals. Establish the baseline first, retain the measurement definitions, and record any changes to the question set or tracking setup.
| Measure | Definition | Evidence to retain |
|---|---|---|
| Work delivered | Approved pages, completed recommendations, and published updates. | Briefs, affected URLs, owners, and release dates. |
| AI visibility | Brand mentions and website citations within the agreed question sample. | Question, tool, market, date, answer, and cited sources. |
| Referral traffic | Website sessions with an identifiable AI referrer. | Analytics source, landing page, and observation window. |
| Qualified conversions | Demos, trials, or activation events that meet your agreed criteria. | The event definition, available attribution, and qualification checks. |
AI answers vary between runs. Recognizable referral traffic covers only part of the discovery journey, and product or marketing changes can affect conversion. The review keeps these limits visible so your next decision rests on evidence you can inspect.
