Skip to content

Does every customer question need its own page?

Similar questions may describe the same task. Check each page’s distinct value before turning them into separate articles.

Anna Neumann2 min read
Document pocket holding two overlapping sheets with gray content bars and a magenta tab.

Examine the task behind the wording

“Connecting CRM and ERP” and “Exchanging customer data between CRM and ERP” may create different expectations. They may also be two entry points into the same decision. Titles alone do not settle that. Read the contents and name the concrete task the reader can perform afterward.

Google puts usefulness for the intended audience at the centre of helpful content. That does not establish a fixed number of permitted pages per topic. Our editorial recommendation is that an additional page needs a recognizable contribution of its own.

Example: combine repetition, preserve substance

This inventory is entirely fictional. Both texts address the same project team and should help it define responsibility for customer data before integration.

Draft

Contents

Decision

A: Connecting CRM and ERP

General explanation of data exchange, followed by a field list without owners.

Bring the repeated explanation into a shared introduction. Complete the field list.

B: Exchanging customer data between CRM and ERP

Same introduction, plus a worked field-ownership example.

Remove the duplicate introduction and keep the concrete example.

The combined article could be called “Connecting CRM and ERP: defining data responsibility”. It contains a completed mapping of field, authoritative system and permitted change, plus a decision for conflicts. The team then need not piece the answer together from two nearly identical introductions.

One possible completed mapping for this example:

Field

Authoritative system

Permitted change

Contact person

CRM

Maintain in CRM; ERP receives the approved state.

Billing address

ERP

Maintain in ERP; CRM displays the approved state.

In this example, a differing billing address from CRM becomes a case for clarification and does not automatically overwrite the ERP state.

The example does not prescribe which system must generally own which customer data.

When a separate page remains useful

A guide to handling existing duplicates may solve a different task: identify, review and merge records in a controlled way. If it has enough distinct substance for that, a linked detailed guide makes sense. A reworded title with the same answer provides a weaker reason.

For existing pages, examine entry points and internal links before merging. Preserve useful sections and make appropriate decisions about old URLs. Complete language translations are a different case from repeated content within one language. Fewer pages are not an end in themselves or a guarantee of better search positions.

Sources

Written by

  • Anna NeumannEditor for Content and Digital MarketingAnna Neumann plans and writes content on digital marketing at ASES. Her topics include search engine optimisation, content strategy and web analytics, with a focus on evaluating marketing activities and their results in a transparent way.

Follow ASES

Read more

All articles

Online Marketing with ASES

SEO, GEO, ads and analytics