Technical SEO - Practical Handbook
Technical SEO is mainly about whether a crawler can discover, fetch, understand and correctly index a page. Canonical, hreflang, sitemaps and robots.txt provide signals or instructions, but they do not replace useful content and good internal linking.
For Google, a canonical declaration is a hint rather than an absolute command, so Google may select a different representative URL.
Related topics: Web Performance, HTTP, HTTPS and TLS, Modern HTML and CSS and Browser DevTools.
1. What Technical SEO is
Technical SEO covers technical factors that affect whether a crawler can discover a page, index content, understand structure, select the correct URL and evaluate performance and page quality.
It does not replace content or links, but poor technical implementation can prevent good content from being properly visible.
2. Crawling and indexing
Crawler:
discover URL
fetch document
analyse links
discover more URLs
Indexing:
analyse content
choose canonical version
store information in the index
A page can be crawlable but not indexed.
3. robots.txt
Typical file:
User-agent: *
Disallow:
Sitemap: https://example.com/sitemap.xml
Block a path:
Disallow: /admin/
robots.txt is not a security mechanism.
4. meta robots
<meta name="robots" content="noindex, follow">
Common values: index, noindex, follow and nofollow.
5. XML sitemap
<url>
<loc>https://example.com/article</loc>
<lastmod>2026-09-19</lastmod>
</url>
A sitemap helps URL discovery but does not guarantee indexing.
6. Canonical
<link rel="canonical" href="https://example.com/product">
Canonical indicates the preferred URL version.
Typical duplicates:
/product
/product?source=campaign
/product?sort=price
7. Redirects
301 is permanent.
302 / 307 are temporary.
Avoid chains:
A → B → C → D
Prefer:
A → D
8. HTTP status codes
Especially important:
200 OK
301 Permanent Redirect
404 Not Found
410 Gone
5xx Server Error
A soft 404 returns 200 even though the content effectively does not exist.
9. HTTPS
Use one consistent HTTPS version of the site.
Avoid parallel indexing of http/https or www/non-www variants. Choose the target version and redirect the others.
10. Title
<title>Page description</title>
It should be unique, descriptive and consistent with the page content.
11. Meta description
<meta name="description" content="Short page description">
It is not a direct ranking signal, but it can influence how a result is presented.
12. Headings
A good hierarchy:
H1
├─ H2
│ ├─ H3
│ └─ H3
└─ H2
Do not use headings only for visual styling.
13. Internal linking
Internal links help crawlers and users.
<a href="/docs/http">HTTP and HTTPS</a>
Avoid important navigation that exists only through JavaScript unless there is a good reason.
14. Structured data
JSON-LD:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Title"
}
</script>
Structured data should describe content that is actually visible.
15. hreflang
For language versions:
<link rel="alternate" hreflang="pl" href="https://example.com/pl/page">
<link rel="alternate" hreflang="en" href="https://example.com/en/page">
Reciprocal linking matters.
16. Core Web Vitals
Important metrics include LCP, INP and CLS. They are not the only performance metrics, but they are worth monitoring.
17. Mobile-first
The site should work correctly on mobile: layout, viewport, fonts, interactions and touch targets.
18. JavaScript and SEO
Modern crawlers can render JavaScript, but rendering may be more expensive and delayed. Important content should be available as directly as practical.
19. Pagination
For large sets:
/page/1
/page/2
/page/3
Each page should have a normal URL and links.
20. Faceted navigation
Filters can generate huge numbers of URL combinations.
?color=black
?color=black&size=m
?size=m&sort=price
Control indexing, canonicals, linking and crawl budget.
21. Open Graph
Not SEO in the strict sense, but important for sharing:
<meta property="og:title" content="...">
<meta property="og:description" content="...">
<meta property="og:image" content="...">
22. Tools
Useful tools include Google Search Console, Bing Webmaster Tools, Lighthouse, PageSpeed Insights, Screaming Frog, curl and browser DevTools.
23. curl
Headers:
curl -I https://example.com
Redirects:
curl -IL https://example.com/old-url
24. Checklist
- HTTPS,
- correct status codes,
- canonical,
- robots.txt,
- sitemap,
- title,
- meta description,
- heading hierarchy,
- internal linking,
- mobile,
- Core Web Vitals,
- structured data,
- no accidental noindex.
25. What you should know
You should understand crawling and indexing, diagnose status codes and redirects, use canonical URLs, prepare robots.txt and sitemaps, check structured data basics and understand the impact of performance and mobile experience.
Official references
- Google Search Essentials: https://developers.google.com/search/docs/essentials
- Canonicalization: https://developers.google.com/search/docs/crawling-indexing/canonicalization
- Localized versions and hreflang: https://developers.google.com/search/docs/specialty/international/localized-versions
- Structured data: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data
- Bing Webmaster Guidelines: https://www.bing.com/webmasters/help/webmaster-guidelines-30fba23a