The Technical SEO Checklist We Run Before Writing a Single Word of Content

Short answer: Great content on a technically broken site is wasted effort. If a page can’t be crawled properly, loads too slowly, or isn’t indexable, no amount of good writing fixes that. We run a technical SEO audit on every new client before a single piece of content gets written — crawlability, site speed, and indexability first.

Why content is the wrong place to start

It’s tempting to start an SEO engagement with the visible, exciting part: writing content, targeting keywords, building out a blog. But content sits on top of a technical foundation, and if that foundation is broken, the content built on it never gets the chance to perform. A brilliant article that a search engine can’t crawl, or that loads so slowly visitors bounce before it renders, produces the same result as no article at all — except now you’ve also spent the time and budget writing it.

That’s why the audit comes first, every time, before a single word of client-facing content gets written.

What we actually check

Crawlability. Can search engines — and increasingly, AI crawlers — actually access and read every page that matters? This means checking robots.txt isn’t accidentally blocking key sections, confirming there’s a clean XML sitemap, making sure internal linking doesn’t leave important pages orphaned with no path leading to them, and verifying there’s nothing structurally preventing a crawler from reaching content that should be indexed.

Site speed. A slow-loading site doesn’t just frustrate visitors — search engines factor load time directly into ranking, and Core Web Vitals specifically measure things like how quickly the main content becomes visible and how stable the layout is while it loads. We check image optimization, unnecessary render-blocking scripts, and server response times, because speed problems compound: a site that’s slow on mobile is losing both rankings and visitors before a single line of copy gets read.

Indexability. Being crawlable isn’t the same as being indexed. We check for accidental noindex tags left over from staging environments, duplicate content issues that confuse search engines about which version of a page to rank, and canonical tags pointing to the right destination. A shockingly common issue on sites that have been through multiple redesigns: old canonical or redirect rules quietly telling search engines to ignore pages that are actually live and meant to rank.

Structured data. Clean, correct schema markup (JSON-LD) helps search engines and AI answer engines understand exactly what a page is about — an article, a service, a business location — rather than inferring it from unstructured text alone. This is also foundational to AEO, which is why SEO and AEO now need to be built together, not as separate projects.

Why this happens before content, every single time

For Bottle Printing Australia, an industrial manufacturing client with no existing marketing infrastructure, the SEO and AEO audit was the second deliverable in the engagement — completed before the monthly content calendar was even built out, because the audit’s findings shaped every content decision that followed. Writing content against an un-audited technical foundation risks building an entire month’s worth of articles around a site structure that needs to change anyway.

The unglamorous truth about technical SEO

Nobody gets excited about a crawlability audit. It doesn’t produce a shareable asset, and it’s invisible to anyone who isn’t specifically looking for it. But it’s the part of SEO that determines whether everything built on top of it — content, backlinks, brand visibility — actually has a chance to rank at all. Skip it, and you’re optimizing content for a foundation that was never checked. Run it first, and every piece of content published afterward has a real shot at performing the way it’s supposed to.

Common questions about technical SEO audits

How often should a technical SEO audit be repeated, or is it a one-time thing? It’s a one-time foundation at the start of an engagement, but it isn’t a “set and forget” step. Site redesigns, platform migrations, and even routine content updates can quietly reintroduce crawlability or indexability issues, so we re-check the foundation whenever something structural changes on the site, not just at the beginning.

What’s the single most common technical SEO issue you find on a new client’s site? Leftover indexability problems from a previous redesign or staging environment — a noindex tag that was meant to be temporary, or canonical tags pointing to the wrong version of a page. These are invisible to anyone looking at the site normally, which is exactly why they tend to go unnoticed for months or years.

Can great content overcome a weak technical foundation? No, not reliably. If a page can’t be crawled or indexed properly, it doesn’t matter how well-written the content is — search engines and AI crawlers may never actually see it. Technical issues don’t lower a page’s ranking, they can prevent it from being eligible to rank at all.

Does site speed really matter as much as content quality for SEO? It matters differently, not necessarily more, but it’s foundational in a way content isn’t — Core Web Vitals are a direct ranking factor, and a slow site loses visitors before they ever read the content regardless of how good it is. Speed and content quality aren’t competing priorities; a technical audit exists so neither one is working against the other.

What a technical audit changes about everything built afterward

Once the technical foundation is confirmed sound, every subsequent decision gets easier to make correctly. A content calendar can be planned against a site structure that’s actually going to support it, rather than working around unknown constraints. A backlink strategy can target pages that are actually indexable, instead of building authority toward a page a crawler might be skipping. Even paid media benefits — a landing page that loads quickly and renders cleanly converts better regardless of how well-targeted the ad driving traffic to it is. This is why the audit isn’t a discrete “SEO task” sitting alongside content and ads — it’s the foundation those other functions are quietly depending on, whether anyone involved in planning them realizes it or not. Getting it right once, at the start, is what lets every deliverable that follows perform the way it’s actually capable of performing.

This is also why we consider the audit a prerequisite, not an optional add-on — a client who skips it isn’t saving time, they’re deferring a rebuild to a later, more expensive point once the content and campaigns already built on top of the broken foundation need to be redone.

Think of it the way you’d think about a building inspection before renovating a house: skipping it doesn’t remove the underlying issues, it just guarantees you’ll discover them at a more disruptive and expensive moment later.