In short: Technical SEO makes sure search engines can crawl, render and index your pages. Check indexing in Search Console, robots.txt and noindex rules, XML sitemaps, canonicals, 301 redirects, Core Web Vitals (LCP, INP, CLS), mobile content parity, structured data, HTTPS, hreflang and JavaScript rendering, then fix what blocks your important pages.

Technical SEO services check and fix the parts of a website that decide whether search engines can find, crawl, render and index its pages. A complete technical SEO checklist covers indexing status, robots.txt and noindex rules, XML sitemaps, canonical URLs, redirects, Core Web Vitals, mobile content, structured data, HTTPS, hreflang for multilingual sites and JavaScript rendering. If any of these block your important pages, no amount of content or links will make them rank.
Every item below is based on Google Search Central documentation, checked on 15 November 2026. Use it to audit your own site, or to check what a technical SEO provider’s proposal actually covers.
The checklist at a glance
| Area | What to check | Where to check it |
|---|---|---|
| Indexing | Important pages are indexed; reasons for pages that are not | Search Console Page indexing report, URL Inspection tool |
| robots.txt | Not blocking pages or resources you need crawled | Your /robots.txt file, Search Console |
| noindex | Only on pages you want kept out of search | Page source, X-Robots-Tag headers |
| Sitemaps | Absolute, canonical, indexable URLs only; submitted | Search Console Sitemaps report |
| Canonicals | One preferred URL per page, consistent across signals | Page source, URL Inspection (Google-selected canonical) |
| Redirects | Permanent moves use 301 or 308; no chains or loops | Crawler tool, browser developer tools |
| Status codes | Missing pages return 404 or 410, not 200 | Crawler tool, Page indexing report (soft 404) |
| Core Web Vitals | LCP, INP and CLS in the good range | Search Console Core Web Vitals report, PageSpeed Insights |
| Mobile | Same primary content, metadata and structured data as desktop | Mobile rendering in URL Inspection |
| Structured data | Valid, complete, matches visible content | Rich Results Test, Search Console |
| HTTPS | Whole site on HTTPS; HTTP redirects to HTTPS | Search Console HTTPS report |
| hreflang | Return links, valid codes, consistent with canonicals | Page source or sitemap |
| JavaScript | Key content and links present in rendered HTML | URL Inspection rendered HTML |
Crawling and indexing
Start in Google Search Console. The Page indexing report shows which URLs Google has indexed and gives a reason for each URL that is not. Not every “not indexed” status is a problem:
- Crawled - currently not indexed. Google crawled the page but did not index it. Google says this is common and not necessarily an issue, but check any important page that shows it.
- Discovered - currently not indexed. Google knows the URL but has not crawled it yet, often because it postponed the crawl to avoid overloading the site.
- Duplicate without user-selected canonical. Google picked another URL as the canonical. Fine if it chose correctly; fix it if not.
Use the URL Inspection tool to check a single page, see which canonical Google selected, and test the live URL.
Check status codes too. Google’s documentation on HTTP status codes says 4xx pages are treated as non-existent and dropped from the index, while repeated 5xx errors slow crawling and can eventually remove pages. A page that returns 200 but shows an error message is flagged as a soft 404.
robots.txt and noindex
robots.txt tells crawlers which parts of a site they may access. Its main purpose is to stop your server being overloaded. Google states plainly that it is not a way to keep a page out of Google: a blocked URL can still appear in results, without a description, if other pages link to it.
To keep a page out of search, use noindex, either as a robots meta tag in the page head or as an X-Robots-Tag HTTP header (useful for PDFs). The page must not be blocked in robots.txt, or Google never reads the noindex rule.
Common mistakes to look for:
- A staging site’s
Disallow: /copied to the live site after launch - noindex left on pages after a redesign
- CSS or JavaScript files blocked, so Google cannot render the page properly
XML sitemaps
Google’s sitemap guidelines set a limit of 50MB uncompressed or 50,000 URLs per sitemap; larger sites split them and use a sitemap index. Other points from the same page:
- Use absolute URLs, such as
https://www.example.com/page/. - List the canonical version of each page only.
- Submit through the Search Console Sitemaps report, the API, or a
Sitemap:line in robots.txt. - Google uses
lastmodonly if it is consistently accurate, and ignorespriorityandchangefreq.
Canonical URLs
Most sites have duplicate URLs: with and without www, with tracking parameters, HTTP and HTTPS, or the same product in two categories. Google’s guide to consolidating duplicate URLs describes the signals you can send:
- Redirects: a strong signal that the target should be canonical.
rel="canonical": also a strong signal, in the HTML head or as an HTTP header.- Sitemap inclusion: a weak signal.
Google’s advice includes adding a self-referencing canonical on the preferred page, using absolute URLs, linking internally to the canonical version, and never sending conflicting signals. It also says not to use robots.txt or noindex to choose a canonical.
Redirects
When you move or merge pages, Google’s redirect documentation recommends a permanent server-side redirect, 301 or 308, when the move is final. Google then treats the target as the canonical. Temporary redirects (302, 303, 307) keep the old URL in search results and suit short-term changes. JavaScript redirects are a last resort, because Google may miss them if rendering fails.
Site migrations are where redirects most often go wrong. Map every old URL to its closest new equivalent before launch, avoid redirect chains, and recheck the Page indexing report in the weeks after.
Core Web Vitals
Google’s Core Web Vitals page sets three targets:
| Metric | Measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading | Within 2.5 seconds |
| Interaction to Next Paint (INP) | Responsiveness | Under 200 milliseconds |
| Cumulative Layout Shift (CLS) | Visual stability | Below 0.1 |
INP replaced First Input Delay as a Core Web Vital on 12 March 2024, so any audit still reporting FID is out of date. Google’s page experience guidance says Core Web Vitals are used by its ranking systems, but also that good scores do not guarantee top rankings. Treat them as a user experience floor, not a shortcut.
Typical fixes include compressing and correctly sizing images, reserving space for images and embeds, reducing heavy third-party scripts such as chat widgets and trackers, and improving server response time.
Mobile-first indexing
Google uses the mobile version of a site’s content, crawled with its smartphone agent, for indexing and ranking. Check that the mobile version has:
- The same primary content as desktop (use accordions or tabs rather than removing text)
- The same headings, title and meta description
- The same structured data
Structured data
Google recommends JSON-LD in most cases. Test markup with the Rich Results Test before release and monitor it in Search Console afterwards. Structured data can make a page eligible for rich results, but Google does not guarantee them, and markup must match what is visible on the page.
HTTPS
Google announced HTTPS as a ranking signal in August 2014, describing it then as a very lightweight signal. Ranking aside, every page and resource should load over HTTPS, HTTP URLs should redirect permanently to HTTPS, and canonicals and sitemaps should list the HTTPS versions. Search Console’s HTTPS report shows pages with problems.
hreflang for multilingual sites
If you publish the same content in several languages or for several countries, for example English for Singapore and Chinese or Malay versions, use hreflang. Google’s rules:
- Declare alternates in the HTML head, HTTP headers or the sitemap. One method is enough.
- Every version must list itself and all other versions. Without return links, Google may ignore the annotations.
- Use ISO 639-1 language codes, optionally with an ISO 3166-1 Alpha-2 region, such as
en-SG. A region code cannot stand alone. - Use
x-defaultfor a fallback or language selector page.
JavaScript SEO basics
Google processes JavaScript sites in three phases: crawling, rendering and indexing. Its JavaScript SEO basics recommend:
- Server-side rendering or pre-rendering, so content is in the initial HTML
- Links as
<a>elements with anhref, since Googlebot only follows those - The History API for routing, not
#fragments - Meaningful status codes, including 404 for missing pages
- No
noindexin the original HTML if you want the page indexed, because Google may skip rendering when it sees one
Use URL Inspection to compare the rendered HTML with what users see.
After the fixes: keeping it fixed, then earning links
Most technical issues are fixed once and then broken again by a plugin update, a redesign or a rushed content change. Regular checks matter as much as the first audit. FYAdvisers’ website maintenance service covers updates, monitoring and fixes like these, so problems are caught before they cost you traffic.
Technical SEO only removes barriers. Once Google can crawl and index your pages, rankings still depend on content and on links from relevant sites, the off-page side explained in on-page vs off-page SEO. Our link building service earns those links for Singapore businesses within Google’s spam policies, with every link reported to you. For a wider review, see the SEO audit checklist, or read how to choose an SEO agency in Singapore if you plan to hire one.
Frequently asked questions
What do technical SEO services include?
A technical audit of crawling, indexing, site structure, redirects, canonicals, sitemaps, page speed and Core Web Vitals, mobile content, structured data, HTTPS, international targeting and JavaScript rendering, followed by a prioritised list of fixes. Some providers also carry out the fixes; others hand them to your developer.
Does robots.txt stop a page appearing in Google?
No. Google says robots.txt is not a mechanism for keeping a page out of Google, and a blocked URL can still appear in results if other pages link to it. Use a noindex rule or password protection instead, and do not block that page in robots.txt, or Google will never see the noindex.
What are the current Core Web Vitals?
Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness and Cumulative Layout Shift (CLS) for visual stability. Google's targets are LCP within 2.5 seconds, INP under 200 milliseconds and CLS below 0.1. INP replaced First Input Delay as a Core Web Vital on 12 March 2024.
Should I use a 301 or 302 redirect when I move a page?
Use a permanent server-side redirect, 301 or 308, when the move is final. Google treats the target as the canonical URL. Use 302, 303 or 307 only for temporary changes, such as an outage, when the original URL should stay in search results.
Is technical SEO a one-off job?
The audit can be one-off, but problems come back as sites change. New plugins, redesigns, migrations and content updates can break redirects, canonicals and speed. A light monthly check in Search Console catches most issues early.
