Technical SEO Health Check for Non-Developers

Technical SEO checklist for non-developers

This one-page PDF turns technical SEO into a set of yes or no checks that a business owner or marketer can complete. It has five groups of checks and a reference table:

• Crawling and indexing: Search Console verified for the whole domain, a sitemap submitted with a “Success” status, robots.txt not blocking pages you want found, and key pages confirmed as indexed.
• Structure and URLs: important pages a few clicks from the homepage, a single version of the site loading, no broken internal links and no redirect chains.
• Security: HTTPS across the whole site with a valid certificate and no mixed content warnings.
• Speed and experience: Core Web Vitals, including the thresholds for a “Good” rating, plus mobile layout and pop-ups that cover content.
• Duplicates and structured data: canonical tags, parameter URLs and any errors in the rich result reports in Search Console.
• Where to check: a table matching each check to the right report or tool.

Why technical SEO matters

Good content can't rank if search engines can't reach it, index it or work out which version of a page is the real one. Technical problems are also easy to miss: a stray noindex tag, a staging rule left in robots.txt or a broken redirect rarely shows up when you browse your own site, yet any of them can keep pages out of Google. A regular health check catches these issues early.

The mistakes we see most often

• Several versions of the same site: http and https versions, or www and non-www versions, all loading separately instead of redirecting to one.
• Redirect chains: old URLs that hop through two or three redirects before reaching the final page.
• Old URLs left broken: pages with traffic or links that now return a 404 error instead of a 301 redirect to the closest match.
• Accidental noindex tags: often left over from a staging site after a relaunch.
• Parameter clutter: filter and tracking parameters creating large numbers of near-duplicate URLs.

What to do first

Start in Google Search Console. If it isn't set up yet, verify a domain property so it covers every version of your site. Then work through these checks in order:

• Open the Pages report under Indexing and confirm your most important pages are indexed.
• Run your top pages through URL Inspection and look for “URL is on Google”.
• Check the Sitemaps report lists your XML sitemap with a “Success” status.
• Visit yoursite.com/robots.txt and make sure nothing important is blocked.
• Open the Core Web Vitals report and note any URLs not rated Good on mobile or desktop.

Indexing comes first because nothing else matters for a page Google hasn't indexed. Speed and duplicate issues can follow once you know your key pages are in.

Core Web Vitals in plain English

Google looks at three measures, and a page counts as Good when at least three in four real visits meet each threshold: how quickly the main content appears (LCP, good at 2.5 seconds or less), how quickly the page responds to a tap or click (INP, good at 200 milliseconds or less) and how much the layout shifts while loading (CLS, good at 0.1 or less). Use the Core Web Vitals report for the site-wide picture and PageSpeed Insights for a single page. For mobile layout, use Lighthouse in Chrome DevTools, since Google retired its Mobile-Friendly Test at the end of 2023.

When to bring in a developer or specialist

Pass an item on when you can see the problem but can't change the setting yourself: redirect rules, canonical tags, robots.txt, HTTPS certificates or slow server responses, for example. It's also worth getting specialist help if large numbers of pages drop out of the index, if Core Web Vitals stay poor after you've compressed your images, or before any redesign or platform move. Take the completed checklist with you: it shows exactly what you've confirmed and what still needs attention.