November 14, 2026

Technical SEO: How to Prepare Your Site for Google and AI

Learn technical SEO best practices to improve your Google rankings, site performance, and organic traffic with a practical checklist.

TechnologySEODocumentation

SEO (Search Engine Optimization) helps search engines discover, understand, and index your site.

Good SEO is not just about keywords. It combines technical SEO, content quality, accessibility, performance, and user experience.

This is a practical checklist you can apply to almost any site. At the end, you'll find a quick summary to save and a list of official sources.

Optimize Your SEO Tags
Open Graph and Social Sharing
Keywords and Search Intent
Technical Fundamentals: HTTPS, URLs, and Redirects
Accessibility and Semantic HTML
Optimize Images
Improve Core Web Vitals
Create a Sitemap.xml
Configure Robots.txt
Make Your Content Crawlable
Structured Data (JSON-LD)
Internal Links and Backlinks
Monitor Your SEO with Google Search Console
Google Analytics 4 (GA4)
Multilingual SEO (hreflang)
SEO and GEO (Generative Engine Optimization)

1. Optimize Your SEO Tags

HTML metadata helps search engines understand your pages and influences how your content can appear in search results.

Every important page should have a unique title and description.

<title>Technical SEO: How to Prepare Your Site for Google and AI</title>

<meta
  name="description"
  content="Learn technical SEO best practices to improve your Google rankings, site performance, and organic traffic with a practical checklist."
/>

<meta name="viewport" content="width=device-width, initial-scale=1" />

<link rel="canonical" href="https://roverx.dev/en/blog/seo-guide" />

Best practices:

Title: aim for 50 to 60 characters.
Description: aim for 150 to 160 characters.
Include your main keyword naturally.
Use unique metadata on every page.
Avoid keyword stuffing.
Set a canonical URL (rel="canonical") pointing to the preferred version of each page, avoiding duplicate content issues.
Include the viewport meta tag, which is the foundation of a responsive site and of Google's mobile-first index.

These character limits are recommendations, not Google ranking requirements. Also, Google often rewrites the snippet based on the user's query, so the meta description does not guarantee the text shown in results.

Keeping pages out of search results:

To prevent a page from appearing in results, use the noindex meta tag:

<meta name="robots" content="noindex" />

For non-HTML files, such as PDFs, the equivalent is the X-Robots-Tag HTTP header:

X-Robots-Tag: noindex

For noindex to work, the page must be crawlable. If it is blocked in robots.txt, Google will never see the tag (see section 9).

2. Open Graph and Social Sharing

Control how your content appears when shared on social networks and messaging apps.

<meta property="og:type" content="article" />
<meta property="og:site_name" content="RoverX" />
<meta property="og:url" content="https://roverx.dev/en/blog/seo-guide" />
<meta property="og:locale" content="en_US" />
<meta property="og:title" content="Technical SEO: How to Prepare Your Site for Google and AI" />
<meta property="og:description" content="Learn technical SEO best practices to improve your Google rankings, site performance, and organic traffic with a practical checklist." />
<meta property="og:image" content="https://roverx.dev/og.png" />

<meta name="twitter:card" content="summary_large_image" />

Use a high-quality preview image, ideally 1200 × 630.

The twitter:card tag defines the preview format on X (formerly Twitter). Without it, the link may appear in a smaller, less attractive format. The other twitter:* tags default to the Open Graph values.

Open Graph does not directly improve Google rankings, but it improves how your links look when shared.

3. Keywords and Search Intent

Technical SEO makes your site accessible to search engines. Content determines which searches your pages are relevant for.

Focus on answering what users are actually searching for.

For example:

Broad keyword	Long-tail keyword
SEO	Technical SEO checklist for developers
Images	How to compress images without losing quality
Next.js	How to generate a sitemap in Next.js

Best practices:

Choose one main search intent per page.
Include relevant keywords in titles, headings, and URLs.
Write descriptive, useful content.
Avoid repeating keywords artificially.
Connect related articles with links (see section 12).

Demonstrate experience and credibility (E-E-A-T):

Google describes content quality with the E-E-A-T concept: experience, expertise, authoritativeness, and trustworthiness. It is not a direct ranking factor, but it guides what Google considers trustworthy content. In practice:

Identify the author and create a page explaining who they are and what they have done.
Show real experience: your own examples, tests, results, and screenshots.
Cite reliable sources and keep information up to date.
Make it clear who is responsible for the site and how to contact them.

Useful keyword research tools include Google Keyword Planner, Ahrefs, and Semrush.

4. Technical Fundamentals: HTTPS, URLs, and Redirects

A few basics affect both crawling and user trust.

HTTPS:

Serve the entire site over HTTPS and redirect HTTP to it.
HTTPS is a lightweight ranking signal, but it is essential for visitor security and trust.

URL structure:

Prefer short, readable, descriptive URLs.
Use lowercase letters and hyphens to separate words.
Avoid unnecessary parameters and meaningless identifiers.
Example: /en/blog/seo-guide is better than /en/blog?id=4821.

Redirects and errors:

Use a 301 redirect when a URL changes permanently.
Avoid redirect chains (A → B → C).
Pages that don't exist should return a real 404 status. A "not found" page returning status 200 is a soft 404 and confuses search engines.

5. Accessibility and Semantic HTML

Accessible sites are easier to navigate, understand, and maintain. Semantic HTML also helps search engines interpret your content.

Best practices:

Use semantic elements: main, nav, article, section.
Keep a logical heading hierarchy (h1 → h2 → h3).
Provide descriptive alt attributes on images.
Use descriptive link text instead of "click here".
Ensure keyboard navigation and sufficient color contrast.

Example:

<main>
  <article>
    <h1>Technical SEO Guide</h1>

    <section>
      <h2>Image Optimization</h2>
      <img
        src="/seo-example.webp"
        alt="Google search results displaying a website"
      />
    </section>
  </article>
</main>

Accessibility is not a standalone Google ranking factor, but many accessibility practices coincide with SEO best practices.

6. Optimize Images

Large, unoptimized images increase page weight and can hurt loading performance.

Best practices:

Prefer modern formats such as WebP and AVIF.
Compress images before uploading them.
Use responsive images with srcset.
Set image dimensions to avoid layout shifts.
Lazy-load offscreen images, but not the main (LCP) image.

7. Improve Core Web Vitals

Google uses Core Web Vitals as part of its ranking systems. These metrics evaluate loading performance, responsiveness, and visual stability in real-world usage.

Metric	Threshold considered good
LCP – Largest Contentful Paint	≤ 2.5s
INP – Interaction to Next Paint	≤ 200ms
CLS – Cumulative Layout Shift	≤ 0.1

How to improve performance:

Reduce unnecessary JavaScript.
Optimize images and fonts.
Minimize render-blocking resources.
Use caching and a CDN when appropriate.
Avoid unexpected layout shifts.

Analyze your site with Google PageSpeed Insights.

Aim for good Core Web Vitals on both mobile and desktop. A perfect Lighthouse score does not guarantee a better ranking.

8. Create a Sitemap.xml

An XML sitemap helps search engines discover your site's important URLs.

On a multilingual site, each language version must have its own <url> entry, and all of them must list the same set of alternates, including their own URL and the x-default.

Example:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <url>
    <loc>https://roverx.dev/en</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://roverx.dev/en" />
    <xhtml:link rel="alternate" hreflang="pt" href="https://roverx.dev/pt" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://roverx.dev/en" />
  </url>
  <url>
    <loc>https://roverx.dev/pt</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://roverx.dev/en" />
    <xhtml:link rel="alternate" hreflang="pt" href="https://roverx.dev/pt" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://roverx.dev/en" />
  </url>
  <url>
    <loc>https://roverx.dev/en/blog/seo-guide</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://roverx.dev/en/blog/seo-guide" />
    <xhtml:link rel="alternate" hreflang="pt" href="https://roverx.dev/pt/blog/seo-guide" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://roverx.dev/en/blog/seo-guide" />
    <lastmod>2026-11-14</lastmod>
  </url>
  <url>
    <loc>https://roverx.dev/pt/blog/seo-guide</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://roverx.dev/en/blog/seo-guide" />
    <xhtml:link rel="alternate" hreflang="pt" href="https://roverx.dev/pt/blog/seo-guide" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://roverx.dev/en/blog/seo-guide" />
    <lastmod>2026-11-14</lastmod>
  </url>
</urlset>

Keep the sitemap up to date and include canonical, indexable URLs.

The lastmod property should reflect real content changes, since Google ignores it when it is unreliable. The priority and changefreq properties are ignored by Google, so they aren't worth your time.

Submit the sitemap through Google Search Console.

A sitemap helps with discovery, but it does not guarantee indexing.

The default sitemap route is usually /sitemap.xml, for example: https://roverx.dev/sitemap.xml.

9. Configure Robots.txt

The robots.txt file controls which URLs rule-following search engine crawlers may access. See Google's robots.txt documentation.

Example:

User-Agent: *
Allow: /
Disallow: /en/login
Disallow: /en/messages
Disallow: /pt/login
Disallow: /pt/messages

Sitemap: https://roverx.dev/sitemap.xml

The file must be accessible at:

https://roverx.dev/robots.txt

Important: robots.txt is not a security mechanism, nor a reliable way to prevent indexing. To keep a page out of search results, use noindex (see section 1). Protect private content with authentication.

AI crawlers:

AI companies often use different crawlers for different purposes, and blocking or allowing them is a choice between protecting your content and being cited in answers:

Training crawlers (such as GPTBot and CCBot) collect content to train models. Blocking them protects your content from that use.
AI search crawlers (such as OAI-SearchBot and PerplexityBot) fetch pages to cite them in answers. Blocking them may reduce your chances of appearing in those answers.

Example that blocks training and allows AI search:

# Model training: blocked
User-Agent: GPTBot
Disallow: /

User-Agent: CCBot
Disallow: /

# AI search: allowed
User-Agent: OAI-SearchBot
Allow: /

User-Agent: PerplexityBot
Allow: /

A few caveats:

A crawler that has its own group in the file (like OAI-SearchBot above) follows only that group's rules and ignores the User-Agent: * group. If you want to keep /login and /messages out of its reach, repeat the Disallow rules inside the group.
These controls depend on the crawler respecting robots.txt, which is voluntary.
Each company defines its own user agents, and they change over time. Check each company's documentation for the current list.
Google-Extended controls the use of your content in Google's AI products and does not affect your site's presence in Search. Blocking Googlebot, on the other hand, removes your site from Search.
If your goal is to be found, blocking AI search crawlers works against it (see section 16).

10. Make Your Content Crawlable

Google needs to access and understand your content before it can rank it.

For JavaScript-heavy applications, consider:

SSR: Server-Side Rendering.
SSG: Static Site Generation.
ISR: Incremental Static Regeneration.

Frameworks like Next.js, Nuxt, and Astro offer rendering strategies that are useful for SEO.

Make sure important content and navigation links are available in the rendered HTML, rather than depending entirely on client-side interactions.

11. Structured Data (JSON-LD)

Structured data describes your page in a format search engines can read without guessing. It can make pages eligible for rich results, such as breadcrumbs in the search snippet. Google recommends the JSON-LD format.

<script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@graph": [
      {
        "@type": "Article",
        "headline": "Technical SEO: How to Prepare Your Site for Google and AI",
        "image": ["https://roverx.dev/og.png"],
        "datePublished": "2026-11-14",
        "dateModified": "2026-11-14",
        "author": {
          "@type": "Person",
          "name": "Mathias Schulz",
          "url": "https://roverx.dev/en/about"
        },
        "publisher": {
          "@type": "Organization",
          "name": "RoverX",
          "logo": {
            "@type": "ImageObject",
            "url": "https://roverx.dev/logo.png"
          }
        }
      },
      {
        "@type": "BreadcrumbList",
        "itemListElement": [
          {
            "@type": "ListItem",
            "position": 1,
            "name": "Home",
            "item": "https://roverx.dev/en"
          },
          {
            "@type": "ListItem",
            "position": 2,
            "name": "Blog",
            "item": "https://roverx.dev/en/blog"
          },
          {
            "@type": "ListItem",
            "position": 3,
            "name": "SEO Guide"
          }
        ]
      }
    ]
  }
</script>

Best practices:

Mark up only content that is visible on the page.
Keep dates accurate and update dateModified only when the content actually changes.
Provide image as a list of URLs, preferably in more than one aspect ratio (such as 16:9, 4:3, and 1:1).
publisher is optional, but it helps associate the content with your organization.
Validate with Google's Rich Results Test and the Schema Markup Validator.

Structured data does not directly boost rankings and does not guarantee rich results. It helps search engines understand the page and makes you eligible for enhanced appearances.

12. Internal Links and Backlinks

Links help search engines discover content and understand the relationships between pages.

Internal links: connect related articles and important pages using descriptive link text.

Backlinks: earn links from relevant, trustworthy sites by publishing useful content, original research, or tools.

Avoid buying links or taking part in link schemes designed to manipulate rankings.

13. Monitor Your SEO with Google Search Console

SEO doesn't end after deployment.

Use Google Search Console to track your site's organic search performance.

Track:

Search impressions and clicks.
Click-through rate (CTR).
Average position.
Indexing and crawling issues.
Sitemap status.
Core Web Vitals reports.

Use the URL Inspection tool to diagnose why certain pages may not appear on Google.

14. Google Analytics 4 (GA4)

Google Analytics helps you understand how visitors interact with your site and which traffic sources bring users to your content.

Use Google Analytics 4 (GA4) to track:

Users, sessions, and page views.
Organic search traffic (google / organic).
Most visited landing pages.
Engagement rate and average engagement time.
Custom events and conversions.

Privacy: GA4 uses cookies and collects visitors' personal data. Privacy laws such as the GDPR (EU) and the LGPD (Brazil) require a legal basis for this, which is usually consent. Tell visitors about the use of cookies and let them accept or decline collection before enabling GA4.

15. Multilingual SEO (hreflang)

If your site supports multiple languages, such as English (/en) and Portuguese (/pt), help Google identify the correct version of each page.

Use hreflang to reference all available translations. See Google's documentation on localized versions.

<link
  rel="alternate"
  hreflang="en"
  href="https://roverx.dev/en/blog/seo-guide"
/>

<link
  rel="alternate"
  hreflang="pt"
  href="https://roverx.dev/pt/blog/seo-guide"
/>

<link
  rel="alternate"
  hreflang="x-default"
  href="https://roverx.dev/en/blog/seo-guide"
/>

Best practices:

Use separate URLs for each language.
Translate titles, descriptions, headings, and content.
Set the correct HTML language (lang="en" or lang="pt").
Include reciprocal hreflang references, including the self-reference.
Use a self-referencing canonical URL on each translated version.
Include both language versions in the sitemap.
Avoid automatically redirecting users based on IP address alone.

16. SEO and GEO (Generative Engine Optimization)

To understand what powers these systems, see the post on Artificial Intelligence.

GEO (Generative Engine Optimization) is the practice of making your content easy to find, understand, and cite in AI-generated answers, such as Google's AI Overviews and AI Mode, ChatGPT, and Perplexity. You'll also see the term AEO (Answer Engine Optimization) used with a similar meaning.

What Google says:

Google's official guidance on AI features in Search treats the topic as an extension of SEO, not a separate discipline. According to that guidance:

These features don't rely on a separate index. To appear in them, the page must be crawlable, indexable, and useful, as in any search.
You don't need llms.txt, Markdown pages, or "chunking" your content into short paragraphs.
There is no special schema that makes a site visible to AI, and structured data is not required.
Generic content that repeats what many sites already say tends to be worth less than original content.

In other words, everything in this guide applies to GEO as well.

What to add (practical suggestions, not official rules):

Open each section with a direct one- or two-sentence answer and leave the detail for later.
Use headings that match real user questions.
Bring your own data, examples, and experience instead of repeating what everyone already says.
Prefer verifiable facts, with sources and up-to-date dates.
Make the author and brand clear (see E-E-A-T in section 3) and seek mentions on other trustworthy sites.
Some AI crawlers don't run JavaScript or have limited rendering capability. Making the main content available in server-rendered HTML can therefore broaden compatibility (see section 10).

How to track:

Periodically ask AI engines about your topic and check whether your site is cited.
In GA4, watch for referral traffic coming from AI assistant domains.

Realistic expectations: no trick guarantees an AI will cite you. What works is the same foundation: a solid technical structure and genuinely useful, original content.

Quick Checklist

Before publishing a page, check:

Unique title and description, with the main keyword.
Canonical URL set and noindex only where necessary.
Open Graph and twitter:card with a 1200 × 630 image.
Site on HTTPS, with viewport and clean URLs.
Semantic HTML, correct heading hierarchy, and alt on images.
Compressed images (WebP/AVIF) with defined dimensions.
Core Web Vitals within good thresholds (LCP, INP, and CLS).
Content present in the rendered HTML (SSR, SSG, or ISR).
Sitemap up to date and submitted, robots.txt reviewed (including the decision on AI crawlers).
Sections that start with direct answers and content with your own data and experience (GEO).
Structured data validated and reciprocal hreflang.
Search Console and GA4 set up to track results.

Official Sources

SEO Starter Guide: Google's introductory SEO guide, covering the fundamentals discussed here.
AI Features and Your Website: Google's guidance on AI features in Search (section 16).
Introduction to robots.txt: how crawl control works (section 9).
Localized Versions: how to indicate language versions with hreflang (sections 8 and 15).

Remember: SEO is an ongoing process, not a one-time setup. Start with technically solid pages, publish useful content, measure the results, and keep improving.

Author

Mathias Artur Schulz

Senior Software Engineer

Bachelor's degree in Computer Science and Postgraduate degree in Software Engineering

Email:mathias@schulz.net.br

Technical SEO: How to Prepare Your Site for Google and AI

Table of Contents

1. Optimize Your SEO Tags

2. Open Graph and Social Sharing

3. Keywords and Search Intent

4. Technical Fundamentals: HTTPS, URLs, and Redirects

5. Accessibility and Semantic HTML

6. Optimize Images

7. Improve Core Web Vitals

8. Create a Sitemap.xml

9. Configure Robots.txt

10. Make Your Content Crawlable

11. Structured Data (JSON-LD)

12. Internal Links and Backlinks

13. Monitor Your SEO with Google Search Console

14. Google Analytics 4 (GA4)

15. Multilingual SEO (hreflang)

16. SEO and GEO (Generative Engine Optimization)

Quick Checklist

Official Sources

Mathias Artur Schulz