🏷 Markup for Bots: Title, Description, and H1-H6 Hierarchy

The search bot doesn't look at your site through human eyes. It doesn't appreciate how beautifully the fonts are chosen. The bot parses the HTML code. To help it quickly understand the page, the code provides special meta tags.

1️⃣ Title Tag — The Main Heading

This is the most critical element of on-page optimization. It's what appears in blue in Google's search results and on the browser tab.

• Length — about 60 characters (so it doesn't get cut off)
• Concise, contains the main keyword
• One per page

For the algorithm, Title is the main identifier of the page.

Code example:

<title>Rent Server with GPU RTX 5090 — Helsinki from $99/mo</title>

2️⃣ Description Tag

This is the couple of lines of grey text under the Title in search results. Description today has almost no direct impact on algorithm position. But it impacts CTR (Click-Through Rate).

This is your sales pitch. If you write: «10% off if ordered before Friday. Fast setup» — a real person is more likely to click your site over a competitor's.

Code example:

<meta name="description" content="GPU server rental from $99/mo. RTX 5090, free setup, 10% off until Friday.">

3️⃣ H1-H6 Hierarchy — Heading Structure

Imagine complex technical documentation. It always has a clear structure: main heading, sections, subsections. Tags H1-H6 do the same job.

• H1 — title of the entire article (only one per page)
• H2 — major semantic blocks
• H3 — sub-sections within H2
• H4-H6 — deeper still (rarely needed)

Google bots use this markup to understand the logic of the document. A solid «wall of text» without subheadings is a signal of poor page architecture.

⚡ BONUS: Schema.org for AI Overviews

Title + Description + H-tags is the «classic» markup. In 2026 with the arrival of AI Overviews (discussed at the end of Module 1), another layer appeared: Schema.org.

Schema.org is a vocabulary of typed data. You tell the bot not just «here's text», but «here's an Article, with author, datePublished, headline». The bot understands structure.

🎯 Key Types for Business

• FAQPage — for question-answer pages. Gets directly into AI Overview
• HowTo — step-by-step instructions. Also AI Overview-friendly
• Article — blog articles with author and date
• Product — products with price, rating, reviews
• LocalBusiness — if you have an office, address, phone
• Course — for educational products (our course uses exactly this)

FAQPage example:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How much does GPU server rental cost?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "From $99/month for RTX 5090."
    }
  }]
}
</script>

🧪 How to Test Your Markup

• Google Rich Results Test — search.google.com/test/rich-results — paste URL, see what Google «sees»
• Schema Markup Validator — validator.schema.org — detailed JSON-LD checking