Technical SEO Audit Checklist: 47 Items Your Phoenix Website Needs to Pass
Content and links cannot overcome a broken technical foundation. Here are the 47 items we check in every Phoenix website audit.
Why Technical SEO Is the Foundation Everything Else Sits On
You can write the best content on the internet and build the most authoritative link profile in your market, and none of it matters if Google cannot properly crawl, render, and index your pages. Technical SEO is the infrastructure layer. If it is broken, everything built on top of it underperforms. In Phoenix specifically, we see technical SEO issues more frequently in businesses that had their websites built by general web designers rather than developers who understand search engine requirements. The site looks fine visually but is riddled with crawl errors, duplicate content, missing structured data, slow load times, and indexation problems that silently prevent it from ranking. A full technical audit takes 4-6 hours and should be repeated quarterly. What follows is our complete 47-point checklist, organized by category, with specific pass/fail criteria for each item.
Crawlability and Indexation (Items 1-12)
1. Robots.txt file exists and is accessible at domain.com/robots.txt. It should not block CSS or JavaScript files that Google needs to render your pages. 2. XML sitemap exists, is submitted to Google Search Console, and includes only indexable pages (200 status, not noindexed, canonical pointing to self). 3. No orphan pages — every important page is linked from at least one other page on the site. Check by comparing your sitemap URLs against pages found through an internal link crawl. 4. Crawl depth — important pages should be reachable within three clicks from the homepage. Service pages buried four or five levels deep get crawled less frequently. 5. No redirect chains — any redirect should go directly to the final destination. Chains of two or more redirects add latency and leak link equity. 6. No redirect loops — test all redirects to confirm they terminate. 7. All internal links return 200 status codes. No broken internal links (404s). 8. Canonical tags on every page pointing to the preferred version. No conflicting canonicals. 9. Hreflang tags if serving multiple languages or regions — not common for Phoenix-only businesses but critical for businesses serving both English and Spanish markets. 10. Pagination handled with rel=next/prev or scroll-based loading — paginated content should not create duplicate title tags and meta descriptions. 11. No accidental noindex tags on pages that should be indexed. Check both HTML meta tags and HTTP headers. 12. Google Search Console shows no critical crawl errors and coverage report shows all important pages as 'Valid.'
Core Web Vitals and Page Speed (Items 13-22)
13. Largest Contentful Paint (LCP) under 2.5 seconds on mobile. This measures how fast the main content loads. The most common LCP culprits in Phoenix business sites: unoptimized hero images, render-blocking CSS, and slow server response times. 14. First Input Delay (FID) or Interaction to Next Paint (INP) under 200 milliseconds. This measures responsiveness. Heavy JavaScript, especially chat widgets and analytics scripts, are the usual offenders. 15. Cumulative Layout Shift (CLS) under 0.1. This measures visual stability. Images and ads without explicit width and height attributes cause layout shift. Web fonts loading after the initial render cause text to shift. 16. Time to First Byte (TTFB) under 600 milliseconds. If TTFB is slow, your hosting infrastructure is the bottleneck — no amount of front-end optimization will fix a slow server. 17. Total page weight under 3MB, ideally under 1.5MB. 18. Images served in WebP or AVIF format with appropriate compression. No images over 200KB unless they are full-screen hero images, which should not exceed 400KB. 19. All images have explicit width and height attributes to prevent layout shift. 20. CSS and JavaScript minified and compressed with gzip or Brotli. 21. Above-the-fold content loads without being blocked by JavaScript. Critical CSS inlined or preloaded. 22. Third-party scripts audited — every external script (analytics, chat, pixels, fonts) contributes to load time. Remove any that are not actively used.
On-Page Elements and Structure (Items 23-34)
23. Every page has a unique, descriptive title tag under 60 characters including the primary keyword and brand name. 24. Every page has a unique meta description under 160 characters that accurately describes the content and includes a call to action. 25. Every page has exactly one H1 tag that contains the primary keyword. 26. Heading hierarchy is logical — H2s under H1, H3s under H2. No skipped heading levels. 27. URLs are clean, descriptive, and contain the primary keyword. No parameter strings, session IDs, or auto-generated gibberish. 28. Internal links use descriptive anchor text, not 'click here' or 'learn more.' 29. Images have descriptive alt text that includes relevant keywords where natural. 30. No thin content pages — every indexable page should have at least 300 words of substantive, unique content. Service pages and location pages should have 800+ words. 31. No duplicate content — check for www vs. non-www versions, HTTP vs. HTTPS versions, trailing slash vs. non-trailing slash versions all resolving to different URLs. 32. Schema markup implemented: LocalBusiness schema on the homepage and contact page, Service schema on service pages, FAQ schema on pages with FAQ sections, Article schema on blog posts, BreadcrumbList schema on all interior pages. 33. Open Graph tags present for social sharing — og:title, og:description, og:image, og:url. 34. Favicon present in multiple sizes for browser tabs, mobile bookmarks, and app icons.
Mobile Usability (Items 35-40)
35. Viewport meta tag present: <meta name='viewport' content='width=device-width, initial-scale=1'>. 36. No horizontal scrolling on any page at any mobile viewport width. 37. Tap targets (buttons, links, form fields) are at least 48x48 pixels with at least 8 pixels of spacing between adjacent targets. 38. Font size minimum 16px for body text on mobile. Anything smaller requires pinch-zooming, which Google considers a mobile usability failure. 39. Forms are mobile-optimized — appropriate input types (tel for phone, email for email), fields are full-width, submit buttons are easily tappable. 40. No intrusive interstitials or pop-ups that cover more than 30% of the screen on mobile. Google has penalized sites for intrusive interstitials since 2017.
Security and Infrastructure (Items 41-47)
41. HTTPS enabled site-wide with a valid SSL certificate. No mixed content warnings (HTTP resources loaded on HTTPS pages). 42. HTTP to HTTPS redirect in place — all HTTP URLs 301 redirect to their HTTPS equivalents. 43. Security headers configured: X-Content-Type-Options, X-Frame-Options, Content-Security-Policy at minimum. 44. No exposed sensitive files — wp-config.php, .env files, database backups, and other sensitive files should not be accessible via direct URL. 45. 404 page returns a proper 404 HTTP status code (not a 200 with a 'page not found' message, which is called a soft 404). 46. Server responds correctly to conditional requests with proper cache headers — static assets should have cache expiration of at least one year. 47. DNS is configured correctly with no unnecessary redirects at the DNS level and CDN is enabled for static assets. When this audit is complete, assign each item a pass, fail, or warning status. Address all fails first, then warnings. Re-audit quarterly. Technical SEO is not a one-time project — it is ongoing maintenance, just like maintaining any other piece of business infrastructure.