A Technical SEO Checklist for Non-Developers
Technical SEO is just making sure Google can find, read and trust your site. You do not need to code to get most of it right. The items that actually move the needle for a small business are crawling, indexing, speed, mobile and clean URLs, and you can check nearly all of them yourself with free tools.
Most technical audits bury a small business owner in warnings, and only a few of them actually matter for a small site. This checklist cuts that noise. Every item below is tagged DIY (you can do it) or Developer (hand it over), with a free way to check each one. Work top to bottom.
The technical SEO checklist at a glance
Google can find and index your site (DIY to check)
You have an XML sitemap submitted (DIY)
Your robots.txt is not blocking the wrong things (DIY to check, Developer to fix)
Your pages load fast enough (DIY to check)
Your site works well on a phone (DIY)
Your URLs are clean and logical (DIY for new pages, Developer for a site-wide change)
You use HTTPS (DIY to check, Developer or host to fix)
You are not splitting ranking signals with duplicate pages (Developer)
Do the first five before you touch the rest. They matter most and they are the most DIY-friendly.
Can Google find and read your site?
This is the whole foundation. If Google has not indexed a page, nothing else about it matters, because it cannot rank.
Quick answer: search Google for site:yourdomain.com. If your pages show up, Google has indexed them. If nothing shows, Google either has not found your site or is blocked from it.
DIY. The proper tool is Google Search Console, which is free. Verify your site once, then use the URL Inspection tool to check whether a specific page is indexed, and the Pages report to see what Google has and has not indexed and why. For a small site this one tool answers most technical questions.
One useful fact from Google: its crawler only reads the first 15MB of a page by default, and ignores anything past that. A normal page is nowhere near that, so this only bites bloated pages. Keep pages lean and it is a non-issue.
Submit an XML sitemap
A sitemap is a list of your pages that tells search engines which pages and files you think are important and helps them crawl your site more efficiently. Google says it does not guarantee every listed page is crawled and indexed, but most sites benefit from having one, especially a new or larger site.
DIY. Google notes that if you use a CMS such as Wix, it is likely your CMS already makes a sitemap available, usually at /sitemap.xml. Check that yours loads by visiting that address, then submit it in Google Search Console under the Sitemaps report.
Google also says a small site, about 500 pages or fewer that are well linked internally, may not strictly need one, but submitting it does no harm.
Check your robots.txt
Your robots.txt file tells crawlers where they may and may not go. The danger for a small business is an accidental block that hides your whole site from Google, which sometimes happens when a site is moved from a staging version to live.
DIY to check, Developer or host to fix. Visit yourdomain.com/robots.txt and read it. If you see Disallow: / with nothing after it, that blocks your entire site and needs fixing fast. On a builder like Wix the defaults are usually safe, so do not edit this unless you know what a line does.
Site speed and Core Web Vitals
Speed is both a ranking factor and a conversion factor. A slow page loses visitors before they read a word. Google measures speed through Core Web Vitals, three plain metrics.
Google's own thresholds, for a good experience, are:
Largest Contentful Paint (LCP): the main content should load within 2.5 seconds.
Interaction to Next Paint (INP): the page should respond to a tap or click in under 200 milliseconds.
Cumulative Layout Shift (CLS): the layout should barely move as it loads, a score under 0.1.
Check your pages free with PageSpeed Insights and the Core Web Vitals report in Search Console. The common fixes a non-developer can do: compress large images before uploading, remove apps or widgets you do not use, and avoid huge auto-playing videos at the top of a page.
Deeper fixes, such as server response time or code-level work, are a Developer job. On a hosted builder, much of this is handled for you, so focus on your images first.
Mobile-friendliness
Google indexes the mobile version of your site first, which Google calls mobile-first indexing. That is the version Google judges you on, so it has to work well on a phone.
DIY. Open your own site on your phone like a customer would. Can you read the text without zooming?
Are buttons easy to tap? Does anything run off the screen? Google recommends responsive design, where the same page adapts to the screen, as the easiest setup to maintain.
A modern template is usually mobile-friendly out of the box, so the issue is often an oversized image or a cramped section you added. Google also warns that your mobile content should match your desktop content, since it indexes from the mobile version.
Clean, logical URLs
A good URL is short, readable and describes the page: yourdomain.com/services/seo beats yourdomain.com/p?id=4821. It helps both people and search engines understand the page.
DIY for new pages, Developer for a site-wide change. For any new page, set a short lowercase slug with words, not numbers. Do not rename the URLs of pages that already rank without setting up redirects, because changing a live URL without a redirect loses its ranking. Renaming many existing URLs is a Developer job precisely because of those redirects.
HTTPS and the padlock
Every site should load over HTTPS, the secure version with the padlock in the address bar. It protects visitors and Google treats it as a basic requirement.
DIY to check, host to fix. Visit your site and look for the padlock. If you see Not secure, your SSL certificate is missing or broken. On most builders and hosts this is included and automatic; if it is broken, your hosting provider fixes it, usually quickly.
Duplicate content and canonical tags
When the same content sits on several URLs, Google wastes crawl effort and splits your ranking signals between them. This is more common on stores with filters and sorting than on a simple service site.
Developer (or your builder's settings). The fix is a canonical tag that points Google to the main version of a page. On most builders this is handled automatically.
If you run a store with many filter URLs, this is worth a developer's look. For a simple small-business site, you likely have nothing to do here.
What needs a developer and what does not
Here is the honest split for a typical small business:
You can do yourself: check indexing in Search Console, submit a sitemap, read robots.txt, run PageSpeed Insights, compress images, test on your phone, set clean slugs on new pages, check for the padlock.
Hand to a developer or your host: fixing a broken robots.txt, server-level speed work, site-wide URL changes with redirects, canonical setup on a large store, anything touching code you do not understand.
If you are on a builder like Wix, a lot of the developer list is already handled for you, which is why a small site rarely needs a big technical overhaul. Spend your time on indexing, speed and mobile first.
FAQ
What is technical SEO?
Technical SEO is the work that lets search engines find, crawl, read and trust your site: indexing, sitemaps, speed, mobile-friendliness, clean URLs and security. It is the foundation that on-page and content SEO sit on top of.
Can I do technical SEO without coding?
Mostly yes. Checking indexing, submitting a sitemap, reading robots.txt, testing speed and mobile, compressing images and setting clean URLs need no code. A handful of fixes, like server speed or site-wide redirects, are best left to a developer or your host.
How do I check if Google has indexed my site?
Search Google for site:yourdomain.com. If your pages appear, they are indexed. For detail, use the free Google Search Console, which shows exactly which pages are indexed and why others are not.
What are Core Web Vitals?
Three metrics Google uses to measure page experience: Largest Contentful Paint (load, aim under 2.5 seconds), Interaction to Next Paint (responsiveness, aim under 200 milliseconds), and Cumulative Layout Shift (visual stability, aim under 0.1).
Do I need an XML sitemap?
It helps, especially for a new or larger site, by making sure Google finds all your pages. Google says a small, well-linked site may not strictly need one. Most builders create one automatically at /sitemap.xml, so submit it once in Search Console.
How do I find technical SEO issues for free?
Use Google Search Console for indexing and Core Web Vitals, PageSpeed Insights for speed, and your own phone for mobile. These three free checks cover most of what matters for a small business.
How often should I run a technical audit?
For a small, stable site, a quick check every few months is enough, plus any time you redesign, move hosting or change your URL structure. You do not need a monthly deep audit unless your site changes often.
Related reading
Try this next
If you want me to run through your site's technical basics and tell you honestly what to fix and what to ignore, you can book a consultation.
Sources
Google Search Central: Understanding Core Web Vitals (checked October 2026)
Google for Developers: Overview of Google crawlers (checked October 2026)
Google Search Central: Learn about sitemaps (checked October 2026)
Google Search Central: Mobile-first indexing best practices (checked October 2026)
Comments