Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Technical SEO: A Beginner's Guide for Business Websites

Updated · 6 min read

Short answer Technical SEO is the work that lets Google reach, load and store your pages: indexing, HTTPS, phone layout, speed, redirects and sitemaps. On Wix or Squarespace the platform does most of it. An owner's part is small: run Search Console, read the Page indexing report, and never change page addresses without redirects.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

What technical SEO covers

Technical SEO is everything that decides whether Google can get to a page, open it and keep it in its index (the list of pages it can show). Writing the page is on-page SEO; links from other sites are off-page SEO.

Google's own bar for getting into results is short. A page is eligible when:

"Googlebot isn't blocked." "The page works, meaning that Google receives an HTTP 200 (success) status code." "The page has indexable content." (Google Search Central: Technical requirements)

Googlebot is Google's crawler, the program that visits pages. A 200 code is the server's way of saying "here is the page." Google adds that meeting the bar "doesn't mean that a page will be indexed; indexing isn't guaranteed" (same page).

Around that core sit the jobs most guides list:

AreaWhat it means in plain words
Crawling and indexingGoogle can find each page and nothing tells it to stay away
SitemapA file listing your pages so Google finds them faster
robots.txtA file telling crawlers which folders to skip
HTTPSThe padlock: traffic between visitor and site is encrypted
Mobile layoutThe phone version shows everything the desktop version does
Speed (Core Web Vitals)Google's three measures of loading, response and layout stability
RedirectsWhen a page address changes, the old one forwards to the new one
Canonical tagsA note saying which of two near-identical pages is the main one
Structured dataCode that labels facts like your address and hours for search engines

Which parts does my website platform already handle?

Most of them, if you're on a hosted builder. Who does what depends on how the site was built:

JobWix, Squarespace and similar buildersWordPressCustom-coded site
HTTPSPlatform, automaticYour host or developerYour developer
SitemapPlatform, automaticUsually your SEO pluginYour developer
Mobile layoutPlatform templatesYour themeYour developer
Server speedPlatformYour hostYour host or developer
Image size and add-onsYouYouYou or developer
Redirects when a page movesYou, in settingsYou, with a pluginYour developer
Search ConsoleYouYouYou

The builder rows come from the platforms' help pages. Wix: "All sites created on Wix have HTTPS automatically enabled at no additional cost" (Wix Help Center: About SSL and HTTPS). Squarespace says SSL "is automatically enabled" for domains pointing to its sites (Squarespace and SSL) and that it updates your sitemap when you add or remove content (Understanding your sitemap). Google itself says a CMS (content management system) such as WordPress, Wix or Blogger has likely "already made a sitemap available to search engines and you don't have to do anything" (Google Search Central: Learn about sitemaps).

On WordPress, one setting deserves a look after every launch: "Discourage search engines from indexing this site." When it's checked, WordPress adds a noindex tag that tells search engines to skip the whole site (WordPress.org: Settings Reading screen). Developers often turn it on while building and forget to turn it off.

What should an owner handle personally?

Four things. None needs code.

  1. Own your Search Console account. It's free, and it's where Google itself reports indexing, HTTPS and speed problems on your site. Add it under your own Google login, not only your agency's. See Google Search Console for a small business.
  2. Read the Page indexing report once a month. If a service page shows as not indexed, find out why. Crawled or discovered, currently not indexed explains the common reasons.
  3. Never change a page address without a redirect. Renaming /drain-cleaning to /services/drain-cleaning breaks the old address in Google and in every link to it. For URL changes Google says "we recommend that you use HTTP permanent redirects if possible, such as 301 and 308" (Site moves with URL changes). Builders have a redirect setting for this.
  4. Keep pages light. Upload photos at the size they're shown, not straight off the camera, and remove chat widgets, sliders and plugins you don't use. These slow phones more than anything the platform controls.

What can a small business skip?

A lot of what audit tools flag. Google says so directly:

  • Crawl budget. Google's guide on it is for sites with 1 million+ pages, 10,000+ that change daily, or many pages stuck as "Discovered - currently not indexed." Otherwise, "you don't need to read this guide" (Crawl budget management for large sites).
  • A hand-built sitemap. Google says you might not need one if your site is "about 500 pages or fewer" and well linked internally (Learn about sitemaps).
  • Duplicate content panic. "Some duplicate content on a site is normal and it's not a violation of Google's spam policies" (What is URL canonicalization). Google picks a main version on its own.
  • AMP. A special fast-page format some guides still push. Google "applies the same standard to all pages, regardless of the technology used to build the page" (About AMP on Google Search).
  • First Input Delay. If a tool or guide grades you on FID, it's out of date. Interaction to Next Paint (INP) replaced it as a Core Web Vital on March 12, 2024 (web.dev).

Does technical SEO help rankings?

It decides whether you can rank at all, then matters less than people think. A page Google can't index gets zero search traffic, so fixing a block can change everything. Past that bar, polish moves little:

"Beyond Core Web Vitals, other page experience aspects don't directly help your website rank higher in search results." (Google Search Central: Understanding page experience)

The same page says Google "always seeks to show the most relevant content, even if the page experience is sub-par." HTTPS is still worth having for trust: Google notes that HTTP sites "can be marked as 'not secure' in the Chrome browser" (Maintaining your website's SEO). For speed details, see Core Web Vitals and website speed.

When do I need a developer?

When the job touches code or the server. Google writes a separate guide for that audience, covering JavaScript, robots rules and structured data (Developer's guide to Google Search). Call one for:

  • A redesign, platform switch or new domain. Google warns: "Expect temporary fluctuation in site ranking during the move" (Site moves with URL changes). Plan redirects first; see why traffic drops after a redesign.
  • A site built as a JavaScript app, where text loads after the page opens.
  • Server errors (5xx codes) in Search Console.
  • Structured data your platform or plugin doesn't add.

Example

Illustrative cases with invented round numbers.

A Squarespace cleaning company

Twenty pages, HTTPS and sitemap automatic. The owner's whole technical job is a 10-minute Search Console check each month. An audit tool's 40 "warnings" about missing sitemap priority values cost nothing to ignore: Google says it ignores sitemap priority and change-frequency values (Build and submit a sitemap).

A WordPress law office after a redesign

Traffic falls to near zero two weeks after launch. The developer left "Discourage search engines" checked. Unchecking it is free; recovery can still take weeks while Google recrawls.

An HVAC company renaming pages (Canadian dollars)

The owner renames 12 service pages for clarity. A web person charges C$150 to map 12 old addresses to new ones with 301 redirects, so phone calls from those pages keep coming.

FAQ

Is technical SEO different from regular SEO?

It's one part. Technical SEO lets Google reach and read pages; on-page SEO makes them good answers; off-page SEO is other sites vouching for you.

Can I do technical SEO myself?

On Wix or Squarespace, mostly yes: you handle Search Console, redirects and image sizes. Custom or JavaScript-heavy sites need a developer for fixes.

How often should I check technical SEO?

Monthly in Search Console for a small site, plus right after any launch, redesign or URL change.

Do I need a paid audit tool?

Not to start. Search Console is free and shows what Google itself found; paid crawlers flag many items Google says small sites can skip.

Different for you?

Keep learning

NextTechnical SEO checklist: what to check and fix firstA technical SEO checklist in priority order: indexing blocks, hacked pages, HTTPS, mobile, errors and redirects, duplicates, speed, then site structure.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Technical requirements
  2. Google Search Central: Learn about sitemaps
  3. Google Search Central: Build and submit a sitemap
  4. Google Search Central: Understanding page experience in Google Search results
  5. Google Search Central: Maintaining your website's SEO
  6. Google Search Central: Crawl budget management for large sites
  7. Google Search Central: What is URL canonicalization
  8. Google Search Central: Site moves with URL changes
  9. Google Search Central: About AMP on Google Search
  10. Google Search Central: Developer's guide to Google Search
  11. web.dev: Interaction to Next Paint becomes a Core Web Vital on March 12
  12. Wix Help Center: About SSL and HTTPS
  13. Squarespace Help Center: Squarespace and SSL
  14. Squarespace Help Center: Understanding your sitemap
  15. WordPress.org Documentation: Settings Reading screen