Technical SEO
Technical SEO is the site and server work that lets search engines crawl, render and index the right URLs: robots.txt, XML sitemaps, clean 200 and 301 status codes, canonicals, HTTPS, mobile-friendly HTML, fast server response and structured data. It does not replace content, but a page Google cannot fetch or index cannot rank.
For site owners, developers and marketers who need search engines to reach and store their pages correctly.
knowledge
- Read time
- 3 min
- Sections
- 5
- Updated
- 14 Nov 2026
- Written by
- WebJi® team
Last editorial update: 14 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
What is technical SEO?
Technical SEO is the site- and server-level work that lets search engines crawl, render and index the right URLs quickly: robots rules, sitemaps, status codes, canonicals, HTTPS, mobile rendering, speed and structured data. It does not replace good content, but if a crawler cannot fetch a page, the content never gets a chance.
| Stage | Question | Typical failure |
|---|---|---|
| Crawl | Can Googlebot request the URL and get a 200? | robots.txt block, 5xx errors, redirect loops |
| Render | Is the main content in the HTML Google processes? | Content only appears after client-side JavaScript |
| Index | Is one preferred URL eligible to be stored? | Duplicates, stray noindex, wrong canonical |
It sits alongside on-page SEO and links from other sites; the split is explained in types of SEO.
How do robots.txt and XML sitemaps control crawling?
Use robots.txt to keep crawlers out of utility paths and to point to your sitemap; use the XML sitemap to list the canonical, indexable URLs you want found. robots.txt blocks crawling, not indexing, so it is the wrong tool for hiding a page — use noindex for that.
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://example.in/sitemap_index.xml- List only canonical URLs that return 200; leave out redirects, noindex pages and parameter copies.
- Never block CSS or JavaScript that pages need to render.
- On large sites, stop crawlers wasting fetches on filter and search URLs.
Details: what robots.txt does and what an XML sitemap is.
Which status codes and redirects matter for SEO?
Indexable pages must return 200, permanently moved pages 301 (or 308) straight to the final URL, removed pages 404 or 410, and temporary outages 503. Long redirect chains waste crawl time and slow visitors.
# Follow redirects and print each hop's status and target
curl -sIL http://example.in/old-page/ | grep -i -E "^HTTP|^location"One hop from http:// or non-www to the final HTTPS URL is ideal. Pages that show "not found" text but return 200 are soft 404s; Search Console reports them, and they should return a real 404. Server errors are covered in 503 Service Unavailable fixes.
How do you handle duplicate content, canonicals and noindex?
Choose one URL per piece of content, 301-redirect copies that should not exist, add a rel="canonical" tag on copies that must stay reachable, and use noindex only for pages that must stay open but out of search. Canonical is a strong hint, not a command.
- Fix host duplicates first: one of www or non-www, HTTPS only, consistent trailing slashes.
- Canonicalise parameter and sort-order variants to the main URL.
- Make every canonical point to a live 200 page, not a redirect or noindex URL.
- Never canonicalise all pages to the homepage.
More in what a canonical URL is.
How do mobile-first indexing and JavaScript affect indexing?
Google indexes the mobile version of pages, so the mobile HTML must contain the same main content, links and structured data as desktop; content injected only by client-side JavaScript may be indexed later or not at all. Server-rendered HTML is the safest default.
- Use responsive design rather than separate mobile URLs.
- Make links real
<a href>elements; Google does not follow click handlers. - Check rendered HTML with URL Inspection → View crawled page in Search Console.
- For multilingual sites, add
hreflangpairs that point to each other.
How do Core Web Vitals and server response time affect SEO?
Core Web Vitals measure loading (LCP), responsiveness (INP) and visual stability (CLS); Google uses them as part of page experience, and slow server response (TTFB) delays LCP. They are a tie-breaker between relevant pages, not a substitute for relevance.
| Metric | Measures | Good |
|---|---|---|
| LCP | Time until the largest content element renders | 2.5 s or less |
| INP | Delay from user interaction to next paint | 200 ms or less |
| CLS | Unexpected layout movement | 0.1 or less |
| TTFB (diagnostic) | Time to first byte of HTML | 0.8 s or less |
INP replaced First Input Delay as a Core Web Vital in March 2024. Thresholds are from web.dev. Use field data from Search Console's Core Web Vitals report, and the website speed test for lab checks.
How does hosting help or hurt technical SEO?
Hosting helps when the server answers quickly, stays up, compresses responses and sits close to your visitors; it hurts when TTFB is slow, errors waste crawl requests or resource limits cause timeouts at busy times. A CDN speeds up static files but not uncached HTML built per request.
- Use page caching for anonymous visitors and object caching for database-heavy sites.
- Serve over HTTP/2 or HTTP/3 with Brotli or gzip compression.
- Watch Search Console's Crawl stats for spikes in server errors or response time.
- Host near your main audience; Indian visitors are usually best served from Indian data centres.
WebJi® hosting starts at ₹299 a month before 18% GST; for heavy pages, the website speed optimisation service fixes the site itself, since no plan name alone improves rankings.
What should a quick technical SEO audit check?
Check indexing reports, status codes, canonicals, sitemap health, mobile rendering, Core Web Vitals, structured data and internal links, in that order. Fix what blocks indexing before tuning speed.
- Search Console → Page indexing: read every "Why pages aren't indexed" reason.
- Crawl the site with an SEO crawler and list 3xx chains, 4xx and 5xx URLs.
- Confirm one canonical host and HTTPS-only redirects.
- Check sitemap URLs all return 200 and are canonical.
- Inspect key templates' rendered HTML.
- Review Core Web Vitals and fix the worst template first.
- Validate structured data; see schema markup in WordPress.
- Find orphan pages and link them from relevant content.
Frequently asked questions
Does crawl budget matter for a small website?
Rarely. Google says crawl budget mainly concerns very large or fast-changing sites. For a site with a few hundred pages, focus on clean status codes, a correct sitemap and internal links instead.
Is HTTPS a ranking factor?
It is a lightweight signal, and browsers warn visitors on HTTP pages with forms. Every site should serve HTTPS with one permanent redirect from HTTP and no mixed-content warnings.
How often should technical SEO be checked?
Glance at Search Console weekly for new errors, run a full crawl monthly or after any redesign, migration or plugin change, and recheck Core Web Vitals after adding heavy scripts.
Can a plugin handle all technical SEO on WordPress?
An SEO plugin handles sitemaps, canonicals, meta robots and schema well. It cannot fix slow hosting, heavy themes, broken redirects from a migration or JavaScript-only content; those need direct work.
Last editorial update: 15 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
Ready to get started with WebJi®?
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.