GEO content procurement
Prioritising existing content before commissioning more pages
Use this eight-field content register to rank existing pages by buyer value, factual risk, evidence gaps, technical readiness and the next action before commissioning more GEO content.
Published by SALIENS · Published
Start with the buyer decision, not the page count
A GEO brief should not assume that every uncovered question needs a new page. An existing service, evidence, organisation or guidance page may already be the right place to answer it. Before commissioning more content, inventory the pages that influence discovery, comparison, due diligence and enquiry, then decide whether each one should be kept, updated, merged, retired or complemented by a genuinely new page.
This is a procurement decision rather than a promise about ranking. Google recommends people-first content that helps an intended audience achieve its goal and warns against adding or removing large amounts of content simply to make a site appear fresh. A useful review therefore starts with buyer value, accuracy and evidence, then records technical and measurement conditions separately.
Complete an eight-field prioritisation register
Use one row per live page and retain the evidence behind every rating. The table below gives a buyer an acceptance format that can be compared across suppliers and reviewed by the page owner.
| Field | Question to answer | Evidence or action |
|---|---|---|
| 1. Buyer value | Which discovery, comparison, evidence, fit or enquiry decision does the page help a named audience make? | Record the buyer question, market, language and intended next decision. A page with no defined user need is not automatically a priority. |
| 2. Factual risk | Could outdated identity, service, price, location, market, language, contact or eligibility information cause a material mistake? | Identify the approved source, fact owner, effective date and any urgent correction. High-risk inaccuracies take precedence over cosmetic work. |
| 3. Evidence gap | Are important claims supported by visible sources, dates, qualifications or delivery evidence? | Map each material claim to its source. Mark unsupported or overbroad claims for correction, qualification or removal. |
| 4. Scope overlap | Does another page answer the same buyer question more clearly or with better evidence? | Compare purpose and ownership. Decide whether to clarify boundaries, consolidate content or keep distinct pages for distinct needs. |
| 5. Technical readiness | Can the intended audience and permitted crawlers reach the important text, and are status, canonical, language alternatives, internal links and relevant metadata coherent? | Record the live checks and the implementation owner. Do not label a published page as indexed or visible without separate evidence. |
| 6. Next step | Can a qualified reader understand the service boundary and take the appropriate next step? | Check the visible contact route, required briefing information and material limitations; do not invent a conversion event. |
| 7. Ownership and review | Who approves facts, implements changes and reviews the page after a material change? | Assign named roles, review triggers and a change record. Preserve the original publication date and change the modified date only after substantive work. |
| 8. Measurement state | What evidence exists for use, discovery, search performance, AI observations, visits or enquiries? | Name the source and date for each measure. Keep unavailable data unavailable and separate delivery evidence from business outcomes. |
Use four priority gates
Rank the work in a sequence that reflects business risk. First correct material inaccuracies and unsupported claims on pages with high buyer value. Next repair blocked or confusing routes to a decision. Then strengthen incomplete evidence and merge avoidable overlap. Only after those checks should the team commission a new page for a buyer question that has no suitable home.
Do not treat age alone as proof that a page needs rewriting. GOV.UK's current content guidance recommends finding relevant content, monitoring whether it is useful and findable, and then updating or retiring it when evidence shows a need. Google likewise advises against drastic changes to content that is already performing well and describes deletion as a last resort when content cannot be salvaged.
- Priority 1 — correct: high buyer value plus a material factual or substantiation risk.
- Priority 2 — unblock: the answer exists but access, structure, language consistency or the next step is broken.
- Priority 3 — strengthen: the page is useful but incomplete, weakly evidenced or unnecessarily duplicated.
- Priority 4 — create: a validated buyer question still lacks a suitable page after the existing estate is reviewed.
Choose an explicit action for every page
A review is not complete if it ends with a vague recommendation to improve content. Assign one controlled action: keep, update, merge, retire or create. For a keep decision, retain the evidence and next review trigger. For an update, state the fact, evidence, copy, metadata or route that changes. For a merge or retirement, check inbound links, language equivalents, required records and the replacement destination before implementation.
Do not refresh a date without a substantive change. Google's people-first guidance specifically identifies changing dates to make pages look fresh when their content has not materially changed as a warning sign. Record the original publication date, the actual modification date and a concise change note so buyers and reviewers can distinguish maintenance from republishing.
| Action | Use when | Acceptance evidence |
|---|---|---|
| Keep | The page has a clear buyer purpose, current facts, suitable evidence and a usable next step. | Dated review record, page owner and next review trigger. |
| Update | The page remains valuable but contains a factual, evidence, scope, language, technical or next-step gap. | Approved change list plus live checks for the affected fields. |
| Merge | Pages materially overlap and one coherent destination can answer the buyer need without losing necessary distinctions. | Content map, destination decision, ownership, link and language handling, and post-release checks. |
| Retire | The page is obsolete, harmful or cannot be salvaged, and retention requirements have been checked. | Approved retirement reason, replacement or status behaviour, dependency checks and dated verification. |
| Create | A validated buyer question has no appropriate existing page after the inventory is reviewed. | Brief naming the audience, question, evidence, owner, acceptance checks and non-duplicative purpose. |
Write the supplier acceptance test before commissioning
Ask a GEO supplier to return the page inventory, the eight evidence fields, the selected action and priority, the responsible approver and implementer, the expected live checks, dependencies and exclusions, and the measurement source for any claimed outcome. Sample the highest-risk decisions and verify that another reviewer can trace each recommendation to a page and source.
Reject a proposal that equates more pages with better visibility, treats unavailable analytics as zero, changes dates without substantive edits, or guarantees crawling, indexing, AI citations, rankings, visits or enquiries. Publication and technical checks prove delivery; external discovery and business outcomes require their own dated evidence.
How SALIENS can prioritise an existing content estate
SALIENS provides GEO audits, AI visibility monitoring, content and technical improvements, and ongoing GEO delivery for UK and international organisations, including scoped English and Simplified Chinese work. We can inventory buyer-facing pages, map facts and evidence, apply a documented priority method, and turn approved decisions into controlled content and technical changes.
Email info@oxfordintelligence.co.uk with your website, priority markets and languages, main services, known high-risk facts, existing content owners and the buyer questions you need to support. SALIENS is operated by Oxford Intelligence Limited. Content maintenance does not guarantee crawling, indexing, mentions, citations, rankings, visits or enquiries.
Sources
- Google Search Central: Creating helpful, reliable, people-first content (checked 3 October 2026)
- Google Search Central: Google Search's core updates and your website (checked 3 October 2026)
- GOV.UK content and publishing guidance: Manage existing GOV.UK content (checked 3 October 2026)
- SALIENS: Designing a brand-blind AI visibility baseline
Prepared with AI assistance using the linked sources and SALIENS service information.