Skip to content
Search

Basics of HTML: what it is and how it works

Basics of HTML describes the core elements, syntax, and semantic structure of Hypertext Markup Language — the standardized markup that organizes web content, embeds resources, and communicates meaning to browsers, accessibility tools, and search engines.

Basics of HTML: Essential Guide for Web Development

What is basics of HTML?

The basics of HTML cover the core elements, attributes, and document structure used to mark up web content. HTML (Hypertext Markup Language) is not a programming language but a standardized system of tags that tells a browser how to display text, images and embedded resources and how content is semantically grouped.

Why basics of HTML matters for SEO

HTML provides the semantic signals search engines use when crawling and indexing pages. Correct use of title tags, meta descriptions, headings (<title>, <meta name="description">, <h1>–<h6>), canonical links (<link rel="canonical">) and structured data influences what content is discovered and how it is shown in search results. Note the distinction: crawling is the fetch/discovery stage, indexing is whether content is stored, and ranking is the ordering of results; good HTML helps with discovery and indexability but does not alone determine ranking.

Also consider mobile-first indexing: Google uses the mobile version as its primary basis for crawling and indexing; since July 2024 Google crawls sites for Search with Googlebot Smartphone by default. That makes responsive HTML, correct viewport metadata and equivalent semantic content on mobile especially important for indexation signals.

How basics of HTML works

An HTML document starts with a doctype and contains two primary sections: <head> for document metadata and <body> for visible content. Elements use angled brackets and may include attributes that modify behavior. Browsers parse HTML into a DOM (Document Object Model), apply CSS and execute JavaScript to render the final page.

Common inline examples: a standard link without a special rel attribute: Example. For paid placements use rel="sponsored": Sponsor. For user-generated links use rel="ugc": Comment link. There is no rel="dofollow" attribute: a normal link is simply one without rel=nofollow, rel=sponsored or rel=ugc.

Types of basics of HTML

HTML elements fall into practical groups:

- Structural/semantic: <header>, <main>, <article>, <section>, <footer> — improve machine understanding and accessibility.
- Metadata: <title>, <meta>, <link> — affect indexing and presentation in search.
- Text-level/formatting: <p>, <strong>, <em>, <span> — for content authoring.
- Media/embedded: <img>, <video>, <iframe>, <picture> — handle assets and formats.
- Interactive/controls: <form>, <button>, <input> — user interaction elements.

How to get started with basics of HTML

Start by authoring simple pages in an editor (VS Code, Sublime Text, or any plain text editor). Create a basic scaffold: <!DOCTYPE html>, <html lang="en">, <head> with <meta charset="utf-8"> and <meta name="viewport" content="width=device-width, initial-scale=1">, then a <body> with headings and paragraphs. Use semantic tags for content sections and add alt text to images for accessibility.

Learn to separate concerns: HTML for content and semantics, CSS for presentation, JavaScript for behavior. Validate your markup, and view pages on mobile devices or emulated viewports to confirm content parity for indexing.

Common basics of HTML mistakes

Frequent errors that affect usability and indexability include missing or late <meta charset> which can break character rendering, absent or duplicated <h1> hierarchy, missing lang attribute on <html>, images without descriptive alt text, inline styles that hide content from assistive tech, incorrect canonical tags, and placing critical content behind JavaScript without server-side fallbacks.

Basics of HTML checking: technical checklist

**Doctype and charset** — where to verify: view-source / first bytes — passes when <!DOCTYPE html> appears and <meta charset="utf-8"> is high in the <head>.

**Viewport and mobile content** — where to verify: view on device or Chrome DevTools » Device Toolbar — passes when <meta name="viewport"> is present and content matches desktop semantic content (parity).

**Canonical and robots meta** — where to verify: view-source and HTTP headers — passes when <link rel="canonical"> points to the preferred URL and no <meta name="robots" content="noindex"> is blocking indexation unintentionally.

Browser and DevTools checks

Open Chrome DevTools to inspect the DOM (Elements panel), simulate mobile viewports (Device Toolbar) and run Lighthouse audits (Lighthouse panel) for accessibility and best-practices recommendations. Use the Elements panel to confirm that semantic tags and visible content exist in the rendered DOM, not just in source comments.

Command-line and server checks

Use curl for raw checks. To inspect response headers: curl -I https://example.com. To fetch the HTML as a specific user agent: curl -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64)" https://example.com (omit -I to get body). Check that status is 200 and there are no unexpected redirects or X-Robots-Tag headers.

Validation and structured data

Run the W3C Markup Validation Service (validator.w3.org) to catch syntactic issues. For structured data, use Google's Rich Results Test and the Schema Markup Validator (schema.org) to verify JSON-LD or microdata. Rich Results Test shows whether a page is eligible for certain rich result types; it is not an indexation report.

If you own the site, use Google Search Console's URL Inspection to see crawl/index data for a specific URL; this is authoritative for your property. For third-party pages, remember that site: queries are indicative but not definitive for indexation status.

Troubleshooting tip: if critical content is present in view-source but missing in the rendered DOM, check for client-side JavaScript that may run slowly or fail; consider server-side rendering or ensuring content is present without JS for reliability in crawling and indexing.

Read the Technical SEO Guide

Frequently asked questions

Q: What is the difference between HTML and CSS?

A: HTML defines structure and semantics of content; CSS controls presentation and layout. Keep content in HTML and styling in CSS to maintain clear separation of concerns.

Q: Do title and meta description tags affect rankings?

A: The title tag is an important relevance signal and is used in SERP displays. Meta descriptions do not directly determine rankings but influence click-through rate. Both affect how pages appear in search but ranking is decided by many signals beyond these tags.

Q: How early should <meta charset> appear?

A: Place <meta charset="utf-8"> near the top of <head> so the browser interprets characters correctly; late charset declarations can lead to garbled text.

Q: If content is loaded by JavaScript, will search engines see it?

A: Modern search engines execute JavaScript, but execution timing, resource limits and rendering differences mean content delivered only via client-side JS is riskier for indexing. If indexing is important, ensure server-side rendered HTML or progressive enhancement so the core content is present without relying exclusively on JS.

Q: How do I make HTML more accessible?

A: Use semantic elements, provide descriptive alt text for images, include labels for form controls, set lang on the <html> element, and follow ARIA best practices where native semantics are insufficient.

Istilah terkait