SALIENS launch progress: what we published and what we can measure

Report delivery separately from visibility

From 12 September to 11 October 2026, the SALIENS launch calendar planned 30 new buyer-focused topics in English and Simplified Chinese. With this review included, 26 topics are present in the published source, representing 52 language pages. The separate 11 September provider-selection guide was the launch seed and is not included in that 26-of-30 total.

Four planned dates are not present in the published article archive: 19 September, 2 October, 5 October and 9 October. They remain recorded as gaps rather than being assigned retrospective publication dates. This matters because a content count is an execution record, not evidence that search engines indexed the pages, AI systems cited them, buyers visited them or enquiries were received.

Review the completed buyer coverage

The first month moved from describing the SALIENS offer to giving buyers reusable ways to scope, compare, govern and evaluate GEO work. The archive now covers five connected purchasing needs.

State what is verified today

The article records in the current source provide the topic, language copy, publication date, sources and route used to generate the English and Simplified Chinese pages. The production checks for completed releases have also tested titles, canonical URLs, reciprocal language alternatives, Article structured data, the visible contact email and sitemap inclusion. Those checks support a claim that the pages were delivered and published.

The connected Search Console property list checked on 11 October did not contain saliens.io. No connected source in this publishing task supplied SALIENS indexing, non-brand impressions or clicks, controlled AI mention or citation observations, or attributable enquiries. These results are unavailable, not zero. Publication volume must not be relabelled as ranking, citation or demand improvement.

Use the right measurement conditions

Google states that eligibility for AI features still depends on the normal Search technical requirements and that crawling, indexing and serving are not guaranteed. It also reports traffic from AI Overviews and AI Mode inside overall Web search traffic in Search Console rather than as a complete prompt-level visibility report. A content programme therefore needs separate records for publication, search performance, controlled AI observations and buyer outcomes.

For links distributed through owned social channels, consistent UTM source, medium, campaign and content values can identify referred sessions in an authorised analytics property. UTM data can support traffic attribution; it does not prove that an AI answer, content change or supplier action caused an enquiry. Enquiries still need a received record, qualification rule and documented matching method.

Run an eight-point month-end acceptance check

A buyer reviewing a GEO content programme should ask for one decision pack rather than a headline article count.

• Output register: which topics and language pages are actually live, with dates and URLs?
• Gap register: which planned items were missed, why, and whether they still have purchasing value?
• Coverage map: which buyer questions, markets, services and stages are covered or still weak?
• Release evidence: do visible content, canonical links, language alternatives, structured data and sitemap records agree?
• Discovery evidence: which pages are indexed and which non-brand queries produced impressions or clicks?
• AI observation evidence: under which fixed questions, markets, languages, systems and dates was the brand mentioned or cited?
• Traffic and enquiry evidence: which tagged visits and received enquiries can be matched under an agreed rule?
• Next decision: update, consolidate, distribute, measure or commission a genuinely new buyer question?

Set the next priorities

The immediate measurement dependency is authorised access to a Search Console property for saliens.io and, where available, a site analytics view with consistent campaign tagging. The content priority is to use verified query, page and enquiry evidence to decide what should be improved or added, while retaining the four missed calendar items as visible gaps rather than automatically backfilling them.

The archive should now operate as a buyer resource and evidence base, not as a reason to continue publishing near-duplicates. Future topics should answer a distinct procurement question, link to the most relevant existing guide, and state which evidence would demonstrate delivery, discovery and business response.

How SALIENS can support the next stage

SALIENS provides GEO audits, AI visibility monitoring, content and technical improvements, and ongoing GEO delivery for UK and international organisations. We can review the first-month archive, map it to buyer questions, establish repeatable search and AI observation records, prioritise evidence-backed updates and maintain English and Simplified Chinese content.

Email info@oxfordintelligence.co.uk with your website, target markets and languages, priority buyer questions, current Search Console or analytics access and the decisions the programme must support. SALIENS is operated by Oxford Intelligence Limited. Delivery does not guarantee crawling, indexation, mentions, citations, rankings, traffic or enquiries.