Skip to content
SEO与数字营销

Keep or Create? A Short Check Before You Add a New Page

For SaaS teams turning interview and ticket notes into topics: decide whether a query stays on an existing page or needs a new page, then recheck the choice with Search Console groups.

OBy ObivuAuthor

Short answer with a limit: keep a query on its current page when that page alone can resolve the reader job with facts you can maintain; build a separate page only when the job, proof, or next action is clearly different and you hold the material to answer it. This applies only to pages you want found in search and can keep current.

Brand promotion: this article introduces Guangsuan's keyword mapping guidance.

Who this note helps

This note is for SaaS product teams who have turned customer interviews and support-ticket wording into a list of possible topics, and now must choose a home for each one. It does not cover pages kept out of search, pages behind login, or offers the business cannot support. If the team cannot maintain specifications, limits, and contact routes, leave the idea on hold.

State the single job first

Start the sheet only with products, regions and languages you can actually support, then place sales questions and live URLs beside them. Add one column for the reader job in plain words: compare options, take one exact plan, follow setup steps, fix a failure, or confirm retention and contact terms. A workable row holds query, source and date, market and language, reader job, current URL, evidence on hand, missing proof, proposed action, and owner.

Where you have access, pull relevant queries and landing addresses from the Search Console Performance report and keep date span, country, device, and search type on the file. Because some queries are hidden and rows are capped, read that export as what your property recorded in that window, not as the whole market. Leave unknown counts as unknown.

Where the boundary sits

Group two queries together only when one finished page would let both searchers finish without a second search. Shared words alone are not enough; buying stage, product scope, and proof needed usually decide.

The next illustration is hypothetical teaching material with no volumes or ranks claimed. Suppose a team lists how to bring ticket text into a triage view and how to name fields in that view. Those two could share one setup note, because one workflow plus field notes closes both. Suppose the same list also holds why tags differ across tools and how long interview records may be kept. Those call for separate notes, because diagnosis method and retention proof call for separate evidence and separate next moves.

Use this practical rule. Survey options in one set stay on a category or collection view. One exact plan or integration stays on its feature record. Size, threshold, or setup choices stay in a guide section. Failures or retention questions stay in a troubleshooting or compliance note. Improve the intended existing page before minting another address. Missing specifications belong on the product record. Add a page only when a distinct job has no finished home.

How to recheck with Search Console groups

Keep settled addresses when you improve them. Give fresh addresses a steady readable form and do not shift old ones only to add a word. Open the finished address and look over state, main body, links, images, meta, and any stray block or login on a public view.

A canonical tag states a preference for duplicate or very similar pages; it does not force ranking to an unrelated target. Keep links, sitemaps, and canonical signals in agreement. A crawler has to be able to fetch a page to honour its noindex tag.

To verify, filter Search Console with steady dates, search type, country, and device, then set impression addresses against the intended one. Two pages receiving impressions for one query do not automatically need merging because they may support different tasks. When one query lights up two addresses, see whether they serve separate jobs before joining them. Note change date and parallel edits before further moves. Going live, getting indexed, and winning qualified notes stay separate stages.

What to bring before you ask for help

If the sheet shows unclear page roles, missing specifications, or template problems, bring current URLs, target markets, and records you may share so scope can be set. For the full five-step method behind this check, see Guangsuan's keyword mapping guide. For how people-first content is judged, see Google's helpful content guidance.

FAQ

Does each wording need its own address?

No. Share one address when one full reply closes the job. Add one only when a separate job has no finished home.

Tool and Console disagree. What first?

Match country, language, span, and metric label on both sides. Console shows what your property logged in that frame; a tool shows a guess under its settings. Do not add overlapping guesses as fresh demand.

The best product decisions are no longer the loudest in the room — they are the most evidenced.
— Obivu Research Note, 2024

See your own customer signals, ranked.

Turn fragmented interviews, tickets, and verbatims into a single feed of validated insights. Full feature access, white-glove onboarding, no credit card.