Technical SEO Checklist for 2026: 25 Checks That Actually Move Rankings

Key takeaways

• Rankings start with access: if Google cannot crawl, render and index a page, nothing else matters.
• Fix redirect chains, broken internal links and accidental noindex tags before investing in new content.
• Core Web Vitals, clean structured data and strong internal linking support every page you publish.
• Helpful, experience-led content remains the deciding factor once the technical foundation is sound.

Most websites do not have a content problem first. They have an access problem. Pages are blocked, duplicated, slow, buried five clicks deep or redirected three times before anyone sees them. This checklist covers the technical work that decides whether your content is even eligible to rank, in the order we use when auditing client sites.

You do not need to be a developer to use it. Each check explains what to look for and why it matters, so marketers, founders and engineers can agree on priorities.

1. Crawling and access

Check robots.txt is not blocking important pages

Open yourdomain.com/robots.txt. Look for Disallow rules that cover folders containing pages you want to rank, or JavaScript and CSS files that Google needs to render the page. A single leftover Disallow: / from a staging site can remove an entire website from search.

Confirm Googlebot can render the page

If your site relies on client-side JavaScript to show its main content, Google has to render it before it can read it. Use the URL Inspection tool in Google Search Console and compare the rendered HTML with what users see. Server-side rendering or static generation removes this risk entirely, which is why we build marketing sites that ship complete HTML.

Make sure important pages are linked, not just listed

Search engines discover most pages by following links. Pages that only appear in a sitemap, with no internal links pointing to them, are called orphan pages. They are crawled less often and usually rank poorly. Every page you care about should be reachable from navigation, a hub page or contextual links in related content.

2. Indexing signals

Find accidental noindex tags

A noindex robots meta tag or X-Robots-Tag header tells Google to drop the page from results. These are often left behind after development or added by plugins. Crawl the site with a tool such as Screaming Frog or Sitebulb and filter for noindex pages. Only utility pages such as thank-you pages, internal search results and error pages should carry it.

Use one canonical URL per page

The same content is frequently available at several addresses: with and without www, with and without a trailing slash, over HTTP and HTTPS, or with tracking parameters. Every page should declare a self-referencing canonical tag that matches the exact URL you want indexed, and every alternative should redirect to it.

Keep the XML sitemap clean

Your sitemap should list only canonical, indexable pages that return a 200 status code. Remove redirected, noindexed and broken URLs. Include an accurate lastmod date when content changes, submit the sitemap in Google Search Console and Bing Webmaster Tools, and reference it in robots.txt.

Check the Page indexing report

In Search Console, the Page indexing report shows which URLs are indexed and why others are not. “Crawled, currently not indexed” on important pages usually signals thin or duplicated content. “Discovered, currently not indexed” often points to weak internal linking or crawl budget issues on larger sites.

3. Redirects and status codes

Remove redirect chains

A redirect chain is when URL A redirects to B, which redirects to C. Each hop slows users down and wastes crawl resources. Update redirects so every old URL points directly to its final destination in one step, and update internal links so they never point to redirected URLs at all.

Use 301 redirects for permanent moves

Permanent changes such as a new URL structure, a merged page or a domain move should use 301 (or 308) redirects. Temporary 302 and 307 redirects tell search engines the original URL will return, which can delay consolidation of ranking signals.

Fix broken links and useful 404s

Internal links to pages that return 404 waste link equity and frustrate users. Fix or remove them. When an old page had backlinks or traffic, redirect it to the most relevant live page rather than letting it 404. Pages that are genuinely gone should return a real 404 or 410 status with a helpful error page, never a “soft 404” that returns 200.

Force HTTPS and one hostname

All HTTP requests should redirect to HTTPS, and either the www or the root domain should be the only version that resolves. Test the four combinations (http, https, with and without www) and confirm each lands on the canonical version in a single hop.

4. Page experience and Core Web Vitals

Core Web Vitals are Google’s field measurements of user experience: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness and Cumulative Layout Shift (CLS) for visual stability. Check them in the Core Web Vitals report in Search Console and in PageSpeed Insights, which uses real Chrome user data where it is available.

Serve modern image formats at the right size

Oversized images are the most common cause of slow LCP. Convert photographs to WebP or AVIF, serve different sizes to different screens with srcset, compress them properly and lazy-load anything below the fold. On one site we audited recently, converting hero images from PNG to WebP reduced individual files from around 1.7 MB to under 70 KB with no visible loss of quality.

Prioritise the main image and fonts

Do not lazy-load the hero image. Give it fetchpriority="high" and preload the critical web font in WOFF2 format. Use font-display: swap so text appears immediately.

Prevent layout shift

Set explicit width and height attributes, or a CSS aspect-ratio, on every image, video and embed so the browser reserves space before it loads. Avoid injecting banners above existing content after the page has rendered.

Keep JavaScript lean

Heavy scripts block interaction and hurt INP. Audit third-party tags, remove unused ones, defer non-critical scripts and avoid loading chat widgets, heatmaps and embeds on pages that do not need them. A realistic target for marketing pages is a fully usable page in under two seconds on a mid-range phone.

5. On-page structure

Write a unique title tag and meta description for every page

Titles should lead with the main topic of the page, stay roughly under 60 characters so they are not truncated, and end with your brand. Meta descriptions do not directly affect rankings, but a specific, benefit-led description of about 140 to 160 characters improves click-through. Avoid duplicating either across pages.

Use one clear H1 and a logical heading structure

Each page should have a single H1 describing its main topic, followed by H2 and H3 headings that outline the content. Headings should help a reader skim the page, not be stuffed with keyword variants.

Add descriptive alt text

Alt text describes images for screen readers and helps search engines understand image content. Describe what the image shows in context. Decorative images should have empty alt attributes so assistive technology skips them.

Add breadcrumbs

Visible breadcrumbs help users understand where they are, create useful internal links up the hierarchy and, with BreadcrumbList structured data, can replace the raw URL in search results.

6. Structured data

Mark up what is genuinely on the page

Use JSON-LD structured data for Organization, WebSite, BreadcrumbList, Article or BlogPosting, Service, Product and other relevant types. Only describe content that users can see. Validate everything with Google’s Rich Results Test and the Schema Markup Validator, and watch the enhancement reports in Search Console for errors.

Keep expectations realistic

Structured data helps search engines and AI systems understand entities and relationships, but it does not guarantee rich results. FAQ rich results, for example, are now shown mainly for authoritative government and health websites, and review snippets have strict eligibility rules. Never add markup for reviews, ratings or data you cannot verify.

7. Content quality signals

Technical work makes pages eligible to rank. Content decides whether they deserve to. Google’s guidance on helpful, reliable, people-first content and its spam policies on scaled content abuse both point in the same direction: pages created mainly to attract search traffic, especially templated or mass-produced pages with little original value, are treated as low quality regardless of how they were written.

Practical checks:

• Show real experience. Include examples, data, screenshots and decisions from actual work.
• Name the author. Add an author byline and a short bio that explains why they are qualified to write about the topic.
• Avoid near-duplicate pages. City pages or service pages that only swap a keyword compete with each other and dilute quality signals. Merge them or make each genuinely distinct.
• Update instead of republishing. Refresh existing articles with new information and update the modified date honestly.

8. AI search readiness

Search is no longer only ten blue links. Google’s AI Overviews and AI Mode, and assistants such as ChatGPT search, Perplexity and Claude, increasingly summarise answers and cite sources. The fundamentals are the same: crawlable HTML, clear structure, specific answers and trustworthy sources.

• Allow the crawlers you want to be cited by in robots.txt, such as OAI-SearchBot, PerplexityBot and ClaudeBot, and decide deliberately on training crawlers.
• Answer common questions directly near the top of a section, then expand with detail.
• Use consistent entity information (company name, services, locations) across your website and profiles.

9. Monitoring after launch

A technical SEO audit is a snapshot. Keep the improvements by monitoring:

1. Search Console weekly: indexing changes, Core Web Vitals, manual actions and security issues.
2. Monthly crawls: new broken links, redirect chains, missing titles and accidental noindex tags.
3. Before every release: confirm robots.txt, canonical tags and redirects on staging and production.
4. After migrations: compare indexed pages, organic landing pages and rankings for the following weeks.

Where to start

If you only have a day, check three things: that robots.txt and noindex tags are not blocking important pages, that every old URL redirects to its final destination in one hop, and that your main templates pass Core Web Vitals on mobile. Those fixes protect everything else you invest in.

Devscale Tech runs technical SEO audits and implements the fixes, because recommendations only help once they are live. If you want a prioritised view of what is holding your site back, explore our SEO services or talk to our team.

Frequently asked questions

What is technical SEO?+

Technical SEO is the work that helps search engines crawl, render, understand and index a website efficiently. It covers site architecture, robots.txt, XML sitemaps, canonical tags, redirects, page speed, Core Web Vitals, mobile usability, structured data and internal linking.

How often should I run a technical SEO audit?+

Run a full audit at least twice a year and before and after any redesign, migration or platform change. Monitor Google Search Console weekly for indexing errors, Core Web Vitals regressions and manual actions so problems are caught early.

Does page speed affect Google rankings?+

Yes, as part of Google's page experience signals, but it is not a substitute for relevance. Faster pages mainly help by improving user behaviour and conversion. Treat speed as a requirement for competing, not a shortcut to the top.

Is FAQ schema still worth adding?+

Google now shows FAQ rich results mainly for well-known authoritative government and health sites, so most businesses will not see the expanded snippet. Valid FAQ markup on genuinely visible questions is still harmless and helps machines understand the page, but it should not be a priority over content quality.