What intellectual-property rights should a GEO buyer clarify?

Do not assume payment transfers ownership

A GEO engagement can produce content briefs, rewritten pages, translations, question sets, monitoring methods, source maps, structured-data recommendations, code, templates and evidence packs. It can also use material the buyer already owns, supplier methods developed before the engagement, licensed software and third-party sources. Treating all of this as one undifferentiated deliverable creates avoidable uncertainty at renewal, publication or exit.

UK Intellectual Property Office guidance says that the creator of a commissioned copyright work is normally its first owner unless ownership is agreed otherwise in writing. A commissioner may otherwise receive only a limited implied licence. Government IPR guidance therefore recommends distinguishing existing IP, new IP and third-party IP, then specifying ownership and use rights in the contract. These principles do not decide the correct arrangement for every GEO purchase, but they show why buyers should record the rights they actually need rather than assume that an invoice settles the issue.

Create one six-part GEO intellectual-property rights register

Complete the register before production work and update it when a new tool, source, asset type or subcontractor enters delivery. Link every material deliverable to a row, the applicable agreement and any supporting licence evidence. Record a specific owner and permitted use; labels such as ‘client property’ or ‘supplier IP’ are not sufficient on their own.

Map rights to the intended operating life

Start with what the buyer must be able to do, not with a default demand to own everything. A perpetual right to publish, edit, translate and transfer accepted website content may be more important than ownership of a supplier's general methodology. Conversely, a short, non-transferable licence can be inadequate if the buyer must maintain a page, give files to a replacement supplier or reuse an evidence pack in a future procurement.

For each deliverable, test the expected users, territories, channels, languages, duration, editing rights and transfer or sublicensing needs. Government guidance notes that licences can be limited by purpose, time or place. Record whether rights survive expiry or termination and whether a fee, account or supplier-controlled service is still required. Seek specialist legal advice where the intended arrangement, underlying rights or jurisdiction is unclear.

• Separate ownership from the practical rights needed to use and maintain the result.
• Name the background components that remain supplier-owned but are embedded in an accepted deliverable.
• State whether a replacement supplier may receive the files and exercise the necessary rights.
• Avoid promising publication or reuse until third-party restrictions have been verified.

Require evidence for third-party and AI-assisted material

A source citation is not itself permission to reproduce protected material. GOV.UK guidance says copyright material normally requires a licence, an acquisition of rights or a valid exception, and that licence terms can restrict the purpose, period or territory. The delivery record should therefore identify copied or adapted material, its source, applicable licence, attribution and any limit on modification or onward use.

Apply the same discipline when a supplier uses an AI or software tool. Record the human creator or reviewer, inputs that were provided, the tool and account context where relevant, material incorporated from elsewhere, verification performed and the right relied on for publication. Do not treat an automated output as proof that it is original, accurate or safe to reuse. If the provenance cannot be supported, replace or remove the material before acceptance.

• Keep licence evidence with the asset or deliverable rather than in a separate, unlinked inbox.
• Check whether attribution, share-alike, non-commercial or no-derivatives conditions apply.
• Record subcontractor and freelancer assignments or licences, not only the prime supplier's promise.
• Make unresolved provenance an acceptance issue with an owner and correction date.

Test one deliverable before accepting the model

Select a representative bilingual page or technical recommendation and trace every component through the register. The buyer should be able to identify its own inputs, supplier background elements, newly created work, third-party materials, the agreed permissions and the editable files required for handover. Then ask a person outside the delivery team to publish a permitted update or prepare a replacement-supplier pack using only the documented rights and files.

Treat the test as failed if ownership is inferred from payment, a licence cannot be found, an embedded component prevents editing, a supplier account is required without continuity, or portfolio and reuse permissions were never decided. Resolve the gap before scaling the same delivery model across more markets, languages or page families.

Ask SALIENS for rights-aware, handover-ready GEO delivery

SALIENS provides GEO audits, AI visibility monitoring, content and technical improvements, and ongoing GEO delivery. A scoped engagement can identify buyer inputs, supplier background methods, new deliverables, third-party sources and tools, English and Simplified Chinese review, licence evidence, permitted uses, editable handover formats and replacement-supplier continuity checks.

Email info@oxfordintelligence.co.uk with your website, markets and languages, planned deliverables, existing content and data, required publication and reuse rights, third-party tools, approval owners, handover needs and procurement timetable. SALIENS is operated by Oxford Intelligence Limited. Rights controls support usable delivery but do not guarantee crawling, indexation, AI mentions, citations, rankings, traffic or enquiries. This guide is a procurement framework, not legal or intellectual-property advice.