There is a specific test for whether a piece of SEO content is worth publishing: could a competitor publish the same page tomorrow by swapping the logo? If the answer is yes, you have produced a commodity. It may be well written, correctly optimised and perfectly structured, and it will still struggle — because search engines and answer engines already have twenty versions of it, and none of them needed yours.
This is a working playbook for producing the other kind. It is written from a Vancouver agency's perspective, and it assumes you do not have a research department, a data science team or an unlimited budget. What you do have — and what almost every business underestimates — is a large stock of first-hand evidence that nobody outside your organisation can access.
Start from the buyer's decision, not the keyword
Commodity content usually begins with a keyword list and works outwards. That produces pages organised around search strings rather than around anything a buyer is trying to decide, which is why so much of it reads like an encyclopedia entry written by someone with no stake in the outcome.
Invert it. Write down the actual decisions your buyers make on the way to purchase. For a professional services firm in Vancouver, those decisions might be: whether to hire in-house or outsource, how to budget for the work, how to compare two very different proposals, how to tell whether the current provider is underperforming, and how to justify the spend internally.
Each of those decisions is a content brief. Keywords then get mapped onto the decision rather than the other way around — and because the page is organised around a real choice, it naturally contains the comparisons, caveats and numbers that generic content omits.
A useful source for this list is your own sales calls. The objections you answer verbally every week are the questions the market is asking and nobody has published a good answer to.
Build an evidence inventory before you write anything
Before commissioning a single article, spend two hours cataloguing what your organisation knows that others do not. Most teams find between fifteen and forty usable assets. Look in:
- Support and service tickets. The recurring failure modes in your industry, with frequencies attached.
- Quotes and proposals. Real price ranges, real scope variations, and the reasons deals are won or lost.
- Project post-mortems. What went wrong, and what you now do differently. Failure content is disproportionately valuable because almost nobody publishes it.
- Analytics and platform data. Aggregated, anonymised patterns across your client base — the kind of thing only an operator can see.
- Screenshots and artifacts. Dashboards, configurations, before-and-after states, annotated to show what matters.
- Practitioner opinion. The judgments your senior people make instinctively that a newcomer would get wrong.
Anything in that inventory can anchor a page. Anything not in it should make you nervous, because content with no evidence behind it defaults to paraphrasing the current search results.
Make local context meaningful, not decorative
"Vancouver SEO services" appended to a generic national article is not local content, and both readers and answer engines increasingly treat it as filler. Meaningful local context changes the substance of the advice:
- Regulatory or municipal realities — permitting timelines, provincial licensing, BC-specific compliance requirements that alter how a service is delivered.
- Market structure — which competitor types dominate locally, how the buying process differs from a larger US market, what agency pricing actually looks like in this city.
- Seasonality that genuinely moves demand. In Metro Vancouver, trades, tourism, home services and education all have distinct demand curves, and advice that ignores them is wrong for half the year.
- Geography that affects service delivery — travel across the region, the difference between serving Downtown and serving the Fraser Valley.
The test is simple: if you deleted the city name and the paragraph still made sense everywhere, the local relevance was decorative.
Interview your experts properly
The fastest route from commodity to non-commodity is a thirty-minute recorded conversation with the person in your company who actually does the work. Writers cannot invent judgment; they can transcribe it.
Run the interview with a short list of questions designed to surface disagreement and specifics:
- What does the standard advice on this topic get wrong?
- What do you do differently from most people in the field, and why?
- Walk me through the last time this went badly. What did you learn?
- What number, threshold or rule of thumb do you use when deciding?
- What would you tell a client not to do?
Keep the transcript. The specific phrasing an expert uses — the unexpected number, the strong opinion, the counter-example — is the material that makes a page quotable, both to a human reader and to a model summarising the topic.
Ship an artifact, not just prose
Pages that get linked to and cited usually contain something a reader can take away and use: a checklist, a template, a decision tree, a comparison table with real criteria, a worked calculation, a diagnostic sequence. The artifact is the reason someone bookmarks or shares the page, and it is also the part competitors cannot copy without obviously copying.
Artifacts do not need to be interactive or expensive. A well-constructed table of "symptom → likely cause → first thing to check" is more valuable than three hundred words describing the same relationships in paragraphs. So is a numbered sequence with the order justified.
Write answer blocks for the questions you actually resolve
Answer engines lift passages that state a claim cleanly and then support it. Structure helps them do that accurately:
- Put a direct 40–70 word answer immediately under each question-shaped heading, then expand beneath it.
- Define terms explicitly the first time they appear rather than assuming shared vocabulary.
- Attach dates to anything time-sensitive, so a model can tell whether the claim is current.
- State limitations. "This applies to businesses with more than one location; single-location businesses should do X instead" is the kind of qualifier that makes a passage safe to cite.
- Avoid burying the conclusion under a preamble. If the answer is "usually no," say so first.
This is the same discipline covered in our guide on making content quotable by AI, and it costs nothing beyond attention to structure.
Set editorial gates that content must pass
Quality collapses when everything is a judgment call. Write down gates and hold every draft to them:
- The swap test. Could a competitor publish this with their logo? If yes, it goes back.
- The evidence gate. At least one piece of first-hand evidence — data, example, screenshot, named opinion — per major section.
- The specificity gate. No unquantified claims where a number exists. "Faster" becomes "typically two to three weeks faster."
- The accuracy gate. A named subject-matter expert signs off on factual claims before publication.
- The utility gate. What can the reader do differently after reading this? If nothing, the page is commentary.
- The redundancy gate. Does this overlap an existing page? If so, improve the existing page instead of adding a competing one.
Gates work because they are refusable. An editor who can send a draft back without negotiating is the cheapest quality control available.
Use AI accountably
Generative tools are genuinely useful in this workflow — for outlining, for reformatting an interview transcript, for stress-testing an argument, for generating the counter-position you have not considered, for tightening prose. They are not useful for supplying substance, because they produce the average of what already exists, which is the definition of commodity content.
A workable division of labour: humans supply evidence, opinion, examples and the final factual review; AI assists with structure, drafts and editing. Every published page has a named human accountable for its accuracy. Never let a model invent statistics, sources, quotes or case studies — a fabricated citation is a credibility failure that outlives whatever ranking it earned.
What this looks like in practice
Three examples of the same nominal topic, treated as commodity versus non-commodity:
| Topic | Commodity version | Non-commodity version |
|---|---|---|
| SEO pricing | "SEO costs vary depending on your needs." | Actual Vancouver retainer bands, what each band buys in deliverables, and the three factors that move a quote up or down. |
| Local SEO for trades | Generic Google Business Profile checklist. | Seasonal demand curves for BC trades, which categories convert, and what happens to visibility during the winter trough. |
| Site migrations | "Redirect old URLs to new ones." | A post-mortem of a migration that lost traffic, what the specific failure was, and the pre-launch checks that would have caught it. |
In each case the difference is not writing skill. It is whether the organisation was willing to disclose what it knows.
Measure it honestly
Distinctive content usually behaves differently from commodity content: slower to gain traction, stickier once it does, and much more likely to attract links and citations. Judge it accordingly.
- Weeks 0–6: indexation and impressions. You are checking that the page exists in the index and is being served for something.
- Weeks 6–12: average position and query breadth. A good page picks up long-tail queries you did not target.
- Quarter 2: clicks, CTR and engaged sessions. If impressions are high and clicks are not, the problem is the title and description, not the content.
- Ongoing: assisted conversions, links earned, and whether the page gets cited in AI answers for its topic.
Evaluate clusters, not single URLs. One page rarely carries a topic; four connected pages usually do.
A 30-day sprint to get started
- Days 1–3: List the buyer decisions. Build the evidence inventory.
- Days 4–7: Pick three decisions with the strongest evidence behind them. Write briefs that name the required evidence for each.
- Days 8–12: Run expert interviews and record them. Pull the supporting data and screenshots.
- Days 13–20: Draft. Build one artifact per page — a table, checklist or decision tree.
- Days 21–24: Run the editorial gates. Send back anything that fails the swap test.
- Days 25–27: Structure for answer engines — question headings, direct answers, definitions, dates, limitations. Check length and readability with the SEO content analyzer.
- Days 28–30: Publish, interlink into the relevant hub, and set a review date 90 days out.
Three genuinely distinctive pages a month will out-perform thirty commodity ones, and they will keep working after the next algorithm update, because their advantage is not structural — it is that nobody else has the material.
If you would rather not build the workflow in-house, that is essentially what our content development service does: extract the evidence, interview the experts, and publish on a schedule. It sits inside a broader SEO program when content is one part of a larger plan.

