How to Run a Technical SEO Audit With a Prioritized Fix Plan

Repeatable Technical SEO Audit: Your Hands-On Guide

A robust technical SEO audit isn't a one-off task; it's a repeatable process that ensures your website's foundation supports its organic growth. This guide provides concrete steps, commands, and a checklist for a hands-on audit, designed for freelancers to deliver actionable, prioritized fix lists.

1. Crawlability: Ensuring Google Can See Your Site

Objective: Verify search engines can access and process your website's content without hindrance.

Tools: Screaming Frog SEO Spider, Google Search Console (GSC).

Steps:

  1. Crawl Your Site:
    • Open Screaming Frog. Enter your domain and click "Start."
    • Check Status Codes: After the crawl, go to the "Response Codes" tab. Filter by "Client Error (4xx)" and "Server Error (5xx)".
      • Action: Identify and fix 404s (broken links) and 5xx errors (server issues). For 404s, implement 301 redirects to relevant live pages or update internal links.
  2. Review robots.txt:
    • Access your robots.txt file (e.g., yourdomain.com/robots.txt).
    • Check for Disallow directives: Ensure you're not accidentally blocking critical CSS, JavaScript, or important pages/sections.
    • Verify Sitemap directive: Confirm it points to your primary XML sitemap.
    • GSC: Go to "Settings > Crawl Stats" to see Google's crawl activity. Look for spikes or drops. Check "Index > Pages" report for "Excluded by robots.txt" reasons.
  3. Crawl Depth & Structure:
    • In Screaming Frog, analyze "Crawl Depth" (under "Internal" tab). Important pages should be reachable within 3-4 clicks from the homepage.
    • Action: If important pages are deep, improve internal linking.

Checklist:

  • robots.txt is valid and not blocking essential resources.
  • No excessive 4xx/5xx errors.
  • Important pages are easily discoverable (low crawl depth).

Common Mistakes: Blocking CSS/JS files, accidental Disallow: / on production, outdated robots.txt.

2. Index Coverage: Getting Your Pages in Google's Index

Objective: Confirm all important pages are indexed and discoverable in search results.

Tools: GSC, Screaming Frog.

Steps:

  1. GSC "Pages" Report:
    • Navigate to "Index > Pages" in GSC.
    • Focus on "Not indexed" reasons:
      • "Crawled - currently not indexed": Often indicates low-quality, thin content, or lack of internal links.
      • "Discovered - currently not indexed": Google knows about the page but hasn't crawled it yet (crawl budget, internal linking issues).
      • "Excluded by 'noindex' tag": Is this intentional? If not, remove the noindex tag.
      • "Blocked by robots.txt": Cross-reference with your robots.txt file.
    • Action: Address the root cause for each "Not indexed" reason. Improve content, add internal links, or remove noindex tags as appropriate.
  2. Screaming Frog noindex Check:
    • In Screaming Frog, filter by "Directives > Noindex." Ensure no critical pages are accidentally noindexed.
  3. Site Search Check:
    • Perform a site:yourdomain.com search on Google. Spot-check if key pages are appearing.

Checklist:

  • All critical pages are indexed.
  • No important pages are accidentally noindexed or blocked.
  • Reasons for "Not indexed" pages are understood and addressed.

Common Mistakes: Leaving noindex tags from staging environments, blocking crawl via robots.txt but expecting indexation.

3. Core Web Vitals (CWV): User Experience & Performance

Objective: Identify and fix performance issues impacting user experience, particularly Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).

Tools: GSC, PageSpeed Insights (PSI), Chrome Lighthouse (DevTools).

Steps:

  1. GSC CWV Report:
    • Go to "Experience > Core Web Vitals" in GSC.
    • Identify URL groups categorized as "Poor" or "Needs improvement" for mobile and desktop.
    • Action: Prioritize fixing issues on "Poor" URLs first.
  2. PageSpeed Insights (PSI):
    • Take a problematic URL from GSC and run it through PSI.
    • Analyze Results: PSI provides both field data (real user experience) and lab data (simulated performance).
    • Focus on diagnostics:
      • LCP: Look for "Eliminate render-blocking resources," "Serve images in next-gen formats," "Reduce server response times."
      • INP: Look for "Reduce JavaScript execution time," "Minimize main-thread work."
      • CLS: Look for "Ensure text remains visible during webfont load," "Set explicit width and height on image elements."
    • Action: Implement PSI's recommendations.
  3. Lighthouse (Chrome DevTools):
    • Open your website in Chrome, right-click, and select "Inspect." Go to the "Lighthouse" tab.
    • Generate a report for "Performance." This offers more granular detail than PSI for development teams.

Checklist:

  • CWV metrics are "Good" or have a clear improvement plan.
  • Images are optimized (compressed, WebP, lazy-loaded).
  • Render-blocking resources are minimized.
  • Layout shifts are addressed (explicit dimensions for media).

Common Mistakes: Large unoptimized images, excessive third-party scripts, lack of image/video dimensions, slow server response.

4. Canonicalization & Duplication: Managing Content Uniqueness

Objective: Ensure search engines identify the preferred (canonical) version of a page and avoid duplicate content penalties.

Tools: Screaming Frog, GSC.

Steps:

  1. Screaming Frog Canonical Check:
    • Crawl your site. Go to the "Canonicals" tab.
    • Look for:
      • Missing Canonical: Pages without a rel="canonical" tag.
      • Incorrect Canonical: Canonical pointing to a 4xx/5xx page, or an irrelevant page.
      • Multiple Canonicals: More than one canonical tag on a page.
    • Action: Implement self-referencing canonicals for unique pages. Correct incorrect canonicals.
  2. Duplicate Content Check:
    • In Screaming Frog, use the "Content > Duplicates" filter to find exact or near-duplicate pages.
    • Action: Consolidate content, use rel="canonical", or noindex non-essential duplicates.
  3. GSC Duplicate Warnings:
    • In GSC "Index > Pages" report, look for "Duplicate, Google chose different canonical than user" or "Duplicate, submitted URL not selected as canonical."
    • Action: Investigate why Google's choice differs and adjust your canonical strategy.
  4. URL Consistency:
    • Ensure consistent use of www vs. non-www, HTTP vs. HTTPS, and trailing slashes. Implement 301 redirects for non-preferred versions.

Checklist:

  • Every page has a self-referencing or correct canonical tag.
  • No significant duplicate content issues.
  • Consistent URL structure enforced with 301 redirects.

Common Mistakes: Forgetting canonicals on paginated series, parameter URLs creating duplicates, canonicals pointing to non-existent pages.

5. Schema Markup: Enhancing Search Visibility

Objective: Implement structured data to help search engines understand your content and potentially display rich results.

Tools: Schema.org, Google's Rich Results Test, Screaming Frog.

Steps:

  1. Identify Key Page Types:
    • Determine which page types would benefit most from schema (e.g., Product, Article, LocalBusiness, FAQ, Recipe, Review, BreadcrumbList).
  2. Test Existing Schema:
    • Use Google's Rich Results Test for your critical pages.
    • Look for: Errors, warnings, and missing recommended properties.
    • Action: Fix errors immediately. Address warnings to improve schema quality.
  3. Screaming Frog Schema Overview:
    • Crawl your site and go to the "Schema" tab. This gives an overview of schema types present across the site.
  4. Implement New Schema:
    • If schema is missing, use Schema.org documentation to create appropriate JSON-LD.
    • Action: Ensure schema accurately reflects the visible content on the page.

Checklist:

  • Critical page types have appropriate, valid schema markup.
  • Schema is error-free and addresses warnings in Rich Results Test.
  • Schema content aligns with page content.

Common Mistakes: Incorrect schema type, missing required properties, schema not updated with content changes.

6. Internal Linking: Spreading Link Equity & Discoverability

Objective: Optimize internal link structure to guide users and search engines to important content and distribute link equity.

Tools: Screaming Frog, GSC.

Steps:

  1. Screaming Frog Internal Link Analysis:
    • Crawl your site. Go to the "Internal" tab.
    • Analyze "Inlinks": Identify important pages with few internal links.
    • Analyze "Crawl Depth": Ensure critical pages are not too deep.
    • Anchor Text: Review anchor text used for internal links (under "Inlinks" tab for a specific URL).
    • Action: Add internal links from relevant, high-authority pages to important pages with low inlink count. Use descriptive, keyword-rich anchor text.
  2. GSC Internal Links Report:
    • Go to "Links > Internal links" in GSC.
    • Identify pages with few internal links: Cross-reference with your important pages.
    • Action: Improve internal linking to these pages.
  3. Orphaned Pages:
    • Compare your sitemap URLs with crawled URLs in Screaming Frog. Pages in the sitemap but not crawled internally are orphaned.
    • Action: Add internal links to orphaned pages if they should be discoverable.

Checklist:

  • Important pages receive sufficient internal link equity.
  • Anchor text is descriptive and varied.
  • No unintentional orphaned pages.
  • Navigation is logical and crawlable.

Common Mistakes: Flat site architecture, too many links in the footer, generic anchor text ("click here").

7. Sitemaps & Robots.txt: Guiding Search Engines

Objective: Ensure robots.txt and XML sitemaps are correctly configured to guide search engine crawlers efficiently.

Tools: GSC, robots.txt validator, XML Sitemap validator.

Steps:

  1. robots.txt Review (Revisited):
    • Confirm User-agent directives are correct.
    • Ensure Sitemap: directive points to the correct, accessible sitemap URL.
    • Use a robots.txt validator (e.g., Google's robots.txt Tester in GSC) to check syntax.
    • Action: Correct any syntax errors or misconfigurations.
  2. Sitemap Validation:
    • In GSC, go to "Sitemaps." Check for errors for your submitted sitemaps.
    • Inspect Sitemap Content: Ensure the sitemap only contains canonical, indexable URLs (no 4xx, 5xx, noindex pages).
    • lastmod Dates: If used, ensure lastmod dates are accurate.
    • Action: Remove non-indexable URLs from the sitemap. Resubmit if changes are made.

Checklist:

  • robots.txt is valid, correctly configured, and points to the sitemap.
  • Sitemap is submitted to GSC and error-free.
  • Sitemap contains only canonical, indexable URLs.

Common Mistakes: Blocking sitemap in robots.txt, sitemap containing non-indexable URLs, outdated sitemap.

Prioritizing Fixes: Impact vs. Effort

Once you've identified all issues, categorize them based on their potential impact on SEO and the effort required to fix them.

High Impact / Low Effort (P1 - Do First): * robots.txt blocking critical pages. * Missing or incorrect canonicals on key pages. * Broken internal links on high-authority pages. * Basic image compression.

High Impact / High Effort (P2 - Plan & Execute): * Major site architecture changes. * Extensive CWV improvements requiring code refactoring. * Implementing comprehensive schema across a large site.

Low Impact / Low Effort (P3 - Tidy Up): * Minor schema warnings. * Optimizing a few non-critical images.

Low Impact / High Effort (P4 - Reconsider): * Avoid these unless all other high-impact issues are resolved.

Output: A clear table or bulleted list for the client:

Problem Location(s) Recommended Fix Impact Effort
404 Error (Broken Internal Link) /old-page/ linked from /important-page/ Implement 301 redirect from /old-page/ to /new-relevant-page/ High Low
Missing Canonical Tag /product-category?sort=price Add <link rel="canonical" href="/product-category/"> High Low
Slow LCP on Product Pages /product-a/, /product-b/ Optimize hero image (WebP, lazy load), defer non-critical CSS High High
"Crawled - currently not indexed" /blog/old-post-1/, /blog/old-post-2/ Improve content quality, add internal links from newer, relevant posts Medium Medium
Schema Warning: Missing reviewCount /product-page/ Add reviewCount property to Product schema (if applicable) Low Low

Ready to transform your website's technical foundation? Get a done-for-you audit with a clear, prioritized fix plan: https://kwork.com/audit/52991071/technical-seo-audit-with-a-clear-prioritized-fix-plan or hire me at https://freelancehunt.com/freelancer/sspoisk

Originally posted at https://guardlabs.online/care/

Комментарии

Отправить комментарий

Популярные сообщения из этого блога

Как обновить 40 000 товаров на OkayCMS за секунды и не потерять 120 тысяч рублей на заказах

Как обновить 40 000 товаров на OkayCMS за секунды и не потерять 120 тысяч рублей на заказах Это было в четверг, года три назад. У нашего клиента на OkayCMS было около 42 000 товаров — сантехника, насосы, фитинги. Курс евро тогда подпрыгнул на 8%, и нам нужно было срочно пересчитать розницу. Включили стандартный импорт. Скрипт поработал минуты три, словил 504 Gateway Timeout на сервере и тихо умер на середине файла. Знаете, что произошло дальше? Половина базы обновилась, а половина осталась со старыми ценами. Хуже того, из-за сбоя в сессии затерлись остатки по топовым немецким насосам. Они встали в статус «в наличии» по цене пятилетней давности. За три часа, пока менеджеры пили кофе и не замечали беды, на сайт пришло девять заказов. Убыток на ровном месте — 124 000 рублей. Из своего кармана мы их не платили, но седых волос у меня прибавилось знатно. Клиента мы тогда еле удержали. Этот факап заставил нас полностью переписать подход к тому, как делается синхронизация цен okaycms. Бо...
Далее...
You’ve done everything right. Your WordPress site is fast, mobile-friendly, and ranks well on Google. You’ve optimized your images, secured your login page, and your human visitors seem happy. So, you decide to run a new kind of test—an "AI Agent Audit"—and the results are a sea of red flags. Your site, for all its human-centric design, is nearly unreadable to the next generation of web users: AI agents. If this sounds like a problem for "the future," think again. That future is arriving much faster than you expect. Welcome to the new frontier of web optimization: Agent Readiness. What is "AI Agent Readiness," Anyway? In the simplest terms, AI Agent Readiness measures how easily an automated system, like the browsing modules in ChatGPT, Perplexity AI, or Google's AI Overviews, can access, understand, and accurately synthesize the content on your website. For two decades, we’ve optimized for search engine *crawlers* (like Googlebot) and human...
Далее...

Архитектура торговых систем: уроки инженера-строителя

Архитектура торговых систем: уроки инженера-строителя Меня зовут Станислав. Мне 58, и большую часть своей сознательной жизни я строил. В 80-х, будучи молодым инженером-схемотехником, я собирал свои первые «конструкции» на базе Z80 — это были клоны ZX Spectrum, мечта любого мальчишки того времени. А с 2004 по 2022 год я строил вещи куда более материальные: моя небольшая фирма в Харькове занималась ремонтом и остеклением балконов. Я знаю запах бетонной пыли, звук перфоратора, входящего в панельную стену, и то чувство ответственности, когда ты подписываешь акт выполненных работ. Ты даешь гарантию, что твой балкон выдержит и шкаф с консервацией, и детские игры, и порывы зимнего ветра. Ты отвечаешь за безопасность людей своей репутацией и деньгами. В 2022 году мой бизнес, как и тысячи других, был уничтожен войной. Пришлось начинать с нуля. Мой инженерный склад ума не позволял мне сидеть сложа руки или полагаться на удачу. Я вернулся к тому, с чего начинал — к системам и логике. Только вм...
Далее...