Technical SEO Basics Every Website Owner Should Know
A website can look clean, show your logo nicely and still be close to invisible on Google. Often the reason is not the writing or the design. It is something under the hood: a page blocked by mistake, a sitemap full of dead links, or a site that takes eight seconds to open on mobile data. Getting the technical SEO basics right is what removes those hidden blocks.
This guide is written for business owners who are not developers. You will learn how Google finds and stores pages, which settings can quietly hide your site, how to handle redirects and duplicate pages, and a short monthly check you can run yourself in Google Search Console.
What technical SEO basics actually cover
SEO work usually falls into three buckets. On-page SEO is about the words, headings and titles on each page. Off-page SEO is about other websites mentioning and linking to you. Technical SEO is everything that decides whether Google can reach, read and store your pages in the first place.
Think of a shop in a busy market. Good products and a nice signboard matter, but if the shutter is half down and the lane is blocked, few people walk in. Technical SEO keeps the shutter up and the lane clear. In practice, it comes down to a handful of things:
- Crawling: can Google's bot reach your pages by following links?
- Indexing: does Google decide to store the page and show it in results?
- Status codes and redirects: do old or moved pages send visitors to the right place?
- Duplicates: does Google know which version of a page is the main one?
- Speed and mobile use: does the site open fast and work well on a phone?
How Google finds, reads and stores your pages
Every page goes through three steps before it can rank. First, Googlebot crawls it, usually after finding a link to it on another page or in your sitemap. Second, Google renders it, loading the HTML, CSS and JavaScript much like a browser does. Third, it decides whether to index the page, which means adding it to the database it uses to answer searches.
A problem at any step stops the page from ranking. A page with no links pointing to it may never be crawled. A page whose main text appears only after heavy JavaScript may be rendered with missing content. A page that looks thin or copied may be crawled but left out of the index.
The easiest way to see this for yourself is the URL Inspection tool in Google Search Console. Paste any page address and it tells you whether the page is indexed, when it was last crawled and whether anything blocked it. If you have not set up Search Console yet, do that first. It is free and takes about ten minutes if you can access your domain settings.
Robots.txt and noindex: two settings that can hide your site
Two small settings cause more lost traffic than almost anything else we come across. Both are useful when used on purpose and harmful when left on by accident.
Robots.txt
This is a plain text file at yourdomain.com/robots.txt. It tells crawlers which folders they should not request. Blocking an admin area, cart or checkout pages is reasonable. The danger is a single line, Disallow: /, which blocks the whole site. Developers sometimes add it while building a site and forget to remove it at launch. Also, never block CSS or JavaScript folders, because Google needs those files to see how the page looks on a phone. Google's introduction to robots.txt is worth reading before you edit this file.
Noindex
A noindex tag tells Google not to show a page in results. WordPress has a setting called Discourage search engines from indexing this site that adds it to every page. It is meant for test sites, yet we have seen live business sites run for months with that box still ticked. If your site runs on WordPress, check it under Settings, then Reading. Our WordPress website service includes this kind of launch check, because it is so easy to miss.
One more detail: robots.txt stops crawling, not indexing. If you want a page out of Google, use noindex and leave the page crawlable so Google can actually see the tag.
XML sitemaps and clean URLs
An XML sitemap is a list of the pages you want Google to know about. It does not force indexing, but it helps Google find new and deep pages faster. That matters most for an online shop with hundreds of product pages or a blog that publishes often. A good sitemap:
- Lists only live pages that load normally, not redirects or deleted pages.
- Leaves out noindex pages, thank-you pages, cart pages and internal search results.
- Updates itself when you add or remove pages. Most SEO plugins and well-built custom sites do this automatically.
- Is submitted in Search Console under Sitemaps, so you can compare how many listed pages are actually indexed.
Clean URLs help both people and crawlers. Compare /products/white-cotton-panjabi with /index.php?id=4821&cat=7. The first tells the reader what the page is about before they click. Keep URLs short, lowercase and separated by hyphens, and do not change them once a page is live unless you add a redirect.
Status codes, redirects and broken links
Each time a browser or crawler asks for a page, your server answers with a three-digit code. These are the ones that come up in almost every technical review:
| Code | What it means | What to do |
|---|---|---|
| 200 | Page loaded normally | Nothing. Every live page should return this. |
| 301 | Page moved permanently | Use it when you change a URL or merge pages. Point it straight to the final page. |
| 302 | Page moved for now | Only for short-term moves. Switch to 301 if the move becomes permanent. |
| 404 | Page not found | Fine for pages that are truly gone. Fix internal links to them, and redirect any that still get visits. |
| 5xx | Server error | Urgent. Repeated server errors make Google crawl less and can drop pages from results. |
Two redirect habits cause trouble. The first is chains, where page A goes to B and then to C. Each hop slows the visitor and wastes crawl time, so point A directly to C. The second is sending every deleted page to the homepage. If a clothing shop removes an old Eid collection page, redirect it to the current collection. If nothing similar exists, a 404 is more honest.
Many small sites in Bangladesh run on low-cost shared hosting, and cheaper plans sometimes throw 500 or 503 errors when a sale or a popular Facebook post brings a rush of visitors. If Search Console shows server errors, fix the hosting before you spend more on content.
Duplicate pages and canonical tags
The same content can often be reached through several addresses. An online shop might show one product at /product/blue-saree, /product/blue-saree?color=blue and /offer/blue-saree. The http and https versions, or www and non-www, may also both load. To Google, these can look like separate pages competing with each other. The fix has three parts:
- Pick one main version of your domain, for example https with www, and 301 redirect the others to it.
- Add a canonical tag on each page pointing to its main URL. Most platforms add one by default, so check it is correct rather than assuming.
- Make your menus, internal links and sitemap use that same main URL. Google treats canonical tags as a hint, and mixed signals make it pick its own version.
Also avoid near-duplicate pages written on purpose, such as ten district pages for one service where only the place name changes. They rarely help and can make the whole site look thin.
Speed and mobile use in plain terms
Google looks mainly at the mobile version of your site when it ranks pages, and most of your visitors are on phones too, often on mobile data that slows down in the evening. Google measures page experience through Core Web Vitals:
- LCP (Largest Contentful Paint): how fast the main content appears. Aim for roughly 2.5 seconds or less.
- INP (Interaction to Next Paint): how quickly the page reacts when someone taps a button or opens a menu.
- CLS (Cumulative Layout Shift): whether things jump around while loading, such as a button moving just as you try to tap it.
The usual fixes are simple: resize and compress images before upload, use WebP, remove plugins and scripts you do not use, avoid heavy sliders at the top and choose hosting with caching turned on. Our guide on website speed and SEO goes through these step by step. If the theme itself is the problem, a lighter custom website design is sometimes cheaper over time than patching a bloated template.
A simple monthly technical SEO check
You do not need an expensive tool to keep technical SEO basics under control. Set aside 30 to 45 minutes once a month for this list:
- Pages report in Search Console: look at why pages are not indexed. A sudden jump in Excluded by noindex tag or Blocked by robots.txt usually means a setting changed.
- Sitemaps report: confirm the sitemap was read and the number of discovered pages roughly matches what you expect.
- URL Inspection: test your homepage and your two or three most important service or category pages.
- Core Web Vitals report: check for mobile pages marked poor, then test those page types in PageSpeed Insights.
- Broken links: click through your main menu and footer on a phone and fix anything that leads to an error page.
- HTTPS: make sure the padlock shows and the SSL certificate has not expired.
- After any redesign or plugin update: repeat steps 1 to 3 within a week. Most technical problems appear right after a change.
Once the foundation is stable, connect your pages with sensible internal links so Google and visitors can reach deeper content. Our article on internal linking for SEO explains how.
FAQ
Do I need a developer for technical SEO?
For checking, no. Search Console, PageSpeed Insights and a careful click-through on your phone will catch most problems. For fixing redirects, server errors or slow templates, a developer usually saves time and avoids breaking something else.
How long after a fix does Google update?
Small fixes on important pages can show within a few days, especially if you request indexing in URL Inspection. Site-wide fixes, like removing an accidental noindex, often take two to six weeks to recover fully, depending on the size of the site.
Does an SSL certificate help rankings?
HTTPS is a light ranking signal, but the bigger reason is trust. Browsers label http sites as not secure, and many visitors leave, especially on pages that ask for a phone number or delivery address.
Is technical SEO a one-time job?
The first cleanup is the biggest piece of work. After that it is maintenance: a monthly check and a careful review after redesigns, theme changes, plugin updates or a move to new hosting.
Need help with technical SEO?
If your pages are not showing on Google and you are not sure why, Nexteio can check indexing, robots and noindex settings, redirects, duplicates and mobile speed, then fix what is holding the site back. You get a plain list of what was wrong and what changed. See our SEO service for details, or start a project and share your website address.