What technical SEO covers, how crawling and indexing work, and a practical order for fixing technical problems on a business website.
This guide explains the main areas of technical SEO and a sensible order for working through them.
01What technical SEO covers
Technical SEO looks at how a website is built and served rather than what each page says. The main areas are:
- Crawlability: whether search engine bots can reach your pages
- Indexing: whether the pages you want in search results are actually stored in the index
- Site architecture: how pages are organised and linked together
- Canonicals and redirects: which URL is the main version of each page
- Structured data: machine-readable information about your business and content
- Page experience: speed, stability and mobile usability
- Rendering: whether content loaded by JavaScript is visible to search engines
02Crawlability
Search engines discover pages by following links and reading XML sitemaps. A page can be hard to crawl when it is blocked in robots.txt, only reachable through forms or scripts, buried many clicks deep, or linked only from pages that are themselves blocked.
Start by checking robots.txt, the XML sitemap and the crawl data in Google Search Console. A crawler such as Screaming Frog shows how a bot moves through the site and where it gets stuck.
03Indexing
Being crawled does not guarantee being indexed. Google may decide a page is a duplicate, too thin, or not the preferred version. The Page indexing report in Search Console lists the reasons pages are excluded.
Common causes of indexing problems:
- A noindex tag left on pages after a site launch
- Duplicate pages created by URL parameters, filters or tracking codes
- Canonical tags pointing to the wrong URL
- Soft 404s: pages that return a 200 status but show little or no content
- Server errors during crawling
04Site architecture and internal linking
Good architecture keeps important pages close to the homepage and groups related pages together. Internal links tell search engines which pages matter and how topics relate.
A useful rule of thumb: every page that should rank needs at least one clear, descriptive internal link from a relevant page, and no important page should depend only on the XML sitemap to be found.
05Canonicals and redirects
When the same content is reachable at more than one URL, a canonical tag tells search engines which version to treat as the main one. Redirects move users and search engines from an old URL to a new one.
Keep redirects to a single hop, use 301 redirects for permanent moves, and update internal links so they point straight at the final URL instead of relying on redirects.
06Structured data
Structured data (schema markup) describes your organisation, services, articles, products or FAQs in a format search engines can read reliably. It can make a page eligible for rich results, but it does not guarantee them, and the markup must match what is visible on the page.
07Page experience and Core Web Vitals
Core Web Vitals measure loading (Largest Contentful Paint), responsiveness (Interaction to Next Paint) and visual stability (Cumulative Layout Shift). They are one of many signals, so a fast site with weak content will not outrank a useful slower one, but poor performance does hurt users and conversions.
Large images, heavy scripts, unoptimised fonts and slow hosting are the usual causes.
08JavaScript and rendering
Sites built with JavaScript frameworks can hide content from search engines if the important text and links only appear after scripts run. Server-side rendering or static generation, as used on this site, makes the main content available in the initial HTML.
09A practical order of work
- Confirm the pages you want indexed are not blocked or set to noindex
- Fix server errors, broken internal links and redirect chains
- Resolve duplicate URLs with canonicals, redirects or parameter handling
- Strengthen internal linking to priority pages
- Improve page speed on the templates that carry the most traffic
- Add accurate structured data
- Monitor Search Console and re-crawl after each change
Frequently asked questions
How often should a technical SEO check be done?
A light check after every significant site change, and a fuller review a few times a year for most business websites. Large or frequently changing sites need ongoing monitoring.
Can technical SEO alone improve rankings?
It removes obstacles. Rankings still depend on content quality, relevance and authority, so technical work is the foundation rather than the whole strategy.
Do I need a developer to fix technical SEO issues?
Some fixes, such as titles or internal links, can be done in a CMS. Others, such as rendering, redirects at server level or template changes, usually need developer access.
Key terms in this guide
Need this done rather than read about it? See Technical SEO Services.
