<\/figcaption><\/figure>\n\n\n\nNow let us go through each area in detail. This is where the real audit work happens.<\/p>\n\n\n\n
[Image Suggestion: A step-by-step checklist graphic with icons for each category. <\/p>\n\n\n\n
Crawlability and Indexing<\/p>\n\n\n\n
This is the foundation. If Google cannot crawl your pages, nothing else matters.<\/p>\n\n\n\n
The things you need to check:<\/p>\n\n\n\n
\u2022 Is your robots.txt file correct and not blocking key pages<\/p>\n\n\n\n
\u2022 Have you submitted your XML sitemap to Google Search Console<\/p>\n\n\n\n
\u2022 Are your important pages actually indexed<\/p>\n\n\n\n
\u2022 Are there any pages accidentally set to no-index<\/p>\n\n\n\n
How to check: Go to Google Search Console and open the Coverage report. It shows exactly which pages are indexed, which have errors, and which are excluded.<\/p>\n\n\n\n
If important pages show as excluded, check if they have a no-index tag or if they are blocked in robots.txt. Fix those first.<\/p>\n\n\n\n
<\/span>Crawl Budget Optimization<\/span><\/h3>\n\n\n\nCrawl budget is the number of pages Google is willing to crawl on your site in a given time. Wasting it on useless pages means important pages get crawled less often.<\/p>\n\n\n\n
What to do:<\/p>\n\n\n\n
\u2022 Block low-value pages like tag archives or search result pages in robots.txt<\/p>\n\n\n\n
\u2022 Fix or remove URL parameters that create duplicate pages<\/p>\n\n\n\n
\u2022 Set up canonical tags on pages with similar content<\/p>\n\n\n\n
One client I worked with had an e-commerce site where every filter combination created a unique URL. That was tens of thousands of near-duplicate pages eating up crawl budget. We fixed it with proper canonicals and robots.txt rules. Rankings improved within a month.<\/p>\n\n\n\n
Simple rule: do not waste Google’s time on pages that do not matter.<\/p>\n\n\n\n
<\/span>Website Speed and Core Web Vitals<\/span><\/h3>\n\n\n\nSpeed is a ranking factor and a user experience factor. A slow site loses both rankings and visitors.<\/p>\n\n\n\n
Google’s Core Web Vitals are the key speed metrics to know: <\/p>\n\n\n\nMetric<\/td> What It Measures<\/td> Good Score<\/td><\/tr> LCP<\/td> How fast the main content loads<\/td> Under 2.5 seconds<\/td><\/tr> CLS<\/td> How much the page layout shifts<\/td> Under 0.1<\/td><\/tr> FID \/ INP<\/td> How fast the page responds to clicks<\/td> Under 200ms<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nCommon speed issues and fixes:<\/p>\n\n\n\nIssue<\/td> Fix<\/td><\/tr> Slow LCP<\/td> Compress images, use a CDN, defer non-critical JS<\/td><\/tr> High CLS<\/td> Set fixed sizes for images and ads<\/td><\/tr> Slow server response<\/td> Upgrade hosting, enable caching<\/td><\/tr> Large page size<\/td> Minify CSS and JS, remove unused code<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nUse Google PageSpeed Insights to check your scores. It gives you specific issues to fix, not just a number.<\/p>\n\n\n\n
<\/span>URL Structure and Internal Linking<\/span><\/h3>\n\n\n\nA clean URL helps both users and search engines understand what a page is about.<\/p>\n\n\n\n
Bad URL example: yourwebsite.com\/page?id=123&cat=56<\/p>\n\n\n\n
Good URL example: yourwebsite.com\/technical-seo-audit-guide<\/p>\n\n\n\n
The good URL tells Google exactly what the page covers. The bad URL tells it nothing.<\/p>\n\n\n\n
For internal linking, the goal is to connect related pages with clear anchor text. This spreads link authority and helps Google understand your site structure.<\/p>\n\n\n\n
Watch out for orphan pages. These are pages with no internal links pointing to them. Google rarely finds or ranks them. Run a crawl with Screaming Frog to find them.<\/p>\n\n\n\n
<\/span>Mobile SEO Checklist<\/span><\/h3>\n\n\n\nGoogle uses mobile-first indexing. That means it looks at your mobile version first when deciding how to rank your site.<\/p>\n\n\n\n
What to check:<\/p>\n\n\n\n
\u2022 Your site uses responsive design and adjusts to all screen sizes<\/p>\n\n\n\n
\u2022 Text is readable without zooming<\/p>\n\n\n\n
\u2022 Buttons and links are easy to tap on a small screen<\/p>\n\n\n\n
\u2022 Pages load fast on mobile connections<\/p>\n\n\n\n
Use Google Search Console under Mobile Usability to see any specific errors on your site.<\/p>\n\n\n\n
<\/span>On-Page Technical Elements<\/span><\/h3>\n\n\n\nThese are the technical elements on each page that Google reads when deciding how to rank it.<\/p>\n\n\n\n
\u2022 Title tags: each page should have a unique title under 60 characters<\/p>\n\n\n\n
\u2022 Meta descriptions: unique, under 160 characters, and includes the target keyword<\/p>\n\n\n\n
\u2022 Canonical tags: tell Google which version of a page is the main one<\/p>\n\n\n\n
\u2022 H1 tags: each page should have exactly one H1<\/p>\n\n\n\n
These are easy to check and easy to fix. A tool like Screaming Frog will flag missing or duplicate title tags and meta descriptions across your whole site in one crawl.<\/p>\n\n\n\n
<\/span>Image SEO Optimization<\/span><\/h3>\n\n\n\nImages are often the biggest cause of slow pages. They are also a missed opportunity for ranking in Google Images.<\/p>\n\n\n\n
What to do:<\/p>\n\n\n\n
\u2022 Convert images to WebP format for smaller file sizes<\/p>\n\n\n\n
\u2022 Compress all images before uploading<\/p>\n\n\n\n
\u2022 Add descriptive ALT text to every image<\/p>\n\n\n\n
\u2022 Use lazy loading so images only load when visible<\/p>\n\n\n\n
<\/span>JavaScript SEO<\/span><\/h3>\n\n\n\nThis one catches a lot of developers off guard. If your site is built with heavy JavaScript frameworks, Google might not be able to read your content properly.<\/p>\n\n\n\n
The issue is that Googlebot renders pages in two waves. First it crawls the HTML. Then it comes back to render JavaScript. But that second wave can take days or weeks. During that time, your content might not be indexed.<\/p>\n\n\n\n
The fix options:<\/p>\n\n\n\n
\u2022 Use server-side rendering (SSR) so Google gets the full HTML right away<\/p>\n\n\n\n
\u2022 Or use pre-rendering for content that does not change often<\/p>\n\n\n\n
\u2022 At minimum, reduce heavy JavaScript on your most important pages<\/p>\n\n\n\n
If your site is built on a framework like Next.js or Nuxt.js, SSR is already built in. Use it.<\/p>\n\n\n\n
<\/span>Schema and Structured Data<\/span><\/h3>\n\n\n\nSchema markup is code you add to your pages to help Google understand what the content is about. It can also earn you rich snippets in search results.<\/p>\n\n\n\n
Rich snippets are those star ratings, FAQs, and recipe details you see directly in Google results. They make your listing stand out.<\/p>\n\n\n\n
Start with these schema types:<\/p>\n\n\n\n
\u2022 Article or BlogPosting for content pages<\/p>\n\n\n\n
\u2022 FAQPage for pages with questions and answers<\/p>\n\n\n\n
\u2022 Product for e-commerce product pages<\/p>\n\n\n\n
\u2022 LocalBusiness if you have a local business<\/p>\n\n\n\n
Use JSON-LD format. It is the cleanest way to add schema without touching your page HTML. Google recommends it.<\/p>\n\n\n\n
Check your structured data using Google’s Rich Results Test<\/a> to make sure it is valid.<\/p>\n\n\n\n<\/span>Full Audit Checklist<\/span><\/h3>\n\n\n\n