Technical SEO Basics Every Business Owner Should Know: What to Check and Fix First

A plain-English guide to technical SEO for business owners: how Google crawls, renders and indexes your site, the silent problems that cap rankings, and the 5-step order I use to fix them without writing code.

Most business owners I meet in Pune have spent real money on a website and real hours on content, and then wonder why the phone is not ringing. The usual assumption is that the writing needs work or that competitors are simply spending more. Very often the actual cause is technical and quiet: a page set to noindex during development and never switched back, a robots.txt file blocking the whole site, images so heavy that the page takes eight seconds to load on a phone. None of these problems show up when you browse your own site on office Wi-Fi.

I am Shreyas Bagal, a solo freelance digital marketer based in Pune, and technical checks are the first thing I do on any SEO project, before a single keyword is chosen. This guide is the version I would give a client over a coffee: plain language, no code, and an order of operations so you fix the things that matter most first. You will learn how Google actually processes a website, what the main technical factors are, which free tools show you the truth, and where a business owner can safely do the work personally versus where paying for help makes sense.

One point of scope. This guide covers the site-wide foundations that apply to almost every business website. It does not cover keyword research, content writing or link building, which are separate jobs. If you want the bigger picture first, read my beginner's guide to SEO, then come back here to make sure the foundations underneath that work are solid.

What is technical SEO, and how is it different from content SEO?

Technical SEO is the practice of making sure search engines can crawl your pages, render them properly, index them and trust them. It is separate from content SEO, which is about what your pages say, and from off-page SEO, which is about who links to you. A simple way to hold the three apart: content decides whether a page deserves to rank, off-page signals decide how much Google trusts it, and technical SEO decides whether the page gets a fair chance to compete at all.

Think of your website as a shop. Content is the stock on the shelves. Off-page work is your reputation on the street. Technical SEO is whether the shutter is up, the lights are on, the door opens and the address on the signboard matches the address on Google Maps. A shop with excellent stock and a jammed shutter sells nothing. That is why I treat technical health as a gate: until the basics pass, effort spent on articles and backlinks is partly wasted, because you are pushing traffic and trust toward pages that cannot use them.

The good news for small businesses is that technical SEO is mostly a one-time job. A typical five to twenty page business website has a short list of things that can go wrong, and most of them are fixable in an afternoon. Large e-commerce sites with hundreds of thousands of URLs need ongoing specialist work. A clinic, a coaching institute or a local service company usually needs a proper audit once, a few fixes, and a light check every quarter.

How does Google crawl, render and index a website?

Google processes a page in three stages: crawling, rendering and indexing. Crawling means Googlebot requests your URL and downloads the page. Rendering means Google runs the page's code, much like a browser, to see the final layout and content. Indexing means Google decides whether to store the page in its database so it can appear in results. A page can fail at any stage, and each failure has a different fix, which is why guessing usually wastes time.

Crawling depends on whether Googlebot can reach the page. Your robots.txt file can forbid it, a login wall can block it, and a page with no internal links pointing to it may never be discovered. My guide on what crawling is in SEO goes deeper on this stage. Rendering depends on your code and speed: content that only appears after heavy scripts run can be seen late or not at all. Indexing depends on quality and instructions: a noindex tag, a canonical pointing elsewhere, or thin duplicate content can all lead Google to skip storing the page.

The important lesson is that being crawled is not the same as being indexed, and being indexed is not the same as ranking. In Google Search Console, statuses such as "Crawled, currently not indexed" and "Discovered, currently not indexed" mean Google saw or heard of the page and chose not to keep it, at least for now. If you have seen those labels, my post on why a website is not showing on Google walks through the likely reasons, and the five steps below give you a working order for the diagnosis.

Which technical SEO factors matter most for a small business?

For a small business site, eight factors carry almost all of the weight: indexability, crawl access through robots.txt, an XML sitemap, page speed and Core Web Vitals, mobile usability, HTTPS security, clean URL structure with canonical tags and redirects, and structured data. Everything else, such as log file analysis or JavaScript rendering budgets, only becomes relevant on large or unusually built sites. Getting these eight right puts a small site ahead of a surprising share of local competitors.

I rank them by the damage they can do rather than by how technical they sound. Indexability and robots.txt sit first because a mistake there can remove your whole site from Google, which no amount of good design can offset. The sitemap and internal links come next because they control discovery. Speed and mobile usability come after because they affect both rankings and, more importantly, whether a visitor stays long enough to enquire. HTTPS, canonicals and redirects keep your signals consolidated. Schema markup sits last because it helps Google and AI answer engines understand your pages but rarely rescues a site that fails the earlier seven.

A sensible reading order follows that ranking, and it is the order I use in the steps below. If you only have one hour, spend it on indexability and mobile usability. If you have a Saturday, work through all five steps in sequence and write down what you changed, so that you can tell later which change moved which number.

Technical factorRisk if ignoredWhere to fix it
Indexability (noindex, Search Console)Page never appears in resultsStep 1 and 2
robots.txt and sitemapPages blocked or found lateStep 2
Page speed and Core Web VitalsSlow loads, lost visitorsStep 3
Mobile usabilityPoor experience on phonesStep 3
HTTPS, canonicals, redirectsSplit signals, trust warningsStep 4
Schema markupWeaker machine understandingStep 5

How do you fix technical SEO on a small business site? The 5-step order

The five steps below are the order I follow on client sites, arranged so that the most damaging and cheapest problems come first. Each step needs only free tools, and the whole sequence takes roughly three hours on a small site. Do them in order: there is no point polishing schema markup on a page that is accidentally blocked from indexing.

Step 1: Check whether your key pages are indexed

Open Google Search Console, paste your homepage into the inspection bar at the top and read the verdict. "URL is on Google" means the page is indexed. "URL is not on Google" comes with a reason. Repeat this for your main service page and your most important blog post. Then open the Pages report and read every reason listed under "Not indexed". This is the single most useful ten minutes in technical SEO, because it replaces guessing with Google's own explanation.

If you have not set up Search Console yet, verify your domain first, following Google's official Search Console help; my Google Search Console beginner's guide shows the setup and the reports worth reading. Some reasons are harmless: pages you deliberately noindexed, or old URLs that redirect. Others are urgent: "Blocked by robots.txt" or "Excluded by noindex tag" on a page you want customers to find. Note the count of each reason. That list becomes your to-do list for step 2, and it also gives you a before-and-after number to compare against once the fixes are done.

If a page is simply "Discovered, currently not indexed", do not panic. On newer sites this often means Google has not yet judged the site worth the crawl effort. Strengthen internal links to the page, improve its content, and see my walkthrough on how to index your website on Google for the request-indexing routine.

Step 2: Remove crawl and indexing blocks

Type yourdomain.com/robots.txt into your browser. If you see a line reading "Disallow: /" under "User-agent: *", you are telling every crawler to stay out of the whole site. That line is common on staging sites and sometimes survives the launch. Next, open an important page, right-click, choose view source and search for the word noindex. If it appears in a meta robots tag, Google is being told not to store that page. These two checks find the most expensive mistakes in technical SEO in under five minutes.

Then look at your sitemap, normally at yourdomain.com/sitemap.xml. It should list only live, indexable pages you want found, not redirected URLs, error pages or noindexed pages. Submit it under Sitemaps in Search Console. My explainers on what robots.txt does and the XML sitemap cover the syntax and common errors if your file looks odd.

Remember that robots.txt controls crawling, not indexing. A blocked page can still appear in results if other sites link to it, just without a description. To keep a page out of Google reliably, use noindex, and make sure robots.txt does not also block it, otherwise Google never sees the noindex instruction. WordPress users should also check Settings, Reading, and confirm "Discourage search engines from visiting this site" is unticked. I have seen that single checkbox left on for months after launch.

Step 3: Fix speed and mobile usability

Run Google PageSpeed Insights on your homepage and one service page, and read the mobile tab first, not the desktop one. Google uses the mobile version of your site for indexing, so mobile is the score that counts. Look at the three Core Web Vitals and the list of opportunities underneath. On most small business sites the same three culprits appear: oversized images, too many plugins or third-party scripts, and cheap shared hosting with slow server response.

The fastest win is images. Any image above about 200 KB on a phone-facing page deserves compression. Convert photos to WebP, set explicit width and height attributes so the layout does not jump while loading, and lazy-load images below the first screen. My image SEO guide gives the exact settings. After images, remove plugins you do not use, and compare your setup against the Core Web Vitals guide for the fixes behind each metric.

Then stop trusting the tools and test on a real phone. Load the homepage on mobile data, read a paragraph without zooming, tap the main call-to-action button and submit your own contact form. Most Indian small business enquiries now arrive from phones, so a form that fails on Android or a button hidden behind a chat widget loses real leads. A clean score means little if the form does not work.

Step 4: Secure the site and clean up duplicates

Confirm that every page loads on HTTPS with a valid certificate and no browser warning. Then test the four versions of your address: http and https, with and without www. Each should end up at a single preferred version through one redirect. If two versions load separately, Google may treat them as duplicates and split your signals. Most hosts offer a free certificate, so a padlock is a basic expectation, not a premium feature.

Next, add a canonical tag to each page pointing to its own preferred URL, which tells Google which version to keep when the same content is reachable through several addresses, such as with tracking parameters or filter options. My guide to canonical URLs explains when this matters. Replace redirect chains, where URL A sends people to B and B sends them to C, with one permanent 301 redirect from A to C. The 301 redirect guide covers how to set these up without losing accumulated link value.

Finish with broken links. Search Console and free crawlers such as Screaming Frog, which is free up to 500 URLs, will list internal links that lead to error pages. Fix each by updating the link or redirecting the old address. Good internal linking also helps Google discover and weight your pages, which I cover in the internal linking strategy guide. Broken links waste crawl effort and frustrate visitors, so this cleanup improves both rankings and enquiries.

Step 5: Add schema markup and re-verify

Schema markup is a block of structured code, usually JSON-LD, that labels what a page is about in a format machines read easily. For a business site, start with Organization or LocalBusiness schema on the homepage, Article schema on blog posts and FAQPage schema where a page has real questions with real answers. Do not mark up content that is not visible on the page, and do not invent reviews or ratings, because that violates Google's guidelines and risks a manual action.

Validate every block with Google's Rich Results Test before publishing. If you use WordPress, a reputable SEO plugin can generate most of this for you, though you should still check the output. My schema markup guide explains the types and the code, and the local business schema guide gives the fields a Pune service company should fill in.

Finally, re-verify. Go back to Search Console, re-inspect the same URLs from step 1, and request indexing for any page you fixed. Wait two to four weeks, then check the Pages report again and compare the "Not indexed" counts with your notes. Google works on its own schedule, so expect gradual change rather than an overnight jump. If numbers have not moved after a month, that is the point to run the deeper checks in my free website SEO audit guide.

What are Core Web Vitals and what scores should you aim for?

Core Web Vitals are three metrics Google uses to describe real-world page experience. Largest Contentful Paint (LCP) measures how quickly the main content appears, with Google's guidance being 2.5 seconds or less. Interaction to Next Paint (INP), which replaced First Input Delay in March 2024, measures how fast the page responds to taps and clicks, with a target of 200 milliseconds or less. Cumulative Layout Shift (CLS) measures visual stability, with a target below 0.1.

These are thresholds Google publishes, and it measures them from real Chrome users over a rolling window, so a lab score in PageSpeed Insights can differ from the field data shown above it. For a small local site with modest traffic, field data may be missing altogether, in which case the lab score is your guide. I treat Core Web Vitals as a tiebreaker rather than a magic ranking lever: great content on a slow page can still rank, but between two similar pages, the faster and steadier one has an edge.

The practical fixes are unglamorous. For LCP, compress the hero image and avoid sliders that load several large images at once. For INP, remove heavy scripts, since chat widgets and analytics stacks are frequent offenders. For CLS, reserve space for images, ads and embedded videos, so the text does not jump as they load. My Core Web Vitals guide lists the fixes by metric. Because Indian mobile connections vary widely, I test on a mid-range Android phone over 4G, not on a fast laptop.

Why does mobile usability matter more than desktop?

Mobile usability matters because Google uses mobile-first indexing: it evaluates and ranks the mobile version of your pages, even for people searching on a desktop. If content, links or structured data exist on your desktop layout but are hidden or missing on mobile, Google may never see them. In India, where most web browsing happens on phones, the mobile layout is also the version most of your customers actually use.

The common mobile problems are easy to spot once you look for them. Text too small to read without pinching, buttons placed so close together that a thumb hits the wrong one, horizontal scrolling caused by a wide table or image, pop-ups that cover the whole screen, and phone numbers that are plain text rather than tappable links. Each one raises the chance that a visitor leaves without enquiring. Search Console no longer has a dedicated Mobile Usability report, so rely on PageSpeed Insights and your own hands-on test.

A related issue is content parity. If your desktop page has a 1,000 word service description and the mobile version collapses it into a short teaser, Google indexes the teaser. Keep the same headings, text, images with alt text, and structured data on both versions. Responsive themes, where one layout adapts to screen width, avoid this problem by design, which is one reason I recommend them over separate mobile sites.

What do HTTPS, canonical tags and redirects actually do?

HTTPS encrypts the connection between your visitor and your server, and browsers flag sites without it as "Not secure". Google has used HTTPS as a lightweight ranking signal since 2014, but the larger effect is trust: a contact form on a page carrying a warning loses submissions. Canonical tags tell Google which URL is the master copy when several addresses show the same content. Redirects send visitors and crawlers from an old address to the correct one. Together they consolidate your signals in one place.

Trouble starts when these three disagree. A page might be reachable at four addresses, canonicalised to a fifth, and redirected from a sixth, and Google has to guess which one you mean. When it guesses differently from you, ranking signals split across versions. I usually fix this by choosing one preferred address format, such as https with no www, then making sure that redirects, canonical tags, sitemap entries and internal links all use exactly that format. Consistency is the whole trick.

Use 301 for permanent moves, for example after changing a URL or merging two pages, and reserve 302 for genuinely temporary ones. When you change a page's address, always redirect the old one to the closest equivalent page, not simply to the homepage, since mass redirects to the homepage are often treated as soft errors. Also update internal links to the new address, so that visitors do not travel through a redirect every time. Keeping redirect chains to a single hop preserves speed and link value.

How does schema markup help traditional search and AI answers?

Schema markup helps by removing ambiguity. A crawler reading your page has to infer that a string of digits is a phone number or that a block of text is a list of questions and answers. Structured data states it outright. In traditional Google search, valid schema can qualify a page for rich results, though Google has reduced the visibility of some types, FAQ rich results included, so I never sell schema as a guaranteed click booster. Its more durable value is clarity: it helps machines understand who you are and what each page covers.

That clarity increasingly matters for AI answer engines. Google AI Overviews, ChatGPT search and Perplexity all read the web to compose answers, and pages that state clear facts, entities and relationships are easier to quote accurately. Schema is not a published requirement for any of them, so I describe it as a helpful signal rather than a switch. If you want the AI-search side of this, my guides on appearing in Google AI Overviews and answer engine optimisation build on the technical base described here.

Entity clarity is the connecting idea. Consistent business name, address, phone number, social profiles and author details, expressed both in visible text and in markup, help search engines and AI systems recognise your business as one distinct entity. My entity SEO guide covers this in depth. Whatever you mark up, keep it truthful and match what visitors can see, because mismatches between markup and page content are a common reason structured data is ignored.

Which free tools should a business owner use for technical SEO?

You can run a solid technical check with four free tools. Google Search Console shows indexing status, sitemaps, crawl problems and search performance for your own site. Google PageSpeed Insights reports Core Web Vitals and specific speed fixes. Google's Rich Results Test validates schema markup. Screaming Frog's free version crawls up to 500 URLs and lists broken links, redirects, missing titles and duplicate content. Bing Webmaster Tools is a worthwhile fifth, as it feeds Bing and other engines.

Use each tool for what it is best at rather than treating any as an oracle. Search Console is the authority on what Google itself thinks of your pages, because the data comes directly from Google. PageSpeed Insights blends lab and field data and can shift score by a few points from run to run, so look for patterns rather than chasing a perfect 100. A crawler shows you your site as a machine sees it, exposing problems that no visitor would ever notice, such as an orphan page with no links pointing to it.

If you are comparing options beyond these, my roundup of the best free SEO tools for small business covers keyword and audit tools too, and my Bing Webmaster Tools guide covers that setup. Keep the tool list short. A business owner who checks Search Console monthly and acts on what it says will outperform one who owns six dashboards and reads none.

What are the most common technical SEO mistakes I see?

The mistakes I see most often are boringly consistent. A site launched with a noindex tag or a blocking robots.txt from the staging environment. A homepage image uploaded straight from a phone camera at 6 MB. A sitemap listing pages that redirect or return errors. Duplicate versions of the site reachable on http and https. A contact form that works on desktop but not on phones. Blog posts with no internal links pointing to them, so Google finds them late or never. None of these needs a developer to spot.

A second group comes from well-meaning plugin use. Installing three SEO or caching plugins that conflict, or a page builder that outputs heavy code and dozens of scripts. Each plugin adds convenience and weight, and the weight shows up in your Core Web Vitals. I usually recommend removing anything you cannot explain the purpose of. A third group is neglect: expired certificates, a domain renewal missed, or a redesign that changed every URL without redirects. Losing old URLs without redirects can wipe out years of accumulated ranking in a week.

On the proof side, I will keep this modest. On one Pune client project, a page moved from position 59 to the top 5 in two months, and technical cleanup was part of that work alongside content and internal linking, so I cannot credit any single fix. What I can say is that the pattern is consistent: when I remove an indexing or speed problem first, the content work that follows performs closer to its potential. My post on how long SEO takes sets out realistic timelines.

How does technical SEO connect to local search and lead generation?

Technical SEO connects to local search through the same foundations: a fast, mobile-friendly, indexable website with consistent business details supports your Google Business Profile, your local landing pages and your citations. Google's local results draw on relevance, distance and prominence, and while the technical layer does not change your distance, a slow or broken site weakens the prominence and relevance signals your website contributes. It also affects what happens after the click, which is where leads are won.

Lead generation is the reason I care about this at all. On paid campaigns, I have kept Meta lead costs in the Rs 20 to 25 range, and the same principle applies to organic traffic: a slow or confusing landing page wastes whatever brought the visitor there. A page that loads in under three seconds on 4G, shows the phone number and WhatsApp button without scrolling and submits the form reliably converts a higher share of the same visitors. Technical work protects the value of every rupee and every hour spent on traffic.

For local businesses, the practical checklist links these together. Keep your business name, address and phone number identical across the site footer, the contact page and your profile listings, as explained in my NAP consistency guide. Add LocalBusiness schema with the same details. Make each service-plus-area page load fast and work on mobile. My local SEO checklist for 2026 shows where technical items fit in the wider work.

When should you hire help instead of doing it yourself?

Do the basics yourself and hire help for diagnosis and repair of the tangled issues. Business owners can reasonably compress images, submit a sitemap, check indexing in Search Console, test the site on a phone and read a PageSpeed report. Professional help pays off for stray noindex tags on templates, redirect chains built up over several redesigns, canonical conflicts, JavaScript content that Google renders poorly and correct schema implementation across many page types.

Be careful about who you hire and what you are told. Ask any consultant to show the specific evidence for each problem: a Search Console screenshot, a crawl export, a specific URL. Be wary of anyone who promises rankings from a technical audit alone, because technical health enables rankings and does not create them. A freelancer can usually complete a small business audit and the fixes in a few hours to a couple of days, and the work rarely needs a full-time developer. My comparison of freelancer versus agency options helps you judge the fit, and SEO costs in India shows what different services typically charge.

If your site is on a custom-coded platform, an e-commerce store with thousands of products, or a WordPress build with a heavy theme, budget for a developer on the fixes even if an SEO specialist does the diagnosis. Your platform matters more than most owners expect, and my WordPress vs Wix vs Shopify comparison explains how each handles the technical basics. Finally, remember the maintenance side: recheck Search Console monthly and run a full audit each quarter or after any redesign.

Frequently asked questions

What is technical SEO in simple terms?

Technical SEO is making sure search engines can find your pages (crawl), load them the way a visitor sees them (render), store them for results (index), and trust them (HTTPS, no errors). It is separate from content quality. A well-written article that Google cannot crawl or load on a phone will not rank. For most small business sites the fixes are one-time jobs that keep paying off for years.

How can I check my website's technical SEO for free?

Start with Google Search Console: paste any URL into the inspection bar and it says whether the page is indexed and why not. Then run Google PageSpeed Insights and read the mobile tab, since Google ranks the mobile version. Finally open your site on a phone and try the main button and contact form. These three checks cost nothing and catch most of the problems that hold small business sites back.

What are Core Web Vitals and what scores should I aim for?

Core Web Vitals are Google's three speed and stability metrics. LCP (Largest Contentful Paint) measures how fast the main content appears, and Google's guidance is under 2.5 seconds. INP (Interaction to Next Paint, which replaced FID in 2024) measures response to taps, aim under 200 milliseconds. CLS (Cumulative Layout Shift) measures visual stability, aim under 0.1. On small business sites the biggest fix is usually compressing oversized images.

Does technical SEO matter if I have great content?

Yes. Great content that Google cannot crawl, cannot load properly on mobile, or has been accidentally set to noindex will not rank, however good it is. Technical SEO is the foundation layer: fix it once and every page you publish benefits. Ignore it and even your best articles get capped by problems you cannot see by browsing your own site normally.

Should I hire a developer for technical SEO?

Not for the basics. Business owners can compress images, submit a sitemap, check indexing in Search Console and test mobile usability themselves. Professional help pays off for diagnosing stray noindex tags, untangling redirect chains, fixing canonical conflicts and implementing schema correctly. These are usually one-time fixes that a freelancer can complete in a few hours, so a full-time developer is rarely needed.

Related guides

Your next step

Do step 1 today: open Google Search Console, inspect your homepage and your most important service page, and write down what it says. That ten-minute check tells you whether you have a technical problem at all and which step to start with. If it turns up something you are not sure how to fix, read my free website SEO audit guide or get in touch and I will take a look.

Follow Shreyas in Google

Get new guides in your Google Search & Discover feed.