Technical SEO checklist: what to check and fix first
Work top-down: a page that can't be indexed can't rank no matter how good everything below it is.
Can search engines index your pages?
If a page is accidentally blocked, nothing else matters — it simply won't appear in search.
noindextags. A stray<meta name="robots" content="noindex">(a leftover from a staging site, or applied site-wide by mistake) hides pages entirely. Check that only the pages you want hidden carry it.robots.txtblocks. ADisallowrule can stop crawlers from ever reaching whole sections. Make sure it isn't blocking pages — or CSS/JS — you need indexed.- The pages you care about are actually submitted. Every important page should appear in your sitemap.xml so search engines can discover it.
Are you sending clear, consistent signals?
Duplicate and conflicting URLs are the most common source of "my pages just won't rank" problems.
- Canonical tags. When the same content is reachable at more than one URL (tracking parameters,
wwwvs non-www,httpvshttps), a canonical tag tells search engines which one is the real version. Getting this wrong — e.g. pointing every page at the homepage — can deindex your whole site. - Redirects. Use a permanent 301 (not a temporary 302) when a URL has truly moved, and avoid long redirect chains. After any migration or URL change, old links should land on the right new page.
- Broken links and 404s. Dead internal links waste crawl budget and frustrate visitors. Fix or redirect them.
- One version of your domain. Pick
https://and eitherwwwor the bare domain, and make every other variant redirect to it consistently.
Is the site fast and usable?
Speed and mobile experience are direct ranking factors and affect every page.
- Core Web Vitals. Loading speed (LCP), responsiveness (INP) and layout stability (CLS) are measured by Google and feed into rankings. Slow or janky pages lose ground.
- HTTPS. A valid SSL certificate is a baseline expectation; browsers flag sites without one as "not secure".
- Mobile-friendliness. Google indexes the mobile version of your site first, so it must be responsive and comfortable to use on a phone.
Can search engines understand the page?
Once a page is reachable and fast, help engines and AI make sense of it.
- Title tags and meta descriptions. Each page needs a unique, descriptive
<title>and meta description — these become your search-result snippet. - Heading structure. One clear
<h1>per page and a logical<h2>/<h3>outline help both readers and crawlers follow the content. - Structured data (schema.org / JSON-LD). Marking up articles, products, FAQs and breadcrumbs can earn rich results and helps engines understand what a page is about.
- Image alt text. Descriptive
altattributes make images accessible and eligible for image search. - Social preview tags. Open Graph tags (and a favicon) control how your links look when shared and in browser tabs — small polish that affects click-through.
- llms.txt. As AI answer engines grow, an
llms.txtfile helps them understand and cite your site.
How do I check all this?
You don't need to audit by hand. Google Search Console reports indexing and Core Web Vitals for your live site, and viewing a page's source (or DevTools) shows its canonical, title, meta and structured data in seconds. The point of this list is knowing what to look for — most sites have two or three of these quietly wrong at any time.
(On ShiftPress sites, the fundamentals here — canonical tags, a clean sitemap, fast static pages, HTTPS and consistent redirects — are generated correctly by default, so most of this checklist is handled for you.)
Frequently asked questions
What is the difference between technical SEO and regular SEO?
Regular (on-page) SEO is about the content itself — keywords, quality, relevance. Technical SEO is about everything that lets search engines access and process that content: indexing, crawlability, site speed, canonicals, redirects and structured data. Great content on a page that can't be indexed still ranks nowhere, which is why technical issues are worth ruling out first.
Which technical SEO issues should I fix first?
Start with anything that stops a page being indexed at all — accidental noindex tags, robots.txt blocks, and broken canonical tags — because those can hide pages entirely. Then fix duplicate-URL and redirect problems, then site speed. Understanding-level items (titles, structured data) come after the page is reliably reachable and fast.
How often should I check technical SEO?
Do a full pass after any big change — a migration, redesign, or URL restructure — since those are when things break. Otherwise a quick monthly look at Google Search Console for new indexing errors or Core Web Vitals regressions is enough for most sites. Technical SEO is mostly "set it up right, then watch for regressions", not constant work.
Prefer to have this handled for you?
ShiftPress moves your website off WordPress and takes care of the technical details on this page — redirects, DNS, sitemaps, speed — while you change your site simply by asking.
Migrate my site ↗