How we work · Our proprietary methodology
AISRO — AI Search & Recommendation Optimisation
Our methodology for connecting search visibility, clear business information and credible evidence—so people and AI systems can better understand what your business does and where it is relevant.
We use AISRO to guide the choice and coordination of audits, products, services and Solution Projects around your business requirement, industry and market. The scope follows the problem; the methodology guides how we approach it.
What is the AISRO methodology?
AISRO is Logue Media’s proprietary AI Search & Recommendation Optimisation methodology. It coordinates SEO, Local SEO, AEO, GEO and AIO to guide how we assess discoverability, clarify business information, connect evidence and review the work.
Our approach is informed by Google Search Central’s published guidance on AI features and SEO. For Google Search, this means sound technical foundations and helpful, reliable content. AISRO is independently developed by Logue Media; Google does not direct, certify or endorse it.
The distinction: AISRO explains how we work. The AI Search Visibility & Readiness System is a Solution Project framework that applies the methodology to a client’s specific problem, with an agreed scope, deliverables and acceptance checks.
Methodology questions
Is AISRO a Solution Project?
No. It is our method for deciding and coordinating the work. A Solution Project applies that method to a particular business requirement and defines what will be delivered.
What is proprietary about AISRO?
Our framework for combining the disciplines, diagnosing the requirement, connecting evidence and governing delivery. We do not claim ownership of SEO or Google’s public guidance.
Does Google require a separate AI optimisation method?
Google says established SEO fundamentals remain applicable to AI Overviews and AI Mode, with no special additional optimisation required. AISRO organises our work across search, answers, evidence and recommendation readiness; it does not promise inclusion.
Being visible is only part of being understood
Different descriptions of the business, its services and its operating locations make interpretation harder. A new page cannot repair contradictions elsewhere. Establish which entity does what, where it operates and which source owns each fact before expanding the content.
A convincing claim needs a relevant source. Generic capability copy, unattributed statistics and decorative images do not establish delivery experience. Bring project facts, expert knowledge and approved customer evidence close to the question they answer.
Search, website and social activity can each look productive while telling different stories. More output may amplify inconsistency. Connect the buyer questions, authoritative pages and supporting evidence so that each channel reinforces a coherent account.
How AISRO works
Agree the requirement, establish the source material and work through a defined scope with review points.
- 01UnderstandBusiness, audience and decisions
- 02ClarifyEntities, questions and sources
- 03ConnectPages, evidence and public facts
- 04ReviewObserved outcomes and new gaps
Start with the business decision. Identify the offering, customers, industry and locations that matter, then establish what people need to understand before they enquire or buy. A visibility concern may come from unclear positioning, weak evidence, access problems or inconsistent business facts; those call for different responses.
Review existing pages, reports and source material before proposing new work. Record the current condition, its commercial implications and the assumptions that still need checking. Agree who owns important facts and what a useful outcome would look like.
Result of this stage: a defined requirement, baseline and review criteria. That brief guides the choice of audit, service or Solution Project.
Give each important fact a reliable home. Map the business, its people, products, services, industries, locations and relevant projects. Establish which page explains each entity and how the relationships help a customer understand the offering.
Group genuine buyer questions around those page purposes. Identify missing explanations, competing versions and claims without support. A hub should link contextually to its spokes, while each spoke returns to the hub and connects selectively to relevant siblings.
Result of this stage: a practical information and evidence map. New pages are proposed only where they contribute independent value; existing useful content is retained and improved.
Choose the intervention that addresses the gap. The response may involve technical repair, clearer answers, better internal links, approved project evidence or more accurate operating information. Set a boundary for each task and identify dependencies before delivery begins.
The Project Evidence & Case Study Engine can supply structured proof. VDRS can recover useful expertise from authorised recordings. These capabilities are selected when the requirement justifies them.
Result of this stage: implemented changes connected to their source and acceptance criteria, with permissions, factual review and unresolved defects recorded.
Verify the work before interpreting the outcome. Check the changed pages, navigation, facts, evidence and relevant technical behaviour against the brief. A recommendation in a report is not an implemented fix, and a saved page is not proof that its interactions work.
Then review dated search, AI-response and enquiry observations against the baseline. Keep the query, location and context consistent where possible. Platform outputs vary, and a single favourable answer cannot establish dependable recommendation visibility or prove causation.
Result of this stage: a change record, remaining gaps and the next review priorities. The methodology supports accountable improvement; it cannot guarantee rankings or recommendations.
Five disciplines, one proprietary methodology
Each discipline contributes a different perspective. AISRO brings them together around the same business facts, audience and evidence. Select a discipline to see its role.
- 1. Search Engine Optimisation (SEO)
- 2. Local Search Engine Optimisation
- 3. Answer Engine Optimisation (AEO)
- 4. Generative Engine Optimisation (GEO)
- 5. Artificial Intelligence Optimisation (AIO)
Make the website accessible and understandable
SEO addresses the website’s technical foundations, page purpose, content and internal relationships. The first question is whether people and search systems can reach and understand the information that matters.
We assess access, indexing signals, page structure and useful content, then prioritise the work against the business requirement. Adding pages is not automatically the answer.
Explore the search marketing services that implement this work.
Connect the business to places it genuinely serves
Local SEO applies accurate business information, relevant service-area context and genuine local evidence. It helps explain where the business operates and which customers it can realistically serve.
We check the consistency of operating facts and the relevance of location content. Local pages need useful, place-specific substance; swapping suburb names into generic copy does not establish local expertise.
Answer the question and support the answer
AEO focuses on the questions people need answered before they can make a decision. A clear direct answer comes first, followed by the explanation, qualification and evidence needed to make it useful.
We organise buyer questions, define the purpose of each answer and connect it to relevant information. Concise answers must remain accurate; shortening them should not remove important conditions.
Connect answers to approved project evidence.
Add original information people can verify
GEO considers how information may be retrieved, interpreted and represented in generated answers. Within AISRO, we prioritise unique, authentic contributions grounded in business expertise and attributable evidence.
- Original statements: useful findings, first-hand observations and expert explanations that add substance beyond generic summaries.
- Statistics: verified figures with their source, date, scope and measurement method. Distinguish our own findings from third-party research and explain limitations.
- Tables: clearly labelled comparisons, specifications or results that make meaningful relationships easier to understand. Use accessible text and consistent units, rather than placing essential data only in an image.
- Videos: relevant demonstrations, expert explanations and approved project evidence, supported by captions, transcripts or useful on-page summaries. Preserve attribution, permissions and context.
These are ways to make evidence useful and understandable, not mandatory GEO formats or guarantees of AI citation. Never invent a statistic or add a table or video merely to appear optimised.
Our approach is informed by Google’s guidance on original, helpful content and AI features and website best practices.
See how a readiness project investigates information and evidence gaps.
Keep the wider AI information environment coherent
AIO considers the clarity and suitability of business information across relevant AI-assisted discovery and recommendation contexts. Within AISRO, it connects the other disciplines to the broader business information and operating environment.
We identify authoritative facts, ownership, update responsibilities and the limits of what can be verified. Where systems or processes need connecting, that becomes a defined implementation requirement.
What can be verified
Follow the evidence through four checkpoints. Open a step to see what should be available for review.
Implementation can be inspected. Rankings, AI citations and recommendations remain external outcomes and cannot be guaranteed.
01 · Define the baseline
Evidence to inspect: the original pages, business facts, source records and dated observations.
Review question: have we distinguished what was checked from what is assumed, and identified the owner of important information?
02 · Trace the decisions
Evidence to inspect: the prioritised gap register and the reason for each proposed action.
Review question: does the proposed product, service or project respond to the diagnosed requirement, with a clear boundary and acceptance condition?
03 · Check the implementation
Evidence to inspect: working pages and contextual links, accurate visible facts, and supported structured data that agrees with the page.
Review question: was the authorised change actually implemented and tested, and are any defects or dependencies still open?
04 · Review the observations
Evidence to inspect: the change record, repeatable checks and dated search or enquiry observations.
Review question: what changed, what remains uncertain and what deserves the next review? Separate implementation evidence from external outcomes we cannot control.
Start with the business requirement
Which situation sounds like yours? Select a starting point.
“I know visibility is a problem, but not why.”
Start with diagnosis before choosing the fix.
“I know what needs doing.”
Choose the relevant capability for a clear, bounded requirement.
“Our sector has specific customers and constraints.”
Frame the work around your industry, audience and evidence.
“Several capabilities need to work together.”
Explore a Solution Project such as AI Search Visibility & Readiness.
Unsure? Tell us what needs to improve.
Related solution pathways
AI Search Readiness
Find where business facts, website structure and supporting evidence break down, then scope the right response for search and AI readiness.
Explore ai search readiness
Project Evidence
Turn completed work into structured evidence that connects approved project facts, media and outcomes with the capabilities they genuinely demonstrate.
Explore project evidence
BAIMI
Translate a business requirement into a coordinated solution across systems, marketing, AI, people and delivery—with clear ownership and acceptance criteria.
Let’s clarify your visibility requirement
A few details will help us identify the right starting point. Open a selector to choose one or several options.