Sitemap
An XML file listing your important URLs so crawlers can discover pages they might not otherwise find.
SEO Basics for Developers
Developers control most of what search engines can understand. These small technical habits make a site easier to find.
SEO is often treated as a marketing job, but the foundations live in the code. Search engines need to fetch your pages, understand their structure and decide what each page is about. Most of that is decided by markup you write.
Semantic HTML and one clear h1
Use the element that matches the meaning: header, nav, main, article and footer describe the page better than a pile of div tags. Give every page a single h1 that states its topic, then use h2 and h3 for sections in a logical order.
This helps screen readers and search engines alike, because both rely on structure rather than appearance to understand the content.
Title and meta description
The title is the headline search engines show and the text in the browser tab, so make it specific and unique per page. The meta description does not directly rank a page, but it is often used as the summary in results, so a clear, honest sentence earns more clicks.
<title>Understanding Async/Await in JavaScript | KRYZO</title>
<meta name="description" content="Learn how promises, async functions and await keep asynchronous code readable, with practical examples.">Avoid duplicate titles and descriptions across pages. Uniqueness tells search engines that each URL is a distinct, useful page.
Canonical URLs
Visitors reach the same page through many URLs: with or without a trailing slash, with tracking parameters or through a print view. A canonical link tells search engines which version is the real one and consolidates ranking signals.
<link rel="canonical" href="https://www.example.com/blogs/seo-for-developers/">Use one consistent URL shape everywhere so the canonical tag and your internal links always agree.
Open Graph basics for sharing
Open Graph tags control how a link looks when it is shared on social platforms. They do not affect search ranking, but they make a shared page far more inviting.
<meta property="og:title" content="SEO Basics for Developers">
<meta property="og:description" content="Technical SEO essentials for developers.">
<meta property="og:image" content="https://www.example.com/cover.jpg">
<meta property="og:url" content="https://www.example.com/blogs/seo-for-developers/">XML sitemaps and robots.txt
robots.txt
A text file at the site root that tells crawlers which paths they may or may not visit.
Reference the sitemap
Point to the sitemap from robots.txt so crawlers find it quickly.
Sitemap: https://www.example.com/sitemap.xml
Disallow: /admin/A sitemap is a hint, not a command, and a Disallow rule removes a page from crawl rather than from the index. Use them to guide crawlers, not to hide content you still want ranking.
Internal links and crawlable navigation
Links are how crawlers move through a site and how ranking value flows between pages. Use real a elements with descriptive text instead of JavaScript click handlers, and link related articles to each other.
Imagine the site with styles and scripts removed. If a person can still reach every page by following links, a crawler can too.
Speed and mobile friendliness
Fast pages that work well on phones perform better because they give users a better experience. Compress images, keep JavaScript small and use a responsive layout. These are covered in more depth in the performance and responsive design guides.
What technical SEO can and cannot do
Clean markup, correct metadata and a crawlable structure remove obstacles, but they are not a ranking guarantee on their own. Search engines weigh content quality, relevance and many other signals. Do the technical basics well so your content has the best possible chance, then let the content do the rest.