The Technical SEO Checklist Every Business Website Should Pass

Most SEO advice for businesses stops at keywords and meta descriptions. The work that decides whether any of that matters happens earlier: search engines have to be able to crawl the site, choose the right URLs to index, and render them without a struggle. That is the technical SEO checklist worth running before you spend another rupee on content.

This guide covers three layers — crawlability, indexing and page experience — with the specific checks to run and what a pass looks like.

Crawlability: can a search engine reach and read your pages?

Crawling is discovery. Before ranking is even a question, confirm that bots can fetch your HTML, that they know which URLs exist, and that they do not waste requests on dead ends or duplicate paths.

robots.txt that blocks only what it should

Open /robots.txt and read it line by line. Staging rules copied to production, a stray Disallow: / left over from a launch, or a CMS plugin that blocks asset directories can quietly remove whole sections of a site from search. Confirm the file allows CSS, JavaScript and image files — Google needs to render pages the way a browser does, and blocked assets hurt that rendering. Check that the sitemap line points to the live sitemap URL, not an old domain.

An XML sitemap that tells the truth

The sitemap should list canonical, indexable, 200-status URLs only. Pages that return 404, redirect elsewhere, or carry a noindex tag have no business in it. On larger sites, use a sitemap index that splits sections by type, keep lastmod values honest, and resubmit after significant structural changes. A sitemap is a hint rather than a guarantee, but a stale one wastes everyone's time.

Internal links and orphan pages

Crawl depth matters. Important pages — services, product categories, pricing, contact — should be reachable within a few clicks of the homepage. Crawl your own site with a tool or a simple spider and look for pages that nothing links to. Orphans usually appear after a navigation redesign, or when a landing page is published only through an ad campaign and never added to the site structure.

Status codes, redirects and canonicals

• Return a proper 404 or 410 for pages that are gone; do not soft-404 by serving a "not found" message with a 200 status.
• Keep redirect chains to a single hop. Every extra hop slows the crawl and dilutes the signal.
• Choose one hostname (with or without www) and one protocol (HTTPS), then 301 everything else to it.
• Make sure each page declares a self-referencing canonical unless it deliberately points elsewhere.

Indexing: getting the right pages in and the wrong ones out

Indexing problems are rarely dramatic. They show up as pages that exist but do not rank, and they are usually self-inflicted.

Know the difference between robots.txt and noindex

A Disallow rule stops crawling; a noindex meta tag or HTTP header stops indexing — but only if the bot can crawl the page to see it. Blocking a URL in robots.txt while relying on a noindex tag is a common contradiction: the tag is never read. Pick one mechanism per intent and document the decision.

Deal with duplicates before Google does

Faceted navigation, tracking parameters, uppercase URLs, trailing slashes and http/https variants all create near-duplicates. Use canonical tags, parameter handling in Search Console, and consistent internal linking so that one clean URL is clearly the preferred version. If you run a multi-language or multi-region site, hreflang is not optional — but it is also not a substitute for canonicals, and conflicting signals between the two cause real confusion.

Watch the Page Indexing report, not just rankings

Search Console's indexing report is the closest thing to a direct line to Google's view of your site. Review "Crawled – currently not indexed" and "Discovered – currently not indexed" regularly. These are not errors, but persistent entries usually point to thin content, duplicated templates, or internal linking that never reaches those URLs. For e-commerce and service catalogues, also confirm that important pages are not being accidentally excluded by a tag manager or a CMS setting that adds noindex to archive and filter pages.

Treat migrations as a controlled operation

Domain changes, CMS replatforms and URL restructuring are where indexing damage happens. Map every old URL to a new one, keep redirects live for at least a year, and compare the before-and-after sitemaps. If organic traffic dips after a launch, check indexing status before rewriting titles.

Page experience: speed, stability and mobile usability

Page experience is not a single score. It is the combination of how fast the main content appears, how quickly the page responds to input, and how much the layout jumps while it loads.

Core Web Vitals, plainly

• Largest Contentful Paint (LCP) — the main content should render within 2.5 seconds; above 4 seconds is poor. Common culprits are unoptimised hero images, slow server response, render-blocking CSS and late-loading fonts.
• Interaction to Next Paint (INP) — the page should respond to taps and clicks within 200 milliseconds; above 500 milliseconds is poor. Heavy JavaScript, long tasks and third-party widgets are the usual cause.
• Cumulative Layout Shift (CLS) — keep it under 0.1; above 0.25 is poor. Reserve space for images and embeds, and avoid injecting banners above existing content.

Measure with PageSpeed Insights and the Chrome UX Report for field data, then use Lighthouse while fixing. Field data reflects what users actually experience; lab data is for diagnosis.

Mobile first, because your visitors may be

Check the viewport meta tag, font sizes that do not require pinch-zoom, tap targets with enough spacing, and forms that work without sideways scrolling. If your analytics show phones dominating sessions, treat desktop as the secondary experience — particularly for enquiry forms, click-to-call buttons and checkout flows.

The unglamorous basics

• Valid HTTPS everywhere, with no mixed-content warnings.
• Compressed images in modern formats, with width and height attributes set.
• Fonts self-hosted or preloaded, with font-display: swap.
• Third-party scripts audited quarterly and removed when no longer used.
• No intrusive interstitials covering the main content on entry.

Turn the checklist into a routine

Technical SEO decays. Plugins update, teams add tags, campaigns publish one-off landing pages and nobody updates the sitemap. A quarterly audit covering crawlability, indexing and page experience — plus a quick monthly look at the indexing report and Core Web Vitals — catches most problems while they are still cheap to fix. Document what passes, so the next person does not have to rediscover it.

None of these checks require a large team. They require someone to own them, and a habit of looking before the next redesign rather than after it.