GuidesSEO

Technical SEO checklist

Technical SEO is making sure search engines can crawl, render, and index your pages, and that the pages load fast and are understood. Work in order: confirm crawl access, confirm indexing, fix rendering, tidy site structure, then speed and structured data. An earlier step failing makes every later step pointless.

Updated November 16, 20266 steps5 min read

Grow my organic traffic →

$1 today. Cancel anytime before day 7.

Technical SEO in order
  1. 1Confirm crawl accessCheck robots.txt, status codes, and that key pages are not blocked.
  2. 2Confirm indexingReview the Page indexing report for the pages you want in search.
  3. 3Check renderingMake sure content and links appear in the rendered page, not only after a click.
  4. 4Fix site structureClean URLs, canonicals, redirects, sitemap, and internal links.
  5. 5Improve speedPass Core Web Vitals on the pages that earn traffic.
  6. 6Add structured dataMark up what is on the page and validate it.
On this page
  1. Crawlability: can Google reach the page
  2. Indexing: is the page in the index
  3. Site structure: URLs, canonicals, sitemap, links
  4. Rendering, mobile, and speed
  5. Security, HTTPS, and international setup
  6. Structured data and ongoing checks
  7. Questions

Crawlability: can Google reach the page

Start with the basics a crawler needs. Important pages should return a 200 status code, not a 404 or a server error. Your robots.txt file should not block them, and no stray noindex tag should be present. Note the difference: robots.txt controls crawling, while noindex controls indexing, and a page blocked in robots.txt cannot have its noindex read.

Check Crawl stats in Search Console for spikes in server errors and slow responses, and run a crawler over the site to list every status code. Links should be real anchor tags with an address, because crawlers discover pages by following them. A button that loads content with a script is not a link. A full site audit automates this pass.

If the site is large, think about crawl budget. Google decides how much to fetch based on how fast your server responds and how much of the site looks worth crawling. Avoid infinite URL spaces such as calendar pages and endless filter combinations, and keep the sitemap clean so that crawling effort goes to pages that matter.

Indexing: is the page in the index

Crawling and indexing are different steps. Crawling is fetching a page. Indexing is deciding to store it for search. A page can be crawled and not indexed. Open the Page indexing report in Search Console and compare the indexed count with the pages you expect to rank.

For each important page that is excluded, read the reason. Common ones are Discovered - currently not indexed, Crawled - currently not indexed, duplicate pages where Google chose another canonical, and soft 404s. Pages that will not index covers the fixes, and the URL Inspection tool confirms a single page.

Do the indexing check before you spend time on anything else in this list. There is no point polishing structured data on a page that is excluded from the index, and a single mistaken noindex on a template can remove a whole section of the site from search.

Want the articles written for you?

Researches keywords and what competitors rank for. Publishes to WordPress, Webflow, Shopify or Framer once you approve.

Site structure: URLs, canonicals, sitemap, links

Give each page one clean URL. Use canonical tags to point duplicate versions, such as tracking parameters and sorted category pages, at the preferred one. Redirect old addresses with a 301 and avoid chains of redirects. Keep your XML sitemap limited to canonical, indexable pages.

Internal links are the structure. Every page you care about should be reachable within a few clicks of the homepage and linked from related pages with descriptive anchor text. Orphan pages, which nothing links to, are rarely indexed well. See internal linking and the fix for broken links.

Faceted navigation on ecommerce sites deserves special care. Filter combinations can create millions of near-duplicate URLs. Decide which combinations have search demand and deserve to be indexed, and keep the rest out through canonicals, noindex, or by not generating crawlable links for them.

Rendering, mobile, and speed

Google indexes the mobile version of a page, so the content, links, and structured data on mobile must match what you intend to rank. If the page depends on JavaScript, use the URL Inspection tool’s live test to see the rendered HTML and confirm the main content and links appear in it. Serve over HTTPS and avoid intrusive pop-ups that cover content.

For speed, measure the three Core Web Vitals on real users: loading, responsiveness, and visual stability. Fix the templates that serve the most pages first. The steps are in the Core Web Vitals guide. PageSpeed Insights shows both field data and a lab test for any URL.

Security, HTTPS, and international setup

Serve the whole site over HTTPS and redirect every HTTP address to its HTTPS version with a single 301. Check that certificates do not expire, and that no mixed content, meaning HTTP resources inside an HTTPS page, remains. Browsers warn on these, and they hurt trust.

If you run several languages or regions, use hreflang annotations so Google serves the right version, and make sure each version links to the others and to itself. Mistakes here are common, since the references must be reciprocal. If the site is one language and one country, you can skip this.

Finally, handle status codes deliberately. Pages that no longer exist should return a 404 or 410, or a 301 to a close replacement. Avoid soft 404s, where a missing page returns a 200 status with a thin message. Search Console lists them, and they waste crawl effort.

Structured data and ongoing checks

Add structured data in JSON-LD that describes what is visible on the page: product schema on product pages, local business schema on location pages, and article or FAQ markup where it fits. Validate it with Google’s Rich Results Test and watch the enhancement reports in Search Console for errors.

Technical SEO is not a one-off. Releases break things: a staging noindex ships to production, a redirect rule loops, a template change slows every page. Re-run the audit after major releases and quarterly otherwise. The part you can hand off: Sprites can crawl the site, audit pages, and run index health and tracking health checks on a schedule, then propose fixes for your approval.

Questions

What is technical SEO?

It is the work that lets search engines crawl, render, index, and understand your site, plus page speed, mobile usability, and structured data. It covers the site itself rather than the content on it or the links pointing to it.

What is the difference between crawling and indexing?

Crawling is Google fetching a page. Indexing is Google deciding to store and process it so it can appear in results. A page can be crawled without being indexed, which is why indexing needs its own check.

How often should I run a technical SEO audit?

Quarterly is a sensible rule of thumb, and again after any major release, migration, or redesign. Check the Page indexing report weekly in between so that regressions do not sit for months.

What is the difference between on-page, off-page, and technical SEO?

On-page SEO covers the content and tags of a page. Off-page SEO covers signals outside the site, mainly links. Technical SEO covers how the site is built and served so that the first two can work.

Can a beginner do technical SEO?

Yes, for the basics. Search Console is free and shows most crawl and indexing issues in plain language. Server configuration and rendering problems may need a developer.

Keep going

Have Sprites grow your organic traffic

  • Researches keywords and what competitors rank for
  • Audits your pages and writes the articles
  • Publishes to WordPress, Webflow, Shopify or Framer once you approve