Technical SEO checklist for small business websites

What is technical SEO?

Technical SEO is the work that makes your website easy for search engines to crawl, index and understand. Content and links decide how well you rank; technical SEO decides whether you can rank at all.

For most small business websites built on WordPress, Shopify, Wix or simple HTML, technical SEO isn't complicated. A few settings and habits cover most of it. This checklist is ordered from most to least important.

1. Is your site secure (HTTPS)?

• Every page should load on https:// with a valid certificate. Most hosts, including Hostinger, offer free SSL.
• http:// versions should 301-redirect to https://.
• Pick one version, www or non-www, and redirect the other to it.
• Check for “mixed content”: images or scripts still loading over http, which can trigger browser warnings.

2. Does it work well on mobile?

Google mainly uses the mobile version of your site for indexing and ranking. In India most visitors are on phones, so this matters twice.

• Text should be readable without zooming, and buttons easy to tap.
• No content hidden on mobile that exists on desktop.
• Pop-ups shouldn't cover the main content as soon as the page loads.
• Test your key pages on a real mid-range Android phone on mobile data, not just on office Wi-Fi.

3. Is it fast enough (Core Web Vitals)?

Core Web Vitals are Google's measures of loading, responsiveness and visual stability:

Common fixes:

• Compress and resize images; use modern formats like WebP; set width and height on images.
• Remove unused plugins, sliders, chat widgets and heavy scripts.
• Use caching and a CDN if your host offers one.
• Choose decent hosting with servers in or near India.
• Lazy-load images below the fold, but not your main hero image.

Check with PageSpeed Insights and the Core Web Vitals report in Search Console.

4. Are your important pages indexed?

Open the Pages report in Search Console to see which pages are indexed and why others aren't. Common reasons:

• Excluded by noindex: fine for thank-you pages and admin areas, a problem for service pages.
• Crawled, currently not indexed: Google saw the page but didn't think it was worth indexing, which is often a sign of thin or duplicate content.
• Discovered, currently not indexed: Google knows the URL but hasn't crawled it yet; internal links help.
• Duplicate without user-selected canonical: similar pages competing; choose one main version.
• Not found (404): broken URLs. Fix the links or redirect them.

Use the URL Inspection tool to test a specific page and request indexing after important updates.

5. Do you have a clean XML sitemap?

• An XML sitemap lists the pages you want indexed. Most CMSs and SEO plugins create one automatically.
• Submit it in Search Console under Sitemaps, and reference it in robots.txt.
• Include only real, indexable pages that return a 200 status, with no redirects, 404s or noindex pages.
• Keep lastmod dates accurate when pages actually change.

6. Is robots.txt set up correctly?

robots.txt tells crawlers which parts of your site they may crawl. A single wrong line can block your whole site.

• Make sure it doesn't contain Disallow: / for all user agents on a live site. This sometimes stays behind after a site goes live from staging.
• Block only areas that shouldn't be crawled, such as admin pages or internal search results.
• Don't use robots.txt to hide pages from search results. Use a noindex tag instead, because blocked pages can still be indexed from links.
• Add your sitemap URL at the bottom.

7. Does each page have one main URL?

The same content reachable at several URLs (with tracking parameters, trailing slashes, http/https, filters or print versions) can split ranking signals.

• Add a canonical tag pointing to the main version of each page.
• Use 301 redirects for old or duplicate URLs that shouldn't exist.
• Link internally to the main version only.
• Keep URLs short, lowercase and readable, with hyphens between words, such as /ac-repair-pune.

8. Are redirects and broken links under control?

• When you change a page's URL, add a 301 redirect from the old URL to the new one.
• Avoid redirect chains, where A goes to B and then to C; point A straight to C.
• Fix broken internal links regularly. Free crawlers and Search Console help find them.
• Create a helpful 404 page with search and links to your main sections.

9. Is your site structure clear?

A clear structure helps visitors and Google find your important pages.

• Important pages should be reachable within two or three clicks from the homepage.
• Use a logical menu: Services, Locations, About, Blog, Contact.
• Link related pages to each other with descriptive anchor text.
• Add breadcrumbs on larger sites.
• Avoid “orphan pages” that no other page links to.

10. Are you using structured data?

Structured data (schema markup) describes your content in a machine-readable way. It can make you eligible for rich results and helps search engines and AI tools understand your business.

Validate with Google's Rich Results Test, and only mark up content that's visible on the page.

11. What else should you check?

• Language and region: set the correct lang attribute. Use hreflang if you have separate Hindi and English versions of pages.
• Images: descriptive file names and alt text.
• JavaScript: important content and links should be in the HTML or render reliably; test with URL Inspection.
• Security: keep your CMS, themes and plugins updated; hacked sites can be flagged in search.
• Uptime: frequent downtime can hurt crawling. Choose reliable hosting.

How often should you check technical SEO?

What should WordPress users check specifically?

Many Indian small business sites run on WordPress, which has a few common technical traps:

• Settings → Reading: make sure “Discourage search engines from indexing this site” is unticked on your live site.
• Permalinks: use “Post name” for clean URLs, and set this before publishing many pages, because changing it later needs redirects.
• SEO plugin: use one reputable SEO plugin for titles, meta descriptions, sitemaps and schema. Don't run two at once.
• Plugins: remove unused plugins; each one can add scripts and slow the site.
• Themes and page builders: lightweight themes load much faster than heavy multipurpose ones.
• Caching and image optimisation: use a caching plugin or your host's built-in caching, plus an image compression plugin.
• Attachment pages and tag archives: these can create many thin pages; noindex or disable them if they add no value.
• Updates and backups: keep WordPress, themes and plugins updated, with automatic backups.

What extra checks do online stores need?

• Faceted navigation: filters for size, colour and price can create thousands of URL variations. Use canonicals and keep filter pages out of the index unless they target real searches.
• Out-of-stock products: keep the page live with alternatives if the product returns; redirect to the closest category if it's gone for good.
• Product schema: include price in INR, availability, reviews and shipping where accurate.
• Pagination: category pages should link clearly to page 2, 3 and so on, and each paginated page should be crawlable.
• Duplicate product descriptions: rewrite manufacturer copy for your most important products.
• Merchant Center: keep your product feed accurate so free listings and Shopping ads can appear.

How do you protect SEO during a redesign or migration?

1. Crawl and export every URL on the old site, along with titles and meta descriptions.
2. Map each old URL to its best new equivalent in a spreadsheet.
3. Build the new site on a staging URL blocked from search engines.
4. Before launch: remove the staging block, confirm robots.txt and noindex settings, and implement all 301 redirects.
5. After launch: submit the new sitemap, test key URLs with URL Inspection and watch the Pages report and traffic daily for the first two weeks.
6. Keep redirects in place long-term; old links and bookmarks will keep using them.

Most traffic drops after a redesign come from missing redirects or a forgotten noindex, both preventable with this checklist.

How do AI crawlers fit into technical SEO?

AI search tools and assistants use their own crawlers alongside Googlebot. Your robots.txt decides which of them can access your content. If you want your guides to be cited in AI answers, allow reputable AI crawlers and make your pages easy to parse: clean HTML, clear headings, fast loading and structured data.

Some sites also publish an llms.txt file: a plain-text summary of key pages intended to help AI tools. It's a newer convention, not a formal standard, but it's quick to add and harmless.

What should you fix first?

Which free tools help with technical SEO?

What mistakes cause the biggest problems?

• Leaving “discourage search engines” or a site-wide noindex on after launch.
• Changing URLs during a redesign without redirects.
• Huge uncompressed images on the homepage.
• Dozens of near-duplicate city pages with only the name changed.
• Ignoring Search Console emails about errors.

Frequently asked questions

Sources and further reading

• Google Search Central documentation
• PageSpeed Insights
• web.dev: Core Web Vitals
• Rich Results Test