Turning a Long Page Into Three

The signals

• Sections answer different questions.
• Different readers want different sections.
• People arrive searching several distinct things.
• The page ranks for one section only.
• You link to it and then say which part to read.

The last is the plainest test. If you regularly send somebody a link and add a sentence telling them which section to look at, the page is doing more than one job.

The search evidence

The most useful signal and the one nobody checks.

Your search reporting shows the queries that led people to each page, and a page that should be split usually shows several unrelated ones.

Where a page receives traffic for what something costs, how long it lasts, and how to fix a specific fault, those are three readers who each want a third of the page.

It is also likely ranking well for one of them and poorly for the others, because the page is only partly about each.

Splitting gives each query a page that is entirely about it, which is what allows the weaker two to compete at all.

Look at the query list before deciding, since sometimes a long page is genuinely about one thing and simply long.

Length alone is not a reason

Worth stating, since the instinct is to split anything that feels big.

A two thousand word page answering one question thoroughly is a good page, and cutting it into three makes three worse ones.

The test is not length, it is whether the sections serve different intentions.

A page with a clear single subject, read start to finish by somebody with one question, should stay whole regardless of size.

Splitting that page produces three pages each too thin to be authoritative and a reader who has to visit all three.

Which page keeps the address

The mechanical decision that matters most, since the existing address carries whatever standing the page has.

Keep the strongest section on the original address, meaning the one with the most traffic and the best position.

Give the other sections new addresses, and link to them prominently from the original.

Do not create three new pages and redirect the old address to a hub, which discards the position the original held.

Where the sections are genuinely equal, keep whichever matches the page title, since that is what the address is known for.

Record the traffic and positions before doing any of it, so you can tell afterwards whether it worked.

A worked example

A page titled everything you need to know about a particular service ran to about two thousand four hundred words.

It covered what the service is, what it costs, how to tell whether you need it, and how to maintain the result afterwards.

The search reporting showed four distinct groups of queries, and the page ranked well only for the cost ones.

They kept the cost material on the original address, retitled the page accordingly, and created three new pages for the others.

Each new page was expanded, since it no longer had to share space, and each linked back to the others.

Within four months two of the three new pages were ranking for their own queries, and the original held its position.

Each page has to stand alone

The writing consequence, and the part done badly most often.

Somebody arriving on the maintenance page has not read the cost page, so a sentence beginning as we discussed above makes no sense.

Each page needs its own brief opening establishing the context, even where that repeats a sentence or two from a sibling.

That small repetition is not a problem and it is what makes each page usable on its own.

What should not be repeated is a whole section, which is the failure that turns a split into duplication.

Where two pages want the same substantial block, that block is a fourth page they both link to.

Link them properly

Since a split without linking loses the reader who wanted more than one part.

Put a short line at the foot of each pointing to the siblings, naming what each covers rather than saying related pages.

Link from within the text where a reader would naturally want the other page, which is more useful than a block at the bottom.

Update anything on the site that linked to the original page, since some of those links were pointing at a section that has moved.

And check the navigation, since a page that was one menu item may now need to be a section with three under it.

Do not split preemptively

A caution about sequencing.

Splitting a page before there is enough material for each part produces three thin pages, which is worse than one adequate one.

The right order is to write the page, let it accumulate, watch what people search for, and split when the evidence appears.

A new page should almost always start as one page, since you do not yet know which sections will matter.

Splitting is a response to a page succeeding, not a way of making one succeed.

The counter-case

Splitting has real costs.

Three pages need maintaining where one did, and a business that struggles to keep one current will keep three less well.

A reader wanting the whole subject now has to visit three pages, which is worse for them than scrolling.

And a split done carelessly, with the original address redirected to a hub, can lose more than it gains.

Split when the sections serve different readers, keep the strongest on the original address, and leave a long single-subject page alone.

What to do

1. Check the queries the page receives.
2. Ask whether sections serve different readers.
3. Ignore length as a reason on its own.
4. Record traffic and positions first.
5. Keep the strongest section on the original address.
6. Give each page its own opening.
7. Link them by name, not as related pages.

Step five is the one with a lasting cost when got wrong, since redirecting a page that ranks well to a new hub discards years of accumulated standing.

Structuring services from the start is covered in one page per thing you sell.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.