Technical SEO Audit Checklist: The CRAWL Framework

Last updated: August 2026 by Afraz Alam, Founder of Afraz Alam Marketing Services. This checklist is the same one I run on client sites before I touch a single keyword.

Here is the technical SEO audit checklist I actually run: 47 checks across 5 layers, in the order I check them. You do not need to hire anyone to run the first pass yourself. You do need to run all 5 layers, not just the 3 everyone remembers (speed, mobile, meta tags), because the layers people skip are usually where the real damage is.

• The CRAWL framework: Crawlability, Rendering and speed, Architecture, Website trust signals, Local and structured data. Five layers, 47 checks total.
• Who this is for: E-commerce and DTC founders, coaches and course creators, and HVAC, plumbing, and electrical business owners who suspect their site is leaking rankings somewhere they cannot see.
• What breaks most often: Layer 4 (website trust signals) and Layer 5 (structured data). Not speed. Everyone checks speed.
• Time to run it yourself: 2 to 4 hours for a site under 200 pages, with the free tools listed below.
• What you will walk away with: A prioritized list of what is actually costing you rankings, not a 200-line export nobody reads.

What Is a Technical SEO Audit, and Why It Beats Writing Another Blog Post

A technical SEO audit is a structured check of everything that decides whether Google can find, load, understand, and trust your site, separate from your content or your backlinks. It answers one question: is anything on the technical side stopping the pages you already have from ranking.

Here is the thing. Most site owners write more content when rankings stall. That is the wrong move if the real problem is that Google cannot crawl half your product pages, or your Core Web Vitals score tanks on mobile, or your canonical tags point at the wrong URL. I have opened audits where the client had 40 blog posts and 6 of them were indexed. The other 34 were invisible. No amount of new content fixes that. The audit does.

Why Listen to Me on This

I run SEO Strategies, Google Ads, and Meta Ads at Afraz Alam Marketing Services out of Kolkata, for clients across the US, UK, UAE, Australia, and Singapore. Before I touch a client's keywords, I run this exact audit. Not a shortened version. All 5 layers.

The reason I care this much about the technical layer is simple: I have watched paid traffic hit a page with a broken canonical tag and a 4.8 second load time, and the conversion rate told the whole story. One Meta Ads campaign I ran for BusiQueens reached 85,251 people and generated 2,498 link clicks, filling 50 of 60 exhibitor stalls. Another, for USA Tech Deals, delivered 171,061 impressions and 864 link clicks across 17 campaigns, starting at a cost per click of $0.17. Traffic like that is expensive to earn. Sending it to a page with a technical problem is the fastest way to waste it, whether that traffic came from an ad or from organic search.

Let me be honest with you: technical SEO is not glamorous work. Nobody shares a screenshot of a fixed robots.txt file on LinkedIn. It is also the part of SEO that determines whether everything else you do even has a chance to work.

The CRAWL Framework: 5 Layers, 47 Checks

I built the CRAWL framework because most audit templates I found online either skip the boring layers or bury them under 200 line items with no order. CRAWL is 5 layers, checked in the sequence that actually matters: a site with a Layer 1 problem cannot be helped by a Layer 5 fix.

The key insight: Layer 4 and Layer 5 are the ones I find broken most often, not Layer 2. Everyone remembers to check speed. Almost nobody checks their canonical tags or their schema markup.

Layer 1: Crawlability and Indexability

This layer checks whether Google can actually reach and index your pages. If a page fails here, nothing else in this checklist matters for that page, because it will not show up in search results at all. This is Layer 1 of the audit Afraz Alam Marketing Services runs on every new client site, before we look at a single keyword.

Start with Google Search Console's Coverage report. It tells you exactly how many of your pages are indexed versus excluded, and why. I check 3 things first every time: the robots.txt file (is it accidentally blocking CSS, JS, or entire folders), the XML sitemap (does it match what is actually live, and is it submitted in Search Console), and orphan pages (pages with zero internal links pointing to them, which crawlers rarely find on their own).

The fastest win here is usually the sitemap. I have found sitemaps still listing pages deleted 8 months earlier, and sitemaps missing entire categories added since launch. Both confuse the crawler about what your site actually is.

What to check in Layer 1

• robots.txt is not blocking CSS, JS, or important folders
• XML sitemap exists, is submitted in Search Console, and matches live pages
• No important pages return a noindex tag by accident
• Search Console Coverage report shows low "Excluded" counts on money pages
• No orphan pages (check with a crawler like Screaming Frog, filter by inlinks = 0)
• Crawl budget is not wasted on faceted navigation or filtered URLs with parameters

Layer 2: Rendering, Speed, and Core Web Vitals

This layer checks whether the page loads fast enough, and renders correctly, on the device most visitors actually use, which for most Afraz Alam Marketing Services e-commerce and local service clients is mobile.

Google's Core Web Vitals measure 3 things: Largest Contentful Paint (how fast the main content loads), Interaction to Next Paint (how fast the page responds to a click or tap), and Cumulative Layout Shift (how much the page jumps around while loading). I pull this from PageSpeed Insights, using the field data (real user data), not just the lab score, because lab scores lie about what real visitors on real 4G connections experience.

If I already wrote about the connection between site build quality and marketing performance in my post on SEO-friendly website development, this is the technical proof of that argument. A beautiful site that takes 5 seconds to load on mobile is not an SEO-friendly site.

What to check in Layer 2

• Core Web Vitals pass on mobile using field data, not just lab data
• Images are compressed and served in a modern format (WebP or AVIF)
• No render-blocking JavaScript or CSS on above-the-fold content
• Fonts do not cause layout shift while loading
• Third-party scripts (chat widgets, ad pixels, review plugins) are not tanking load time
• Server response time (TTFB) is under 600ms on your key pages

Layer 3: Architecture and Internal Linking

This layer checks how your pages connect to each other. A page can be fast, indexed, and well written, and still underperform because it is buried 5 clicks from your homepage with 2 internal links pointing to it.

I map site architecture as a simple pyramid: homepage, then category or service pages, then individual product or blog pages. Every important page should be reachable within 3 clicks from the homepage. For HVAC, plumbing, and electrical clients specifically, this usually means your service-area pages (Phoenix, Dallas-Fort Worth, Houston, whichever cities you cover) need direct links from the main navigation or homepage, not just from a buried sitemap page.

You can review the full service catalog structure Afraz Alam Marketing Services recommends clients build toward on the SEO services page, which walks through how I structure site architecture during onboarding.

What to check in Layer 3

• Every money page is 3 clicks or fewer from the homepage
• Category and service pages link down to relevant products or subpages
• Blog posts link up to the relevant service or product page, not just to each other
• No dead-end pages with zero outbound internal links
• Breadcrumb navigation is present and matches the actual URL structure

Layer 4: Website Trust Signals

At Afraz Alam Marketing Services, this is the layer I find broken the most, and the one nobody thinks to check. It covers HTTPS, redirects, and canonical tags, the signals that tell Google which version of a page is the real one.

Redirect chains are the classic problem. A URL that redirects to a second URL, which redirects to a third, wastes crawl budget and dilutes link equity at every hop. I have found chains 4 redirects deep on sites that went through 2 redesigns without anyone auditing the old URLs. Self-referencing canonical errors are the second most common issue: a page's canonical tag pointing at a different page entirely, which tells Google to ignore the page you actually want ranked.

Here is an imperfect truth: I still find canonical errors on client sites after the first audit, because a plugin update or a new page template silently reset them. This layer is not a one-time fix. It needs a recheck every few months.

What to check in Layer 4

• Site is fully on HTTPS, with no mixed content warnings
• All old URLs redirect in a single hop (301), never a chain
• Canonical tags point to the correct, live version of each page
• No duplicate content across www/non-www or trailing-slash variants
• 404 pages are handled cleanly, not silently redirecting everything to the homepage

Layer 5: Local and Structured Data Signals

This layer checks whether your site speaks a language search engines and AI answer engines can parse directly: schema markup, and for local businesses, NAP (Name, Address, Phone) consistency tied to your Google Business Profile. At Afraz Alam Marketing Services, this is the layer I push hardest on for HVAC, plumbing, and electrical clients.

For coaches, course creators, and e-commerce brands, the priority schema types are usually Organization, Product, and FAQPage. For HVAC, plumbing, and electrical businesses, LocalBusiness or the more specific Plumber, Electrician, or HVACBusiness schema types matter more, because they directly feed the local pack results your ideal customer sees when they search "electrician near me" at 11pm with a real problem.

Structured data is also the layer that increasingly decides whether AI answer engines like Google's AI Overviews or ChatGPT cite your site at all. A page an LLM can parse cleanly, with clear schema and a visible Q&A section, gets cited more than a page that reads well to a human but says nothing structured to a machine.

What to check in Layer 5

• Schema markup is present and validates with no errors (test in Google's Rich Results Test)
• NAP (name, address, phone) matches exactly across your site, Google Business Profile, and directory listings
• LocalBusiness schema is present on every service-area page, for local service businesses
• FAQPage schema is used where you have a visible FAQ section
• Review or aggregate rating schema reflects real, current reviews, never fabricated ones

The Full 47-Point Checklist

Here is the same 47-point checklist Afraz Alam Marketing Services runs, all 5 layers in one list, so you can work through it in order without flipping back and forth. Print it, or copy it into a spreadsheet.

Free vs Paid Audit Tools

You do not need a paid tool to run the first pass of this checklist. Here are the tools Afraz Alam Marketing Services actually uses, free and paid. You need a paid one only if you want to automate the recheck every quarter without doing it by hand.

How Often to Run This Audit

At Afraz Alam Marketing Services, we run the full CRAWL checklist quarterly at minimum for every client, and Layer 4 specifically (redirects and canonicals) after every redesign, plugin update, or CMS migration, because that is when it breaks.

DIY vs Hiring It Out

You can run this entire checklist yourself with the free tools above. What you are paying for when you hire someone is not the checklist itself. It is the judgment call on which of the 47 issues to fix first when you find 30 of them at once.

I do not believe in guesswork here. If you run the DIY pass and Layers 1 through 3 come back clean but Layer 4 or 5 turns up more than 5 issues, that is usually the point where a second set of eyes pays for itself.

The Mistakes I Keep Finding on First Audits

The fact is, the same handful of mistakes show up on almost every first audit I run, across e-commerce, coaching, and local service sites alike.

The biggest one: businesses fix Layer 2 (speed) obsessively because it is the layer with the friendliest dashboard, and ignore Layer 4 and 5 because checking a canonical tag or validating schema takes more manual digging. I have opened Rich Results Test on a client's homepage and found 0 schema types detected, on a site that had been live for 3 years. That is not a speed problem. That is a Layer 5 problem, and it was quietly capping how well that homepage could ever show up in the local pack.

The second mistake is treating the audit as a one-time event instead of a quarterly habit. A theme update, a new plugin, or a redesign can silently reintroduce a Layer 1 or Layer 4 issue you already fixed. Your website looks fine. It's just not making you money, and the reason is usually sitting in a layer nobody rechecked.

The key insight: A technical SEO audit is not a report you file away. It is a prioritized to-do list, run in the CRAWL order, rechecked every quarter, so the same issue never costs you rankings twice.

Frequently Asked Questions

What is a technical SEO audit?

A technical SEO audit is a structured review of the parts of your site that control whether search engines can crawl, index, load, and understand your pages. It covers site speed, crawlability, site architecture, redirects and canonicals, and structured data, separate from your content quality or backlink profile.

What does a technical SEO audit actually include?

Using the CRAWL framework above, it includes 5 layers: crawlability and indexing, rendering and speed, site architecture, website trust signals like redirects and canonicals, and structured data. A full audit runs all 47 checks across those 5 layers, not just a speed test.

How do you perform a technical SEO audit yourself?

Start with Google Search Console for indexing and Core Web Vitals data, run a crawl with a free tool like Screaming Frog for internal links and canonicals, validate your schema in Google's Rich Results Test, and check redirect chains manually on your top pages. Follow the 47-point checklist in order, Layer 1 through Layer 5, so you are not fixing symptoms before root causes.

How often should you run a technical SEO audit?

Quarterly, at minimum, for most small businesses. E-commerce sites with frequent product changes benefit from checking Layers 1, 2, and 4 monthly. Recheck Layer 4 (redirects and canonicals) and Layer 5 (schema) immediately after any redesign, migration, or major plugin update.

How much does a technical SEO audit cost?

Running it yourself costs nothing but your time, roughly 2 to 4 hours for a site under 200 pages using the free tools listed in this post. Hiring it out varies by site size and scope. Afraz Alam Marketing Services quotes it after a short call, once I know how many pages and how many past redesigns your site has been through.

What tools do you need for a technical SEO audit?

4 free tools cover most of the checklist: Google Search Console, Google PageSpeed Insights, the free tier of Screaming Frog (up to 500 URLs), and Google's Rich Results Test. A paid tool like Ubersuggest's Site Audit adds ongoing tracking and a prioritized issue list if you want to automate the quarterly recheck.

What is an SEO audit score, and what counts as good?

Most audit tools generate a score out of 100 based on how many checks pass. There is no universal "good" number because the weighting differs by tool. I care less about the single score and more about which layer the failing checks cluster in: 5 failures spread across Layer 1 mean something different than 5 failures concentrated in Layer 5.

Questions, disagreements, or something I missed in this checklist? Reply on my Instagram @afrazalammarketingservices or drop a comment below. I read everything.