AI optimisation
AI technical requirements
On this page
- Crawlability for AI bots
- How structured data helps AI understand your content
- Implement and validate structured data
- How to signal E-E-A-T technically
- Author information should be visible on the page
- How to make your company information easy to find
- HTTPS provides basic trust
- How to show update dates
- Speed and performance can affect crawling
- Core Web Vitals
- Shorten the server response time
- Build the site mobile-first and responsive
- Make the site mobile-friendly
- Technical checklist for AI optimisation
- The technical foundation needs ongoing maintenance
- The next step is the content
- Need help with technical implementation?
Good content is not enough if AI tools cannot find it, understand it or trust it.
AI optimisation requires a solid technical foundation
- Crawlability: can AI bots reach your content?
- Structured data: does AI understand what the content is about?
- E-E-A-T signals (experience, expertise, authoritativeness and trustworthiness): does AI trust you as a source?
- Speed and performance: does the site work quickly for visitors and search engine crawlers?
The basic requirement for Google’s AI features is that the page is indexed and eligible to be shown with a snippet. Everything else is good technical SEO that makes the content easier to find and understand.
Crawlability for AI bots
Can AI tools reach your content?
Before AI can cite you, it has to find your content. Technical shortcomings often block AI bots from crawling important pages.
Review robots.txt
Check that robots.txt does not block important pages or resources.
Common problems
Blocking the whole site
User-agent: *
Disallow: /That rule is often correct on staging sites but forgotten when the site goes live.
Blocking important sections
User-agent: *
Disallow: /blog/If your most citable content is in the blog, you are preventing AI from seeing it.
Blocking resources AI needs
User-agent: *
Disallow: /css/
Disallow: /js/AI tools (Google in particular) need to be able to read CSS and JavaScript to render pages correctly.
What to do
Review robots.txt regularly. Make sure that
- No important pages are blocked
- CSS, JavaScript and image resources are accessible
- Only unimportant pages (admin, duplicate content) are blocked
How to control which AI bots reach your site
Each AI service has its own user agent that you can address in robots.txt, and each one controls something different:
- OAI-SearchBot controls visibility in ChatGPT search. Blocked sites are not shown in ChatGPT’s search results, other than as navigational links.
- GPTBot collects content that may be used to train OpenAI’s models. The two bots are controlled separately, so you can allow OAI-SearchBot and block GPTBot.
- ChatGPT-User visits pages when a user asks ChatGPT to. Robots.txt does not always apply to such visits.
- PerplexityBot controls visibility in Perplexity’s search results and is not used to train models.
- Google-Extended controls whether content may be used to train Gemini and to ground answers in the Gemini apps and Vertex AI. It does not affect Google Search.
For AI Overviews, AI Mode and AI features in Discover, there is a separate control in Search Console, under Settings. There you can choose whether the site should be included.
Create a well-structured XML sitemap
A well-structured sitemap helps AI bots find all your important content.
How to build the sitemap
- Include only important pages, the ones you want AI to index
- Exclude 404s and redirects: update the sitemap when pages are removed
- Keep the sitemap current: add new pages automatically
- Use the correct URL format: https:// and consistently with or without a trailing slash
- Include lastmod (last modified): it helps AI understand what has been updated
Example of a correct sitemap entry
<url>
<loc>https://example.com/guide/seo-grunderna</loc>
<lastmod>2026-01-15</lastmod>
</url>Submit the sitemap to
- Google Search Console
- Bing Webmaster Tools
- Any other search engines you want to reach
Link internally to important pages
Internal links help search engine crawlers find your pages.
Make sure that
- All important pages have internal links (not just a place in the sitemap)
- There are no “islands” (pages that can only be reached via a direct link)
- Important pages can be reached in a few clicks from the home page
- Link text is descriptive (not “click here”)
Pages that are buried deep or lack internal links are crawled less often.
JavaScript rendering can hide content from bots
For JavaScript-heavy sites (React, Vue, Angular), the question is whether AI bots can render the content.
Problem
If all content is added via JavaScript after the HTML has loaded, some bots cannot see it.
Solutions
- Server-side rendering (SSR): the content is in the initial HTML
- Static site generation (SSG): pre-generated HTML pages
- Prerendering: generating HTML for bots
Test: use Google’s URL Inspection Tool in Search Console to see how Google renders your page. Other AI bots may behave differently, so also check that the most important content is in the HTML the server sends.
Any text that users can see should also appear in the rendered HTML.
How structured data helps AI understand your content
Structured data (schema markup) tells search engines explicitly what different parts of the content mean.
What structured data does for you
Google does not require structured data for its AI features. The markup is part of the standard SEO foundation and shows search engines more clearly:
- Is this an article? A product page? An FAQ?
- Who is the author?
- When was it published?
- What is the main image?
Which schema types are worth using?
Article schema
For blog posts, guides and articles.
Add the properties that suit the content
headline: the article’s titleauthor: the author (Person or Organization)datePublished: publication datedateModified: last updated (if the article has been revised)image: main image (URL)publisher: the publishing organisation
Example (JSON-LD format)
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Komplett guide till SEO 2026",
"author": {
"@type": "Person",
"name": "Anna Example",
"url": "/team/anna-example"
},
"datePublished": "2026-01-10",
"dateModified": "2026-01-28",
"image": "/images/seo-guide-2026.jpg",
"publisher": {
"@type": "Organization",
"name": "Example Company Ltd",
"logo": {
"@type": "ImageObject",
"url": "/logo.png"
}
}
}Organization schema
For company information (usually on the home page or About us page).
Why it matters
It strengthens E-E-A-T by clearly defining who is behind the content.
Include
name: company nameurl: websitelogo: logocontactPoint: contact informationsameAs: social media and other profiles
Example
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Company Ltd",
"url": "https://www.example.com",
"logo": "/logo.png",
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+46-8-XXXXXX",
"contactType": "Customer Service"
},
"sameAs": [
"https://www.linkedin.com/company/examplecompany",
"https://www.facebook.com/examplecompany"
]
}Person schema
For author profiles.
It strengthens E-E-A-T by showing who is writing and what background the writer has.
Include
name: the author’s namejobTitle: title or roleworksFor: organisationsameAs: LinkedIn, Twitter and similardescription: short biography
Example
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Anna Example",
"jobTitle": "SEO specialist",
"worksFor": {
"@type": "Organization",
"name": "Example Company Ltd"
},
"sameAs": [
"https://www.linkedin.com/in/anna-example"
],
"description": "SEO specialist with 15 years of experience in search engine optimisation and digital strategy."
}Implement and validate structured data
JSON-LD is the first choice
Google recommends the JSON-LD format (as in the examples above).
Why
- Easier to implement (goes in a
<script>tag) - Kept separate from the HTML structure
- Easier to maintain
Place it in: <head> or at the end of <body> on the relevant page.
Always validate
Use Google’s Rich Results Test: https://search.google.com/test/rich-results
Make sure that there are
- No errors (these must be fixed)
- As few warnings as possible (these should be fixed)
- All required properties for the type in question
Common errors
- Missing required fields for the type in question
- Incorrect URL formats
- Dates that are no longer current
- Image URLs that do not work
How to signal E-E-A-T technically
Beyond the content itself, there are technical ways to signal expertise, authority and trust.
Author information should be visible on the page
Show the author on every article
Include
- The author’s name (visible on the page)
- A link to the author’s bio page
- A short description or title
Example
<div class="author-info">
<img src="/images/anna-example.jpg" alt="Anna Example">
<p>Written by <a href="/team/anna-example">Anna Example</a></p>
<p>SEO specialist with 15 years of experience</p>
</div>Mark up the author in structured data
Connect the article to Person schema (see above).
That way you tell search engines explicitly who wrote the content.
How to make your company information easy to find
Create a proper About us page
The page should include
- Company history
- Team (with photos and backgrounds)
- Contact information
- Company registration number (organisationsnummer, for Swedish companies)
Show contact information on every page
Place in the footer
- Address
- Phone
- Company name and registration number
A dedicated contact page
- More ways to get in touch
- A map, if useful
- Opening hours, where relevant
HTTPS provides basic trust
An SSL certificate is in practice a requirement: without one, browsers warn visitors that the site is not secure. HTTPS is also a lightweight ranking signal in Google Search, so sites without it can rank slightly worse.
Make sure you have
- A valid SSL certificate
- All pages on HTTPS (not just the home page)
- No mixed content warnings (HTTP resources on an HTTPS page)
- HTTP redirected to HTTPS (301 redirect)
Test: visit your site with https://. The browser should show a padlock.
How to show update dates
Show the dates on the page
Show both the publication date and the update date:
Example
<p>Published: 10 January 2026</p>
<p>Last updated: 28 January 2026</p>Include the dates in structured data
Use both datePublished and dateModified in Article schema.
Why
If an article from 2020 was updated in 2026, you want search engines and AI tools to know.
Speed and performance can affect crawling
Slow server responses can cause Google to crawl less. Above all, fast pages give visitors a better experience.
Core Web Vitals
Core Web Vitals measure how real visitors experience a page’s loading, interactivity and visual stability.
LCP (Largest Contentful Paint)
Target: under 2.5 seconds
How quickly does the main content load?
Optimise
- Compress images
- Use a CDN
- Minify CSS/JS
- Lazy-load images further down the page
INP (Interaction to Next Paint)
Target: under 200 milliseconds
How quickly does the page respond to interaction?
Optimise
- Reduce JavaScript execution time
- Defer non-critical JavaScript with the defer attribute
- Code splitting
CLS (Cumulative Layout Shift)
Target: under 0.1
Does the content move around while the page loads?
Optimise
- Set width and height for images
- Reserve space for dynamic content
- Font-display: swap for web fonts
Shorten the server response time
Target for TTFB (Time To First Byte): under 0.8 seconds. TTFB is not part of Core Web Vitals.
Optimise
- Fast hosting
- Caching (server-side and CDN)
- Database optimisation
- Efficient code
Measure with
- Google PageSpeed Insights
- WebPageTest
- Search Console (Core Web Vitals report)
Build the site mobile-first and responsive
Google primarily indexes the mobile version.
Make the site mobile-friendly
Have the same content on mobile and desktop
Whatever is on desktop must also be on mobile.
Common problems
- Important text that only exists in the desktop version
- Images missing on mobile (to save bandwidth)
- Structured data missing on mobile
If content is on desktop but not on mobile, AI may miss it.
How to test responsive design
The site should work well on all screen sizes.
Test on
- Real mobile devices (not just simulation on desktop)
- Different screen sizes (phones, tablets)
- Both portrait and landscape orientation
How to check mobile usability
Check the mobile version with
- Lighthouse in Chrome
- The Core Web Vitals report in Search Console
Fix the problems the tools report.
Technical checklist for AI optimisation
Check the following when you prepare the site technically for AI visibility:
Crawlability
- Robots.txt does not block important pages
- XML sitemap up to date and correct
- All important pages have internal links
- JavaScript renders correctly (if relevant)
Structured data
- Article schema on articles/blog posts
- Organization schema on the home page/About us
- Person schema on author profiles
- All schema types validated without errors
E-E-A-T signals
- Author information visible on articles
- Author markup in structured data
- A clear About us page with team information
- Contact information in the footer
- HTTPS enabled across the whole site
- Update dates visible and correct
Performance
- Core Web Vitals in the green (LCP, INP, CLS)
- Server response time under 0.8 seconds
- Images optimised and lazy-loaded
- CSS/JS minified
Mobile-first
- Content parity between desktop and mobile
- Responsive design works on all devices
- No mobile issues in Lighthouse or the Core Web Vitals report
The technical foundation needs ongoing maintenance
Technical AI optimisation is not a one-off job.
What you should check regularly
Monthly
- Validate structured data (it may have broken during updates)
- Check Core Web Vitals
- Review the mobile version in Lighthouse
Quarterly
- Update Organization schema if the company information has changed
- Review author profiles (new staff, updated credentials)
- Check that robots.txt is still correct
After major updates
- Test that structured data works after a CMS update
- Verify that rendering still works
- Check that important pages are not accidentally blocked
The next step is the content
With the technical foundation in place, you can focus on creating content that AI cites.
Our guide to AI content methodology shows how to create content worth citing, based on structure, E-E-A-T and fact density.
Need help with technical implementation?
We implement structured data, improve crawlability and strengthen E-E-A-T signals for better AI visibility.
Want to know where you stand today?
Call us, or fill in the form and we will get back to you.