A technical SEO audit checklist is a practical set of checks used to find website issues that stop important pages from being crawled, indexed, understood or prioritised correctly by search engines.
Use it when your website has valuable products, services or content, but search visibility is weaker than expected. The checklist helps you move from “something is wrong” to a clear list of technical issues, likely causes, evidence and fixes.
This page gives you a working checklist, shows how to use it, explains what each check is for and helps you decide which issues should be fixed first.
For broader support, see our technical SEO South Africa service page.
Quick technical SEO audit checklist
Use this as a working checklist. For each item, record the issue, affected URLs, evidence, priority and fix owner.
Crawlability
Check whether search engines can reach important pages.
Look for blocked URLs, server errors, broken internal links, orphan pages and pages that only appear through forms, filters or JavaScript interactions.
This is critical because a page that cannot be crawled properly cannot perform properly in search.
Indexation
Check whether the right pages are eligible to appear in search.
Look for important pages marked noindex, low-value URLs being indexed, duplicate parameter URLs, internal search pages, test URLs and thin pages.
This is critical because important pages may be hidden while low-value URLs consume attention.
Canonicals
Check whether canonical tags point to the correct preferred URL.
Look for canonicals pointing to redirected, blocked, noindexed or irrelevant pages. Also check whether canonical tags match internal links and XML sitemaps.
This is high priority because conflicting canonical signals can cause the wrong URL to be treated as the preferred version.
Redirects
Check whether redirects are clean, direct and relevant.
Look for redirect chains, loops, temporary redirects, irrelevant destinations and old URLs redirected to the homepage.
This is high priority because poor redirects can weaken relevance and create confusing crawl paths.
Internal links
Check whether priority pages receive useful contextual links.
Look for orphan pages, vague anchor text, internal links pointing to redirected URLs and support content that does not link to relevant commercial pages.
This is high priority because internal links help clarify page importance, topic relationships and conversion paths.
Site architecture
Check whether the website has a clear structure.
Look at navigation, folder logic, breadcrumbs, page depth, resource hubs, service pages and parent-child relationships.
This is high priority because strong architecture helps search engines and users understand how pages relate to each other.
XML sitemaps and robots controls
Check whether sitemap and robots rules support the intended crawl and indexation strategy.
Look for redirected URLs, noindexed URLs, duplicate URLs or blocked URLs inside sitemaps. Also check whether robots.txt blocks important sections by mistake.
This matters because sitemaps and robots rules should support discovery, not send mixed signals.
Page templates
Check whether key templates support SEO consistently.
Review service, category, product, location, blog and resource templates for repeated issues with H1s, titles, canonicals, schema, breadcrumbs, internal links and mobile performance.
This is high priority because one template issue can affect many URLs.
Metadata
Check whether titles and meta descriptions are clear, useful and unique.
Look for missing titles, duplicate titles, vague descriptions and keyword-stuffed metadata.
This is medium priority because metadata supports relevance, clarity and click appeal.
Structured data
Check whether schema matches visible page content.
Look for invalid schema, unsupported FAQ schema, duplicate schema blocks and markup that does not match what users can see on the page.
This is medium priority because structured data should describe the page accurately, not make unsupported claims.
Core Web Vitals and performance
Check whether important templates are fast, stable and usable on mobile.
Focus first on service, category, product and other commercially important templates.
This is medium priority because performance affects user experience and technical quality.
JavaScript
Check whether important content and links can be discovered and rendered.
Look for product links, category content, menus, pagination or filters that only work after user interaction.
This is high priority when JavaScript affects discovery, crawl paths or important page content.
How to use this checklist
Start with evidence, not assumptions.
For a small website, you can review the most important pages manually and compare them with Google Search Console. For a larger website, use a crawler, Search Console, PageSpeed Insights and manual template checks.
Work through the checklist in this order:
- Crawl the site and export status codes, titles, canonicals, indexability, redirects and internal links.
- Compare crawler findings with Google Search Console indexing, sitemap and experience reports.
- Review priority templates manually, especially service, category, product and resource templates.
- Group findings by page type instead of treating every URL as a separate problem.
- Prioritise issues by crawl risk, indexation risk, commercial value, affected URL count and implementation effort.
- Turn findings into developer, SEO, content or CMS tasks.
- Validate fixes after deployment with a re-crawl, URL inspection, template check or Search Console review.
Google’s Search Central documentation covers crawling and indexing as core parts of how content is discovered and processed for Search: Google crawling and indexing documentation.
How this checklist differs from similar SEO work
A technical SEO audit checklist is not the same as a full SEO audit, a tool export, a content audit or a roadmap.
A technical SEO audit checklist finds technical barriers such as crawl issues, indexation problems, canonical conflicts, redirect errors, template issues and performance problems.
A full SEO audit is broader. It may include technical SEO, content, keyword targeting, competitors, backlinks, local SEO and conversion paths.
A site audit tool export is raw data. Tools can show errors, warnings and URL patterns, but they do not decide which issues matter most commercially.
A technical SEO roadmap comes after the audit. It turns findings into fix phases, owners, dependencies and implementation priorities.
A content audit focuses on content quality, intent fit, duplication, freshness and performance, rather than crawl paths and technical signals.
An ecommerce SEO audit may include technical SEO, but it gives more attention to categories, products, filters, faceted navigation, pagination and platform templates.
The checklist helps you find and organise the problems. The roadmap decides what should be fixed first, by whom and in what sequence.
When to run a technical SEO audit checklist
Run this checklist when there is a technical reason to question how the site is being discovered, processed or prioritised.
Good triggers include a website migration, redesign, ecommerce platform change, traffic drop, new site section, Search Console warning or weak commercial page performance.
For example, after a migration, old URLs may redirect poorly or important pages may be missing from internal links. After an ecommerce platform change, filters and category templates may create crawl and indexation problems. After a redesign, metadata, schema, breadcrumbs and internal links may have changed without being reviewed.
This keeps the checklist tied to real SEO problems rather than turning it into a generic technical best-practice exercise.
Crawlability checks
Crawlability is the first question: can search engines reach the pages that matter?
A page may be live on the site but still difficult to discover. For example, a service page might not be linked from the main navigation, service hub, footer or any related guide. It exists, but it is isolated from the site’s internal authority flow.
Collect examples of blocked URLs, server errors, orphan pages, broken internal links and important pages that are only accessible through scripts or forms.
A crawlability issue is fixed when the affected page returns the correct status code, is not blocked, can be reached through internal links and appears in the expected crawl path.
Indexation checks
Indexation checks confirm whether the right pages are eligible to appear in search.
This does not mean every URL should be indexed. A healthy site usually separates pages that should appear in search from URLs that should support users without becoming search targets.
For example, an ecommerce site may have useful category pages for “men’s running shoes” and “women’s trail running shoes”, but thousands of filter URLs created by colour, size, price, sort order and brand combinations. Without a clear indexation strategy, these variations can create duplication and crawl waste.
Use Google Search Console to compare submitted, indexed, excluded and discovered URLs. Then check whether excluded URLs are intentionally excluded or whether important pages are being left out. Google’s indexing FAQ explains that crawling and indexing depend on several factors, so no audit should promise instant indexation or guaranteed visibility: Google crawling and indexing FAQ.
A fix is confirmed when important URLs are indexable, low-value URLs are controlled intentionally and Search Console begins to reflect the intended pattern.
Canonical checks
Canonical tags help search engines understand the preferred version of duplicate or very similar pages.
This matters when similar content appears through parameters, filters, product variants, tracking URLs, HTTP/HTTPS versions or trailing slash differences.
A common problem is a category page that points its canonical tag to a filtered version. Another is a canonical tag pointing to a redirected or noindexed URL. Both create conflicting signals.
Google describes canonicalisation as the process of selecting a representative URL for duplicate pages: Google canonicalisation documentation.
A canonical fix is confirmed when the preferred URL is live, indexable, internally linked, present in the sitemap where appropriate and consistent across duplicate variants.
Redirect checks
Redirects are most important when URLs have changed.
During migrations and redesigns, old pages often disappear, move or get consolidated. The mistake is redirecting too many old URLs to the homepage. That may be convenient, but it weakens relevance because a user looking for a specific service lands on a generic page.
A better redirect preserves intent. An old technical SEO service URL should redirect to the closest current technical SEO page. An old product category should redirect to the closest equivalent category, not to the store homepage.
Use a redirect report to identify chains, loops, temporary redirects, irrelevant destinations and internal links that still point to redirected URLs. Google’s redirect documentation explains how redirects are used in Search: Google redirects documentation.
A redirect issue is fixed when old URLs resolve in one step to the closest relevant live page and internal links are updated to point directly to the final URL.
Internal linking checks
Internal links show which pages matter and how topics connect.
The key question is not “does the site have links?” but “do the right pages receive the right contextual links from the right places?”
A common issue is resource content that attracts visitors but never links to a relevant service page. Another is a commercial page that only receives navigation links and has no contextual support from related guides, diagnostics or resources.
For this topic, support content should help users understand the checklist while also routing qualified readers toward technical SEO South Africa.
An internal linking issue is fixed when priority pages have relevant contextual links, anchors describe the destination clearly and old redirected link targets have been updated.
Site architecture checks
Site architecture is the structure behind crawl paths, user journeys and topical clarity.
A useful audit should map how the website is organised, not just count page depth. Look at whether hubs, service pages, resources, categories and supporting guides form a clear hierarchy.
This page, for example, should not sit as an isolated resource. It should connect upward to the technical SEO hub, sideways to related diagnostics and back to the resources section where users can continue learning.
A site architecture issue is fixed when priority pages are easier to reach, parent-child relationships are clearer and support content links toward relevant commercial next steps.
Sitemap and robots checks
Sitemaps and robots controls should support the site’s crawl and indexation strategy.
A sitemap should contain useful canonical URLs. It should not include redirected URLs, noindexed URLs, duplicate variants, filtered URLs or old migration pages.
Robots rules should prevent crawl waste where appropriate, but they should not block important sections by mistake. Blocking a staging folder may be correct. Blocking a live category path or important product image folder may create avoidable discovery problems.
A sitemap or robots issue is fixed when sitemap URLs are live, indexable, canonical and useful, and robots rules match the intended crawl strategy.
Page template checks
Template issues often matter more than one-page issues because they scale.
If one article has a weak title tag, that is a page-level issue. If every service page template handles titles poorly, that is a template issue. If every product page template omits structured data or creates duplicate H1s, the impact can spread across hundreds or thousands of URLs.
Review service, category, product, location, blog and resource templates separately. The aim is to find patterns that repeat, not just isolated errors.
A template issue is fixed when the corrected pattern is applied consistently across the affected URL group and a sample of live pages confirms the change.
Metadata checks
Metadata helps clarify page purpose and click appeal.
The audit should identify whether titles and descriptions are missing, duplicated, unclear or misaligned with search intent. The goal is not to force keywords into every title. The goal is to make each page’s purpose clear.
A weak title such as “Services | Company Name” does not say enough. A stronger title such as “Technical SEO Services for South African Websites | Company Name” gives the user and search engine a clearer page topic.
A metadata issue is fixed when important pages have unique, useful titles and descriptions that match the page content and search intent.
Structured data checks
Structured data should describe what is visibly present on the page.
Do not add schema because it sounds useful. Add it when the page supports it. FAQPage schema, for example, should only be used when visible FAQs appear on the page. Product schema should match visible product information. LocalBusiness schema should match visible business details.
Google’s structured data documentation explains how structured data helps Google understand page content and how eligibility depends on following its guidelines: Google structured data documentation.
A structured data issue is fixed when markup validates, matches visible content and is applied only to suitable page types.
Core Web Vitals and performance checks
Performance should be reviewed by template and commercial importance.
A slow blog post may be worth improving, but a slow product, category or service template may affect many more users and search journeys. Focus first on templates that support revenue, enquiries or priority organic traffic.
Look at mobile loading, large images, render-blocking scripts, heavy third-party tools, poor hosting response times and layout shifts from banners or late-loading elements. Google’s Core Web Vitals documentation covers user experience metrics for loading, responsiveness and visual stability: Google Core Web Vitals documentation.
A performance fix is confirmed when the affected template improves in lab testing and, where enough field data exists, real-user performance trends in the right direction over time.
JavaScript checks
JavaScript becomes an SEO issue when important content or links are difficult to discover, render or follow.
This is common on ecommerce filters, product grids, faceted navigation, interactive menus, location selectors and content loaded after the page opens.
For example, if product links only appear after a user clicks a filter, a crawler may not discover all important product URLs through normal links. If category copy loads after interaction, the rendered page may not show the content consistently.
Google provides JavaScript SEO guidance for sites that rely on rendered content: Google JavaScript SEO basics.
A JavaScript issue is fixed when important content and links are visible in rendered HTML and can be discovered through crawlable paths.
Practical examples of technical SEO audit findings
These examples show how checklist findings become practical recommendations.
Ecommerce filters
Size, colour and sort filters create thousands of crawlable URLs. The likely fix is to control indexation, canonical handling and internal linking for filter URLs. Validate by re-crawling filter paths and confirming unwanted variants are controlled.
Website migration
Old service URLs redirect to the homepage. The likely fix is to redirect each old URL to the closest matching current page. Validate by testing old URLs and confirming one-step redirects to relevant destinations.
Canonical conflict
A category page canonical points to a filtered version. The likely fix is to correct canonical logic at template level. Validate by inspecting sample category URLs and checking consistency.
Internal linking gap
Technical guides do not link to technical SEO service pages. The likely fix is to add contextual links to the relevant commercial hub. Validate by re-crawling source pages and confirming the links appear.
Sitemap mismatch
The sitemap includes redirected and noindexed URLs. The likely fix is to submit only canonical, indexable URLs. Validate by exporting sitemap URLs and confirming they return 200, are indexable and are canonical.
Template issue
Every product page has the same title tag pattern. The likely fix is to improve title generation rules using product and category data. Validate by checking a sample of live product pages after deployment.
JavaScript issue
Product links load only after interaction. The likely fix is to ensure crawlable HTML links are available. Validate by comparing raw and rendered HTML, then re-crawling product grids.
How to prioritise technical SEO findings
A long issue list is not a strategy. Prioritisation is where the audit becomes useful.
Use four questions:
- Does this issue stop important pages from being crawled or indexed?
- Does it affect a high-value page type, such as services, categories or products?
- Does it affect many URLs because it is template-level?
- Can the fix be implemented safely and validated clearly?
Critical issues block important pages from being crawled, indexed or accessed. High-priority issues affect important templates, commercial pages or large URL groups. Medium-priority issues reduce clarity or efficiency but do not block core visibility. Low-priority issues are useful refinements but unlikely to change performance alone.
The strongest fixes usually affect important pages, commercial templates, crawl paths or indexation signals.
How to confirm fixes have worked
Technical SEO work should be validated after implementation. A ticket marked “done” is not the same as an issue being fixed.
For crawlability fixes, re-crawl the affected URLs and confirm they return the correct status code and are internally linked.
For indexation fixes, use URL inspection and Search Console reports to confirm the intended signals.
For canonical fixes, check live canonical tags, sitemap URLs and internal links for consistency.
For redirect fixes, test old URLs and confirm one-step redirects to relevant final destinations.
For internal linking fixes, re-crawl source pages and confirm new links and anchors are present.
For structured data fixes, test the live URL and confirm schema matches visible content.
For JavaScript fixes, compare raw and rendered HTML, then confirm important links and content are discoverable.
Validation prevents the same issue from reappearing in the next audit.
What a useful audit output should include
A useful technical SEO audit should produce decisions, not just data.
A weak audit output says: “150 pages have duplicate titles.”
A useful audit output says: “The product page template generates duplicate titles because it only uses the product type, not the product name, brand or category. This affects 150 product URLs. Update the title logic at template level and validate using a sample of live product pages after deployment.”
A strong audit should include the issue, affected URL examples, evidence, reason it matters, recommended fix, priority, owner, developer notes where needed, validation method and next-step roadmap.
This helps the team move from diagnosis to implementation.
What to do after completing the checklist
After completing the checklist, group findings into a practical action plan.
Start with anything that blocks crawlability, indexation or access to important pages. Then move to template-level issues that affect large sets of commercial URLs. After that, handle metadata, structured data, sitemap cleanup, performance improvements and lower-priority refinements.
For a structured follow-up process, see our SEO audit roadmap guide.
If the site is an online store, technical issues often affect categories, products, filters, pagination and platform templates. In that case, review ecommerce technical SEO support as a next step.
Where to go next
Choose the next page based on the problem you are trying to solve.
If you need help with technical crawl, indexation, templates or site architecture, visit technical SEO South Africa.
If you have an ecommerce site with category, product, filter or platform issues, review ecommerce technical SEO.
If you have audit findings but no clear implementation plan, use the SEO audit roadmap.
If you want more practical SEO guides and checklists, browse SEO resources South Africa.
Book an SEO diagnostic review
A technical SEO audit checklist helps you identify crawl, indexation, structure, template, performance and internal linking issues. The bigger value comes from deciding which issues matter most and turning them into an implementation plan.
If your website has technical SEO issues, migration concerns, ecommerce crawl problems, indexation gaps or unclear fix priorities, SEO Strategist can help you review the problem and build a practical action plan.
Book an SEO diagnostic review to identify what is limiting visibility, what should be fixed first and how technical SEO should support your wider search strategy.