Technical SEO checklist for a solo site (2026)

Most solos over-invest in one thing — content — and ignore the layer underneath it. That’s a mistake, because the layer underneath decides whether the content is ever seen. Technical SEO is the boring plumbing: crawling, indexing, speed, redirects, canonicals. None of it makes your writing better. All of it determines whether your writing gets a chance to rank at all. The good news is that, unlike content, the plumbing is mostly a fix-once job — get it right and it keeps working while you write. This is the checklist, in the order I’d run it. It pairs with the on-page SEO checklist (what’s on the page) and the wider build a services site that ranks track.

1. Crawlability & indexation — the part that silently kills pages

This is where most “my great page won’t rank” problems actually live. Before a page can rank it has to be crawled and indexed, and the two most common solo mistakes both happen here.

• The accidental noindex. A leftover <meta name="robots" content="noindex"> from a staging build, or a CMS toggle (“discourage search engines”) left on after launch, tells Google to ignore the page entirely. It is the single most damaging, easiest-to-miss fault on a young site.
• The over-broad robots.txt block. Disallow: rules are blunt — one careless line can wall off a whole section. Remember: robots.txt blocks crawling, not indexing, and noindex controls indexing. Confusing the two is how pages end up half-blocked.

Then make indexing happen: submit your sitemap in Google Search Console, use URL Inspection to request indexing for important pages, and watch the Pages report to see what’s indexed and what was excluded — and why.

2. The XML sitemap — your map for the crawler

An XML sitemap is a simple list of the URLs you want indexed. It doesn’t force indexing, but it tells search engines what exists and helps them find pages that aren’t well linked yet — which matters on a small, young site where internal links are still thin. Most decent builders and CMSs generate one automatically; your job is to submit it in Search Console and keep it clean. A good sitemap lists only canonical, indexable, 200-status pages — no redirects, no noindex pages, no 404s. If the page shouldn’t be in Google, it shouldn’t be in your sitemap.

3. Site speed & Core Web Vitals — fix it at the source

Page experience is a ranking signal, and a real conversion one. The three Core Web Vitals — loading (LCP), interactivity (INP), and visual stability (CLS) — are what Google measures, and they matter most on mobile, where most searches happen and connections are weaker. A page that’s snappy on your desktop fibre can crawl on a phone over patchy 4G.

The solo trap is treating speed as a plugin you add later. It isn’t — it’s a consequence of choices you make early:

• Fast, reliable hosting and a builder that outputs lean pages, not a heavy template stuffed with sliders and third-party scripts.
• Compressed, correctly-sized images (the single biggest payload on most pages).
• Fewer scripts. Every analytics, chat and font script is weight. Cut what you don’t need.

You measure with PageSpeed Insights and the Core Web Vitals report in Search Console — but you fix it upstream, in the stack, which is exactly why the build a services site that ranks order puts the stack before the content.

4. Mobile-friendliness & HTTPS — the non-negotiables

Two things that are simply table stakes now:

• Mobile. Google indexes the mobile version of your site, so “looks fine on desktop” is not enough. Tap targets must be reachable, text readable without zooming, nothing cut off. Test on a real phone, not just a narrowed browser window.
• HTTPS. A valid SSL certificate is a baseline ranking signal and a trust one — browsers flag plain http as “Not secure”. Any credible host gives you free auto-renewing SSL; make sure http redirects to https sitewide so you’re not running two versions of the site (see §6).

5. Clean URL structure — readable, stable, logical

Your URLs are read by humans and machines. Keep them short, lowercase, hyphen-separated and descriptive — /services/logo-design/ beats /page?id=482. Mirror your site structure so the URL tells you (and Google) where the page sits. And once a URL ranks, don’t change it casually — every change needs a redirect, and changing URLs you don’t have to is how solos lose hard-won positions. Clean, stable URLs also make your internal linking strategy far easier to keep tidy.

6. Canonicals & duplicate content — pick one version of every page

Duplicate content rarely means plagiarism — for a solo it almost always means the same page reachable at several URLs, which splits ranking signals and confuses Google about which to show. The usual culprits:

• http and https; with-www and without-www
• trailing-slash vs no-slash variants
• URLs with tracking, sorting or filter parameters (?ref=, ?sort=)

Fix it with two tools used together. 301-redirect all the variants to one chosen version (one protocol, one www-choice, one slash convention). And add a self-referencing canonical tag to every page — <link rel="canonical" href="..."> pointing to its own preferred URL — so each page declares the version you want indexed. A wrong canonical (pointing every page at the homepage, a classic mistake) can de-index your whole site, so verify them.

7. Broken links & redirects — stop leaking trust and crawl budget

Broken internal links and dead pages waste crawler effort and leak the authority your links are meant to pass. Two habits keep it clean:

• Fix or redirect 404s. When you remove or move a page, 301 it to the closest relevant live page (not blanket-redirect everything to the homepage — Google treats that as a soft 404).
• Avoid redirect chains. A → B → C wastes crawl and slows the page; point A straight at C.

Audit broken links periodically — it’s a five-minute crawl, and it protects the internal-linking authority you worked to build.

8. Structured data — the basics, as part of the build

Structured data (schema) doesn’t boost rankings directly, but it helps search engines and AI answer engines understand your pages and can win rich results and citations. The technical baseline is JSON-LD that’s valid and matches the page — Article/BlogPosting plus BreadcrumbList as a base, FAQPage where you have a Q&A. It’s enough of a topic on its own that it has its own guide — treat that as the companion to this checklist, and add schema as part of every build rather than an afterthought.

The takeaway

• Indexation first: no stray noindex, no over-broad robots.txt; confirm money pages are indexed in Search Console before blaming the content.
• Submit a clean XML sitemap — only canonical, indexable, 200 pages.
• Speed is built, not bolted on — fast hosting, lean pages, compressed images; it matters most on mobile, alongside mobile-first indexing and sitewide HTTPS.
• One version of every page: 301 the variants, self-referencing canonicals everywhere.
• Fix 404s and redirect chains, and add valid schema as part of the build.

This is the plumbing, not the show — but it’s what lets the show run. Get it right once, then go win on the part you control page by page: the on-page SEO checklist, and the traffic that follows.

Part of the complete SEO for solopreneurs guide.