Technical SEO helps search engines access, render and understand the important pages on your website. It also supports a reliable experience for visitors. A technically healthy website does not automatically rank well, but technical problems can prevent useful content from being discovered, indexed or used properly.
This checklist is designed for website owners, SEO beginners, marketers and developers. Work through it in order, record evidence for every issue and prioritise fixes by their impact on important pages. You do not need to fix every warning from an SEO tool. Focus first on problems that block access, create incorrect indexing signals, break key journeys or affect many valuable URLs.
How to Use This Technical SEO Checklist
- Start with a list of important pages: homepage, key services, categories, products and high-value articles.
- Check the live website and crawl it with a suitable SEO crawler.
- Compare crawler findings with Google Search Console and URL Inspection.
- Record the affected URLs, evidence, likely cause, priority and recommended fix.
- Make changes carefully, especially to robots.txt, canonicals, redirects and noindex rules.
- Test the affected pages after implementation and monitor the results.
Use a simple issue log with these columns: issue, example URL, number of affected URLs, evidence, business impact, priority, owner, fix and validation date. A tool warning is a clue to investigate, not proof that a search problem exists.
1. Website Accessibility and Basic Health
First confirm that visitors and search engine crawlers can reach the website. Check the following:
- Important pages load successfully without server or network errors.
- The preferred hostname and protocol are consistent, such as one HTTPS version of the domain.
- HTTP URLs and unwanted hostname variants redirect to the preferred version where appropriate.
- Important page templates work on desktop and mobile browsers.
- Critical CSS, JavaScript, images and other required resources are accessible to crawlers.
- The website does not expose staging, development or private content unintentionally.
- CMS, themes, plugins and server software are maintained with a suitable security process.
- Forms, navigation, checkout and other important user journeys work as expected.
How to check: open representative pages in a browser, inspect response codes with a crawler or browser developer tools, and review hosting or server monitoring for availability problems. Do not assume that a single successful browser visit proves that every URL works.
2. Crawling and Robots.txt
Crawling is the process by which search engine bots request URLs and discover links. Robots.txt provides crawling instructions for compliant crawlers. It is not a security mechanism and does not reliably remove a URL from the search index.
Robots.txt checklist
- Confirm that the robots.txt file is available at the root of the relevant host.
- Check that important content sections are not accidentally disallowed.
- Review rules for staging paths, internal search results, filters and other URL patterns before blocking them.
- Check that important CSS and JavaScript resources needed to render pages are not blocked.
- Make sure sitemap declarations, if included, point to the correct sitemap URL.
- Test important rules with an appropriate robots.txt testing method and verify actual URLs.
Important distinction: robots.txt controls crawling. If a page must be excluded from Google’s index, use an appropriate noindex directive or access restriction, and make sure Google can crawl the page to see that directive. Blocking a URL in robots.txt can prevent Google from seeing its noindex tag.
Reference: Google’s robots.txt documentation.
3. Indexability and Google Search Console
A page being live does not mean it is indexed. Check whether important URLs are eligible for indexing and whether Google has selected the expected canonical URL.
Indexing checklist
- Important pages return the expected successful HTTP status code, normally 200.
- Pages intended for search do not contain an unintended noindex meta tag or X-Robots-Tag header.
- Pages that should remain private or excluded have the correct access or index-control setup.
- Important pages have crawlable internal links.
- Google Search Console’s Page Indexing report is reviewed for relevant patterns.
- URL Inspection is used to investigate representative important URLs.
- Live URL tests are used when checking the currently accessible page, while remembering that a live test does not guarantee indexing.
- Unexpected indexed URLs, duplicate versions and excluded important pages are investigated.
Do not try to force every URL into Google’s index. Thin, duplicate, private, filtered or otherwise low-value URLs may not need to be indexed. Decide which pages should be discoverable based on their purpose and value.
Reference: Google Search Console Page Indexing report.
4. XML Sitemap Checklist
An XML sitemap helps search engines discover URLs that you consider important. It is a discovery hint, not a guarantee that every URL will be crawled or indexed.
- Submit the correct sitemap or sitemap index in Google Search Console.
- Include canonical, indexable URLs that you want search engines to discover.
- Exclude URLs that redirect, return errors, are blocked or carry a noindex directive.
- Use the correct absolute URL format and the preferred HTTPS hostname.
- Make sure sitemap files follow the supported XML format and size limits.
- Use lastmod only when it reflects a meaningful page update, not as a way to request crawling.
- Keep image or video sitemap information accurate when it is relevant to the site.
- Review sitemap processing status and investigate parsing errors or unexpected URL counts.
- Keep sitemap entries aligned with canonical URLs and the site’s current URL structure.
For large websites, organise sitemap files by content type or section when that makes monitoring easier. Avoid submitting several duplicate sitemap variants without a clear reason.
Reference: Google’s sitemap guidelines.
5. Canonical Tags and Duplicate URL Management
Websites can expose similar content through multiple URLs, such as tracking parameters, filter combinations, print pages or alternate hostnames. Canonical tags help indicate which URL should be treated as the preferred version, but Google treats canonicalisation as a signal rather than an absolute command.
- Important indexable pages have a canonical URL that points to the intended preferred version.
- Canonical URLs use the correct protocol, hostname and path.
- Canonical tags do not point to unrelated pages or redirect destinations.
- Internal links and sitemap entries generally support the same preferred URL.
- Pagination, filters, product variants and tracking parameters have a deliberate URL strategy.
- Multiple conflicting canonical tags are avoided.
- Canonical targets are accessible and are not unintentionally noindexed.
- HTTP/HTTPS and www/non-www variants resolve consistently.
Do not canonicalise genuinely different pages simply because they share a template or topic. Choose canonical targets based on content equivalence and the purpose of each URL.
Reference: Google’s URL canonicalisation guidance.
6. HTTP Status Codes, Redirects and Error Pages
HTTP status codes tell browsers and crawlers what happened when a URL was requested. Incorrect status codes and redirect chains can create poor user journeys and confusing signals.
| Status | Meaning | What to check |
|---|---|---|
| 200 | Successful response | The page returns the intended content, not an empty or error-like page. |
| 301 | Permanent redirect | Use for a URL move intended to be permanent. |
| 302 | Temporary redirect | Use when the move is genuinely temporary. |
| 404 | Not found | Removed pages should return an honest not-found response when no suitable replacement exists. |
| 410 | Gone | Can indicate that a resource has been intentionally and permanently removed. |
| 5xx | Server error | Investigate server, application, hosting or network failures. |
- Redirect old URLs to the closest relevant replacement when one exists.
- Remove unnecessary redirect chains and loops.
- Update internal links to point directly to final destination URLs.
- Do not redirect every deleted URL to the homepage.
- Ensure custom 404 pages return a real 404 status rather than a soft 404.
- Review important external backlinks before deciding how to handle removed URLs.
- Test redirects after migrations, redesigns and permalink changes.
Reference: Google’s redirect guidance.
7. Website Architecture and Internal Linking
A clear site structure helps people navigate and helps crawlers discover relationships between pages. There is no universal rule that every important page must be exactly three clicks from the homepage. Focus on logical organisation and useful links.
- Main navigation links to the most important sections.
- Important pages are reachable through crawlable HTML links.
- Related articles, products and services link to one another where useful.
- Anchor text describes the destination naturally.
- Breadcrumbs help users understand where they are, when appropriate.
- Important pages are not orphaned without internal links.
- Navigation works with keyboard and touch input.
- Internal links do not point unnecessarily through redirects or to broken URLs.
- Large archives and pagination provide a discoverable path to relevant content.
Do not add internal links only to increase a count. Each link should help a visitor discover a relevant next page.
8. Mobile Experience and Responsive Design
Google uses the mobile version of content for indexing. Check that the mobile version contains the important information and signals available on desktop.
- Pages use a responsive layout that adapts to common screen sizes.
- Main content and important metadata are available on mobile.
- Text is readable without horizontal scrolling or forced zoom.
- Menus, buttons, forms and navigation are usable on touch screens.
- Important images and videos load correctly.
- Content is not hidden behind interactions that prevent access.
- Pop-ups and overlays do not make important content difficult to use.
- Mobile and desktop versions provide consistent primary content and structured data.
Test key templates, not just the homepage. A product page, article, contact form and category page may behave differently.
Reference: Google’s mobile-first indexing guidance.
9. Core Web Vitals and Page Performance
Page performance affects how visitors experience a website. Core Web Vitals are a set of user-experience metrics. The current key metrics are Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS).
| Metric | Good threshold | What it measures |
|---|---|---|
| LCP | 2.5 seconds or less | Loading performance of the largest visible content element. |
| INP | 200 milliseconds or less | Responsiveness to user interactions. |
| CLS | 0.1 or less | Visual stability and unexpected layout movement. |
These thresholds are assessed at the 75th percentile of page loads. Field data and lab tests provide different kinds of evidence; use both where available.
Performance checklist
- Review field data in PageSpeed Insights or the Chrome User Experience Report where available.
- Test important templates, not only one URL.
- Resize and compress large images and serve suitable formats.
- Set image dimensions or aspect ratios to reduce layout shifts.
- Prioritise loading of the main above-the-fold image when appropriate.
- Reduce unnecessary JavaScript and long main-thread tasks.
- Review unused CSS, render-blocking resources and font loading.
- Use caching and content delivery infrastructure where it makes sense.
- Measure the result after each meaningful performance change.
Do not assume that a perfect lab score guarantees good field performance. Real users have different devices, networks and interaction patterns.
Reference: Web Vitals documentation.
10. HTTPS and Website Security
HTTPS protects data exchanged between a browser and the website. Security is essential for user trust and safe operation, even though installing a certificate does not guarantee higher rankings.
- All public pages use valid HTTPS certificates.
- HTTP versions redirect correctly to HTTPS.
- Internal links, canonical tags and sitemap URLs use HTTPS consistently.
- Mixed-content warnings are investigated.
- CMS, plugins, themes and server software receive security updates.
- Administrator accounts use strong authentication and appropriate access controls.
- Backups and recovery procedures are tested.
- Forms and payment flows use secure handling for sensitive information.
Do not publish private information in public URLs or expose administrative and staging systems to search engines.
11. JavaScript SEO and Rendering
JavaScript can create page content and links after the initial HTML response. Google can render JavaScript, but rendering adds complexity and may be delayed. Other crawlers and tools may not process JavaScript in the same way.
- Check that the initial HTML contains essential content where practical.
- Make sure important content appears in the rendered HTML.
- Use crawlable links with meaningful href destinations.
- Ensure required JavaScript and CSS resources are accessible to Googlebot.
- Avoid requiring user clicks or login actions to reveal essential page content.
- Check that client-side navigation produces meaningful URLs.
- Use appropriate server-side rendering or pre-rendering where it improves reliability and performance.
- Verify canonical and robots directives are consistent between the original and rendered HTML.
- Use URL Inspection to review Google’s rendered page when investigating a problem.
Reference: Google’s JavaScript SEO basics.
12. Structured Data and Schema Markup
Structured data helps describe page information in a format search engines can understand. Correct markup may make a page eligible for certain search appearances, but valid structured data does not guarantee that a rich result will be shown.
- Choose schema types that accurately describe the visible page content.
- Make sure structured data reflects information users can see on the page.
- Use appropriate properties and required fields for the selected type.
- Avoid fabricated reviews, ratings, prices, author credentials or business details.
- Check for duplicate or conflicting schema generated by themes and plugins.
- Validate markup with the Schema Markup Validator and Google’s Rich Results Test where relevant.
- Monitor relevant enhancement reports in Search Console.
- Update structured data when the underlying page information changes.
Do not add every available schema type to every page. Use markup only where it accurately describes the content and follows the relevant search feature guidelines.
References: Google structured data introduction and Schema Markup Validator.
13. International and Multilingual SEO
If a website serves multiple languages or countries, technical signals should help search engines understand the intended audience and the relationship between page variants.
- Choose a URL structure suitable for the business and its international needs.
- Publish genuinely useful localised content rather than mechanically duplicating pages.
- Use valid hreflang annotations for relevant language or regional variants.
- Make sure hreflang references are reciprocal and point to valid canonical URLs.
- Use an appropriate self-referencing canonical on each language version when applicable.
- Avoid automatically forcing users to another language based only on location or IP address.
- Keep navigation and language switching clear for visitors.
Only apply this section if the website genuinely serves multiple languages or regions.
Reference: Google’s localized versions guidance.
14. Large Websites and Crawl Budget
Crawl budget is not a priority for every website. Most small and medium websites should first focus on discoverable internal links, correct indexability, useful content and server reliability. Crawl-budget management becomes more relevant for very large sites or websites with frequently changing, complex URL spaces.
- Identify URL patterns that generate large numbers of low-value variations.
- Review faceted navigation, internal search and tracking parameters.
- Keep important pages discoverable through internal links and accurate sitemaps.
- Use robots.txt rules carefully for URL spaces that do not need crawling.
- Review server logs when you need evidence of actual crawler requests.
- Check whether important URLs are being crawled and whether unnecessary patterns dominate requests.
- Coordinate URL handling with developers, especially for ecommerce filters and large catalogues.
Do not block URLs simply because a crawler tool labels them as low priority. Understand the purpose of the URL and the effect of the rule before changing crawl access.
Reference: Google’s large-site crawl budget guide.
15. Website Migration and Redesign Checklist
Website migrations can affect many URLs and technical signals at once. Prepare a migration plan before changing domains, platforms, URL structures or major templates.
- Export and retain a list of current URLs and important page data.
- Map old URLs to the closest relevant new URLs.
- Prepare permanent redirects for URLs that have moved permanently.
- Update internal links, canonical tags, hreflang and sitemap entries.
- Check robots.txt and noindex settings before launch.
- Test redirects, status codes, templates, forms and important journeys in staging.
- Do not block the live site from crawling after launch by mistake.
- Submit or update the relevant sitemap in Search Console.
- Monitor indexing, traffic, errors and important landing pages after release.
- Keep redirects in place for an appropriate period and update important external references where possible.
Never launch a redesign without a URL mapping and rollback or recovery plan.
16. Technical SEO Tools
Use tools to collect evidence, then verify important findings. Different tools crawl and interpret pages differently.
| Tool | Primary use |
|---|---|
| Google Search Console | Indexing information, URL Inspection, sitemaps and search performance. |
| PageSpeed Insights | Performance diagnostics and field data where available. |
| Screaming Frog SEO Spider | Website crawling, status codes, titles, links, canonicals and directives. |
| Chrome DevTools | Inspect HTML, network requests, rendering and performance behaviour. |
| Rich Results Test | Check eligibility for supported Google rich result features. |
| Schema Markup Validator | Validate schema vocabulary and markup structure. |
| Server logs | Investigate actual requests from crawlers and other clients. |
You can begin with free tools. Paid crawling and monitoring platforms may save time on larger projects, but their scores and warnings should not replace technical verification.
17. Technical SEO Audit Priority Framework
Not every issue deserves the same urgency. Use the following framework to decide what to fix first:
| Priority | Example | Suggested response |
|---|---|---|
| Critical | Important pages blocked, site-wide noindex, widespread server failures or migration redirects missing. | Investigate immediately and validate the fix. |
| High | Key pages return errors, wrong canonicals, important content inaccessible or major mobile template failures. | Schedule promptly and check all affected templates or URLs. |
| Medium | Broken internal links, redirect chains, duplicate metadata or sitemap inconsistencies. | Group by pattern and resolve systematically. |
| Low | Minor warnings with no clear impact on users or important URLs. | Document and review during routine maintenance. |
Priorities depend on the website and the evidence. A single issue on a critical checkout page may matter more than hundreds of warnings on low-value URLs.
18. Weekly and Monthly Technical SEO Maintenance
Weekly checks
- Review important website pages and key user journeys.
- Check Search Console for unusual indexing or crawling changes.
- Investigate new critical server errors or broken URLs.
- Review deployments or plugin updates that could affect templates.
Monthly checks
- Run a crawl of important website sections.
- Review redirects, canonicals, robots directives and sitemap health.
- Test representative mobile templates and page performance.
- Review structured data changes and relevant Search Console reports.
- Check backups, software updates and security maintenance.
- Update the issue log and confirm that previous fixes remain valid.
Before a major release
- Test staging and production crawl access.
- Review URL mappings, redirects and canonical signals.
- Check page templates, forms, navigation and structured data.
- Confirm analytics and Search Console tracking remain functional.
- Assign owners for launch monitoring and issue response.
Frequently Asked Questions About Technical SEO
What is the most important technical SEO task?
Start by ensuring that important pages are accessible, return the correct status, are not unintentionally blocked or noindexed, and can be discovered through useful internal links. The highest priority depends on the website’s actual problems.
Does robots.txt remove a page from Google?
No. Robots.txt controls crawling, not reliable index removal. If a page needs to be excluded from the index, use an appropriate noindex directive or access restriction and make sure the crawler can access the directive.
Does submitting an XML sitemap guarantee indexing?
No. A sitemap helps search engines discover URLs, but Google decides which pages to crawl and index. Keep sitemap entries accurate and monitor the relevant Search Console reports.
Are Core Web Vitals a direct ranking factor?
Core Web Vitals are part of Google’s page experience considerations. Good scores do not guarantee rankings, and relevance and content quality remain important. Use the metrics to improve real user experience, not as a substitute for useful content.
Does every website need crawl-budget optimisation?
No. Most small websites should focus on correct internal links, indexability and useful content. Crawl-budget work is more relevant to very large websites or sites with complex URL generation and frequent changes.
Is structured data required to rank?
No. Structured data can help search engines understand supported information and may make eligible pages qualify for certain search features. It does not guarantee a rich result or a ranking improvement.
How often should I run a technical SEO audit?
It depends on site size and release frequency. A monthly crawl is a useful routine for many active websites, while large or frequently changing sites may need more regular automated checks. Always test after major releases and migrations.
Can a technical SEO audit guarantee better rankings?
No. An audit identifies potential issues and opportunities. Results depend on the problem, the quality of the fix, competition, content and many other factors. A good audit explains evidence, priority and validation instead of promising a ranking outcome.
Official Technical SEO Resources
- Google: Maintaining Your Website’s SEO
- Google: Introduction to Robots.txt
- Google: Sitemaps Overview
- Google: Consolidate Duplicate URLs
- Google: JavaScript SEO Basics
- Google: Introduction to Structured Data
- Web.dev: Web Vitals
Final Technical SEO Checklist
Technical SEO is an ongoing process of checking, prioritising, fixing and validating. Start with the pages that matter most to users and the business. Use crawler reports, Search Console, browser tools and server evidence together. Record every important change and confirm that the fix works on the live website.
A clean technical foundation helps your content become accessible and understandable, but it is only one part of a successful SEO strategy. Continue with the On-Page SEO Checklist to improve the content and page elements visitors interact with.