A technical SEO checklist makes sure search engines can find, render and understand your pages. Start with crawl access and indexing, then fix duplicate URLs, redirects and HTTPS, add accurate structured data, and finally tune speed and mobile usability. Technical fixes remove obstacles; they do not promise rankings. Good content and a clear offer still decide whether a page deserves to rank.
Key takeaways
- Fix what blocks discovery first: robots rules, noindex tags, broken sitemaps and server errors.
- Every important page should have one clean, canonical URL that returns a normal success response.
- Structured data should describe what is visibly on the page, nothing more.
- Internal links are how crawlers and people move through your site; orphan pages are easy to miss.
- Speed, mobile layout and JavaScript rendering matter, but they rarely rescue weak content.
How search engines see your website
Search engines work in three broad steps. They crawl (a bot fetches your URL), they render and index (they process the page and store a version of it), and they serve (they choose which stored pages to show for a query). Technical SEO mostly deals with the first two steps. If a page cannot be crawled, or is told not to be indexed, no amount of copywriting will help it appear.
A useful mindset: your website should be easy for a bot with limited time to understand. Clean URLs, predictable links, fast responses and unambiguous signals all help. For the official explanation of how this works, Google's documentation at Google Search Central is the best reference.
Priority 1: crawlability and indexing
These issues can make a whole section of a site invisible, so check them first.
Robots rules
The robots.txt file at the root of your domain tells crawlers which paths they may fetch. A common and costly mistake is leaving a "disallow everything" rule from a staging site in place after launch. Open yourdomain.com/robots.txt and confirm it does not block pages you want found. Remember that robots.txt controls crawling, not indexing, so it is not the right tool to hide sensitive content.
Noindex tags and status codes
Check that important pages do not carry a noindex meta tag, and that they return a normal 200 response. Pages that return errors, or that are accidentally set to noindex by a template or plugin, quietly drop out of search results. Review a sample of your main pages, not just the home page.
XML sitemap
A sitemap is a list of the URLs you want indexed. Keep it limited to canonical, indexable pages, update it automatically when content changes, and submit it in the search console tools the search engines provide. A sitemap full of redirected, blocked or duplicate URLs sends mixed signals.
Priority 2: one page, one URL
Duplicate content is rarely a penalty, but it does dilute signals and waste crawl effort. The same page may be reachable through several addresses: with and without www, with trailing slashes, with tracking parameters, or through filters on a catalogue.
Canonical tags
A canonical tag tells search engines which version of a page you prefer. Use self-referencing canonicals on normal pages and point parameter or variant URLs to the main version. Treat canonicals as a strong hint rather than a command.
Redirects
Use a permanent redirect (301) when a page moves for good, and redirect to the most relevant new page rather than the home page. Avoid redirect chains, where A goes to B and B goes to C; each hop slows things down and adds risk. After any redesign or migration, keep a list of old URLs and test that each one lands in the right place.
HTTPS
Your whole site should load over HTTPS, with HTTP versions redirecting to the secure address and no mixed-content warnings. Beyond SEO, it protects visitors and is an expectation in 2026 for anything with a form or login.
Priority 3: structured data and internal links
Structured data
Structured data (usually schema.org markup in JSON-LD format) gives search engines a machine-readable description of a page: an organisation, an article, a product, an FAQ, a breadcrumb trail. Follow three rules. Mark up only what is visible to users. Keep details such as name, address and phone number identical to what you publish elsewhere. Validate it with the testing tools that search engines provide. Structured data can make a page eligible for richer displays, but it never obliges a search engine to show them.
Internal linking
Internal links tell crawlers which pages matter and how topics relate. Practical habits:
- Link from high-traffic pages to the pages you want to grow, using descriptive anchor text rather than "click here".
- Make sure every important page is reachable within a few clicks from the home page.
- Find orphan pages (no internal links pointing to them) and either link them or remove them.
- Add breadcrumbs on deeper pages so the structure is clear.
Priority 4: mobile, speed and JavaScript
Mobile-friendliness
Search engines predominantly evaluate the mobile version of a page, so it should contain the same main content, headings and structured data as the desktop version. Check that text is readable without zooming, buttons are easy to tap and nothing important is hidden behind elements that do not load.
Page speed
Speed affects both visitors and crawlers. Compress and correctly size images, load only the scripts you need, enable caching and consider a CDN. Core Web Vitals, the three metrics Google uses to describe real-user loading, responsiveness and stability, are a good starting point for measuring speed.
JavaScript rendering
Modern search engines can render JavaScript, but rendering is an extra step that can be delayed or fail. If key content, links or metadata only appear after client-side scripts run, test how the page looks to a crawler. Frameworks that support server-side rendering or static generation make this easier, which is one reason we favour them in website development projects. Make sure links are real anchor links, not click handlers that only work in a browser.
A prioritised technical SEO checklist
Work through this in order, and record what you change and when.
- Confirm robots.txt and noindex settings do not block important pages.
- Check that key pages return a 200 status and no server errors appear in your search console reports.
- Choose one preferred domain version and force HTTPS everywhere.
- Publish and submit a clean XML sitemap.
- Add self-referencing canonical tags and resolve duplicate URLs.
- Fix redirect chains, broken internal links and soft 404s.
- Add structured data that matches visible content, then validate it.
- Improve internal linking and remove orphan pages.
- Test mobile layout and tap targets on a real phone.
- Measure speed, then fix the largest image, script and layout problems.
- Check that key content and links appear without relying on user interaction.
Common mistakes
- Treating an audit tool's score as the goal instead of fixing real blockers.
- Blocking CSS or JavaScript files that pages need in order to render.
- Marking up reviews or ratings that visitors cannot see on the page.
- Redesigning a site without a redirect map.
- Running everything through a plugin and never checking the output.
A worked example
Imagine a distributor, the kind of business covered in our manufacturing and distribution work, with a catalogue of a few thousand products. After a redesign, its category filters create thousands of parameter URLs, its sitemap still lists old addresses and several product pages return soft errors. A sensible order of work would be: fix the status codes, set canonical tags for filtered pages, rebuild the sitemap with only canonical product and category URLs, then add product structured data and improve category-to-product internal links. Speed work comes after the site is clean, because there is little point speeding up pages that search engines are not indexing correctly.
FAQ
How often should I run a technical SEO audit?
A light review each month, using your search console reports, catches most surprises. A fuller audit makes sense once or twice a year and always before and after a redesign, platform change or migration.
Does technical SEO promise higher rankings?
No. It removes barriers so your content can be found and understood, but rankings also depend on relevance, content quality, competition and many other factors. Be wary of anyone who promises a position.
Is a sitemap required?
Not strictly, since crawlers can find pages through links, but a sitemap is helpful for larger or newer sites and for pages with few internal links. Keep it accurate rather than exhaustive.
Can I do technical SEO myself?
Many basics, such as checking robots rules, titles, redirects and sitemaps, are manageable for a non-specialist with the free search console tools. Template-level changes, rendering issues and migrations usually need a developer involved.
Next steps
Start with the first three items on the checklist; they take little time and catch the most damaging problems. If you would like a second pair of eyes, our SEO services include technical audits, and you can contact us to talk through your site with no obligation. If you are planning a rebuild, bring SEO into the brief early, so the build is planned around crawlable pages, clean URLs and a redirect map from the start.
