Skip to content
Plumb
Light theme onCheck a URL

DocsGuides

Technical SEO

Technical SEO is everything that decides whether search engines and AI systems can crawl, render, understand and show a page. Content and links earn rankings; technical SEO makes sure nothing stands in the way.
  • Guide

What it Covers

A page meets search engines in a fixed order: it is crawled, rendered, judged on mobile, matched to a language and country, understood through its structured data, and finally shown as a result or a link card. A problem at any step hides the steps after it: a page blocked by robots.txt is never rendered, and a page that only shows its content after JavaScript runs may be indexed empty.

The sections below follow that order. Each lists what to check and the tool that checks it.

1. Crawling

Can crawlers reach the page, and are they allowed to fetch it?

  • robots.txt rules for Googlebot and every other crawler, including the CSS and JavaScript the page needs: robots.txt Tester.
  • AI crawlers such as GPTBot, ClaudeBot and PerplexityBot, which follow their own robots.txt groups and are often blocked by firewalls: AI Bot Access Tester; and llms.txt, the proposed index for language models: llms.txt Tool.
  • Sitemaps that list every indexable URL and nothing else: Sitemap Generator.
  • Broken links and redirects, which waste crawl requests and lose link value: Broken Link Checker; and server rewrite rules: .htaccess Tester.

2. Rendering and Indexing

What does the page contain once it has been fetched, and may it be indexed?

  • The raw HTML against the rendered DOM: titles, canonicals, links and text that only exist after JavaScript runs: Fetch & Render.
  • noindex in the meta robots tag or the X-Robots-Tag header, and the canonical URL (see the rel="canonical" guide).
  • Dynamic rendering and cloaking: whether crawlers get the same content as visitors: Pre-rendering Tester.

3. Mobile

Google indexes the mobile version of a page. Content, links or structured data missing on mobile are missing from the index.

4. International Targeting

Which version of a page each visitor should see. hreflang annotations must be valid and reciprocal (see the hreflang guide): hreflang Tags Tester. Pages that change their content by the visitor's language or location are hard to index: Locale-Adaptive Tester.

5. Structured Data

schema.org markup tells search engines what a page is about (a recipe, a product, an event) and makes it eligible for rich results. It must be valid schema.org and carry the properties Google requires: Schema Validator, Schema Generator.

6. How a Page Is Shown

Where to Start

  1. Run the quick check on your most important pages: twelve readings across these areas in about a second.
  2. Fix anything red before anything amber: a crawling or indexing problem outweighs every other finding.
  3. Crawl the whole site for broken links and build its sitemap once the pages are crawlable.
  4. Keep an eye on Google's algorithm updates when traffic changes suddenly.