Most business owners think SEO is about keywords and content. It is, eventually. But before
any of that matters, your site has to be technically sound enough for Google to find, crawl, and
understand it. A technical SEO audit is how you find out whether it is.
Technical SEO covers the infrastructure of your site: how it is built, how fast it loads, how search engines move through it, and whether the signals it sends are clean and consistent. None of it is glamorous. All of it matters.
This checklist walks through every major area of a technical SEO audit in the order that makes the most sense to work through it. Start at the top. The issues you find early often explain the problems you would find later.
Content and backlinks get most of the attention in SEO conversations. They matter. But a site with technical problems can underperform regardless of how good the content is, because Google cannot reliably find, index, or render it.
of website traffic comes from
organic
search
BrightEdge, 2024
of online experiences start with
a
search engine
Junto, 2024
is the threshold where bounce rates
increase dramatically with page load
Google, 2024
Technical SEO problems are quiet. They do not throw error messages your visitors can see. They just quietly reduce how many pages Google indexes, how fast those pages load, and how confidently Google can serve your site to people searching for what you offer.
A technical audit does not need to be done every week. But it should be done at least once when a site is new, once after any major redesign or platform migration, and once a year as ongoing maintenance. The issues compound when left unaddressed.
A technical audit without the right tools is guesswork. Before working through the checklist below, make sure these are in place.
Go to search.google.com/search-console and verify ownership of your site. Search Console is the primary source of truth for how Google sees your site. It shows indexing status, crawl errors, manual actions, Core Web Vitals data, and sitemap submission results. If it is not connected, you are auditing blind.
Connect Google Analytics to understand traffic patterns, bounce rates, and page-level performance. GA4 is the current version. If your site is still running Universal Analytics, it is time to migrate.
Tools like Screaming Frog (free up to 500 URLs) or Sitebulb crawl your site the way Google does and surface broken links, redirect chains, missing tags, duplicate content, and more. Run a crawl before working through this list so you have data to reference.
PageSpeed Insights gives you Core Web Vitals scores and specific recommendations for any URL. You will use it throughout this audit to test individual pages and verify fixes.
Work through each section in order. Items marked as high priority have the most direct impact on whether Google can find and rank your pages. Do not skip to the end.
Visit yoursite.com/robots.txt. The file should exist and should not be blocking pages you want indexed. A misconfigured robots.txt is one of the fastest ways to accidentally de-index your entire site. Check it at Google Search Console under the robots.txt tester.
Your XML sitemap should be at yoursite.com/sitemap.xml. Submit it in Google Search Console under the Sitemaps section. Check how many URLs were submitted versus how many were indexed. A large gap signals indexing problems worth investigating.
Use your crawl tool to find any pages with a noindex tag. Cross-reference with pages you want to rank. It is more common than you would think to accidentally block important service pages or blog posts with a misconfigured plugin setting.
In Google Search Console, go to Pages and review any URLs marked as errors. Pay particular attention to 404 errors on pages that used to exist and may have backlinks pointing to them. These should be redirected, not just deleted.
Canonical tags tell Google which version of a page is the authoritative one. Check that every page has a self-referencing canonical, and that pages with duplicate or near-duplicate content point their canonical to the correct primary URL. Incorrect canonicals cause Google to index the wrong version of your pages.
Your sitemap should list only canonical, indexable, non-redirecting URLs. If it includes redirect URLs, noindex pages, or URLs that return errors, remove them. A clean sitemap helps Google prioritize crawl budget on the pages that matter.
URLs should be lowercase, use hyphens not underscores, and describe the page content. Avoid dynamic parameters where possible. A URL like yoursite.com/services/web-design is better for both users and search engines than yoursite.com/page?id=42.
Duplicate content occurs when the same or very similar content appears at multiple URLs. Common causes include www vs non-www versions, HTTP vs HTTPS versions, trailing slash vs no trailing slash, and paginated pages. Use your crawl tool to identify duplicates and resolve them with canonicals or redirects.
Your entire site should load over HTTPS with a valid SSL certificate. Check that HTTP URLs redirect to HTTPS, that there are no mixed content warnings (HTTP resources loading on HTTPS pages), and that your certificate is not expiring soon. You can verify at SSL Labs.
Every redirect adds latency and dilutes link equity. A redirect chain occurs when URL A redirects to URL B which redirects to URL C. Chains of more than one hop should be collapsed so URL A points directly to the final destination. Your crawl tool will identify these automatically.
Important pages should be linked from multiple places within the site. Orphaned pages with no internal links are harder for Google to find and are often under-indexed. Check your crawl data for pages with zero or one internal link and address them.
If your site has paginated content such as blog archives or product listings, make sure each page is indexable and self-canonicalized. Avoid blocking paginated pages in robots.txt unless you have a specific reason to do so.
Run your key pages through PageSpeed Insights. The three Core Web Vitals are Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Google uses these as ranking signals. A failing score is a structural disadvantage regardless of how good your content is.
Unoptimized images are the single most common cause of slow load times. Convert images to WebP or AVIF format, compress them before uploading, and set explicit width and height attributes to prevent layout shift. Tools like Squoosh make this straightforward.
Alt text serves two purposes: it tells Google what an image shows, and it provides context for screen readers. Every meaningful image on your site should have alt text that describes the image accurately. Decorative images should have empty alt attributes.
JavaScript and CSS files that load before the page renders slow down your LCP score. Defer non-critical JavaScript, inline critical CSS, and use async loading where possible. Your PageSpeed Insights report will flag specific files causing issues.
A slow server adds latency before any page content loads. Check your Time to First Byte (TTFB) in PageSpeed Insights. If it is above 600ms, investigate your hosting, caching configuration, and whether a CDN would help.
Caching stores static resources so returning visitors load your site faster. GZIP or Brotli compression reduces the size of HTML, CSS, and JavaScript files transferred over the network. Both should be configured at the server level and are standard on quality hosting platforms.
Images that are not visible when the page first loads should not be loaded immediately. Lazy loading defers these until the user scrolls to them, reducing initial page weight and improving LCP. This is a native HTML attribute: loading=’lazy’.
Run your site through Google Search Console under the Mobile Usability report. Common issues include text
too small to read, clickable elements too close together, and content wider than the screen. Each is fixable
and each affects your rankings since Google indexes the mobile version of your site first.
The viewport meta tag tells mobile browsers how to scale your page. Without it, your site may render at desktop width on mobile devices. Every page should include: meta name=’viewport’ content=’width=device-width, initial-scale=1′.
Buttons and links should be at least 48px tall and wide with sufficient spacing between them so users can tap accurately on a phone. Small or clustered tap targets are flagged by Google and create poor experiences that increase bounce rates.
Body text should be at least 16px on mobile. Smaller text forces users to zoom, which degrades the experience and signals to Google that your mobile UX needs work.
Google’s intrusive interstitial penalty targets popups that cover the main content on mobile immediately after a user arrives. Full-screen popups that appear on load are the most common trigger. Small banners and cookie notices are generally acceptable.
Title tags should be unique across your site, between 50 and 60 characters, and accurately describe the page content. Duplicate or missing title tags reduce Google’s ability to understand and differentiate your pages. Your crawl tool will flag duplicates and pages with missing or truncated titles.
Meta descriptions do not directly affect rankings but they influence click-through rates in search results. Keep them between 150 and 160 characters, make them compelling, and ensure they accurately summarize the page. Duplicate meta descriptions across pages signal thin or duplicated content.
Every page should have exactly one H1 that matches or closely reflects the page topic. H2s and H3s should create a logical outline of the content. Do not skip heading levels and do not use headings purely for visual styling. Search engines use heading structure to understand page organization.
Structured data helps Google understand your content and can trigger rich results in search. Common types for small businesses include LocalBusiness, FAQ, and Review. Validate your implementation at Google’s Rich Results Test.
Internal and external links that point to 404 pages damage user experience and waste crawl budget. Run your crawl tool and filter for 4xx response codes. Fix internal broken links by updating the URL. For broken external links, either update the URL or remove the link.
Open Graph tags control how your pages appear when shared on social platforms. At minimum, include og:title, og:description, og:image, and og:url on every page. Without them, social shares display generic or missing previews.
Check the Manual Actions report in Google Search Console. A manual action means a Google reviewer has flagged your site for a policy violation. This is different from an algorithmic penalty and requires specific steps to resolve and request reconsideration.
The Core Web Vitals report in Search Console shows real-user data from Chrome users visiting your site. Unlike PageSpeed Insights which tests a single page on demand, this report reflects actual performance across all pages over time. Address any URLs marked as Poor or Needs Improvement.
The Pages report in Search Console shows which URLs Google has indexed, which it has excluded, and why. Review the Excluded tab carefully. Some exclusions are intentional but others, like Crawled but not indexed or Discovered but not indexed, indicate pages Google found but decided not to include.
The Performance report shows clicks, impressions, average position, and click-through rate over time. Look for sudden drops in any of these metrics, which can indicate a recent technical change, an algorithmic update, or a crawling issue.
The Links report shows which sites link to yours and which of your pages receive the most internal links. Review external links for any low-quality or spammy sources that could be influencing your site’s authority negatively.
An audit is only useful if it produces a prioritized action list. Not everything you find will be equally important. Here is how to triage what you find.
Anything that prevents Google from finding or indexing your pages is the highest priority. robots.txt issues, noindex errors, and sitemap problems belong here. Until these are resolved, every other fix is less effective.
Poor scores on LCP, INP, or CLS are ranking signals that affect every page on your site. Image optimization and render-blocking resource fixes often produce the fastest improvements and should be tackled before more complex server-side changes.
These are quick wins that improve crawl efficiency and preserve link equity. Most can be resolved in a single session with your crawl data in front of you.
Duplicate content dilutes ranking signals across multiple URLs. Consolidating with canonicals or redirects helps Google consolidate authority on the right pages.
Title tags, meta descriptions, heading structure, and schema markup are the last layer. These matter, but they are most effective once the foundational issues above are resolved.
A technical audit is not a one-time project. It is a recurring practice. Sites change, platforms update, plugins conflict, and new pages get added. The businesses that rank consistently are the ones who check the foundation regularly, not just at launch.
A Discovery session with Josiah covers your site’s full technical foundation, including crawlability, page speed, mobile performance, and Search Console health. You leave with a prioritized fix list and no jargon.
Josiah Partin helps small business owners build websites and systems they actually understand and control. He leads The Valley List, holds certifications in Google Ads, Yoast SEO, CCNA, and CompTIA, and has spoken at the Marietta Area Chamber of Commerce, Marietta College, and regional programs on web fundamentals, SEO, and practical systems for growing businesses.