Technical SEO files: robots.txt, sitemaps, canonicals and hreflang
A handful of small files and tags decide how search engines crawl and index a site. robots.txt says what may be crawled, the XML sitemap lists what should be found, canonical tags pick one URL among duplicates, hreflang connects language versions, and structured data describes the page in machine-readable form. Mistakes in any of them are easy to make and hard to notice, because the page still looks fine in a browser.
Below is a short guide to each, followed by the tools that write or check it. Most run in your browser; the ones that fetch a URL say so on their page. None needs an account.
Updated · How we write and check guides
robots.txt
robots.txt controls crawling, not indexing. A disallowed URL can still appear in search results if other pages link to it, just without a description. To keep a page out of the index, let it be crawled and add a noindex robots meta tag or X-Robots-Tag header instead.
Each crawler obeys only the most specific User-agent group that matches it. Within a group, Google applies the most specific (longest) matching rule, and when an Allow and a Disallow rule are equally specific, Allow wins. Paths are case-sensitive.
Checks robots.txt syntax and identifies crawler rules that may block important pages.
Creates robots.txt files with configurable crawler permissions and sitemap references.
Set allow and disallow paths to get robots.txt text with sitemap and crawl-delay lines.
XML sitemaps
An XML sitemap lists the canonical URLs you want search engines to find, with an optional lastmod date. One file may hold up to 50,000 URLs or 50 MB uncompressed; larger sites split the list across several files tied together by a sitemap index.
List only URLs that return 200, are their own canonical and are not noindexed. A sitemap that contradicts a page's own signals sends mixed messages and wastes crawling. Reference the sitemap from robots.txt and submit it in Search Console.
Checks XML sitemap structure, required elements, and URL formatting.
Check sitemap entries for malformed URLs and duplicate locations.
hreflang
hreflang annotations connect translated or regional versions of a page so searchers get the right one. Every version lists all the versions, itself included, and the links must be reciprocal: if page A names page B, page B must name page A.
Codes are an ISO 639-1 language, optionally followed by an ISO 3166-1 region: en-GB is valid, en-UK is not. x-default marks the page for everyone who matches no listed version.
Checks supplied language mappings for missing alternate references.
Structured data (JSON-LD)
JSON-LD describes a page's entities, such as an article, a product, an organization or a breadcrumb trail, in a script tag that search engines read. The markup must describe what is visible on the page.
Valid markup makes a page eligible for rich results; it does not guarantee them, and Google limits some types (FAQ rich results, for example, now appear only for well-known government and health sites).
Redirects
Use a permanent redirect (301 or 308) when a URL has moved for good, and a temporary one (302 or 307) only when the original will come back. Point old URLs straight at the final destination: every extra hop adds latency, and Google stops following a chain after about ten hops.
More tools in Website & SEO.