Service Page or Blog Post? Assign the Search Intent First

Use a service page when the reader needs to evaluate an offer and decide whether to hire a provider. Use an article when the reader needs to understand a problem, compare approaches or complete a specific planning task. Before creating either, check whether an existing page already serves that purpose well.

The words in a query help, but they do not decide the page type alone. A question about cost may belong within a service page, a detailed budgeting article or both with different boundaries. The important distinction is the decision each page helps someone make, not whether the title includes a question mark.

Identify the Job Behind the Query

Write a plain-language description of the searcher's need. Someone searching for a migration provider may want scope, evidence, process and an enquiry route. Someone asking how redirects should be mapped may need an explanation and a practical method before they are ready to discuss a project.

Classify the likely intent as information seeking, investigation or an action such as hiring. Treat the classification as a working interpretation rather than a fact permanently attached to a phrase. The same words can carry different meanings depending on context, location and the surrounding search results.

Handle Mixed Intent Without Creating Two Copies

Mixed intent does not automatically require two pages. Ask whether one strong page can answer the question at an appropriate depth while supporting the reader's next decision. A concise explanation of a service can live on its commercial page without requiring a separate generic definition article.

Create a supporting article when the informational task needs enough distinct depth to justify it. A migration checklist, for example, can teach planning and verification while the service page explains how the agency delivers that work. Their vocabulary overlaps, but their responsibilities should remain recognisably different.

Search Your Existing Website Before Commissioning Content

Review service, platform, industry and article inventories together. Include drafts and approved plans, not only published pages. Otherwise two writers may create similar content because each searched a different part of the site.

Record current URLs, primary purposes, supporting topics and important internal links. Where authorised performance data exists, inspect the queries and outcomes already associated with a page. Do not replace an established article solely because its title does not match a newly preferred page-type label.

Distinguish an Ownership Reservation from a Ranking Claim

A keyword owner register is an editorial control: it says which page is intended to answer the dominant need. It does not mean that the page ranks for every related query or that no other page may use those words. Keep intended ownership separate from observed search performance.

If an existing page is weak but correctly scoped, improvement may be better than creating a competitor for it. If the topic is already covered in an approved unpublished brief, coordinate with that work. A new URL should not be the default response to an incomplete inventory.

Review Search Results as Evidence, Not a Template to Copy

Look at a relevant sample of current results through an authorised search method. Note whether they are service offers, guides, comparisons, tools or mixed formats. Read enough of the pages to understand the task they serve; snippets alone can obscure their actual scope.

Record the query, date and relevant context with the observation. Search results change, and a small sample is not a complete market study. Use it alongside customer questions and your own service knowledge rather than treating the visible page types as an instruction to imitate competitors.

Choose the Format That Can Satisfy the Task

A service page needs enough detail to support a buying decision: the problem addressed, scope, approach, relevant evidence and next step. An article needs a substantive answer to its question, with conditions, examples and limitations where useful. Neither should become a thin introduction that sends the reader elsewhere for everything important.

Avoid creating slightly varied pages simply to capture more phrases. Google's spam policies identify doorway and scaled low-value content as problems. A larger inventory is not inherently a stronger website when the pages add little distinct value.

Define the Boundary Before Writing the Outline

For each proposed page, record one dominant purpose, the intended reader, the primary topic and explicit exclusions. Then identify the existing pages it should support. Exclusions are especially useful because they prevent a writer from expanding into a neighbouring page's full responsibility.

The following is an illustrative owner register for a fictional agency. It demonstrates editorial boundaries, not measured keyword volumes or actual ranking results.

Reader need	Page type	Dominant responsibility	Exclusion
Hire a team to migrate a website	Service page	Delivery scope, process, evidence and enquiry	Do not reproduce the entire technical checklist
Preserve search continuity during a redesign	Article	Planning and verification method	Do not become a second service sales page
Choose between two CMS platforms	Comparison article	Requirements and trade-offs	Do not cover every possible platform
Evaluate WordPress implementation expertise	Platform page	Platform-specific delivery capability	Do not duplicate the general migration offer
Understand a completed migration project	Case study	Truthful project scope and evidence	Do not invent outcomes or become a generic guide

This map permits natural shared terminology. What it prevents is several pages making the same promise to the same reader with only a different title and a few substituted words.

Give the Writer a Useful Link Plan

Identify links where the reader genuinely needs a next step. An article explaining migration risks can link to the service when discussing implementation support. A service page can link to a detailed guide when a prospective client needs more background.

Do not require a fixed number of exact-match links per section. Anchor wording should explain the destination naturally. A page with clear intent and a few useful references is preferable to one that repeatedly interrupts the answer with near-identical commercial links.

Use a Keep, Revise, Create or Defer Decision

Keep the existing page when it already answers the need well and there is no demonstrated reason to change it. Revise it when its purpose is right but the answer, evidence or structure is incomplete. Create a new page when the need is distinct and the team can provide enough useful substance.

Defer when the proposed distinction is unclear or the necessary evidence is missing. Deferral is a content-quality decision, not an admission that the topic is unimportant. A pending research question should not be filled with generic copy merely to complete a publishing calendar.

Decision question	If yes	If no
Does an existing page already serve this task?	Review its quality and performance	Investigate the proposed gap
Can a targeted revision satisfy the need?	Improve the owner	Test whether a distinct page is justified
Is the new purpose materially different?	Define scope and evidence	Combine the idea with the existing owner
Is there enough useful, accurate material?	Approve the brief	Defer until evidence or scope is adequate

Keep the record with the brief and update it when the page changes. That prevents later editors from recreating a deferred or consolidated topic because they cannot see the earlier reasoning.

Evaluate Overlap Without Reflexive Deletion

Two pages appearing for some of the same queries is not automatic proof of harmful cannibalisation. Examine their purposes, the queries involved and the value each provides. One may answer an early research question while another supports a later hiring decision.

Where authorised Search Console data is available, compare query and page patterns over suitable periods. Consider changes in content, indexing and demand before attributing movement to overlap. Avoid declaring a penalty from a shared word or a short fluctuation in performance.

Choose the Smallest Correction That Resolves the Problem

If titles obscure otherwise distinct pages, clarify the titles and openings. If an article drifts into a neighbouring guide, tighten its scope and link to the deeper explanation. If two pages are genuinely redundant, assess consolidation with preservation of useful content and an appropriate URL plan.

Do not delete or redirect an established page without reviewing its links, traffic, enquiries and historical purpose where that evidence is available. Record the reason, preserve a recoverable copy and verify the destination. Consolidation can be sensible, but it should be a deliberate change rather than a cleanup reflex.

Do Not Use Canonicals as a Shortcut for Content Strategy

Google's canonicalisation guidance concerns preferred URLs for duplicate or very similar content. It is not a general instruction to point every supporting article at a commercial page.

A distinct article and service page should normally stand on their own editorial purposes. If they are so similar that a canonical seems necessary to resolve competition, revisit the content decision first. Metadata cannot make two indistinguishable answers meaningfully different for a visitor.

Maintain the Owner Map as the Website Grows

Before a new brief is approved, search the register by topic, intent and related vocabulary. After a substantial revision, update the purpose, exclusions and links. Review category archives too, since their role is to help readers navigate a coherent collection rather than become another competing guide.

This process matters particularly for B2B sites that offer services across several platforms and industries. The same capability can appear in several contexts without requiring a copied sales page for every combination. Build a new destination only when the context changes the useful answer enough to justify it.

If your library already contains confusing overlap, begin a focused search-structure review with the current owner map and a sample of affected pages. That makes it possible to preserve useful work while correcting the specific ambiguity, rather than rebuilding the content strategy from scratch.