Rank Maxer

Technical SEO Checklist for Site Owners

Technical SEO is the part of SEO that makes your site findable, readable, and clean enough for search engines to trust. If it breaks, good content can sit unseen.

You don’t need to become a developer to run a useful technical SEO check. You need a consistent order: access first, indexability second, page signals after that.

Use this checklist before a redesign, after a migration, or any time organic traffic drops and nobody knows why.

1. Confirm the site loads on HTTPS

Open your homepage with https:// in front of the domain. The page should load without a browser warning.

Then test the http:// version. It should redirect to HTTPS.

Bad signs:

  • Browser “not secure” warnings
  • Expired SSL certificate
  • Mixed content warnings
  • HTTP and HTTPS both loading separately
  • Redirect loops

HTTPS is table stakes now. If your certificate is broken, fix it before chasing smaller SEO issues.

2. Pick one hostname

Your site should prefer either www or non-www, not both.

Test:

https://example.com/
https://www.example.com/

One should redirect to the other. Internal pages should preserve their paths:

https://www.example.com/services/
        -> 301
https://example.com/services/

If both versions load, read the www vs non-www guide and fix the duplicate hostname problem.

3. Check robots.txt

robots.txt tells crawlers which parts of your site they can visit. It lives at:

https://example.com/robots.txt

Look for obvious blockers:

User-agent: *
Disallow: /

That one line blocks the whole site. Sometimes it gets left behind after development.

Run the free Robots.txt Checker and look at:

  • HTTP status
  • Disallow rules
  • Allow rules
  • Sitemap directives
  • Warnings

If important sections are blocked, fix this before auditing page content.

4. Check the XML sitemap

Your XML sitemap should list the canonical URLs you want search engines to discover.

Common locations:

https://example.com/sitemap.xml
https://example.com/sitemap_index.xml

Use the Sitemap Checker to find sitemap files and count discovered URLs.

Check for:

  • Missing sitemap
  • Empty sitemap
  • Old staging URLs
  • Mixed www and non-www
  • HTTP URLs on an HTTPS site
  • Deleted pages
  • Redirecting URLs
  • Noindex URLs

A sitemap should be boring. If it surprises you, something is probably wrong.

5. Verify Search Console

Google Search Console tells you what Google sees.

Check the Pages report for:

  • Crawled but not indexed
  • Discovered but not indexed
  • Not found 404
  • Redirect errors
  • Blocked by robots.txt
  • Alternate page with proper canonical tag
  • Duplicate without user-selected canonical

One excluded URL may be fine. A pattern is the story. If every service page is “discovered but not indexed,” Google may know the URLs exist but see no reason to store them yet.

6. Test indexability on important pages

Pick your ten most important pages. For a small site, that may be all pages.

Each page should:

  • Return 200 OK
  • Avoid noindex
  • Have a self-referencing canonical tag
  • Be linked from somewhere on the site
  • Be included in the sitemap if you want it indexed

Watch for accidental noindex tags:

<meta name="robots" content="noindex">

Developers and page builders sometimes add this during staging and forget to remove it.

A redirect sends one URL to another. Redirects are normal, but messy chains waste crawl attention and slow users down.

Good:

http://example.com/page
        -> 301
https://example.com/page

Messy:

http://www.example.com/page
        -> 301
https://www.example.com/page
        -> 301
https://example.com/page
        -> 301
https://example.com/new-page

Fix internal links so they point directly to the final URL. Also repair internal links that return 404.

8. Check titles, descriptions, and headings

Technical SEO meets on-page SEO here.

Each indexable page should have:

  • A unique title tag
  • A useful meta description
  • One H1
  • H2s that organize the page
  • No important text hidden in images

Duplicate titles make pages harder to tell apart. Missing descriptions won’t usually block rankings, but they make search snippets weaker and often reveal thin pages.

9. Check canonical tags

A canonical tag names the preferred URL for a page:

<link rel="canonical" href="https://example.com/services/" />

Use canonicals to reduce duplicate URL confusion. Don’t use them to hide a broken site structure.

Common mistakes:

  • Canonical points to the wrong page
  • Canonical uses HTTP instead of HTTPS
  • Canonical uses www while redirects prefer non-www
  • Every page canonicalizes to the homepage
  • Paginated or filtered pages canonicalize carelessly

Canonicals are signals. Redirects and internal links should agree with them.

10. Confirm mobile usability

Open important pages on a real phone.

Check:

  • Text is readable without zooming
  • Menus open
  • Buttons are easy to tap
  • Forms work
  • Tables don’t break the layout
  • Sticky headers don’t cover content

Google uses mobile-first indexing, which means its view of your page is based primarily on the mobile version. A desktop-only audit misses too much.

11. Check speed and Core Web Vitals

Run key pages through PageSpeed Insights. Focus on the field data if the page has enough traffic, then use lab diagnostics to find likely fixes.

Typical fixes:

  • Compress large images
  • Serve modern image formats
  • Lazy-load below-the-fold media
  • Remove unused scripts
  • Reduce third-party tags
  • Fix layout shifts from images without dimensions

Speed isn’t the only ranking factor, but slow pages lose visitors. That alone makes the work worth doing.

12. Add structured data where it fits

Structured data labels page content for search systems. Use it only when it matches visible content.

Useful types:

  • Organization
  • LocalBusiness
  • Article
  • BreadcrumbList
  • FAQPage
  • Product
  • Service

Test markup with Google’s Rich Results Test or Schema.org Validator. Bad schema can create more noise than no schema.

Common technical SEO mistakes

Auditing content before access. If crawlers can’t reach the site, title tags are not the first problem.

Trusting the sitemap blindly. A sitemap can list URLs that redirect, 404, or use the wrong hostname.

Fixing only the homepage. Internal pages often carry the real SEO value.

Ignoring generated pages. Tag pages, search pages, filters, archives, and parameters can create thousands of weak URLs.

Treating warnings as equal. A blocked service page matters more than a missing alt attribute on a decorative image.

Practical next step

Run this quick pass today:

  1. Check HTTPS and hostname redirects.
  2. Run the Robots.txt Checker.
  3. Run the Sitemap Checker.
  4. Open Search Console’s Pages report.
  5. Inspect your five most valuable pages for indexability, title tags, H1s, canonicals, and mobile layout.

Write down only blockers and high-impact fixes. A short list that gets fixed beats a giant audit nobody opens.

FAQ

How often should I run a technical SEO audit?

Run a light check monthly and a deeper audit after redesigns, migrations, CMS changes, theme updates, or sudden traffic drops.

Can technical SEO improve rankings by itself?

It can if technical issues were holding pages back. Once the site is crawlable and clean, content quality and authority still matter.

Do small sites need technical SEO?

Yes. Small sites can still block crawlers, publish broken sitemaps, duplicate hostnames, or hide important pages from Google.

What tool should I start with?

Start with Search Console and the free robots and sitemap checkers. Use a crawler when you need to inspect many pages at once.