Skip to content

SEO

Technical SEO checklist — the 15-point audit I run before launch

September 12, 20269 min readRasel Hossain
SEO

Quick answer

A technical SEO audit covers crawlability, indexing, performance and structured data: submit an XML sitemap, set one canonical URL per page, fix 404s and redirects, pass Core Web Vitals, compress images to AVIF or WebP, and add schema markup. Run the full checklist before every launch.

Content wins rankings, but technical SEO decides whether Google can find, render and trust that content. This is the exact checklist I run before any site goes live — it takes about an hour and catches nearly every indexing problem I have ever seen in production.

Crawlability and indexing first

If Googlebot cannot crawl a page cleanly, nothing else matters. Verify the site in Google Search Console, submit the XML sitemap, and confirm the important pages are indexed — not sitting in “Discovered, currently not indexed”.

  1. Submit sitemap.xml and check index coverage in Search Console
  2. One canonical URL per page — no www/http/trailing-slash duplicates
  3. Redirect chains collapsed to a single hop; every 404 either fixed or given a proper 404 page
  4. robots.txt allows CSS/JS; noindex only on genuinely private pages (admin, API, thank-you)

Then performance and structure

Google's published Core Web Vitals thresholds are LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1. Images are usually the biggest lever: serve AVIF or WebP with explicit dimensions, lazy-load below-the-fold media, and defer third-party scripts so they never compete with the first paint.

Finally, add structured data where it earns rich results — Organization and BreadcrumbList sitewide, Article or Product plus FAQPage on eligible pages — and confirm every page has one H1, a unique title under 60 characters and a meta description under 160. I run this full flow on every development project before handover.

Technical SEO is not a one-time task — re-run the checklist after every redesign, migration or CMS change.

Field notes
#Technical SEO#Core Web Vitals#Schema#Next.js

How to do it

  1. 1

    Verify and submit

    Verify the domain in Google Search Console and submit the XML sitemap.

  2. 2

    Collapse duplicates

    Enforce one canonical URL per page with 308 redirects for www, HTTP and trailing-slash variants.

  3. 3

    Fix crawl errors

    Resolve 404s, redirect chains and broken internal links; confirm index coverage.

  4. 4

    Pass Core Web Vitals

    Compress images to AVIF/WebP, defer third-party scripts and hit LCP < 2.5s, INP < 200ms, CLS < 0.1.

  5. 5

    Add structured data

    Ship Organization, BreadcrumbList and page-level Article/FAQ schemas, then validate with the Rich Results Test.

Frequently asked questions

How long does a technical SEO audit take?

A focused audit of a small-to-medium site takes 1–2 hours with Search Console, PageSpeed Insights and a crawler. Large sites with thousands of URLs need a day or more, mostly for log-file and crawl-budget analysis.

How often should I repeat the checklist?

Run the full checklist before every launch, migration or redesign, and do a light version quarterly — checking index coverage, Core Web Vitals and broken links. Rankings decay silently when nobody watches.

Can I do technical SEO myself without a developer?

The content half — titles, descriptions, headings, alt text, internal links — yes. The code half — redirects, canonical logic, sitemap generation, schema, performance budgets — usually needs a developer for an hour or two.

What is the single highest-impact technical fix?

Fixing indexation: pages stuck in “Crawled, not indexed” or “Discovered, not indexed”. Clean canonicals, honest lastmod dates in the sitemap and fast server responses recover more traffic than any other single change.

More articles

Related reading from the same areas — practical notes on shipping software.

View all articles

Liked the article?

Have a similar problem in your business? Let's talk about building the fix.

Start a project