A SaaS vendor stopped its own pages from competing with each other

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

SaaS vendors accumulate content the way code accumulates branches, and this workflow-automation vendor had three publishing teams doing it at once: engineering writes the docs, marketing writes the blog, product marketing writes the landing pages. All three had answered the same how-to questions independently, and Google shuffled three near-identical URLs in and out of results without ever consolidating authority behind one. Inbound links pointed at all three variants; the planned content calendar promised more of the same next quarter.

What it was costing

The vendor's blog, docs, and landing pages had all answered the same how-to questions independently. Google shuffled three near-identical URLs in and out of results, and none consolidated enough authority to hold a position.

What they could see

• Three near-identical URLs rotated in and out of the results for the same how-to queries, none holding a position.
• Writers kept discovering their piece outranked by an internal twin published by another team months earlier.
• The docs and the blog contradicted each other on the same feature's setup steps.
• Inbound links were split across the competing variants, diluting every page's authority at once.

The constraints we worked inside

• Docs belonged to engineering, blog to marketing — neither would accept the other editing their pages.
• Inbound links pointed at all three variants; consolidation had to preserve the equity.
• Product marketing had planned new pages; the plan needed rewriting, not just the pages.

What had been tried before

Marketing added canonical tags pointing blog posts at the matching landing pages.

Engineering's docs were never included, so the third variant kept competing; canonicals also pointed at the weaker page, and Google ignored several of them.

A content audit spreadsheet listed every overlapping page with a recommended action per row.

Without the owners in the room, the actions sat unread; the audit aged out, new overlapping posts shipped anyway, and the spreadsheet became archaeology.

What we proposed

We proposed deciding ownership once, in writing, with both teams in the room: every overlapping query cluster gets a declared home — docs, blog, or landing page — with the others canonicalizing or re-angling. Then equity moves deliberately: redirects and internal links consolidate authority onto the owning page, checked against the backlink profile so nothing with links gets orphaned. Finally the pipeline itself gets rewired — a topic-assignment rule routes new content to its owner before it's written, so cannibalization cannot quietly regenerate next quarter.

Just as important is what we ruled out, and why:

• Merging everything into the docs — Blog and landing pages serve buyers evaluating, docs serve users configuring; one home for all formats would flatten intent and both teams would quietly ignore the ruling.
• Deleting the weaker two of each cluster — Inbound links point at all three variants; deletion orphans that equity. Redirects and re-angling preserve it — removal is the one move that cannot be taken back.
• A committee approval gate for every new article — A review board moves slower than publishing and would be routed around within a month; automatic assignment by question cluster needs no gate at all.

How the work ran

Delivered by the growth pod — SEO strategist over 5 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

Query-cluster mapping

The overlaps were invisible team by team; clustering every URL by question made the triples explicit and gave the ownership conversation a single shared artefact.

Canonical/redirect plan

Equity sat on three variants with real backlinks; the plan moved it deliberately — canonicals where content stays, redirects where it merges — with nothing orphaned.

Internal linking

After ownership is decided, links must point at the owner or clusters re-fragment; the link pass rewired blog, docs, and landing cross-references to match.

Search Console

Free, already verified, and the queries data showed the shuffling happening — then showed consolidation working as positions stabilized instead of rotating.

What went wrong

How we worked together

Cadence

A weekly 30-minute sync with the docs lead and the content lead deliberately in one room; a written ownership log updated after each session.

Client side

The docs lead owned technical pages, the content lead owned the blog, and product marketing owned the calendar that the assignment rule now governs.

Decisions

Ownership calls were made in the joint session and recorded same-day; any tie neither team would concede went to the VP of product with a recommendation.

They provided

Search Console access, publishing access on both the docs and blog systems, the product marketing calendar, and both leads' weekly hour.

What changed

The headline: primary how-to terms held in top-3 positions, 10 weeks after consolidation — 31 → 47, read from Rank tracking. A second check: new overlapping pages published under the assignment rule at 0.

Writers check the owner map before drafting now — the triple-publishing habit is broken at the source, which is the only place it could be broken. Pages hold positions instead of rotating, the contradiction between docs and blog is closing as clusters consolidate, and the two teams meet monthly about topics rather than turf. Product marketing's calendar got shorter and more honest the same week the rule shipped.

The result was read from Rank tracking against the pre-engagement baseline over the stated window, with a guardrail check on new overlapping pages published under the assignment rule. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The ownership map binding each query cluster to its owning page
• The topic-assignment rule as a one-page decision doc
• The redirect and canonical plan file with its backlink checks
• A Search Console monitoring view for the consolidated clusters
• The decision-doc template for resolving future ownership ties