<!-- Canonical: https://www.aigentcy.com/blog/technical-seo-and-ai-search/ -->

# Technical SEO and AI search optimization: turn visibility into qualified demand

Fix the crawl and index faults first, write pages that people and AI assistants can read, cover the searches your main site was never built for, and judge the work by qualified enquiries.

Aigentcy 31 August 2026 13 min read Updated 7 September 2026

## Key takeaways

-   Write down what a qualified enquiry is before you spend on search. Everything else is measured against that definition.
-   Six crawl and index faults cause most lost visibility: bad canonicals, stale sitemaps, wrong robots rules, blocked assets, structured data that lies, and slow pages.
-   Google says its AI features need nothing beyond an indexed, snippet-eligible page. Clear headings, an answer near the top and honest structured data do the rest.
-   Your main site wins your brand and main services. A focused site per specific search topic covers the demand it was never built for.
-   Report impressions, qualified enquiries and assisted conversions as three separate numbers. A citation in an AI answer is not a lead.

**From a search to a qualified enquiry**

The count shrinks at each step, so each step needs its own number and its own owner. The figures are the article's worked example, not a result.

Your search report says impressions are up. Your sales team says the enquiries look the same as last quarter. Somewhere between those two numbers, the buyers you wanted went elsewhere.

Part of that gap is new. When Google shows an AI summary, people click a normal result on 8% of visits, against 15% without one, according to [Pew Research](https://www.pewresearch.org/short-reads/2025/07/22/google-users-are-less-likely-to-click-on-links-when-an-ai-summary-appears-in-the-results/). [Ahrefs](https://ahrefs.com/blog/ai-overviews-reduce-clicks/) measured a 34.5% lower click rate for the top result when an AI Overview appears.

So a page can rank, get read by a machine, and send you nothing.

The rest of the gap is old. Pages a crawler can’t reach, duplicate addresses that split credit, slow pages on phones, and copy that never answers the buyer’s question. This guide covers both halves of technical SEO and AI search optimization in the order to fix them, and ends with how to judge the work in enquiries rather than charts.

## What qualified demand means

Define the enquiry you want before touching the website. Agree it with whoever handles the leads, and write it down. Every later decision is measured against that sentence.

A workable definition has three parts:

-   **A need you serve.** The person wants something on your service list, in a form you deliver.
-   **A place you serve.** The right country, language or region.
-   **A plausible fit.** A company size, budget or timing your team would take on.

Everything outside that is either research traffic, which is useful and counted separately, or noise. Keep the two apart in every report. Mixed together, the noise hides the signal.

| Demand type | Example search | What to measure | How to report it |
| --- | --- | --- | --- |
| Branded | “your company name reviews” | Share of brand searches that land on your pages | Protect it. Don’t count it as growth |
| Service intent | “payroll outsourcing cost” | Qualified enquiries per hundred visits | The number the programme is judged on |
| Research | “what is a service level agreement” | Return visits and next-page clicks | A capacity measure. Never a lead count |
| Wrong fit | Outside your region or offer | Count and cause | Filter it, then check the page that attracted it |

## The crawl and index faults that break most often

Google has to find a page, fetch it, render it and decide to keep it before anyone can search for it. Each step has a common way to fail. And most of those failures are invisible from a browser, which is why they last for months.

| Fault | What it costs you | How to check | The fix |
| --- | --- | --- | --- |
| Canonical URLs. Several addresses for one page: with and without www, trailing slash, tracking parameters | Links and signals split across copies. Google picks one address, sometimes the wrong one | Search Console URL inspection shows the Google-selected canonical | One address per page, redirect the rest, rel="canonical" on the page. Google ranks redirects strongest, then the canonical tag, then sitemap inclusion |
| Sitemaps. Missing, stale, or listing redirects, errors and pages marked noindex | New pages take weeks to appear. Crawl effort goes to dead addresses | Open the sitemap. Every listed page should return 200 and be indexable | Generate it from the build with a real last-modified date, then submit it in Search Console |
| Robots rules. A staging Disallow: / copied to production, or bot protection at the CDN blocking Googlebot | Pages vanish or show with no description | Fetch /robots.txt. Test a key page in URL inspection | Allow crawling. Use noindex for pages you want kept out, because robots.txt is not a way to hide a page |
| Blocked assets. CSS or JavaScript files disallowed, or content that only appears after a script runs | The rendered page is empty to the crawler. Google won’t render JavaScript from blocked files | Turn JavaScript off and read the page | Serve the main content in the HTML. Allow the assets |
| Structured data. Markup that disagrees with the visible text, or fails validation | No rich results, and a trust problem if it claims things the page doesn’t say | Google’s Rich Results test | Keep to types you can keep true (Organization, Article, FAQ) and match the visible text |
| Page speed. Slow largest paint, slow response to taps, layout that jumps | Buyers leave, and Core Web Vitals feed ranking | Search Console’s Core Web Vitals report and Lighthouse | Right-sized images, fewer third-party scripts, stable layout |

The speed thresholds are public. Google’s [Core Web Vitals](https://web.dev/articles/vitals) call a page good when the largest content paints within 2.5 seconds, input gets a response within 200 milliseconds and the layout shift score is 0.1 or lower.

For scale, the [2024 Web Almanac](https://almanac.httparchive.org/en/2024/performance) found 43% of sites passed all three on mobile. So a fast site is still a minority position.

### A technical SEO checklist you can hand to your web team

Ask for a yes or a fix on each line. None of them needs an SEO specialist to check.

1.  Every page has one address, and the other variants redirect to it.
2.  The sitemap lists only live, indexable pages and carries real modified dates.
3.  `robots.txt` on production allows crawling of the pages that sell.
4.  A key service page reads correctly with JavaScript turned off.
5.  Structured data validates and says nothing the page doesn’t say.
6.  The largest paint on the service pages is under 2.5 seconds on a phone.
7.  The whole site is served over HTTPS with no mixed content.
8.  The contact form on a phone works, and the submission reaches the team that answers it.
9.  Search Console is verified and someone reads the coverage report monthly.
10.  A test enquiry sent today shows up in the CRM with the page it came from.

Rank the fixes by the journey each fault interrupts. Fix a blocked service page that buyers land on before a missing alt text on a page nobody visits. Group related faults, name an owner and verify the repair on a phone as well as a desktop.

## How AI assistants and AI search read a page

Google’s position is short. Its [guidance on AI features](https://developers.google.com/search/docs/appearance/ai-features) says there are no additional requirements to appear in AI Overviews or AI Mode. A page must be indexed and eligible to show with a snippet. The same document says you don’t need new machine-readable files or special schema for these features. So the checklist above is the entry ticket.

But the features read differently from a classic result. Google describes a “query fan-out”: the system issues several related searches on sub-topics and assembles an answer from the passages it finds. A page wins a citation when one of its passages answers one of those sub-questions cleanly.

How a page reaches an AI answer

```mermaid
flowchart TD
accTitle: How a page reaches an AI answer
  A[Page published] --> B{Crawl allowed?}
  B -->|No| X[Invisible to search]
  B -->|Yes| C[Rendered and indexed]
  C --> D{Snippet eligible?}
  D -->|No| X
  D -->|Yes| E[Query fan-out]
  E --> F{Passage answers a sub-question?}
  F -->|Yes| G[Cited with a link]
  F -->|No| H[Ranked but not cited]
```

That changes how a page should be written. The principles below are public guidance, and they help human readers for the same reasons.

-   **Headings that state the question.** “How much does a POS system cost” beats “Pricing considerations”. A crawler and a buyer both scan headings first.
-   **The answer near the top.** The first paragraph under a heading gives the answer. Detail, caveats and evidence follow it.
-   **FAQ blocks with real answers.** Two or three sentences per answer, in the words a buyer would use. A question with a one-line brush-off earns nothing.
-   **Structured data that matches the page.** Article, FAQ and Organization types, saying exactly what the visible text says.
-   **Key content as text.** Prices, service scope and locations in HTML, never only in an image or a PDF.
-   **Pages that read without JavaScript.** Not every assistant runs a browser. Google does. Others fetch the HTML and read what’s there, so server-rendered pages travel further.
-   **Deliberate preview controls.** `nosnippet`, `max-snippet` and `noindex` limit what Google shows. `Google-Extended` limits training and grounding in Google’s other products and, by Google’s account, has no effect on Search. Decide, rather than inherit a default.

**What each reader takes from a page**

An AI answer is assembled from passages, so the passage that answers the question has to be findable under the heading that names it. The same layout is what a buyer scans on a phone.

Other assistants publish their own crawler rules and they change often. Check each one’s current documentation before you pay for “generative engine optimization” as a separate service. Ask the seller which of the principles above the work would change, and what evidence would show it helped.

| Reader | What it needs from the page | What breaks it |
| --- | --- | --- |
| Google’s crawler | Crawl allowed, HTML content, one canonical address | Robots blocks, blocked assets, duplicate URLs |
| Google AI Overviews and AI Mode | An indexed, snippet-eligible page with a clear passage per question | Long build-ups, answers buried in the middle, nosnippet set by accident |
| Other AI assistants | Server-rendered text a simple fetch can read | Content that appears only after scripts run |
| A buyer on a phone | A fast page, a readable answer, a form that works | Slow paint, tiny tap targets, a form that fails silently |

## Focused sites and branded keyword coverage

Your website already wins the searches it was built for: your brand and your main services. Buyers also search for something specific, such as “POS system for restaurants” or “payroll outsourcing costs”. Google answers each of those with a page about exactly that thing. And the winning page often sits on a site about that one topic.

A focused site, often called a micro site, is one domain about one service or search topic. It carries a handful of pages that answer the buyer’s questions on that topic, its own enquiry form, and your brand. Your main site stays what it is. The focused site covers demand the main site was never built to chase.

Branded keyword coverage is the other half. People search your brand plus a word: “\[brand\] pricing”, “\[brand\] reviews”, “\[brand\] alternatives”. If you have no page for those searches, a review site or a competitor answers them for you. Cover them with pages you control, so the first thing a buyer reads about your pricing comes from you.

**Your website plus focused sites, one enquiry inbox**

The main site keeps the brand and main-service searches and lends its colours, logo and tone to the focused sites. Every enquiry from any of them arrives with the page and search that earned it.

### When a focused site is the wrong tool

The choice depends on how much a topic has to say. This is the one place where the site-versus-page decision matters, so decide it per topic.

| Situation | Better choice | Why |
| --- | --- | --- |
| The topic fits on one page | A page on your main site | It inherits the site’s existing authority and links |
| The topic is a service with its own buyer questions, pricing and comparisons | A focused site | The whole domain is about the thing the buyer typed |
| Brand-plus-word searches | Pages on your main site, or one brand site | The brand carries the ranking. The page supplies the answer |
| Many topics, same copy with a name swapped | Neither | Google’s scaled content abuse policy covers many pages that add no value, however they were produced |

We build [Flotta](https://www.flotta.ai/) for the second row. It reads your existing website for brand, colours and tone, maps the searches your customers make into topics, and builds and runs a focused site for each one with its own enquiry form.

Every page passes automated checks and a second-model review before you approve it. Every enquiry arrives with the page and search that earned it. The options look like this side by side:

| Option | Who does the work | Time until pages are live | Quality control | Do you know which page earned each lead? |
| --- | --- | --- | --- | --- |
| Your website as it is | Nobody new | Already live | Your existing review | Depends on the tracking in place |
| An agency | The agency’s team | After briefs, drafts and revisions | Experienced people review each page | If attribution is in the brief |
| A content hire | One writer | One page at a time | Self-edited unless you review | If they wire up the tracking |
| Focused sites run by a platform | The platform runs, you approve | After generation passes the checks | Automated checks, a second-model review, your approval | Every lead carries its page |

## How to measure

Treat visibility, visits and enquiries as three separate numbers with three separate owners. A citation can happen without a visit. A visit can help a reader without producing an enquiry. And an enquiry can look fine until sales finds it’s outside your region.

| Measure | Definition | Source | What it can’t tell you |
| --- | --- | --- | --- |
| Impressions | Times a page appeared in results, including AI features | Search Console, Web search type | Which impressions were inside an AI answer. Google reports them together |
| Sampled AI appearances | Whether you appear for a fixed set of buyer questions, checked on a schedule | Your own log of questions, dates and cited pages | Market-wide visibility. It’s a sample under recorded conditions |
| Qualified enquiries | Form, call or email that meets your written definition | CRM, with the source page and search term attached | Whether the page caused the decision or confirmed it |
| Assisted conversions | An enquiry that came by phone or direct visit after an earlier session read a search page | Analytics attribution with a stated lookback window | Certainty. Label it assisted and keep it separate |

Sample AI answers the same way each time. Choose the questions before looking at the results, include early and late stages of the decision, record the date and wording, and keep the misses. Swapping hard questions for ones that already show you is the fastest way to fool yourself.

A worked example shows why the stages need separate numbers. These are assumptions for the arithmetic, and they are neither a customer result nor a benchmark.

| Scenario | Visits per month | Enquiry rate | Enquiries | Qualified share | Qualified enquiries | Cost per qualified enquiry at EUR 1,500 per month |
| --- | --- | --- | --- | --- | --- | --- |
| Today | 2,000 | 1.0% | 20 | 40% | 8 | EUR 188 |
| Better pages, same traffic | 2,000 | 1.5% | 30 | 50% | 15 | EUR 100 |
| More traffic, same pages | 3,000 | 1.0% | 30 | 40% | 12 | EUR 125 |

The middle row wins without any extra traffic. That is the usual shape: the pages and the fit move the number more than the volume does. Don’t extend it to revenue without win rates and deal sizes from your own CRM.

## Start with one enquiry journey

Pick one service and follow its journey from a search to a qualified enquiry in the CRM. Run the checklist on the pages involved, fix what interrupts the journey, and send a test enquiry through to the team. Our [lead generation automation case study](https://www.aigentcy.com/case-studies/odoo-lead-generation-automation/) shows what the handover into a CRM looks like when it works.

Then look at the searches that journey misses. If a topic has its own buyer questions, give it a focused site. If it is one page’s worth, write the page. Either way, the enquiry definition from the first section decides whether it worked.

Bring three things to the next review:

-   The affected pages and the faults found on them.
-   A sample of qualified and unsuitable enquiries from the same period.
-   The agreed baseline for impressions, enquiries and qualified enquiries.

If you want the focused sites run for you, [Flotta](https://www.flotta.ai/) does that work and returns each enquiry with its source. If the bottleneck is what happens after the enquiry arrives, our [process automation](https://www.aigentcy.com/services/process-automation/) team handles the routing, the CRM and the follow-up.

## Frequently asked questions

Is AI search optimization different from normal SEO?

For Google, no. Its own guidance says there are no additional requirements to appear in AI Overviews or AI Mode beyond being indexed and eligible for a snippet. What changes is how the page is read: AI features assemble answers from passages, so a page needs a clear answer under a clear heading rather than a long build-up.

Should we fix technical SEO or publish more content first?

Fix the faults that stop buyers reaching or using the pages you already have. A blocked page, a broken contact form or a canonical pointing at the wrong address wastes every new article you publish. Once the journey works, add pages for the buyer questions you can't answer today.

How do we know if AI assistants cite us?

Google reports AI Overview and AI Mode traffic inside the ordinary Web search type in Search Console, so you can't separate it there. Sample a fixed set of buyer questions on a schedule, record whether you appear and which page is cited, and keep the misses as well as the hits.

Do micro sites hurt our main website?

Not when each one covers a distinct search topic with pages written for that topic. Your main site keeps its brand and service searches. Problems start when many sites carry the same copy with a name swapped in, which Google treats as scaled content abuse.

What should a technical SEO audit give us?

A short list of faults ranked by the buyer journey each one interrupts, an owner for each fix, and a way to verify the repair. A report with three hundred warnings and no ranking is a data export.

## Related reading

-   [AI content quality at volume: expertise in, drafts out](https://www.aigentcy.com/blog/ai-generated-content-quality/)A cheap draft can be expensive to approve. Put the expertise in before the machine writes, let deterministic checks and a critic reject what fails, and measure cost per approved article.
-   [AI cost management: what an accepted result costs](https://www.aigentcy.com/blog/enterprise-ai-cost-control/)How to report AI spend the way finance reports everything else: by team, by workflow and by accepted result, with unknown charges kept separate from zero.
-   [An AI governance framework your team can operate](https://www.aigentcy.com/blog/enterprise-ai-governance-framework-guide/)A decision guide for the people who sign off AI systems: how much governance each one needs, who does what in the first 90 days, what it costs to run, and the evidence that proves the rules were followed.
-   [Lead qualification and follow-up in Odoo](https://www.aigentcy.com/case-studies/odoo-lead-generation-automation/)Case study

[See Flotta, our SEO and content platform](https://www.flotta.ai/) [Talk to us about your project](https://www.aigentcy.com/contact/)