Set up your client project: brand voice, keyword targets, and past posts
A Juma Project is a shared space where the team keeps everything Juma needs to know about a client. Build one project per client, add context as you go, and every post pulls from the same foundation, so a draft reads the same whether it's run by the content lead or a freelancer covering a busy week. Add these items once and every post, refresh, and cluster the team runs starts on-brand and on-strategy.
What to add
Brand Voice Guide
How the client sounds: tone, vocabulary, sentence rhythm, and the words to avoid. With this in the project, every post comes out in the right voice from the first draft instead of needing a rewrite for tone.
SEO Playbook & Content Style Guide
How the team structures a post: heading rules, how long sections should run, whether posts lead with a Quick-Answer, and how internal links are handled. This shapes the draft so it matches the format an editor already signed off on.
Keyword & Topic Targets
The queries and topics the client wants to own, plus any that are off-limits. Juma checks new post ideas against this list so the team builds toward a plan instead of chasing one-off keywords.
Published Post Library
A list of existing posts or the sitemap. Juma uses it to avoid writing something the client already ranks for, to spot posts worth refreshing, and to map internal links from a new post back into the existing library.
Guide Juma with project info
Add a short description to each knowledge item in the project's info field so Juma knows what each file is and when to use it. For example:
- Brand Voice Guide: "How this client writes. Apply to every post, refresh, and social adaptation."
- SEO Playbook & Content Style Guide: "Our post structure and heading rules. Follow this layout when drafting."
- Keyword & Topic Targets: "Queries the client wants to own. Check new topics against this before choosing one."
- Published Post Library: "Existing posts and sitemap. Use to avoid overlap and to map internal links."
Write a post that AI Overviews can quote
Frequently Asked Questions
How much time does this Flow save compared to writing an SEO post manually?
Writing a research-backed SEO post by hand takes a strong writer most of a working day: keyword research, outlining, drafting, and formatting for search. Juma returns a publish-ready draft in minutes, with the research, structure, and meta fields already done. The team edits and approves before anything publishes.
The time back is real, but the judgment stays with the team. Juma handles the repeatable work, the research pass, the first draft, and the formatting, while the writer decides the angle, sharpens the argument, and signs off. Strategy, taste, and judgment stay human, and there's human review on every output before it goes live.
What does the publish-ready post include?
A finished post runs around 2,000 words as a branded document and includes a Quick-Answer summary, a definitional opening section, core points in scannable bullets, a section mapped to People Also Ask, an FAQ that answers exact search queries, a comparison table, numbered getting-started steps, and the meta title, description, and slug ready for the CMS.
Because Juma researches the audience first, the post targets a real query the client can win rather than a keyword picked in isolation. The team gets a draft that's structured to publish, not an outline to build out. Every draft is a starting point the editor shapes, not a final word.
How does a post win an AI Overview citation?
An AI Overview is the AI-generated answer Google shows above the search results, and it quotes pages that give a clean, self-contained answer. Juma writes each post so the answer is easy to lift: a Quick-Answer block up top, sections that stand on their own, and an FAQ that matches the exact questions people ask.
Post element |
Why it helps win an AI Overview citation |
Quick-Answer summary |
Gives the answer engine a clean 40 to 60 word block it can lift and quote directly. |
Definitional section |
Matches "what is [X]" queries with a direct, self-contained definition near the top. |
FAQ mapped to People Also Ask |
Answers the exact questions AI Overviews pull from, in the phrasing people search. |
Comparison table |
Structured data earns roughly 2.5 times the citation rate of the same facts written in prose. |
Meta title, description, and slug |
Helps the post get indexed and understood for the target query so it's eligible to be cited. |
The Flow explains why each element is there, so the team learns the pattern and can apply it to the next post. It's a repeatable structure, not a one-off trick.
What research does Juma do before it starts writing?
Before drafting, Juma researches the client's site and audience: the queries that audience searches, the People Also Ask questions around the topic, the pages currently winning those results, and the query cluster with the best citation odds. It uses that to choose a topic, not just a keyword.
When Google Search Console or Ahrefs is connected, the research gets sharper. Juma grounds the topic choice in the client's real impressions, positions, and query gaps, so the post targets something the client is genuinely close to winning. Without a connection, it works from public research and the context in the client's project.
Can I use my own brand voice and keyword targets?
Yes. Run the Flow inside the client's Juma Project and every post comes out in that client's voice, against the keyword and topic targets the team has set. One Project per client, and Juma remembers the brand context without re-briefing before each post.
For agencies, that means the whole team works from the same brand voice and target list without paying per seat. Juma's pricing is credit-based with unlimited seats, so an account manager, a writer, and a freelancer can all run the Flow on the same client Project. Add the brand voice guide and keyword targets once, and every post, refresh, and cluster the team runs stays on-brand and on-strategy.