How to Build an SEO Content Plan for a Kenyan Business

A content calendar tells you when something should publish. An SEO content plan tells you why the work deserves a place in the calendar.

Without that distinction, a Kenyan business can publish four articles a month while its most important service page remains vague, two older pages compete for the same search and nobody has time to verify prices or measure enquiries.

A useful plan decides:

• which existing pages to keep, improve or merge;

• which missing pages to create;

• which customer task and business outcome each page supports;

• what must happen before another item can begin;

• who owns the research, writing, review and publication;

• what the team can maintain after publication; and

• which evidence will move an item up, down or out of the queue.

This guide begins with a completed keyword map. If you still have a list of untested ideas, start with How to Do Keyword Research for a Kenyan Business. If you cannot decide whether a term needs a service page, category, product page, comparison or guide, use the search-intent page-selection guide before scheduling it.

A plan needs a queue, not a quota

“Publish every Tuesday” creates a cadence. It does not prove that Tuesday's topic fits the audience, fills a gap or supports a commercial page.

Google's people-first content guidance asks whether a site serves an intended audience and has a primary purpose. It also warns against producing many topics in the hope that some attract search traffic. Your plan should therefore constrain output as much as it schedules it.

• One business may need to repair five service pages before adding a blog.

• Another may already have strong commercial pages but lack guides that answer buying questions.

• A retailer may prioritise category and product data.

• A local professional may need one location page and a complete Business Profile rather than twelve location-swapped articles.

Do not start with an article count. Start with the work the site and customer need.

1) Choose one business outcome for the planning cycle

An SEO plan cannot optimise for “more traffic” in the abstract. Choose one outcome that the business can recognise and support.

Examples include:

• generate qualified quotation requests for a priority service;

• increase discovery of a product category with reliable stock and delivery information;

• reduce repeated pre-sale questions through a pricing or process guide;

• improve non-branded discovery in a market the business genuinely serves; or

• consolidate scattered pages into one clear route for a customer task.

Then write the conversion path:

Search task → page → useful decision → business action

For a Nairobi commercial-cleaning company, the path might read:

Find and assess an office-cleaning provider → Nairobi service page → understand scope, evidence and price factors → request a site visit.

This path exposes weak plans. A checklist article may attract the right industry audience, but it should not outrank the service page when the service page cannot yet explain the offer. A broad “benefits of a clean office” post may not contribute a useful decision at all.

Keep the planning cycle narrow. One primary offer, category or audience gives a small team enough focus to connect pages, evidence and measurement.

2) Set the horizon from capacity, not ambition

A 12-week plan works well for many small teams because it creates room to publish, observe and adjust without pretending that a full year will remain unchanged. The right horizon still depends on your market, resources and review requirements.

List the people and constraints that shape real output:

Count substantial actions rather than “pieces of content.” Updating a core service page, merging three duplicates and implementing redirects may consume more effort than a new guide. A product-category cleanup may require data work, filters and developer review.

If your team can complete one substantial action every two weeks, plan six actions across 12 weeks. Keep a small buffer for corrections, delayed approvals and opportunities from new evidence. Do not fill every day merely because the calendar has empty cells.

3) Convert the keyword map into an action backlog

Bring forward only clusters that passed your keyword and intent checks. Each row needs enough information to support a decision.

Do not write titles yet. A polished headline can make a weak opportunity feel approved before you settle the page's job.

For example, the cluster “office cleaning services Nairobi” might map to an existing service page that needs improvement. “Office cleaning cost Nairobi” might map to a substantial price section or a separate guide, depending on the result set and customer questions. The backlog records that distinction before anyone drafts.

4) Allocate work to existing pages before creating URLs

Search the site inventory for an owner of every task. Check navigation, live articles, service pages, categories, Search Console landing pages and old URLs that no longer appear in menus.

Choose one action:

• Keep: The page already does the job and needs no material change.

• Improve: The correct owner exists but lacks decisive information, evidence or a clear next step.

• Merge: Several pages split one job and would serve readers better together.

• Create: No credible page owns the task.

• Leave: The opportunity lacks fit, evidence, resources or a useful outcome.

This step usually shrinks the publishing calendar. That is progress.

Suppose a company has /office-cleaning/, /commercial-cleaning-nairobi/ and /corporate-office-cleaners/. Do not schedule a fourth page until you compare their purpose, content, links and performance. The right action may involve one stronger service page, selected redirects and improved internal navigation.

Include technical and linking work in the plan. A merge without redirects can lose useful routes. A new guide without a crawlable internal link may remain isolated. A service-page update without a tested enquiry form may improve information while preserving a conversion failure.

5) Put every item through three gates

Use the gates in order. An item that fails one gate does not enter the current schedule.

Eligibility gate: should this work exist?

An item passes when you can answer yes to all four questions:

1. Does it solve a real task for the intended audience?

2. Does it fit an offer, product, purpose or expertise the site can support?

3. Does it have one distinct page owner?

4. Can the team provide the evidence and useful information the page requires?

If the page depends on invented prices, copied competitor claims or expertise the business does not have, move it to Leave or hold it until the evidence exists.

Dependency gate: what must come first?

Place foundational work before support work.

• Fix the core service or category page before publishing several articles that point to it.

• Agree on one canonical owner before writing close variants.

• Collect original product data before optimising product copy.

• Secure expert review before drafting high-stakes financial, legal, medical or safety guidance.

• Build the required template or calculator before promising an interactive tool.

The dependency gate turns a topic list into a sequence.

Capacity gate: can the team finish and maintain it?

Estimate the real work: research, subject review, writing, visuals, technical implementation, publication and later updates.

An eligible page can still wait when the team lacks a reviewer, reliable source or maintenance owner. Moving it to Later protects the standard of current work. It also prevents a backlog from pretending that every idea has equal commitment.

The three gates produce four groups:

• Now: eligible, unblocked and worth current capacity;

• Next: eligible but dependent on a Now item or near-term evidence;

• Later: potentially useful but lower priority, higher effort or less stable;

• Leave: poor fit, duplicate intent or unsupported work.

This framework organises judgement. It does not calculate ranking probability or business value for you.

6) Sequence pages by the decision path

Once items pass the gates, arrange them around the customer's route and the site's architecture.

A practical sequence often follows this order:

1. Fix the destination. Improve the service, product, category or location page closest to the business action.

2. Resolve ownership. Merge or refocus pages that compete for the same task.

3. Answer the blocking question. Create a price, comparison, process or eligibility page that helps someone evaluate the destination.

4. Build earlier-stage support. Add guides, checklists and explainers that serve a distinct task and link naturally to the commercial page.

5. Strengthen proof. Publish approved case studies, original data or examples when the business has real evidence and permission.

Do not force every plan into this exact order. A seasonal deadline, product launch, regulatory change or urgent site error may change the queue. Record the reason when you override the normal dependency path.

Internal links should follow the same logic. A beginner guide can lead to a detailed comparison; the comparison can lead to a category or service page; the commercial page can link back to useful cost or process information. Links help readers continue their decision rather than merely distribute keywords.

7) Build a 12-week plan the team can execute

The following example uses a hypothetical Nairobi commercial-cleaning company. Assume the team can complete one substantial SEO content action every two weeks.

The review in weeks 11–12 does not prove final SEO impact. Search demand, crawling, competitors and ranking systems can change, and some pages need longer observation. The review checks whether the pages work, Google can discover them, the intended queries begin to appear and customers can complete the next step.

If the company lacks credible cost information, the price guide fails the eligibility gate. The team could move the checklist forward or spend the slot collecting pricing inputs. The plan changes because evidence changes.

8) Give every scheduled item a complete brief

A calendar date does not tell a writer what to produce. Attach a brief that preserves the reasoning behind the slot.

At minimum, record:

• primary reader and task;

• approved query cluster;

• page type and canonical URL;

• existing-page action;

• business next step;

• required sections based on the task;

• claims and sources that need verification;

• original evidence, examples or assets available;

• internal links in and out;

• author, subject reviewer and publisher;

• maintenance owner and review trigger; and

• completion criteria.

“Write 1,500 words about office cleaning” does not qualify as a brief. Google explicitly says it has no preferred word count. Scope the page around what the customer needs to finish the task.

Use statuses that reveal the actual bottleneck:

Backlog → Evidence ready → Brief approved → Drafting → Subject review → Editorial review → Ready to publish → Live → Measuring → Refresh due

Do not move an item to Drafting when prices, product details or expert review remain unavailable. Starting early does not remove the dependency; it creates rework.

9) Use Glarify to organise the plan, not approve it

Glarify's content-planning page describes content-gap analysis, keyword-driven planning, competitor analysis, a content calendar and performance tracking. These functions can reduce the manual work of moving ideas between a keyword list, page opportunities and a production queue.

Use Glarify to help:

• collect candidate ideas from search-performance patterns;

• associate keywords with current or planned pages;

• identify possible gaps or overlapping ownership;

• place approved items in a calendar or workflow; and

• revisit performance after publication.

Keep the three gates outside the automation. A suggested topic still needs business fit, a distinct task, credible evidence, an owner and maintenance capacity. A competitor gap may reveal something your business should ignore. A high-impression query may need an existing-page update rather than a new article.

The keyword-research guide covers Glarify's discovery and page-mapping role in more detail. In the content plan, the tool organises approved decisions; it does not make them final.

10) Measure pages against their intended job

Track production without confusing it with performance.

Delivery checks

• Did the planned owner go live at the correct canonical URL?

• Do the image, links, metadata, forms and mobile layout work?

• Did redirects and internal links follow the approved map?

• Can search engines crawl the page, and does the sitemap include the canonical URL?

• Did the team record the publication or material update date?

Google advises site owners to update sitemaps for new URLs and use lastmod for meaningful updates, while noting that sitemaps do not guarantee immediate crawling or indexing. Treat discovery as a check, not a promised deadline.

Search evidence

In Search Console, review:

• queries that surface the page;

• pages shown for the intended query cluster;

• impressions and clicks over comparable periods;

• click-through rate in the context of the query and result; and

• country and device where they change the interpretation.

Google's Performance report guidance recommends focusing more on impression and click trends than position alone. A position number can change without producing a useful visit or business action.

Business evidence

Match the metric to the page:

• service page: qualified enquiries, calls or bookings;

• category or product page: product views, availability interactions, add-to-cart or purchases where tracking and consent support them;

• comparison or pricing guide: movement to a relevant commercial page and assisted enquiries;

• practical guide: completion, download, return visits or progression to the next useful page.

Do not assign revenue to one article merely because a lead visited it. Use your analytics and sales process to define attribution honestly.

Google's Search Console annotations can mark a launch, merge or material update on the performance chart. Keep the note short and exclude personal information. An annotation provides context; it does not prove causation.

11) Replace automatic refreshes with review triggers

Every live page needs a reason and a time to review it.

Use event-based triggers for volatile information:

• a price, fee, tax or product specification changes;

• a law, official process or platform interface changes;

• the business enters or leaves a service area;

• stock, delivery, eligibility or package details change;

• a cited source moves or updates; or

• customers repeatedly ask a question that the page should answer.

Use performance triggers for page ownership and fit:

• an unintended page begins appearing for the target query;

• relevant impressions rise but clicks remain weak;

• the result set shifts towards another page type;

• a page attracts visits but few appropriate actions; or

• several pages split links, queries and internal navigation for one task.

Do not change the date or rewrite paragraphs merely to signal freshness. Google's people-first guidance warns against changing dates when content has not changed substantially and against adding or removing content only to make a site seem fresh.

Stable pages can receive a scheduled editorial review. Volatile pages need a named owner and shorter trigger window. The plan should record who notices the change and who approves the update.

12) Use one table as the source of truth

Your planning sheet, project board or content tool should retain these columns:

Filter the same table into the backlog, 12-week calendar, review queue and measurement view. Avoid separate spreadsheets that disagree about URL ownership or status.

At the end of each cycle, make four decisions:

1. Keep successful pages accurate and connected.

2. Improve pages with a clear task but weak execution.

3. Merge or refocus pages with overlapping ownership.

4. Replace speculative backlog items with opportunities supported by better evidence.

An SEO content plan works when it reduces confusion: fewer unsupported ideas, clearer page owners, realistic commitments and evidence that changes the next decision.

If your inventory has duplicate pages, missing commercial destinations or more ideas than your team can evaluate, request an SEO audit from Amplify SEO. The audit should identify the pages to keep, improve, merge or create before you commit to a longer publishing schedule. You can also review Amplify's current SEO packages when you need ongoing implementation.

Publishing Notes

• Inventory decision: Create /blog/seo-content-plan-kenyan-business; no exact-intent article appeared in the 16-article live sitemap checked on 3 August 2026

• Cannibalisation boundary: /blog/how-to-do-keyword-research owns discovery and keyword mapping; /blog/search-intent-page-type owns page-format selection; this guide owns sequencing, capacity, workflow, measurement and refresh decisions

• Internal-link dependency: Publish or confirm /blog/search-intent-page-type before activating that reader-facing link

• Suggested inbound links: the conclusion of /blog/how-to-do-keyword-research, the relevant planning section of /blog/seo-tips, and the worksheet in /blog/search-intent-page-type

• Primary sources checked on 3 August 2026: Google Search Central, Google Search Console Help, Amplify's live blog inventory and Glarify's public content-planning pages

• Glarify disclosure: Glarify appears as an external product link because its planning workflow fits the topic. This article claims no affiliate relationship, authenticated test, time saving, ranking outcome or traffic result.

• Hypothetical example: The Nairobi commercial-cleaning company, capacity and 12-week sequence illustrate the method. They do not represent documented search volume, rankings, clients, leads or revenue.

• CTA: Amplify SEO audit first; packages as a secondary implementation route

• Featured media: Original AI-assisted topic illustration inside Amplify's deterministic 1536×1024 featured-image template

• AI usage: AI assisted research organisation, drafting and featured-image generation. Final editorial review must verify current sources, links, metadata, image crops, ownership and live rendering before publication.

• Technical follow-up: The blog sitemap emits amplifyseo.lovable.app locations; align it with the canonical amplifyseo.co.ke host. Use /blog/how-to-do-keyword-research as the live canonical slug for the prior guide.