A technical audit checklist systematically identifies crawl barriers, indexing issues, site speed bottlenecks, and structural problems that prevent search engines from properly understanding and ranking your site. This guide walks through the core audit sequence—from crawl analysis and rendering checks to Core Web Vitals and security—using tools and decision frameworks practitioners rely on daily.
Begin every technical audit by confirming search engines can discover and access your pages. Download and parse robots.txt to verify you haven't accidentally blocked critical sections—common mistakes include disallowing CSS or JavaScript resources that Googlebot needs for rendering. Cross-reference your XML sitemap against actual crawlable URLs; tools like Screaming Frog will flag pages in the sitemap that return 404s or redirects, and pages excluded from the sitemap that should be indexed. Check HTTP status codes for every discovered URL. Redirect chains longer than two hops waste crawl budget and dilute link equity. Soft-404s—pages returning 200 but displaying 'not found' messages—confuse indexing. For large Canadian e-commerce sites or directories, segment your crawl by subdirectory or URL pattern to spot regional issues, such as /fr/ paths misconfigured to return English content. Confirm canonical tags point to the correct version, especially on paginated category pages or product variants where parameters proliferate.
Many modern frameworks—React, Vue, Next.js—deliver content client-side, creating a gap between what users see and what Googlebot initially receives. Use the URL Inspection tool in Google Search Console to compare the raw HTML response against the rendered output. If critical headings, product descriptions, or internal links appear only after JavaScript execution, you risk delayed or incomplete indexing. Run a crawl with JavaScript rendering enabled in Screaming Frog or Sitebulb, then compare it to a non-rendering crawl. Missing title tags, meta descriptions, or canonicals in the raw HTML are red flags. Implement server-side rendering or static generation for key landing pages—product detail pages, category hubs, cornerstone blog posts. For single-page applications, ensure proper handling of route changes and canonical URLs; history API navigation often leaves stale canonicals in the DOM. Prerendering services can bridge the gap for smaller teams, but verify the prerendered snapshot matches live content to avoid cloaking penalties.
Google's Core Web Vitals—Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift—use real-user thresholds from the Chrome User Experience Report. Pull field data for your domain through PageSpeed Insights or the CrUX API; if fewer than 75 percent of page loads meet the 'good' threshold, you face ranking consequences. Lab tools like Lighthouse and WebPageTest identify causes—render-blocking CSS, oversized hero images, third-party scripts—but scores in a clean lab environment often look better than real-world mobile performance on throttled networks. Audit image formats and compression: convert JPEGs to WebP or AVIF where browser support allows, lazy-load below-the-fold media, and size images to match display dimensions. Check font-loading strategies; font-display swap prevents invisible text but can trigger layout shifts if fallback metrics differ. Measure server response time separately; a slow Time to First Byte cascades into poor LCP regardless of front-end optimization. Canadian sites serving users across wide geographies benefit from a CDN with Toronto, Montreal, and Vancouver edge nodes to reduce latency.
Schema markup enhances search appearance—review stars, breadcrumbs, FAQs, event cards—but invalid or mismatched markup can strip those features. Run every template type through Google's Rich Results Test and the Schema Markup Validator. Common errors include missing required properties—Organization schema without a logo URL, Product schema without offers or aggregateRating—and mismatched itemtype hierarchies. Confirm JSON-LD snippets parse correctly; trailing commas or unescaped quotes break the entire block. For local Canadian businesses, ensure LocalBusiness schema includes accurate address, telephone with country code, and openingHours in ISO 8601 format. E-commerce sites must validate Product and Offer schema on every SKU; dynamic pricing updates should regenerate the markup server-side to reflect current availability and price. Use Search Console's Enhancements reports to track rich-result indexing; pages eligible but not showing often have competing markup from plugins or page builders that conflict.
Google's mobile-first index uses the mobile version of your site as the primary crawl target. Audit viewport meta tags to ensure width=device-width and initial-scale=1; missing or incorrect viewport settings cause horizontal scrolling and trigger mobile-usability warnings in Search Console. Test tap-target spacing—buttons and links need at least 48×48 CSS pixels with adequate padding to avoid accidental clicks on touch devices. Check font sizes; body text below 16px forces pinch-to-zoom, flagged as a usability issue. Confirm critical content and internal links exist in the mobile DOM, not hidden behind hamburger menus that require interaction to reveal. Run a mobile crawl and compare link graphs; if your mobile navigation omits category links or footer sections present on desktop, you create orphaned pages. Responsive images should serve appropriately sized variants using srcset and sizes attributes to avoid shipping 3000px-wide hero images to phones on cellular networks.
Sites serving both English and French must implement hreflang annotations to signal language and regional targeting. Each URL needs reciprocal hreflang tags pointing to all alternate versions, including a self-referencing tag. Use en-CA and fr-CA rather than generic en or fr to specify Canadian variants; this prevents Google from showing a UK English page to Toronto users or a France French page to Montreal searchers. Validate hreflang in bulk using tools like Merkle's hreflang tag testing tool or Sitebulb's hreflang audit. Common mistakes include orphaned hreflang references—tags pointing to URLs that return 404 or noindex—and missing return tags, which invalidate the entire cluster. Confirm each language version has unique, translated content; automated translation without human review often produces nonsensical or keyword-stuffed text that degrades user experience. Use separate URL structures—subdirectories like /en/ and /fr/ or subdomains—and set the appropriate lang attribute in the HTML element to reinforce language signals.
HTTPS is a confirmed ranking signal and a trust prerequisite. Verify your SSL certificate covers all subdomains—www, non-www, and any regional or staging environments accessible to crawlers. Check for mixed-content warnings where HTTPS pages load images, scripts, or stylesheets over HTTP; browsers block these resources, breaking layout or functionality. Use a crawler to identify insecure resources and update references to protocol-relative or full HTTPS URLs. Confirm HSTS headers are present to force secure connections and prevent downgrade attacks. Review your security.txt file if you operate a high-value domain; this allows researchers to report vulnerabilities responsibly. Audit redirect chains from HTTP to HTTPS and from non-www to www (or vice versa); multiple 301s slow page loads and leak referrer data. For Canadian businesses handling payments or personal information, ensure compliance with PIPEDA data-protection requirements and display clear privacy-policy links in the footer.
Run a comprehensive technical audit quarterly if you publish new content regularly or monthly during active development and migration projects. Crawl your site after every CMS update, theme change, or plugin installation to catch configuration drift early. Use continuous monitoring through Search Console and automated crawlers to alert you to sudden spikes in 404s, indexation drops, or Core Web Vitals degradation between full audits.
Screaming Frog excels at raw speed and granular filtering for large sites, making it ideal when you need to export specific URL segments or integrate with Google Analytics and Search Console APIs. Sitebulb provides more guided audit reports with visual issue clustering and prioritization, useful for presenting findings to clients or stakeholders. Both handle JavaScript rendering; choose based on whether you prioritize flexible data export or structured, client-ready deliverables.
Yes, especially for sites that serve different templates or hide content on mobile. Google's mobile-first index crawls the mobile version, so missing navigation links or content sections on mobile can orphan pages and lose rankings. Run separate crawls with mobile and desktop user agents, then diff the link graphs and on-page elements to identify discrepancies. Responsive sites with identical DOM still benefit from mobile performance audits focused on Core Web Vitals.
Crawl budget is the number of pages Googlebot fetches from your site in a given period, influenced by server speed, site authority, and crawl demand. Indexation is whether those crawled pages are added to Google's index. You can waste crawl budget on low-value pages—faceted navigation, session IDs, duplicate parameter variations—leaving high-value content undiscovered. Audit your server logs to see what Googlebot actually requests, then block or consolidate low-value URLs to prioritize strategic pages.
Use a specialized hreflang validator like Merkle's tool or Sitebulb's hreflang audit, which checks reciprocal tags and flags orphaned references across the entire cluster. Export your hreflang tags from your sitemap or crawl, then cross-reference each URL to ensure every alternate link returns a matching return tag. For complex implementations, maintain hreflang in a centralized XML sitemap rather than in-page tags to simplify updates and reduce the risk of missing reciprocal links.
Prioritize issues that actively block indexation—robots.txt disallows, noindex tags on key pages, server errors—since unindexed content cannot rank regardless of quality. Address severe Core Web Vitals failures that push pages below mobile-usability thresholds next. Lower-priority fixes like redirect-chain optimization or schema refinements can proceed in parallel with content development and link acquisition. Technical health and content quality compound; fixing one without the other leaves ranking upside unrealized.