Audit your content library against real search performance data. Get page-by-page scoring, quick wins with rewritten titles, cannibalization checks, and a prioritized 90-day action plan.
Point Juma at a website with Google Search Console connected. You get back a PDF with the strategic overview and an Excel tracker with every page scored, the top rewrites ready to implement, and a 90-day plan sorted by estimated traffic impact.
The team starts with a full picture of which pages are earning their keep and which ones aren't. Every page on the site gets sorted into one of five buckets: quick wins that are close to performing (ranking on page 1-2 but underclicking), rewrite candidates stuck on page 2-3 with enough search volume to justify the effort, pages to protect, archive candidates, and healthy pages to leave alone.
For the top 10-15 pages by opportunity size, the analysis goes deeper: the actual page gets scraped alongside the top-ranking competitors, the SERP gets checked for features like AI Overviews and featured snippets, and each recommendation comes with a rewritten title and meta description with character counts. A page with 1.3 million impressions and a 0.14% CTR gets a different kind of attention than a page with 200 impressions and no clicks.
Most SEO audits check pages against a best-practice checklist: title length, meta description present, heading structure. That approach treats every page equally. When the audit starts from actual search performance data, the priorities shift. A page with 1.3 million impressions and a 0.14% CTR is a different problem than a page with 200 impressions and no clicks. The first needs a better title tag. The second might not be worth fixing at all. Starting from search data means the team works on the pages that will actually move the numbers.
Multiple pages sometimes compete for the same keywords without the team realizing it. This prompt checks the full content library for overlap and recommends which pages to merge, redirect, or differentiate.
Check if any of our client's pages are cannibalizing each other. For any overlapping pages, tell us which one to keep, which to redirect, and what anchor text to use for internal links.
The audit flagged a page worth investigating. This prompt runs a deep single-page diagnosis with competitor scraping, SERP feature analysis, and a specific fix plan.
Diagnose why our client's page at [URL] is underperforming. Compare it against the top-ranking competitors for its main keywords and tell us exactly what to change.
The audit found topics competitors cover that the client does not. This prompt takes those gaps and turns them into a prioritized content plan with keyword targets, content type recommendations, and a publishing sequence.
Take the content gaps from the audit and build a quarterly content plan. Prioritize by keyword difficulty and business relevance, and recommend a content type for each topic (blog post, landing page, comparison page, or guide).
A Juma Project is a shared space where the team stores everything Juma needs to know about a client. Create one project per client, add context as you go, and Juma will use what's relevant every time the team runs a flow. If the project already exists from other work, just add the SEO-specific items below.
Target Keywords
The keywords the client cares about most: branded terms, product terms, category terms. With this in the project, every audit compares performance against the keywords that matter to the business, not just whatever has the most impressions.
Competitor URLs
The 3-5 domains the client competes with in search. Juma uses these to pull competitive keyword data and benchmark the client's content against the right landscape instead of generic industry averages.
Past Audit Results
The most recent SEO audit, content inventory, or performance report. When running a follow-up audit, Juma compares against the previous baseline and flags what improved, what declined, and what is new since the last review.
Business Goals
What the client is trying to achieve with organic search: lead generation, product signups, brand awareness, e-commerce revenue. This shapes how Juma prioritizes recommendations. A page driving demo requests matters differently than a page driving blog reads.
Add a short description in the project's info field that tells Juma what each file contains and when to use it. For example: "Target Keywords: priority keyword list from Q1 2026 planning. Competitor URLs: top 5 organic competitors identified during onboarding. Past Audit: March 2026 full content audit, use as baseline for comparison." This helps Juma pick the right files for the right task without guessing.
