The reader navigates, they do not read

Pillar page content writing services
built as the map a reader crosses once, not the article they sit down with.

Pillar page content writing in Nigeria is judged by a question nothing else on this site is judged by: where does somebody click when they arrive with a question they have never asked you before. Not whether the page is comprehensive, well written or thorough. Whether it puts them one hop from the answer, and whether they leave having found it.

The spokes decided before the hub is written. What no single spoke can hold, and therefore what belongs on the hub. Headings in the reader's words, not the team's. And a click test on somebody with a question you have never been asked.

WHAT THE WORK IS 01 / 04

Every other kind of writing here is read. This one is crossed, and the reader is gone in under a minute.

  • 01 SpokesDecided before writing.
  • 02 GapsWhat no spoke can hold.
  • 03 RoutesOne hop, every time.
Spokes settled first One question per spoke Reader's words in headings Tested by watching a click

The Writely difference

A pillar page is the only kind of writing on this site whose reader is not trying to read it.

A proposal is weighed. A guide is followed. Minutes are scanned for the decision. A newsletter is judged against the last one. Here somebody is crossing, and the only thing that matters is whether they end up where they needed to go.

The reader navigates, and leaves fast

Open this page with one question in mind. Within a minute you are gone, and in most cases you never scroll past the first third. That is not a failure of the writing, it is the page working, because the reader came for an answer and an answer is a link away. Which means the question that matters is not whether the page reads well. It is whether somebody with question X finds the link for X in one hop, or whether they read three sections that are next to what they needed and still leave without it. Comprehensive, well organised and thoroughly written are all secondary here in exactly the way they were secondary on a how-to guide, but for a different reason. You can also explore content analysis writing.

Coverage is the trap, not the goal

By its own definition a pillar page should be comprehensive, so the pull is always towards covering the whole subject. That pull produces the standard failure of this genre: a page that covers everything and therefore answers nothing in particular. A reader with a specific question finds six sections adjacent to it and none of them on it, and concludes the site has not got what they came for. The discipline is a decision about each part of the subject on its own, taken on purpose. Does this get its own page, does it get a section here, or does it get nothing yet. Most published pillar pages never made that decision at all, which is why so many of them read as a long article with links stapled on at the end. You can also explore research paper writing.

The links come before the prose

A pillar page is not an article with links added to it. It is a commitment to build a cluster, and a cluster with a hub and nothing underneath it is a dead end that looks finished. So the honest order is unusual and worth stating plainly: decide what the supporting pages will be, write the hub so it sits underneath them, and only then write a word of prose. Written the usual way round, the result is a comprehensive article from which three sections must later be torn out to become their own pages, or a hub that competes with its own spokes for the same ground. The page is a piece of design that happens to contain text, and treating it as a writing task is the most reliable way to get the structure wrong.

It can be wrong about what it does not contain

A supporting page covers one thing, so it can be right or wrong about that one thing and you will find out. A pillar page is judged on its routing instead, and routing failures are quieter and more expensive. If somebody asking question X cannot find the link for X, every page underneath is starved, because the traffic never arrives to be routed. This is why the genre fails slowly and why it is so often fixed by rewriting when rewriting is not the problem. Nothing about the prose changes the reader's experience of being unable to find the thing they came for, and that is why the useful check is not a reading of the page but a watch of somebody using it.

Find what your pillar page is missing

Eight things this genre has to settle, and most published hubs settle three.

None of these are about writing well. They are about whether a reader with a question finds their route, which is a different problem and a much harder one to check.

Settle what exists underneath, first

Before any drafting, write the list of supporting pages this hub will sit on top of, with the single question each one answers. That list is the real design, and the prose comes after it. A pillar page written before that list exists is a page whose structure you will have to unpick later, and the sections you tear out are usually the ones that were doing the most work. So the first conversation about a pillar page should be about the spokes and not about the hub.

One question per supporting page

The most common fault in a cluster is a supporting page that answers two questions, which means it answers neither well and competes with a page that already covers one of them. If you cannot write the question in a reader's own words in one line, the page is two pages, and the honest move is to split it before writing rather than after. Worth checking against search demand too, since two pages competing for one phrasing is also how a site ends up ranking neither.

The hub holds what no single spoke can

Once the spokes are settled, the hub's job becomes obvious and it is not the one most people give it. It is not the summary of the spokes. It is the material that only makes sense when everything is in view: what the subject is, how the parts relate, what to look at first depending on why somebody arrived, and the decisions somebody has to make before choosing a route. That is genuinely useful and almost nobody writes it, because a comprehensive summary is easier to produce and reads as thorough. A hub made of summaries gives a reader with a question nowhere to go, since every route leads to another summary.

Headings in the reader's words

The navigation a reader actually uses on a crossing page is the headings, and nothing else. So the headings have to be the words a reader would use for their own question, not the words the team uses internally. A heading written as an internal project name is invisible to somebody scanning, because they are not looking for it. This is the single highest-return change available on a page that is not being read, and it takes nothing but the decision to ask what somebody would have typed. Where the team's language and the reader's differ, the reader's wins every time, even when it seems less precise.

Link at first mention, not in a block at the end

There is a standard convention of gathering related links into a block at the foot of the page, and on a pillar page it reliably fails, because a reader with a question is above the fold and moving. The link that works is the one attached to the sentence where the topic first comes up, since that is the moment the reader has decided it is what they came for. So the discipline is that every route is offered where it is first wanted, and a page that relies on a footer block has no routes at all for the reader who actually arrived.

Cut anything the spokes already say

Overlap between a hub and its spokes is common and expensive, because the two pages then compete for the same ground and the reader is offered the same content twice in two places. It also undermines trust, because a reader who lands on a spoke and finds the hub already said it has been sent somewhere rather than answered. What is left should be the material that has no other home, which is usually shorter than seems comfortable.

Watch somebody who has never asked you anything

The check that applies here is not a read-through, because a read-through tests whether you like it, which you will. Give the page to somebody with a real question they have never put to you, do not help them, and watch where they click and what they do next. Four outcomes matter. Whether the right link was visible without scrolling. Whether they went down the wrong route first. Whether they arrived, meaning whether the spoke actually answered what the hub promised. And whether they came back to try another route, which means the routing failed even if the first click was reasonable. Repeat with three people, because the failures are consistent.

What this service cannot do

Four limits, worth stating before the brief. We cannot promise a page will rank, since ranking is not decided by the page alone and nothing in the writing controls it. We cannot build the spokes, so a hub delivered before the supporting pages exist is a hub pointing at nothing. We cannot invent demand for a subject nobody is searching for, which is the commonest reason a cluster should not be built. And we cannot judge a cluster by a single page's numbers, because a hub that works looks unimpressive on its own and only shows what it is doing in the pages underneath it.

A reader who reads your pillar page top to bottom is bad news. It means they could not find their route, and everything underneath them is being starved by the same failure.

A better brief, a better hub

Send us the supporting pages you have, and the questions your customers actually ask. The hub follows from those.

The useful help starts with the spokes rather than with the subject, because the subject is usually agreed and the structure is what is undecided. Given a list of pages and the questions people bring to each one, the job of the hub becomes a matter of routing rather than of coverage, which is a problem that can actually be solved. This service writes pillar pages as maps: spokes settled before drafting, one question to a page, what no single spoke can hold written here, headings in the reader's words, routes offered at first mention, and a click test on somebody who has never asked you a question before.

  • List the pages that will sit underneath this one.
  • Write the one question each page answers.
  • Say what your customers actually ask you.
  • Say what is not getting an answer yet.
  • Name the two routes that matter most.
  • Tell us who could try the page cold.
Share your brief
HUB CHECK Before you publish

Six things before you publish.

Spokes listed, one question each
No paragraph a spoke already covers
Headings in the reader's words
Every route linked where first wanted
Gaps written, not summaries
Cold click test done

How the work is done

From a list of pages nobody has written yet to a hub that routes in one hop.

Spokes, gaps, routes, test. The order is not a preference. A hub drafted before the supporting pages are settled gets written to compete with them, which is the failure this genre is known for.

01 / THE SPOKES

Decide what exists underneath

Write the list before the hub, and for each page one line saying the single question it answers, in the words a reader would use. Where a line needs two questions, that is two pages, and splitting it now takes minutes while splitting it after writing gives the reader a page that answers half of anything. Then check the list against what people are genuinely searching for, because a cluster built around a subject nobody asks about is a lot of work producing nothing. You can also explore research proposal writing.

02 / THE GAPS

Write what no single page can hold

Now look at the list and ask what is left over: the material that only makes sense with the whole subject in view. That is the hub's real content, and it is not a summary of the list. It includes what the subject is, how the parts relate, what to look at first depending on why somebody arrived, and the choices a reader has to make before picking a route. Then go through the draft and delete any paragraph a spoke already covers, because duplication between a hub and its own pages is the commonest fault in this genre and it charges the reader twice. What survives should be shorter than seems right, and every paragraph left should have nowhere else to go. You can also explore case study research design writing.

03 / THE ROUTES

Put each link where it is first wanted

Write the headings in the reader's own words, because on a page people cross rather than read, the headings are the entire navigation and everything else is decoration. Then attach each route to the sentence where its topic first arises, rather than gathering links into a block at the foot, which on this kind of page is reliably never reached by somebody who already knows what they want. Check every route is visible before the fold for the questions that matter most, since the first screen decides whether the reader leaves. And write the link text as the question being answered rather than as a label for the page, because the reader is choosing an answer and not browsing a category. You can also explore essay writing.

04 / THE TEST

Give it to somebody who has never asked you

The last step is the one that answers the only question this genre asks, and almost nobody performs it. Take three people who have never written to you, give each a real question they actually have, and watch without helping. Record which link they went to, whether they had to scroll to see it, whether they arrived, and whether they came back for another route. That record is the whole review and it is more informative than any reading of the draft, because a read-through only tells you whether you like it. Then check the spokes the same way, since a hub that routes correctly into a page that does not answer is a broken route in practice. Fix and repeat once. You can also explore academic editing and proofreading.

What actually gets handed over

Four documents. The hub is the one that goes live, and it is the smallest of the four.

A hub that is longer than the spokes it routes to is usually a hub that has absorbed them. These four are the parts senders never produce, and three of them are not prose at all.

The spoke list

One line per supporting page, each giving the single question that page answers, in the words a reader would use rather than the words the team uses internally. Marked against what already exists and what is planned, so the routes that will carry real traffic on the day the hub goes live are visibly distinct from the ones that are still a publishing plan. It is short, it takes an afternoon, and it is the document that decides everything else, because the hub written before this list exists is a page that has to be unpicked later. It is also how you find out the subject does not support what you were hoping.

The gap note

The material that only makes sense with the whole subject in view and therefore has no other home: what the subject is, how the parts relate, what to look at first depending on why somebody arrived, and the choices a reader makes before choosing a route. This is the actual content of the hub, and it is almost never written, because a summary of the spokes is easier to produce and reads as thorough. The note also records what was left out on purpose and why, which is the only way to tell later whether the hub has quietly become an article again. Short, and usually the hardest paragraph on any of the pages underneath to write.

The hub with its routes

The page itself, with every route attached to the sentence where its topic first arises rather than gathered into a block at the foot, and every heading written in the reader's own words. The second thing it records is what was cut: for each paragraph, which spoke already covers it, if any. That column is what stops the hub and its own pages competing for the same ground, and it is the fastest way to see that a hub has turned into an article, since a page where every paragraph has a destination is a page that has none. Nobody reads the foot of a page they are crossing.

The click record

What three people who had never written to you did when given a real question each. Which link they went to, whether they had to scroll to see it, whether the page they arrived at answered what the hub had promised, and whether they came back for another route. That last entry is the one that matters, because a reader who returns is a routing failure even when the first click was reasonable. It is the only measurement in this genre that tests the thing the genre is for, and a hub shipped without one is a map that has never been walked.

The click record is the part senders skip and the part that measures the only thing this genre is for. Three strangers and twenty minutes tell you more than a month of checking how the page reads.

What a hub has to settle

Six things, and most published hubs settle two.

These are the acceptance criteria, and each can be checked in ten minutes before the page goes live rather than discovered when the pages underneath get no visitors.

  • One question to a supporting page, in the reader's words.
  • No hub paragraph a spoke already covers.
  • Every heading is a phrase a reader would use.
  • Every route linked at first mention, above the fold.
  • What has no other home is written here.
  • Three strangers have tried to use it.
THE HUB Six things

Six things a hub must settle.

One question per spoke
No duplication with spokes
Headings in the reader's words
Routes above the fold
Gaps written, not summarised
Three cold click tests

Explore related academic support

The pages a cluster is actually made of.

A pillar page is not a genre of writing so much as an arrangement of it, and these are the arrangements that hold it together. Everything a hub routes to is one of these, and the quality of the cluster is the quality of the pages underneath it.

Building a hub without spokes? Say so in the brief. A map with nothing underneath it still looks finished from the outside, which is why it is worth saying which of these thirty are already live.

Where the standards come from

Two platform authorities, one working standard, and four people whose subject is structure.

This list is on purpose not eight blog posts agreeing with each other, because agreement is the problem with most published advice on pillar pages rather than the solution. Two of these are the platform authorities, since how a site is organised and how a hub is treated are both settled upstream of anybody's writing. The rest are a working standard, a record of documented practice at a large site, the research on how people behave on a site rather than on a page, and four bodies or writers whose subject is routing. Every resource here was confirmed to answer before it was listed. These external resources are informative references, not Writely service pages.

HOW THE PLATFORM DECIDES

Google Search Central

The documentation that settles what a search system actually rewards, and the most important thing on this list for a reason that is the opposite of the usual one. Its guidance on whether a page is worth existing at all, on the relationship between pages covering the same ground, and on writing something genuinely useful rather than written for the machine are all directly load-bearing here. The material on subtopics and on giving each page one clear purpose is the closest thing published to a working definition of what a supporting page should be, and it is worth reading before the spoke list is written rather than after.

Open resource
WHERE READERS GO AND WHY

Nielsen Norman Group

The source for the click test this page rests on, because it is where the research on how people move through a site rather than reading a page has been done properly for twenty years. Two pieces matter most here. Their work on how visitors judge whether they are in the right place, which is the decision a reader makes in the first seconds and which a pillar page is judged on. And their material on wayfinding, on link placement, and on why a link collected at the foot of a page is a link nobody reaches. That is the evidential backing for putting routes at first mention.

Open resource
THE SUBJECT ITSELF

Ahrefs Blog

The most thorough public working-out of this particular subject, and the one place to go for the mechanics: how to research a subject before building a cluster, how to tell whether a page has earned its own space, and how to read the numbers that show whether a hub is routing or merely existing. Read for the decisions rather than the advice, since the advice is the part everybody already has. Two habits worth stealing: looking at what the pages ranking for a question already cover, so the new one has a reason to exist, and treating a cluster as a set of claims to be covered rather than a list of phrases to be covered.

Open resource
A WORKING STANDARD

Semrush Blog

A second detailed treatment of the same mechanics, and worth having beside the first because where two practitioners doing the same job disagree is where the useful judgement is. Its material on topical authority, on mapping a subject before writing it, and on spotting the page that competes with another page of the same site is the most practically useful part, since overlapping pages are the commonest fault in a cluster and the hardest to see from inside. It also has the clearest published account of the difference between covering a subject and owning it, which is the distinction a hub has to get right.

Open resource
DOCUMENTED PRACTICE AT SCALE

GitHub Documentation

A documentation set organised as a genuine cluster rather than as a set of pages, so it is worth reading for the structure rather than the subject matter, which is software. Two decisions are directly transferable. How a landing page routes a reader to the small number of paths that matter without making them read it first. And how a sprawling reference is split into pages that each answer one question, which is exactly the constraint a supporting page has to satisfy. Also useful is their habit of saying plainly when a page is one of several, so a reader knows which one they are on.

Open resource
WRITING FOR A PUBLICATION

Content Design Toolkit

The closest thing available to a house rulebook for writing on a site that has to work for readers rather than for search, and the useful part is its insistence that every page has one job it can be judged against. Its guidance on naming things, on writing in the reader's vocabulary rather than the organisation's, and on keeping a page to a size a person will actually finish is all directly applicable to a hub, where the temptation to make the page do every job is the whole problem. The material on front-loading the answer is also the reason the two most-wanted routes belong in the first screen rather than in a list at the foot.

Open resource
HOW THE FIELD ACTUALLY REASONS

Search Engine Journal

The trade publication for this subject, and the reason it is on the list is that it reports what practitioners are actually seeing rather than what is supposed to work, which for a genre this dependent on how a system behaves is the more valuable signal. Its coverage of how site structure affects how pages are surfaced, of internal linking practice that has genuinely worked, and of the pattern of hub pages that succeeded and the pattern of those that did not is the closest thing to a record. Read the reporting rather than the advice, since the advice is already repeated everywhere.

Open resource
THE CONSTRAINT EVERY HUB HAS TO MEET

Content Marketing Institute

The body that has surveyed this field for longer than anybody, and the reason it earns a place here is that it is the honest counterweight to everything else on this list. Its research on what audiences actually want from content, on the gap between what organisations publish and what readers look for, and on how much of what gets produced is ever read puts a hard number on the problem this page describes. A hub is a commitment to produce more pages, and the finding that most of what gets produced is not read is the reason the routing test matters more than the writing.

Open resource

Local context, wider reach

Nigeria at the centre. Africa in view.

Writely is rooted in Nigeria and designed for remote academic and business support. Whether you are building a content map for a company, a university, a polytechnic, a college of education, a research institute, a hospital, a non-profit, a church, a campus, a home office, or from another part of Africa or another country entirely, you can work on it here.

Remote-friendly academic support

Pillar page content writing across Nigeria

Explore pillar page content writing for companies, teams and organisations in major Nigerian cities, communities and states. Four things are genuinely different here, and all four belong in the structure rather than in a later revision. Search behaviour is unevenly distributed across the country, so a hub written for one large city and copied unchanged for another is usually routing most of its readers to the wrong first hop. Connectivity shapes what a reader can use, which means a page that depends on a lot of loading before the first link is visible has already lost people who are on a phone. Publishing capacity is uneven too, so a hub promising twenty supporting pages that nobody will write is worse than a hub promising four. And because a hub is a promise about the future of a site, the age of the routes matters more here, and a stale route does more harm.

Lagos Abuja Port Harcourt Kano Ibadan Enugu Benin City Uyo Kaduna Calabar Jos Abeokuta Awka Akure Warri Owerri Zaria Sokoto Bauchi Maiduguri

Nigeria states and the Federal Capital Territory

Writely’s academic support is available remotely across Nigeria, including:

  • Abia
  • Adamawa
  • Akwa Ibom
  • Anambra
  • Bauchi
  • Bayelsa
  • Benue
  • Borno
  • Cross River
  • Delta
  • Ebonyi
  • Edo
  • Ekiti
  • Enugu
  • Gombe
  • Imo
  • Jigawa
  • Kaduna
  • Kano
  • Katsina
  • Kebbi
  • Kogi
  • Kwara
  • Lagos
  • Nasarawa
  • Niger
  • Ogun
  • Ondo
  • Osun
  • Oyo
  • Plateau
  • Rivers
  • Sokoto
  • Taraba
  • Yobe
  • Zamfara
  • Federal Capital Territory

Remote support across Africa

Country-level discovery

Writely welcomes conversations with students, researchers and candidates across Africa, including learners in:

Nigeria Algeria Angola Benin Botswana Burkina Faso Burundi Cabo Verde Cameroon Central African Republic Chad Comoros Côte d’Ivory Democratic Republic of the Congo Djibouti Egypt Equatorial Guinea Eritrea Eswatini Ethiopia Gabon Gambia Ghana Guinea Guinea-Bissau Kenya Lesotho Liberia Libya Madagascar Malawi Mali Mauritania Mauritius Morocco Mozambique Namibia Niger Rwanda São Tomé and Príncipe Senegal Seychelles Sierra Leone Somalia South Africa South Sudan Sudan Tanzania Togo Tunisia Uganda Western Sahara Zambia Zimbabwe

Questions, answered

Start with what you need to move forward.

If your question is not covered here, send the essentials in a chat. A precise brief usually leads to a more useful starting point.

Ask your question
What is pillar page content writing, and what is it not?
It is writing a hub page and deciding what sits underneath it, which is an arrangement task more than a writing task. A pillar page is not a long article and it is not a summary of your other pages. It is the page a reader crosses to reach the right supporting page, and its reader arrives with one question and leaves within a minute. What distinguishes the genre is that the reader is not reading it, so the useful test is not whether it reads well but whether somebody holding question X finds the route to X in a single hop.
How is a pillar page different from a normal article?
An article is read from the top and usually ends with a summary of what was said. A pillar page is crossed and never read through, and it ends with the reader somewhere else. That changes almost every decision about it. Length stops being a virtue, since a longer hub is usually one that has absorbed its own supporting pages. Headings stop being decorative and become the entire navigation. And the links matter more than the paragraphs, because the paragraphs are what a reader skips and the links are what they use. Build an article as though a reader will finish it and you will produce a page that is read by nobody and routes nowhere.
How long should a pillar page be?
Shorter than you expect, and shorter than seems comfortable, because a hub that has outgrown its job has usually started competing with its own supporting pages. There is no useful target number, since what matters is whether every paragraph has somewhere else it could live. Test it that way: for each paragraph ask which supporting page covers it, and cut anything that has an answer. What survives should be the material that only makes sense with the whole subject in view, which is usually between four and eight substantial sections. A hub longer than that is worth checking against the supporting pages rather than trimming.
How many supporting pages should a pillar page have?
As many as the subject genuinely divides into, which is often fewer than people hope. Each supporting page must answer one question that is worth a page of its own, and anything that cannot be written as a single question is either two pages or a paragraph. The practical constraint is publishing capacity rather than the subject. A hub promising twenty supporting pages that nobody will write is worse than a hub promising four, because a route that leads nowhere is worse than a missing route, since the reader was sent there on purpose. Start with four and let the cluster prove itself.
How do you decide which topics get their own page?
Three tests, in order. First, can you write the question that page answers as a single line in the reader's own words? If it needs two lines, it is two pages. Second, do people actually ask it, which is worth checking rather than assuming, since the commonest reason a cluster should not be built is that the subject has no demand behind it. Third, is there anything to say that is not already said somewhere else on the site? That third one catches the overlapping page, which is the commonest fault in a cluster and the hardest to see from inside, because both pages look reasonable on their own.
What should a pillar page contain?
What no single supporting page can hold. That means what the subject is and how the parts relate, what to look at first depending on why somebody arrived, the choices a reader has to make before choosing a route, and the two or three destinations that matter most. It should also state plainly which page answers which question, since that is the navigation itself. What it should not contain is a summary of the supporting pages, because that gives a reader with a question nowhere to go, as every route leads to another summary.
How should internal links work on a pillar page?
Attached to the sentence where each topic first arises, not gathered into a block at the foot. A reader with a question is above the fold and moving, and two hops of scrolling to reach a list of links is enough for the intention to go. Write the link text as the question being answered rather than as a label for the page, because the reader is choosing an answer rather than browsing a category. And check the two or three routes that matter most are visible without scrolling at all, since the first screen is where the reader decides whether they are in the right place.
How do I know if my pillar page is working?
Watch somebody use it with a question they have never asked you, and watch three of them, without helping. Record which link they went to, whether they had to scroll to see it, whether the page they reached answered what the hub had promised, and whether they came back for another route. A reader who comes back is a routing failure even if the first click was reasonable. Then look at whether the pages underneath are getting visits at all, since a hub that routes nobody starves everything below it while looking perfectly healthy on its own. The numbers on the hub itself are close to useless for this.
Is a pillar page the same as a landing page?
No, and they are confused constantly because both are described as a page that exists to send people somewhere. A landing page exists to convert a specific action, and everything on it works towards that one outcome, so it is written for one reader in one situation who has arrived from somewhere specific. A pillar page has no single action and many destinations, and it serves readers arriving with many different questions from many different places. A landing page is read closely and repeatedly. A pillar page is crossed once and never seen again.
How often should a pillar page be updated?
When a route breaks rather than on a schedule, because the failure that matters is a link leading somewhere that no longer answers the question. Set the triggers on the things that change: a supporting page rewritten around a different question, a route removed, a new page published that should be reachable from the hub. The other trigger is the age of the hub itself, since a page written three years ago is usually routing on a structure that has since changed. Keep the two most-wanted routes in the first screen when you do touch it, because that is where the reader makes their decision and it is the part most likely to have drifted.
Can you write the pillar page or do I keep it?
We write it and you own it, though the structural judgement is yours and has to be made first. What we produce is the spoke list with one question per page, the gap note, the hub with its routes, and the click record once somebody has tried it. What we cannot do is decide what your customers actually ask, since that comes from your sales conversations and your search data and not from us. Nor can we promise the page will rank, because that is not settled by the writing. Where the honest finding is that a subject should not have a cluster at all, that is said before drafting.
Where is Writely available, and how do I start?
Writely is based in Nigeria and works remotely with companies, teams and organisations across Nigeria and the rest of Africa. Use the Chat with us button to send the list of pages you already have and the questions your customers actually ask, because the spoke list is written before anything else and everything follows from it. Say which of those pages are already live, since those are the routes that will work on the day the hub goes up. Mark the two destinations that matter most, and tell us if any of your questions are not getting an answer anywhere on the site yet, since those are usually where the useful new page is.

Your next move

Send us your page list and your customers’ questions. We’ll write the hub that routes between them.

Whether you need the spokes settled, the gaps written, the routes placed or the whole thing tested on somebody who has never asked you anything, start a clear conversation with Writely.

Request services