Technical SEO checklist: 9 steps with free tools

With Search Console, PageSpeed Insights and a browser: auditing your site’s technical footing yourself, from indexing to hreflang.

· 13 min readSEO

Short answer

A technical SEO check can be done with free tools: work through Search Console’s Pages report, the sitemap, robots.txt, redirects, canonical and hreflang tags, mobile rendering, structured data and Core Web Vitals in order. Most “not indexed” rows are not errors; it is enough that your important pages are in the index.

Your new service page has been live for three weeks, yet it doesn’t show up on Google even when you type its name. You open Search Console; in the Pages report, the list under “Not indexed” is longer than the list of indexed pages. The first reaction is panic, but most of the rows in that list are harmless and the real problem usually hides in one or two of them. This technical SEO checklist is written so that you can tell which is which without a paid tool or an agency.

What you need: a verified Google Search Console property for your site, PageSpeed Insights and a browser. For each step we set out four things: what to check, where to check it, what “fine” looks like, and what to do if it isn’t.

There is a logic to the order. For a page to appear in search, Google first has to find the address, then be able to crawl it, then index it; how the result looks and how the page feels to use only come up after that. The list follows the same order; if a page is stuck at an earlier stage, fixing the later ones won’t help.

The four stages of the technical SEO checklist: discovery, crawling, indexing and appearance Discovery Sitemap Internal links Crawling robots.txt Redirects Indexing noindex Canonical hreflang Mobile rendering Appearance Structured data Core Web Vitals Tools: Search Console, PageSpeed Insights, a browser The four stages of the technical SEO checklist: discovery, crawling, indexing and appearance Discovery Sitemap Internal links Crawling robots.txt Redirects Indexing noindex Canonical hreflang Mobile rendering Appearance Structured data Core Web Vitals Tools: Search Console, PageSpeed Insights, a browser
Figure: the checklist follows the order Google works in; you check that the address is found first, then crawled, then indexed, and last how it appears in the search result.

Start here: reading the Pages report properly

1. The Pages report: which pages are indexed, and why the others aren’t

The Page indexing report splits the addresses Google knows on your site into indexed and not indexed, and groups the second set by reason.

  • Where: in Search Console, “Pages” under “Indexing” in the left-hand menu.
  • Fine looks like: every page you want to appear in search is on the indexed side. The not-indexed list doesn’t have to be empty; Google’s help page itself says you should not expect every address to be indexed, and that the goal is to have the canonical version of each page in the index.
  • If not: click the reason, look at the example addresses and act only on the pages that matter. Pasting an address into the search box at the top opens URL Inspection, which shows that page’s last crawl and whatever is blocking it.

The table below explains the reasons you will see most often.

Reason in the report What it means When it is normal When to look closer
Page with redirect The address forwards to another address and is not indexed itself Old addresses, http or www versions When it is a current page that shouldn’t redirect
Alternate page with proper canonical tag The page’s canonical tag correctly points to another page, and that page is indexed Addresses with parameters, duplicate versions of the same content When it is a page you want to rank in its own right
Crawled - currently not indexed Google crawled the page but did not index it Thin pages such as tags, archives and internal search When it is a service, a product or an article you put work into
Discovered - currently not indexed Google knows the address but hasn’t crawled it yet Newly published pages When weeks have passed and the page matters
Excluded by ‘noindex’ tag The page itself asks not to be indexed Thank-you, basket and account pages When you didn’t add that tag on purpose
Blocked by robots.txt Google is not allowed to crawl this address Admin panel, filter parameters When the blocked address is a content page
Not found (404) The address no longer exists Pages that really were removed and have no equivalent When the page has an equivalent or receives links

On “Crawled - currently not indexed”, Google states that it does not index every page and that this message alone does not point to a problem. If you see it on an important page, use URL Inspection to confirm there is no technical block. If there is none, the issue usually lies in the content: the page is very similar to another page on the site, or it doesn’t answer a question in its own right.

Discovery: does Google know your addresses

2. Sitemap

  • Where: yoursite.com/sitemap.xml in the browser (or the address given in your robots.txt file), and “Sitemaps” in Search Console.
  • Fine looks like: the sitemap has been submitted and its status is “Success”. It holds only pages you want indexed, that don’t redirect and that carry their own canonical address. When you filter the Pages report with the control at the top to “All submitted pages”, very few addresses remain not indexed.
  • If not: have your site’s platform generate the sitemap and submit it in Search Console. Remove any addresses in it that redirect, return 404 or carry noindex. Also check that your important pages receive at least one internal link, from the menu or from other pages; a sitemap should not be treated as enough by itself.

Crawling: can Google reach the pages

3. robots.txt and noindex

  • Where: yoursite.com/robots.txt in the browser. The robots.txt report under “Settings” in Search Console shows when and how Google last read the file.
  • Fine looks like: the file opens, its Disallow lines cover only paths you don’t want crawled, such as the admin panel or internal search, and the style and script files the page needs in order to render are not blocked.
  • If not: a Disallow: / line that closes the whole site is usually a leftover from the staging environment; remove it. Don’t use robots.txt to take a page out of search. According to Google’s documentation the file manages crawling; it is not a way of keeping a page out of Google, and if a blocked address is linked from elsewhere it can still appear in results, without a description. For a page that shouldn’t appear in search, add noindex or protect the page with a password. Don’t combine the two: a noindex on a page closed off by robots.txt is never read.

4. Redirects

  • Where: the browser’s address bar. Try the four spellings of your home page in turn: http and https, with www and without.
  • Fine looks like: all four end at the same single address. The same goes for spellings with and without a trailing slash. Pages that have moved for good go to their new address with a 301, in one step.
  • If not: choose the version you prefer and redirect the others to it permanently. Reduce chains that pass through several redirects to a single step, and point menu and in-text links straight at the final address. If you are changing the whole address structure, the job goes beyond this item; we set out the steps in keeping your SEO through a site rebuild. For individual pages, when to choose 301, 404 or 410 is covered step by step in 301 redirects and 404 errors.

Indexing: which version, in which language

5. Canonical tag

When the same content opens at more than one address, Google picks one of them as the canonical version. Your job is to state your preference consistently.

  • Where: search for rel="canonical" in the page source (right-click, “View page source”). URL Inspection in Search Console also shows the canonical you declared and the one Google selected, side by side.
  • Fine looks like: each page’s canonical tag points to its own full address, that address returns a 200 status and it is spelt the same way as in the sitemap. In URL Inspection the two canonical addresses match.
  • If not: fix the tag in the template. According to Google’s documentation, a redirect and rel="canonical" are strong signals and inclusion in a sitemap is a weak one; when they all point to the same address, your preference is clear. Don’t use robots.txt or noindex to indicate the canonical version. We walk through finding and fixing duplicate addresses one by one in our canonical tags article.

6. hreflang on two-language sites

  • Where: search for hreflang in the page source of the Turkish and the English version. Search Console does not check this for you; according to the help page, alternate language pages are not detected in the Pages report.
  • Fine looks like: the Turkish page lists both itself and its English counterpart; the English page carries the same two lines. The addresses are written out in full, and each language version’s canonical tag points to itself.
  • If not: add the missing return link. According to Google’s documentation, if two pages don’t point to each other the tags are ignored. Don’t point the English page’s canonical tag at the Turkish page; a translation is not a duplicate, and this mistake takes the English version out of the index. Giving the tag in the HTML, in an HTTP header or in the sitemap is equivalent for Google; choosing one is enough. If you are adding a second language for export, the multilingual section of our B2B SEO guide covers the content side of the work.

7. Mobile rendering

Google crawls pages with a browser that behaves like a phone, and that is the version it indexes. Content that shows on desktop but doesn’t load on mobile does not exist as far as Google is concerned.

  • Where: “Test live URL” in URL Inspection, then the screenshot and HTML of the tested page.
  • Fine looks like: the main content, headings and links are visible in the screenshot, and the list of resources that couldn’t be loaded contains none of the files that carry the page’s layout.
  • If not: move main content that is hidden on mobile, or that only loads after a tap, into the page’s initial state, and check again that robots.txt isn’t blocking style and script files.

Appearance: the search result and page experience

8. Structured data

  • Where: Google’s Rich Results Test (paste an address or code). Search Console also opens separate reports for the types it detects on your site.
  • Fine looks like: the test finds the markup on the page and shows no errors. The information in the markup is the same as what the visitor sees on the page.
  • If not: fix the errors; warnings are mostly optional fields. Don’t add review ratings or question-and-answer markup that isn’t visible on the page. Valid markup does not guarantee a rich result; it only makes the page eligible for one.

9. Core Web Vitals

  • Where: the Core Web Vitals report in Search Console (mobile and desktop separately), and PageSpeed Insights for a single page. The report rows and the gap between field and lab data are explained in Core Web Vitals explained: how to read LCP, INP and CLS.
  • Fine looks like: your addresses are in the “Good” group. The targets in Google’s documentation: LCP within 2.5 seconds, INP under 200 milliseconds, CLS under 0.1.
  • If not: open an example from a group of addresses marked “Poor” in PageSpeed Insights and start with the largest item. On sites with few visits the report may say there isn’t enough data; in that case the lab measurement in PageSpeed Insights shows the way. We explained in detail what each metric tells you and where to begin in why a fast site sells more. Google also notes that good scores alone do not guarantee a top position.

Common mistakes

  • Trying to bring every row in the not-indexed list down to zero, and pressing “Request indexing” for old addresses that redirect.
  • Closing off a page with robots.txt in order to remove it from search, and so also preventing the noindex from being read.
  • Carrying a noindex or a Disallow: / line from the staging environment over to the live site.
  • Putting pages in the sitemap that redirect, whose canonical tag points to another address, or that carry noindex.
  • Pointing the second language version’s canonical tag at the main language, and leaving hreflang one-way.
  • Expecting a result the same day after a fix. The report updates as Google crawls the page again; once the fix is made, you need to start the process with the validation button on that reason’s page and wait.

This list is the skeleton of a technical audit. Where a large e-commerce catalogue, filtered pages or an interface drawn with JavaScript is involved, a deeper crawl is needed; in our SEO service the first month goes to that audit and to a prioritised list of the problems. If you are going to bring in outside help, we gathered what to look for in an audit report in how to choose an SEO agency.

Common questions

How do I fix “Crawled - currently not indexed”?

First decide whether the page matters; nothing needs doing for tag and archive pages. If it is an important page, use URL Inspection to confirm there is no noindex, canonical or robots.txt block. If there is no technical block, strengthen the content that sets the page apart from similar ones and link to it from related pages. Google states that an address in this state does not need to be resubmitted.

Do I need a paid tool for a technical SEO check?

On a small or medium-sized site you don’t need one for the nine steps in this list; Search Console, PageSpeed Insights, the Rich Results Test and a browser are enough. Paid crawling tools are useful on sites with thousands of addresses, for running the same checks in bulk and seeing patterns such as redirect chains or broken internal links in one pass.

How often should I run a technical SEO check?

Run the whole list straight after every major release, such as a change of theme, platform or address structure. In between, looking at the Pages and Core Web Vitals reports at regular intervals is enough; Search Console also emails property owners when it detects a new problem.

If you do only one thing today, do this: write down the addresses of the five pages you care about most and paste each one into URL Inspection in Search Console. If all five say “URL is on Google”, your footing is sound and you can work through the rest of the list with a clear head. If even one doesn’t, the reason is written on the same screen, and the table above tells you whether that reason calls for alarm.

Sources

This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 10 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.

Tell us about
your project.

Fill in the form or write to us directly, and we will agree on a day to talk.

Your first meeting is with Deniz Sezer, founder of Detmore.

First meeting free · Reply within one working day · Written proposal in 2 to 3 days · NDA ready

What do you need? pick as many as you like

Name, email and phone are required.

Contact

We reply within one working day.