A Google Search Console performance report exposed an awkward pattern: five B2B copywriting service pages kept trading positions for the same query. During routine monitoring, they moved between positions 20 and 30. The agency had created narrow pages to capture niche demand, yet those pages were competing for the same searcher. The response was to consolidate overlapping services into unified hubs, then give search engines and prospective clients a clearer route through the site.
Five B2B Copywriting URLs in One Search Console Query
The useful detail in the Search Console report was the repeated URL swap. A page would appear for the broad B2B copywriting query, lose its place to another service page, and return later. None established a stable position beyond page three during the observed period. That pattern suggested the site had several plausible answers to the query and no clearly preferred destination.
Each service page had a reasonable premise in isolation. A buyer looking for SaaS copywriting might value examples and language specific to software companies. A buyer searching for tech copywriting might expect a similar specialization. But when several pages share the same underlying offer, audience, and conversion goal, their distinctions can become clearer to the agency that wrote them than to the person searching.
The strategist’s first question was therefore about page purpose: what different decision could a visitor make on each URL? If the answer amounted to choosing between near-identical descriptions of the same copywriting service, the architecture was adding a choice without adding much information.
The pivot preserved useful specialization while changing where it lived. A broad hub could answer the primary B2B copywriting query above the fold, then develop narrower applications in substantive sections below. That gave the general search a clear destination and left room for industry-specific detail. The decision required an inventory first; a redirect chosen solely from the Search Console report could have buried material that served a genuinely different intent.
How 32 Service Pages Split Relevance and Links
The site’s original architecture contained 32 thin service pages targeting small variations of a copywriting offer. SaaS copywriting, tech copywriting, and software copywriting illustrate the problem. Those phrases can reflect different buyer language, yet three URLs only earn separate places in the architecture when their content and intended decisions differ enough to justify them.
For the broad B2B copywriting query, the pages supplied overlapping signals: similar service descriptions, similar terminology, and similar routes to an enquiry. Search engines had to select among several candidate URLs rather than encounter one well-developed page. Keyword cannibalization, in this case, described that internal competition for the same intent. It did not mean every mention of B2B copywriting elsewhere on the site needed to disappear. Supporting pages could still exist where they addressed a distinct task or audience.
The inbound-link inventory added a second reason to consolidate. During a diagnostic window, the team mapped links from 41 distinct referring domains to 17 different sub-pages in the 32-page set, based on project outcomes. Those links were spread among URLs that substantially overlapped. A useful citation to a narrow service page could help that page, but it did little to establish a single, obvious destination for the broader service query.
That distribution shaped the technical decision. The team ruled out applying cross-domain canonical tags to a preferred page. The pages lacked enough unique value to justify retaining the whole thin-page structure and asking a canonical signal to sort it out. Consolidation addressed both the content and the URL architecture: useful material would move into stronger destinations, and retired URLs would redirect there.
The diagnostic distinction matters when reviewing another agency site. Pages that share a keyword are not automatically duplicates. Compare their offers, examples, FAQs, and calls to action. If their differences disappear once the industry label changes, a separate URL may be splitting attention and links that the shared service page could use more coherently.
Grouping Copywriting Services Around Buyer Intent
The audit started with what each page actually contained. The team extracted service descriptions, value propositions, examples, FAQs, and calls to action from the 32 URLs, then compared them for repeated claims and distinct buyer questions. This was a qualitative review of page purpose, informed by observed search behavior, rather than a keyword exercise that assigned one page to every phrase variation.
The resulting groups followed the problem a client was trying to solve. Someone comparing providers for a broad copywriting engagement needed a service overview, evidence of fit, and a way to enquire. Someone considering a specific deliverable needed enough detail to assess scope and approach. Those needs could coexist on a hub when the narrower material strengthened the main offer. They warranted separate destinations only when a page supported a meaningfully different search and decision.
That reasoning produced nine detailed hubs from the 32-page inventory. Search intent clustering took precedence over the agency’s departmental categories. An internal team might divide work by industry, channel, or account ownership; prospective clients rarely arrive with that organizational chart in mind. They search for an outcome and assess whether the page can help them commission it.
Give Each Hub a Primary Decision
For each proposed hub, the team needed a clear primary query theme and a corresponding client decision. The page opening could establish the offer immediately. Its H2 sections could then answer substantial questions inherited from the former service pages, while H3 sections handled narrower distinctions, such as deliverables or the circumstances in which a particular type of copy is useful.
Moving a paragraph into a longer page was insufficient on its own. Redundant introductions needed editing; useful examples needed context; repeated FAQs needed a single precise answer. The content extraction and merging phase required a multi-week production sprint to enrich the nine hubs. That production work was part of the SEO intervention, because redirects to thin or muddled destinations would leave the underlying relevance problem largely intact.
Consider the practical application for the SaaS and tech copywriting pages. Instead of leaving the old URLs to cannibalize each other, the agency redirected them to a single B2B technology copywriting hub. The new page opened with a unified value proposition, used H2s to address specific SaaS onboarding sequences versus hardware white papers, and featured a single, prominent portfolio section. By structuring the page around the buyer's actual decision process, this consolidated hub captured the primary search volume while retaining the long-tail traffic that the fragmented pages had previously split.
Mapping 23 Retired URLs to Nine Hubs
Once the hub content had a defined purpose, the team built a URL-level redirect map in staging. The 32 original service pages would resolve into nine hubs, leaving 23 deprecated pages that needed permanent redirects. Each retired URL received one selected destination. Several retired pages could point to the same hub, but no source URL was left with an ambiguous target. Choosing that target required the content audit, not just a similarity in URL slugs. A software copywriting page, for example, should reach the hub that answers the service intent its visitors expressed and carries forward its worthwhile material. Sending every retired page to a general services index would simplify the spreadsheet while making the destination less useful.
Test the Redirects Before Replacing the Navigation
The map recorded each existing URL beside its intended hub URL. The team then tested the proposed changes during a 72-hour pre-launch window in the staging environment. Each deprecated page needed to return a permanent redirect to its final destination, and each hub needed to load as a usable page. Google’s documentation on permanent 301 redirects provides the relevant guidance for signalling a lasting URL move.
The team also crawled the legacy architecture and replaced internal links that still pointed to deprecated pages. This order matters: a redirect can preserve a route from an old URL, but navigation, contextual links, and calls to action should lead directly to the current destination. Direct links make the intended hierarchy visible to crawlers and spare visitors an unnecessary hop.
A second crawl checked for redirect chains and orphaned hubs before launch. If an old URL redirects to another retired URL, the path is harder to maintain and easier to break during later edits. If a hub has no relevant incoming internal links, publishing it has done little to connect it to the service architecture. The completed map, crawl results, and updated internal anchors gave the team a testable release, rather than a list of redirects to inspect only after traffic changed.
Reading Rankings and Enquiries After the Move
The post-launch review ran over a 90- to 120-day monitoring period. Its first test was whether the primary queries stopped rotating among several service URLs. A stable hub appearing for a target query would indicate that the new architecture had made the preferred destination easier to identify. The team watched that pattern alongside the wider visibility of the consolidated service set, including narrower searches affected during the expected transition.
Lead assessment required a different reading of performance. A thin page can attract a visitor who recognizes a phrase in its title yet still needs substantial explanation before enquiring. A thorough hub gives that visitor a service definition, relevant applications, and a clearer path to contact in one place. The post-consolidation analysis therefore focused on the content and fit of organic enquiries through the hubs, alongside ranking stability, rather than treating a traffic increase as the sole measure of success.
Search Console can document the query and URL pattern; it cannot, by itself, establish whether an enquiry is a qualified opportunity. That distinction limits what can be concluded from ranking movement alone. Enquiry review can reveal whether prospective clients describe work aligned with the hub’s offer, while the query report shows whether search engines are sending those visitors to the intended page. The reported qualitative shift was toward better-qualified organic leads, with URL swapping for primary target queries ceasing during the post-launch assessment. The useful interpretation is narrower than “consolidation always improves leads”: in this site, clearer service pages and clearer query destinations supported a more direct evaluation of the agency’s offer. A buyer could move from a broad search to specific copywriting applications without choosing among several near-duplicate service pages.
That same path makes future reporting cleaner. When one hub represents an offer, the team can review its search queries, landing-page enquiries, and content gaps together. If a narrow query performs poorly, the question becomes whether its section answers the buyer’s need adequately, rather than which overlapping URL should own the term this week.
Build One Email Copywriting Hub From Three Pages
Consider a smaller version of the same problem. An agency has pages titled “B2B Email Copywriting,” “Newsletter Copywriting Services,” and “Drip Campaign Copywriter.” All three describe writing emails for business clients, and their visitors ultimately need to assess the same underlying service. The consolidation target is an “Email Marketing Copywriting” hub that gives each application enough space without maintaining three competing service introductions.
Step 1: Choose the Existing URL to Keep
Export in most cases roughly six months of URL performance data for the three pages. Record the queries and landing-page performance associated with each URL, then compare their relevance to the broader email marketing copywriting offer. Review existing inbound links and the pages’ current internal links as part of that choice. The strongest primary hub URL is the one that can credibly represent the combined service while retaining the most useful existing signals; its present title need not become the hub’s final title.
Suppose the B2B Email Copywriting URL is the best fit after that review. Keep its URL, revise its page title and opening to present the wider email marketing copywriting service, and use the other two URLs as source material. This is a decision rule for the example, not an assumed performance finding: the export and link review determine which URL actually wins on a live site.
Step 2: Move Distinct Questions Into the Hub
Read the newsletter and drip-campaign pages line by line. Take the newsletter page’s distinct explanation of recurring editorial emails and its useful FAQs; discard its repeated general pitch. Take the drip-campaign page’s explanation of sequenced messages and the questions specific to that deliverable. Build H2 sections for newsletter copywriting and drip campaigns beneath the hub’s main service explanation. Use H3 headings for narrower questions that need their own answers.
Write a new above-the-fold opening that tells a prospective client what the agency delivers across the full email program. Beneath it, make the distinctions practical: newsletter copy supports a recurring communication; drip-campaign copy supports a planned sequence. Keep the calls to action consistent so a visitor can enquire about either application without returning to a services index to find the right form.
Step 3: Redirect Both Subordinate Pages and Repair Links
Draft one permanent 301 redirect from the Newsletter Copywriting Services URL to the retained hub URL and another from the Drip Campaign Copywriter URL to that same hub. Test both in staging and confirm that each lands directly on the live hub, with no intermediate redirect. Update service navigation and contextual links so their anchors point straight to the retained URL. Then crawl the three-page set again to confirm that the two old paths redirect and the hub remains linked from relevant pages.
The resulting page has a single service proposition, a newsletter section, a drip-campaign section, and the distinct FAQs clients need to evaluate each. The final check is simple enough to copy: search the site for links to the two retired URLs, replace any that remain, open both old URLs to verify their destinations, and read the hub from its first paragraph through its enquiry path as a prospective email-copywriting client would.
