A technical SEO audit finds the structural problems on your website that prevent Google from crawling, indexing, and ranking your pages. Most websites have at least three to five significant technical issues — and many have more. Fixing them does not guarantee rankings, but failing to fix them guarantees you will not reach your potential.
This checklist covers every area of technical SEO that matters in 2026. Work through it in order. Each section builds on the previous one.
1. Crawlability and indexing
Google can only rank pages it has found and indexed. Crawlability problems are the most fundamental technical SEO issues — and the easiest to overlook.
Check your robots.txt. Visit yourdomain.com/robots.txt. Confirm it does not block important pages or directories from being crawled. A misconfigured robots.txt can accidentally prevent Google from crawling your entire site.
Submit your sitemap to Google Search Console. Your XML sitemap tells Google which pages exist and when they were updated. Go to Search Console → Sitemaps → enter your sitemap URL. Confirm there are no errors or warnings.
Check indexing status. In Search Console, go to Pages → review the “Not indexed” tab. Common reasons include: noindex tags, crawl errors, duplicate content, and soft 404s. Each needs a specific fix.
Use site:yourdomain.com in Google. This search shows approximately how many of your pages Google has indexed. If the number is significantly lower than your total page count, you have an indexing problem.
Check for crawl errors. Search Console → Settings → Crawl Stats shows you how many pages Googlebot crawls daily and whether there are any crawl errors. A spike in errors or a sudden drop in crawl rate often precedes ranking drops.
Verify canonical tags. Every page should have a canonical tag pointing to the preferred version of that URL. Check that canonical tags are self-referencing on original content and pointing to the correct URL on duplicate or near-duplicate pages.
2. Site architecture and URL structure
URLs should be clean and descriptive. /services/web-design is better than /page?id=47. URLs with numbers, query parameters, or no meaningful structure are harder for both users and Google to understand.
Check for orphan pages. These are pages that exist on your site but have no internal links pointing to them. Google may never find them. Use a crawl tool (Screaming Frog, Ahrefs, or Sitebulb) to identify pages that receive no internal links.
Review your internal link structure. Important pages should receive more internal links. Your most valuable content — service pages, pillar blog posts, key landing pages — should be linked from multiple places across the site.
Check redirect chains. A redirect chain is when Page A redirects to Page B which redirects to Page C. Each redirect adds load time and dilutes link equity. Redirect chains should be resolved so Page A redirects directly to Page C.
Verify HTTPS. Your site should be fully served over HTTPS with no mixed content warnings. Check Chrome DevTools Console for any HTTP resources being loaded on HTTPS pages.
Check for duplicate pages. WWW vs non-WWW, HTTP vs HTTPS, trailing slash vs no trailing slash — these create four potential versions of every URL. Only one should be accessible; the others should redirect to the canonical version.
3. Core Web Vitals
Core Web Vitals are Google’s user experience signals. They affect rankings, particularly in competitive queries where content quality is similar across ranking pages.
Largest Contentful Paint (LCP) — measures how long it takes for the largest visible element on the page to load. Target: under 2.5 seconds. Common causes of poor LCP: unoptimised images, slow server response time, render-blocking JavaScript.
Interaction to Next Paint (INP) — measures responsiveness when a user interacts with the page. Target: under 200ms. Poor INP is usually caused by heavy JavaScript execution blocking the main thread.
Cumulative Layout Shift (CLS) — measures visual stability as the page loads. Target: under 0.1. CLS is caused by images without defined dimensions, dynamically injected content, and web fonts loading late.
How to check: Google Search Console → Core Web Vitals shows field data for your site. PageSpeed Insights at pagespeed.web.dev shows lab data for individual pages. Both matter.
Fix images first. Images are the most common cause of both slow LCP and high CLS. Every image should have explicit width and height attributes, be in WebP format where possible, and use loading="lazy" for below-the-fold images.
Audit your JavaScript. Use Chrome DevTools → Performance panel to identify long tasks. Long tasks (over 50ms) on the main thread block interactivity and hurt INP.
4. Structured data
Structured data (schema markup) tells Google specifically what type of content is on your page. It enables rich results — FAQ dropdowns, review stars, event listings, article bylines — which increase click-through rates from search results.
Check existing schema. Use Google’s Rich Results Test (search.google.com/test/rich-results) to see what schema Google detects on your pages. Verify there are no errors or warnings.
Add schema where missing. Priority schema types for most business websites:
- Organization — name, logo, contact details, social profiles
- LocalBusiness — address, opening hours, service area (for businesses serving specific locations)
- WebSite — enables the Sitelinks search box in Google
- BreadcrumbList — shows page hierarchy in search results
- FAQPage — shows expandable FAQ answers in search results (significant click-through boost)
- Article / BlogPosting — for blog content, enables article rich results
- Product — for e-commerce, required for free product listings in Google Shopping
- Review / AggregateRating — shows star ratings in search results
Validate all schema. Every schema implementation should be tested with the Rich Results Test before publishing. Invalid schema does not produce rich results and can cause Search Console warnings.
5. Page speed
Page speed affects rankings, conversion rates, and user experience. Slow pages rank lower, convert worse, and increase bounce rates.
Compress images. WebP format produces images 25–35% smaller than JPEG at equivalent quality. Every image on your site should be converted to WebP. Use tools like Squoosh or Cloudflare Image Resizing.
Enable browser caching. Static assets — CSS, JavaScript, images, fonts — should be cached by browsers so returning visitors load pages faster. Configure cache headers with long expiry times for assets that do not change frequently.
Minimise render-blocking resources. CSS and JavaScript that block page rendering delay LCP. Load critical CSS inline, defer non-critical JavaScript, and remove unused CSS.
Use a CDN. A Content Delivery Network serves your static assets from servers close to the user. For UAE businesses targeting international visitors, or for Mauritius businesses targeting European buyers, a CDN significantly reduces load time for distant users.
Check server response time (TTFB). Time to First Byte should be under 200ms. Slow TTFB is caused by slow hosting, slow database queries, or lack of server-side caching. Upgrade hosting or implement server-side caching if TTFB exceeds 500ms.
6. Mobile optimisation
Google uses mobile-first indexing. Your site’s mobile version is what Google primarily uses to determine rankings, regardless of where your traffic comes from.
Test mobile usability. Search Console → Mobile Usability shows pages with specific mobile issues: text too small, clickable elements too close together, content wider than screen.
Test on real devices. Chrome DevTools’ device emulation is useful but not the same as testing on a real phone. Test on at least one Android and one iOS device.
Check tap target sizes. Buttons and links should be at least 48×48px to be reliably tappable on touch screens. Smaller targets cause accidental taps and high bounce rates.
Verify font sizes. Body text should be at least 16px on mobile. Text smaller than 12px is flagged as “text too small to read” in Search Console.
7. Hreflang and international SEO
For websites targeting multiple languages or countries, hreflang tags tell Google which version of a page to show users in each locale.
Implement hreflang correctly. Each hreflang tag must reference every alternate version, including itself. If you have English, Arabic, and French versions of a page, each page must have hreflang tags for all three plus x-default.
Use correct language codes. en for English, ar for Arabic, fr for French. For country-specific targeting, use en-AE for English in UAE, en-US for English in the US, fr-MU for French in Mauritius.
Confirm hreflang in Search Console. Search Console → Enhancements → Hreflang shows implementation errors. The most common: missing reciprocal tags, incorrect language codes, and pages returning 404 errors.
8. Content quality signals
Technical SEO cannot compensate for poor content — but strong technical fundamentals amplify good content’s performance.
Check for thin content. Pages with fewer than 300 words or that primarily duplicate other pages on your site can dilute your site’s quality signals. Consolidate thin pages or expand them to cover the topic adequately.
Check for duplicate content. Use a tool like Siteliner or Copyscape to identify pages that share significant amounts of content. Duplicate content confuses Google about which version to rank.
Verify title tags and meta descriptions. Every page should have a unique title (50–60 characters) and description (150–155 characters). Duplicate titles cause Google to rewrite them. Missing descriptions leave Google to generate its own, which may not represent the page well.
Check heading hierarchy. Each page should have exactly one H1 tag containing the primary keyword. H2s and H3s should structure the content logically. Heading tags should not be used purely for visual styling.
How to prioritise what you fix first
Not all technical SEO issues have equal impact. Prioritise in this order:
- Indexing issues — If Google cannot find or index your pages, nothing else matters.
- Core Web Vitals failures — Especially if you are in competitive verticals.
- Schema markup gaps — High ROI for the time invested, directly improves click-through rates.
- Duplicate content and canonicalisation — Prevents Google from splitting ranking signals across multiple versions of the same page.
- Page speed — After the above are resolved, sustained page speed improvement compounds over time.
Run this audit quarterly. Technical SEO is not a one-time project — sites accumulate issues as they grow.
If you want a technical SEO audit conducted on your site with specific recommendations, contact the Carril Agency team. We audit websites across UAE, US, and Mauritius markets.
FAQ
How long does a technical SEO audit take?
For a site under 500 pages, a thorough technical audit takes 2–4 hours of analysis plus time to document findings. For larger sites, allow 1–3 days. Using automated tools like Screaming Frog or Ahrefs Site Audit speeds up the data collection phase significantly.
What tools do I need for a technical SEO audit?
Free: Google Search Console, Google PageSpeed Insights, Google’s Rich Results Test, Chrome DevTools. Paid (recommended): Screaming Frog ($200/year), Ahrefs or Semrush ($100–200/month). A professional audit uses both free and paid tools.
How often should I run a technical SEO audit?
Quarterly for most sites. After any major site update, redesign, or migration. After a significant traffic drop — technical issues are often the cause of sudden ranking changes.
Can technical SEO alone improve my rankings?
Technical SEO removes obstacles to ranking — it does not create rankings on its own. A technically perfect site with poor content and no backlinks will not rank for competitive terms. Technical SEO is foundational: it ensures your content and links can work as intended.
What is the most common technical SEO issue?
Crawlability and indexing problems are the most common, particularly on sites that have been migrated, rebuilt, or grown organically without technical oversight. Robots.txt errors that accidentally block important pages are surprisingly common and easy to miss.
How do I know if my technical SEO is working?
Track organic impressions and clicks in Google Search Console over 60–90 days after fixing technical issues. Indexing improvements typically show in Search Console within 2–4 weeks. Core Web Vitals improvements appear in field data 28 days after the fix is deployed (Google uses a 28-day rolling average).
Do I need a developer to fix technical SEO issues?
Some issues — editing robots.txt, adding schema markup, fixing meta tags — can be handled without developer skills using CMS plugins or direct file editing. Core Web Vitals improvements, redirect fixes, and server-side changes usually require developer involvement. Webflow-hosted sites can resolve many technical issues without code.
