Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Technical SEO checklist: what to check and fix first

Updated · 9 min read

Short answer Check in order of damage. First, can Google reach and index your pages at all. Second, is the site hacked or flagged. Then HTTPS on every page, the same content on phones, no server errors or broken redirects, and one address per page. Speed and structure come after. Search Console and PageSpeed Insights cover all of it free.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

Technical SEO checklist, in priority order

Technical SEO is the plumbing under your website: whether Google can reach your pages, read them and trust them. Fix it in order of damage. A blocked site gets zero search traffic; a slow one loses a little. Stop at the first check that fails and fix it before moving on.

#CheckWhat goes wrong if it failsFree tool
1Google can reach and index your pagesThe page can't appear in Google at allSearch Console: URL Inspection, Page indexing
2The site isn't hacked or flaggedSpam pages, warnings, lost trustSearch Console: Security issues; a `site:` search
3Every page loads on HTTPS"Not secure" warning; duplicate addressesYour browser's address bar
4Phones get the full pageGoogle ranks what the phone version showsYour phone; Lighthouse
5No server errors or broken redirectsPages drop out; old links go nowhereSearch Console: Page indexing
6One address per pageGoogle picks the version, not youURL Inspection: "Google-selected canonical"
7Speed and Core Web VitalsA small ranking edge between close pagesPageSpeed Insights
8Links, sitemap and URLsDeep pages found late or neverSearch Console: Sitemaps
9Only if it applies: structured data, JavaScript, other languagesMissed extras, unread contentRich Results Test; URL Inspection

1. Can Google reach and index your pages?

This check outranks everything else on the list. Google's technical requirements are short: Googlebot (Google's crawler, the program that visits pages) isn't blocked, the page returns an HTTP 200 code meaning "success", and the page has indexable content such as text (Google Search Central: technical requirements). Google adds that meeting them makes a page eligible, not guaranteed.

What to look for:

  • A noindex tag, a line in the page code telling Google to leave the page out. Builders add it site-wide with one "hide from search engines" switch, sometimes left on after launch.
  • A robots.txt block. Robots.txt is a file that tells crawlers where they may go. It does not hide a page from Google:
"it is not a mechanism for keeping a web page out of Google. To keep a web page out of Google, block indexing with noindex or password-protect the page." (Google Search Central: Introduction to robots.txt)
  • A password or login in front of pages you want found.

Run URL Inspection on your home page and your top service page. If either isn't indexed, the step-by-step fix is in website not showing up on Google and crawled or discovered, currently not indexed.

2. Is the site hacked?

A hacked site can rank for casino or pill searches under your name, and visitors may see browser warnings. Google's prevention guide gives two checks: search `site:yourdomain.com` and look for pages or topics you didn't write, and open Search Console's Security issues report, which lists hacked pages Google found and how to fix them (Google Search Central: Preventing malware infection). Turn on email forwarding of Search Console messages so a warning reaches you.

Prevention is dull and works: strong passwords, apps and plugins only from sources that offer support, and updates kept current. On WordPress, out-of-date plugins are the usual way in; on hosted builders the platform patches the software for you.

3. Does every page load on HTTPS?

HTTPS is the padlock: the connection between the visitor and your site is encrypted. Google made it a ranking signal in 2014 but called it "a very lightweight signal—affecting fewer than 1% of global queries" (Google Search Central Blog, 2014). Today its page experience checklist asks plainly: "Are your pages served in a secure fashion?" (Google Search Central: Understanding page experience). The bigger cost of skipping it is the "Not secure" label browsers show, which scares off form fills.

Three checks:

  1. Type `http://yourdomain.com` and confirm it sends you to the `https://` address. Try the `www` and non-`www` versions too; all should end at one address.
  2. Look for mixed content: an HTTPS page that still loads an image or script over plain HTTP, which web.dev says weakens the page's security (web.dev: What is mixed content?). Old embeds and hard-coded image links are the usual cause.
  3. Certificates cost nothing. Let's Encrypt, a nonprofit, gives free TLS certificates (the file that enables HTTPS) to more than 700 million websites (Let's Encrypt). Most hosts and all major builders install one automatically.

4. Do phones get the full page?

Google ranks the phone version of your site:

"Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central: Mobile site and mobile-first indexing best practices)

So the check isn't only "does it look fine on a phone" but "does the phone show everything". Google says to make sure the mobile site "contains the same content as your desktop site" (same page). Watch for service details, reviews or FAQs hidden or removed on small screens.

Google's Mobile-Friendly Test and Search Console's Mobile Usability report were retired on December 1, 2023 (Google Search Central Blog). Test on your own phone, on mobile data, and run Lighthouse in Chrome for a list of problems.

5. Any server errors, 404s or redirect chains?

Server errors (5xx codes) make Google crawl less, and already indexed pages are "eventually dropped" if they keep failing (Google Search Central: HTTP status codes and network errors). A 404 ("not found") on a page that used to rank throws away its links. The Page indexing report in Search Console lists both.

Redirects send an old address to a new one. Google's site-move guide asks you to point straight at the final page, "ideally no more than 3 and fewer than 5" hops in a chain, and to keep redirects "generally at least 1 year" (Google Search Central: Move a site with URL changes). Most broken redirects come from a redesign; see traffic dropped after a website redesign.

6. Does each page have one address?

The same page often answers at several addresses: with and without `www`, HTTP and HTTPS, with tracking codes added. Google picks one to show, the canonical. This is not a penalty:

"Some duplicate content on a site is normal and it's not a violation of Google's spam policies." (Google Search Central: What is canonicalization)

The cost is that Google, not you, chooses the version, and your reports split across addresses. Redirect the duplicates to the address you want. Where you can't, a canonical tag (a line in the page code naming the preferred address) is Google's fallback (Google Search Central: SEO Starter Guide). URL Inspection shows which address Google chose.

7. Is the site fast enough?

Speed counts, but it comes after relevance. Google says it "always seeks to show the most relevant content, even if the page experience is sub-par" (Google Search Central: Understanding page experience). Good speed helps most when several pages answer the search equally well.

Google measures speed with three Core Web Vitals. Pass marks (web.dev: Web Vitals):

MetricMeasuresGood
LCP (Largest Contentful Paint)When the main photo or text appears2.5 seconds or less
INP (Interaction to Next Paint)How fast the page reacts to a tap200 milliseconds or less
CLS (Cumulative Layout Shift)How much the page jumps while loading0.1 or less

INP replaced the older First Input Delay (FID) in March 2024 (Google Search Central Blog), so guides that still list FID are out of date. PageSpeed Insights shows real visitors' scores over the previous 28 days when your site has enough traffic (PageSpeed Insights: About). What moves the scores and how much they matter: Core Web Vitals and Google ranking.

Google finds pages mainly by following links, so every service and area page needs a normal link from another page on your site, ideally from the menu or the home page. A page nothing links to (an orphan page) gets found late or never.

A sitemap is a file listing your pages for search engines. Google says you might not need one if your site is "small", meaning "about 500 pages or fewer", and well linked internally (Google Search Central: Learn about sitemaps). Most builders create one anyway; submit its address once in Search Console's Sitemaps report.

Keep addresses readable. Google's starter guide prefers words useful to people, like `/pets/cats.html`, over strings of random characters (Google Search Central: SEO Starter Guide).

9. Only if it applies to your site

  • Structured data (schema markup) is code that labels your business name, hours and reviews for search engines. It can earn richer listings, but Google "does not guarantee that your structured data will show up in search results" (Google Search Central: General structured data guidelines). See local business schema markup.
  • JavaScript-heavy sites (custom apps rather than builders) may hide content until code runs. Google calls server-side rendering "still a great idea" because "not all bots can run JavaScript" (Google Search Central: JavaScript SEO basics). Check URL Inspection's rendered view shows your text.
  • A second language. Pages in two languages need extra markup so each searcher gets the right one. See multilingual website SEO.

Skip what the checklist doesn't ask for. Security headers protect visitors but don't appear on Google's page experience checklist. A two-second load target isn't a Google rule; 2.5 seconds for LCP is the published mark.

Example

Illustrative cases with invented numbers.

A plumber after a redesign (US dollars)

Calls from Google fall by half. Check 1 passes, check 5 fails: 40 old service pages now return 404. Redirecting each to its new page costs about $300 of a web developer's time. Speed was never the problem.

A dental office on WordPress

Search Console's Security issues report flags hacked pages: hundreds of spam pages added through an old plugin. The office has its host clean the site, updates every plugin, removes the unused ones and requests a review. Only then does it look at speed.

An accountant on Squarespace (Canadian dollars)

Checks 1 to 6 pass; the builder handles HTTPS, sitemap and server. PageSpeed shows a slow LCP from a 4 MB header photo. Resizing it costs C$0 and an hour.

FAQ

How often should I run a technical SEO check?

Check Search Console's Page indexing and Security issues reports monthly. Run the full list after any redesign, platform change or domain move.

Do I need paid tools like Semrush or Screaming Frog?

Not for a small site. Search Console, PageSpeed Insights and Lighthouse are free and cover every check. A crawler helps on large sites.

Does Google penalize duplicate content?

No. Google says some duplication is normal and not a spam violation; it picks one version to show. Redirect or canonicalize so it picks yours.

Is technical SEO different for Wix or Squarespace sites?

Less is yours. Builders handle HTTPS, servers, sitemaps and updates. You still own the noindex switch, redirects for renamed pages, photo sizes and apps.

Different for you?

Keep learning

NextTechnical SEO Audit: How to Run One Step by StepHow to run a technical SEO audit on a small business site: crawl it, read the errors, compare with Search Console, then rank fixes by what they cost you.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Google Search technical requirements
  2. Google Search Central: Introduction to robots.txt
  3. Google Search Central: Preventing malware infection
  4. Google Search Central Blog: HTTPS as a ranking signal (2014)
  5. Google Search Central: Understanding page experience in Google Search results
  6. web.dev: What is mixed content?
  7. Let's Encrypt
  8. Google Search Central: Mobile site and mobile-first indexing best practices
  9. Google Search Central Blog: Mobile-friendly testing tool (retired)
  10. Google Search Central: How HTTP status codes and network errors affect Google Search
  11. Google Search Central: Move a site with URL changes
  12. Google Search Central: What is canonicalization
  13. Google Search Central: SEO Starter Guide
  14. web.dev: Web Vitals
  15. Google Search Central Blog: Introducing INP to Core Web Vitals
  16. PageSpeed Insights: About PageSpeed Insights
  17. Google Search Central: Learn about sitemaps
  18. Google Search Central: General structured data guidelines
  19. Google Search Central: Understand the JavaScript SEO basics