SEO: build a sound search foundation
Audit crawling, indexation, rendering, canonical URLs, sitemaps, internal links and performance. Map relevant queries to useful pages, then implement the technical and on-page fixes.
SEO, AEO & GEO services.Make your expertise discoverable.
Technical SEO, answer engine optimization and generative engine optimization for business websites. Connect crawlable pages, useful answers and credible sources to the enquiries that matter.
Plan your projectFrom your workflow to a working system
- 1Search intent
- 2Useful, accessible content
- 3Measured discovery
The right scope.
Built around your needs.
Start with the problem that matters. Combine the capabilities your project needs, with boundaries agreed before the build.
AEO: answer the buyer’s actual question
Organize service pages, comparisons and guides around clear questions and direct, supported answers. Improve headings, definitions and visible evidence so readers can understand each answer in context.
GEO: make expertise easier to reference
Clarify your business identity, original expertise and source-backed claims. Review crawler access and content availability for AI search, with structured data that matches what visitors can see.
Measurement: connect visibility to enquiries
Establish a baseline for qualified organic traffic and conversions. Track a defined set of queries, answer mentions and source citations over time, recording platform, date and testing conditions.
One foundation. Three discovery goals.
SEO, AEO and GEO share the same website and business facts. Inspect each layer to see its role and the evidence to review.
SEO: its responsibility
Make important pages accessible, indexable and relevant to the searches your audience uses. Connect page content to a clear conversion path.
What to review
Inspect server HTML, canonical URLs, sitemap coverage, internal links, search queries and the available traffic and enquiry baseline.
Illustrative planning model. Your architecture and deliverables are agreed during scoping.
See where
it could take you.
Illustrative applications to help shape your brief. These are possible project scopes, not customer case studies.
The starting point
Your website describes what you do, but buyers cannot find the page that answers their problem.
The approach
Map commercial search intent to services, improve the page hierarchy and repair crawlability, metadata and internal links. Give each page a relevant next step.
What the work can produce
A prioritized audit, an agreed set of implemented page improvements and a baseline for qualified enquiries. Illustrative scope, not a ranking forecast.
Start where
your project is.
The first step depends on what is already known. These starting points help define an engagement; scope, price and timing are agreed separately.
Explore an uncertain idea
The problem is clear, but the approach is not.
- 1Question
- 2Prototype
- 3Decision
What you take forward
A bounded experiment, findings and a recommendation on what to validate next.
A prototype is not a production-ready service.
Deliver a defined scope
You know the workflow and can agree acceptance checks.
- 1Scope
- 2Build & review
- 3Handover
What you take forward
Agreed deliverables, verification evidence and operating instructions for the scoped release.
Changes to scope need an explicit decision on cost and timing.
Improve an existing system
A live system needs focused changes or ongoing care.
- 1Review
- 2Prioritize
- 3Release & observe
What you take forward
A prioritized backlog, reviewed changes and an agreed maintenance or support boundary.
Coverage, response targets and access are agreed per engagement.
A clear path.
Through the work.
Scope and deliverables are agreed for each project. These stages guide the conversation.
- 1
Establish the baseline
Agree the audience, priority services, markets and conversion goals. Review the website and available Search Console, analytics and content evidence.
- 2
Implement the priorities
Fix the highest-impact technical issues and improve the agreed pages. Keep recommendations tied to search intent, accurate business facts and maintainable content.
- 3
Verify and review
Check server-rendered pages, metadata, schema, links and mobile behavior. Compare results with the baseline and agree the next changes from the evidence.
Evidence for the work. Tools for the question.
Technology is a scoping decision. These are relevant tools and building blocks to discuss against your existing systems, operating constraints and maintenance needs.
Search evidence
Search ConsoleAnalyticsCrawl reports
Use available account evidence to distinguish indexing problems, query relevance and conversion performance before prioritizing work.
Website implementation
Server-rendered HTMLJSON-LDPerformance checks
Verify the content people and crawlers receive. Use structured data that describes visible information and check the actual mobile experience.
Answer visibility
Query setsCitation logsContent reviews
Use dated, repeatable samples to review answer quality, business mentions and linked sources. Keep these measures separate from organic leads.
What should be checked
before handover.
Turn quality expectations into reviewable evidence. The exact checks and responsibilities belong in the project scope.
Reviewable technical changes
Check status codes, canonicals, sitemap entries, metadata, rendered headings and internal links against the agreed page inventory.
Accurate, useful content
Review business facts, answer context, authorship and supporting sources. Avoid fabricated proof, keyword stuffing and unsupported claims.
Comparable measurement
Document baseline dates, data access and query conditions. Report what changed and what remains uncertain, alongside qualified conversions where measurable.
Before
we begin.
Practical answers to help turn your idea into a scope everyone understands.
What is the difference between SEO, AEO and GEO?
SEO improves a website’s technical foundations and relevance for organic search. AEO organizes useful answers to specific questions. GEO focuses on making accurate, credible information accessible for generative search experiences. They overlap and work from the same content and technical foundation.
Can you improve our existing website?
Yes. We can start with an audit and targeted implementation on your existing stack. A rebuild is only considered when the evidence shows that the current setup blocks the agreed requirements.
Do you guarantee rankings or citations in AI answers?
No. Search rankings, AI mentions and source citations are controlled by the platforms and can change. We agree the work, deliverables and measurement approach, rather than promising a specific position or inclusion.
Do AEO and GEO require special schema or an llms.txt file?
There is no special schema required for Google’s generative search features. Accurate structured data can describe visible content; it does not guarantee inclusion. An llms.txt file can be an optional discovery document for tools that use it, rather than a substitute for accessible HTML or an established ranking requirement.
What do you need to scope the work?
Share your public website, target audience, markets, priority offerings and desired enquiries. Available Search Console and analytics reports help establish a baseline. Read-only access can be arranged during the project; do not put credentials or confidential reports into a public brief.
Can this be an audit or an ongoing engagement?
We can scope a one-off audit, audit plus implementation, or recurring content and technical reviews. Deliverables, access, reporting cadence and pricing are agreed for the project.
Often better together.
Still have questions?
Start with the brief.
Bring the problem you want solved. We’ll shape it into a project brief you can keep — or let AI draft a first approach.