Technical SEO Audit Checklist: Fix These 10 Issues to Rank Higher

Technical SEO Audit Checklist: Fix These 10 Issues to Rank Higher

Technical SEO is the foundation every piece of content builds on. Your site might have excellent blog posts and strong backlinks, but if Google cannot crawl, index, and understand your pages, those strengths cannot translate into rankings. This checklist covers the ten technical issues that most commonly hold small business sites back, with specific instructions for finding and fixing each one.

What You Need for This Audit

All ten checks can be completed with free tools:

• Google Search Console (search.google.com/search-console): requires ownership verification
• Google PageSpeed Insights (pagespeed.web.dev): no account required
• Screaming Frog SEO Spider (screamingfrog.co.uk): free version crawls up to 500 URLs
• Google Rich Results Test (search.google.com/test/rich-results): no account required

Work through the list in order. Issues 1 to 3 take priority because no other optimisation matters if pages are not indexed.

Issue 1: Pages Not Being Indexed

What it is. Google indexes the pages it finds valuable enough to include in search results. Pages that are not indexed will not appear in search, regardless of content quality.

How to find it. In Google Search Console, go to Indexing > Pages. The "Not indexed" section shows excluded pages with the reason for each: "Excluded by 'noindex' tag", "Discovered but not indexed", "Crawled but not indexed", "Blocked by robots.txt."

How to fix it. For pages showing "Excluded by 'noindex' tag": remove the noindex meta tag from the page HTML or your CMS SEO settings. For "Blocked by robots.txt": review your robots.txt for rules blocking important pages. For "Discovered but not indexed": these pages need more internal links pointing to them and more substantive content.

After fixing, use the URL Inspection tool in Search Console to request re-indexing.

Issue 2: Core Web Vitals Failures

What it is. Core Web Vitals are three performance metrics Google uses as a confirmed ranking signal.

• LCP (Largest Contentful Paint): how quickly the main content loads. Target: under 2.5 seconds.
• INP (Interaction to Next Paint): how quickly the page responds to interactions. Target: under 200 milliseconds.
• CLS (Cumulative Layout Shift): visual stability, how much elements shift after loading. Target: under 0.1.

How to find it. Google Search Console > Experience > Core Web Vitals. This uses real-world field data from Chrome users, which is what Google uses for ranking. Also check PageSpeed Insights at pagespeed.web.dev for per-page scores and specific recommendations.

How to fix common failures:

• LCP: compress and convert images to WebP, add explicit dimensions to images, preload the hero image, improve server response time
• INP: reduce JavaScript execution time, defer non-critical scripts, break up long tasks
• CLS: add explicit width and height attributes to every image, use font-display: swap with appropriate fallback fonts to prevent layout shift from font loading

Issue 3: Broken Internal Links

What it is. Internal links pointing to pages that return 404 errors. They waste crawl budget and signal poor site maintenance.

How to find it. In Screaming Frog, crawl your site. Navigate to Response Codes > Client Error (4xx). This shows all pages returning errors. Check the "Inlinks" column to see which pages are linking to the broken URLs.

How to fix it. For each broken link: if the page moved, update the link or add a 301 redirect from old to new URL. If the page was deleted and no replacement exists, remove the broken link. If the page should exist but does not, create it.

Issue 4: Duplicate Content and Missing Canonical Tags

What it is. Multiple URLs serving substantially identical content split ranking signals instead of consolidating them. Common causes: www vs non-www, HTTP vs HTTPS, trailing slashes vs without, product pages accessible through multiple category paths.

How to find it. In Screaming Frog > Canonicals tab. Look for pages with a missing canonical (blank column) or where the canonical URL differs unexpectedly from the page URL.

How to fix it. Every page should have a self-referencing canonical tag: <link rel="canonical" href="https://yoursite.com/this-page/" />. Your CMS SEO plugin (Yoast, RankMath) typically handles this automatically. For site-wide duplicate issues, set up 301 redirects to consolidate traffic on your preferred URL format.

Issue 5: Missing or Broken XML Sitemap

What it is. An XML sitemap tells Google which pages exist and when they were last modified. Without one, Google discovers pages only through links, which may leave important pages undiscovered.

How to find it. Check yoursite.com/sitemap.xml or yoursite.com/sitemap_index.xml. In Google Search Console > Sitemaps, verify it shows a green "Success" status.

How to fix it. Most CMS platforms generate sitemaps automatically: Yoast SEO and RankMath for WordPress, Shopify and Webflow both generate /sitemap.xml automatically. If pages are missing from your sitemap, check whether they are set to noindex or whether the sitemap generation has limits.

Issue 6: Robots.txt Errors

What it is. The robots.txt file controls what crawlers can access. A misconfigured file can accidentally block Google from indexing important content.

How to find it. Visit yoursite.com/robots.txt and review the Disallow directives. Dangerous patterns include Disallow: / (blocks everything) or Disallow rules targeting directories with important content.

How to fix it. Your robots.txt should block non-public paths (admin panels, account dashboards, cart pages) and allow everything else. A safe template:

Test your robots.txt in Search Console > Settings > robots.txt tester.

Issue 7: Mobile Usability Problems

What it is. Google uses mobile-first indexing: it ranks pages based primarily on the mobile version. Pages with mobile usability issues receive rankings based on a degraded experience.

How to find it. Google Search Console > Experience > Mobile Usability. Common issues: text too small to read, clickable elements too close together, content wider than the screen.

How to fix it. Test your key pages in Chrome DevTools (F12, toggle device toolbar) at iPhone and Android screen sizes. Fix: minimum body font size of 16px, minimum tap target size of 48x48px with 8px spacing between targets, ensure no elements have fixed pixel widths wider than the mobile viewport.

Issue 8: HTTPS and Mixed Content

What it is. HTTPS is a confirmed ranking signal. Mixed content occurs when an HTTPS page loads resources over HTTP, which triggers browser security warnings and can suppress rankings.

How to find it. Look for the padlock icon in Chrome. If it shows a warning, mixed content is present. Chrome DevTools > Console shows mixed content warnings.

How to fix it. If your site is still on HTTP: enable SSL via your host (most provide free Let's Encrypt certificates) and set up 301 redirects from HTTP to HTTPS. For mixed content on an existing HTTPS site: find the HTTP resource URLs in DevTools and update them to HTTPS in your CMS.

Issue 9: Missing or Malformed Structured Data

What it is. Structured data (JSON-LD schema markup) helps Google understand your content and enables rich results: FAQ dropdowns, star ratings, breadcrumbs. Missing structured data is a missed opportunity for better SERP visibility.

How to find it. Run Google's Rich Results Test on your homepage, a blog post, and your contact page. Google Search Console > Enhancements also shows structured data errors.

How to fix it. Priority schema types for most small businesses:

• Organisation or LocalBusiness: business name, address, phone, URL, social profiles
• Article or BlogPosting: on all blog content
• FAQPage: on pages with FAQ sections (generates expanded FAQ snippets in search results)
• BreadcrumbList: enables breadcrumb display in search results

Most CMS SEO plugins handle Organisation schema automatically. FAQPage schema requires manual addition or a plugin that generates it from your FAQ sections. Validate all markup with the Rich Results Test before publishing.

Issue 10: Slow Time to First Byte

What it is. TTFB (Time to First Byte) is the time between a browser making a request and receiving the first byte of a response. Target: under 600 milliseconds. A slow TTFB signals server-side problems that delay everything else on the page.

How to find it. In PageSpeed Insights, look for the "Reduce server response times" recommendation. Also visible in Chrome DevTools > Network tab: click the HTML document request and check the Waiting (TTFB) time in the Timing panel.

How to fix it:

• Page caching: for WordPress, WP Rocket or Nitropack generate cached HTML pages instead of building them from the database on every request
• Content delivery network (CDN): Cloudflare's free plan caches static assets at edge servers globally, reducing latency for visitors far from your server
• Database optimisation: for dynamically generated pages, slow database queries are the most common cause of high TTFB

For more detail on the 18 technical factors that influence rankings, read the technical SEO checklist 2026. For a broader SEO strategy context, read why your website is not ranking.

For a broader look at how technical SEO fits into a full search strategy, read SEO for small business. If completing this audit is not practical alongside your core business responsibilities, an experienced SEO specialist can audit and fix all ten issues in one to two weeks. Our SEO service includes a full technical audit as the foundation of every engagement. Get in touch to start with a review of your site.