Technical SEO Checklist 2026: 25 Points to Check on WordPress
From HTTPS to hreflang, Core Web Vitals to structured data — a complete reference that freelancers and agencies can use directly with their clients.
- Technical SEO is the invisible foundation of search rankings: without it, even the best content stays hidden. These 25 points cover 95% of the issues found on WordPress sites.
- The Performance and Mobile sections have become top priorities since Core Web Vitals became an official Google ranking signal in 2021.
- Orilyt automatically checks the majority of these 25 points in a single audit — a significant time saver for freelancers managing multiple clients.
Technical SEO isn't glamorous. While blog posts accumulate likes, it's the misconfigured robots.txt, the forgotten XML sitemap or a redirect chain that prevents Google from properly indexing your site. And clients only realize this when their traffic drops.
In 2026, the technical fundamentals of SEO matter more than ever. Google has strengthened its requirements around mobile performance, Core Web Vitals have become established ranking signals, and mobile-first indexing is fully deployed. A technically well-configured WordPress site has a structural advantage over its competitors.
This 25-point checklist is organized into 5 logical sections. It's designed to be used as-is during a client audit, as a discussion framework, or as a quarterly tracking grid. For each point, you'll find what's checked and why it matters.
1. Technical Fundamentals
These are the prerequisites. Without them, everything else is fragile. These 5 points must be green before working on anything else.
HTTPS has been a trust signal for Google since 2014. In 2026, a site without HTTPS is penalized and Chrome displays a security warning. Verify that the certificate is valid, not expired, and that all resources (images, scripts, CSS) are loaded over HTTPS — not mixed HTTP.
The XML sitemap is the map you give Google to explore your site. It must list all important pages, be accessible at the standard URL (/sitemap.xml or /sitemap_index.xml), and be submitted in Google Search Console. On WordPress, Yoast SEO and Rank Math generate sitemaps automatically.
The robots.txt file tells search engines what they can or cannot crawl. A misconfiguration can block indexing of the entire site (classic mistake: "Disallow: /" left in production). Verify it's accessible, doesn't block important CSS/JS resources, and points to the sitemap.
URLs should be readable, short and free of technical parameters. On WordPress, set permalinks to "Post name" (/my-post/) rather than /?p=123. Avoid uppercase letters, unencoded special characters, and double slashes. Consistency is key: /blog/my-post/ or /my-post/ — pick one format and stick with it.
The canonical tag tells Google which is the "official" version of a page when duplicate content exists. It's essential on e-commerce sites (filters, pagination) and blogs (categories, tags, archives). On WordPress, SEO plugins handle this automatically — but verify they don't generate incorrect canonicals (e.g. a category page canonical pointing to itself with parameters).
2. Content & Markup
Semantic markup helps Google understand the structure and topic of your pages. These 5 points directly impact how your pages appear in search results.
The meta title is the most important on-page factor. It must be unique per page (never duplicated), contain the primary keyword, and be 50-60 characters long. Google truncates titles that are too long in SERPs. On WordPress, each post and page needs its own SEO title — not just the article title.
The meta description isn't a direct ranking factor, but it influences click-through rate (CTR) in SERPs. It should summarize the content in 150-160 characters, include an implicit call to action, and be unique. On WordPress, pages without a meta description will have one generated by Google automatically — often unengaging.
Every page should have exactly one H1 (the main title) and a logical hierarchy H2 > H3 > H4. Don't skip levels (H1 → H3). On WordPress, the article title is automatically the H1 — don't repeat it in the content. A clear heading structure helps Google understand content organization and improves accessibility.
The alt attribute describes the image to search engines and screen readers. It should be descriptive and relevant (not just "image" or the filename). On WordPress, add alt text when uploading to the media library. Decorative images can have an empty alt (alt="") to signal to screen readers that they carry no information.
Structured data enables Google to display rich snippets in SERPs: review stars, prices, events, FAQ, recipes... On WordPress, Yoast SEO and Rank Math automatically add Article, WebPage and BreadcrumbList schemas. For e-commerce or review sites, add Product and Review schemas. Test with Google's Rich Results Test.
3. Performance
Since 2021, Core Web Vitals are an official ranking signal. Performance is no longer optional — it's a SEO requirement. These 5 points cover the most frequent issues.
Google measures LCP (largest element loading, target < 2.5s), INP (interaction responsiveness, target < 200ms) and CLS (visual stability, target < 0.1). This data comes from real users via Chrome UX Report. Check them in Google Search Console > Page Experience, or in PageSpeed Insights.
TTFB measures server response time before a single byte of data is received. A TTFB above 800 ms signals a server-side issue: overloaded shared hosting, no PHP cache (OPcache), slow database queries, or no CDN. No front-end optimization will compensate for a high TTFB.
Compression reduces the size of text files (HTML, CSS, JavaScript) by 60 to 80% before sending them to the browser. Brotli is more efficient than Gzip but requires a compatible server. Check with a tool like GTmetrix or the "Content-Encoding" header in DevTools. On WordPress, most caching plugins enable compression automatically.
Cache headers tell the browser how long to store static resources (images, CSS, JS, fonts). Without caching, every visit re-downloads everything. A well-configured cache dramatically improves performance for returning visitors. On WordPress, W3 Total Cache, WP Rocket or .htaccess rules handle this.
Total page weight directly impacts load time, especially on mobile. Goal: stay under 2 MB. Main levers: convert images to WebP, enable lazy loading, minify CSS and JavaScript, remove unused WordPress plugins (each adds JS/CSS), and use a CDN for static assets.
4. Mobile & UX
Mobile-first indexing has been the standard since 2023. Google indexes and ranks sites based on their mobile version. Mobile UX is no longer a bonus — it's the primary criterion.
The site must adapt correctly to all screen sizes without horizontal scrolling. On WordPress, modern themes are responsive by default — but CSS customizations and page builders (Elementor, Divi) can introduce issues. Test with Google's Mobile-Friendly tool or Chrome DevTools in emulation mode.
The <meta name="viewport" content="width=device-width, initial-scale=1"> tag must be present in the <head> of all pages. Without it, mobile devices display a scaled-down desktop version. On WordPress, all well-coded themes include it — but check if you're using legacy themes or custom landing pages.
Text that is too small forces mobile users to zoom, degrading the experience and the UX signal sent to Google. The recommended minimum is 16px for body text. Captions and secondary text can be at 14px, but no smaller. Also check that text/background contrast meets WCAG criteria (minimum ratio of 4.5:1).
Google recommends touch targets of at least 48x48 pixels with 8px spacing between them. Buttons that are too small or too close together cause accidental taps and degrade INP. On WordPress, check mobile menus, CTA buttons and in-text links — they are often too small on legacy themes.
Google penalizes popups and interstitials that cover main content on mobile, especially on page load. Acceptable cases: GDPR consent popups, age verification, banners taking up less than 20% of the screen. Newsletter subscription popups that appear immediately on load are in the risk zone.
5. Indexing & Crawl
Google must be able to crawl and index your site efficiently. These 5 points ensure your content is visible and correctly understood by search engines.
Google Search Console is the essential tool for monitoring a site's SEO health. It must be configured with a verified property, the sitemap submitted, and no critical errors (excluded pages, coverage issues, red Core Web Vitals). Check the "Coverage" tab regularly — 404 errors and incorrect redirects appear there.
An orphan page is one that's not referenced by any internal link. Google struggles to discover it and often rates it as low-importance. Check with a crawler (Screaming Frog, Sitebulb) that all your important pages are reachable from at least one internal link. On WordPress, published posts without a category or without a menu link are the main orphans.
Internal linking distributes authority (PageRank) across pages and helps Google understand the site's topical structure. Every important page should receive links from other relevant pages. Use descriptive anchor text (not "click here"). On WordPress, related posts, sidebar widgets and natural in-content links form the base of internal linking.
A redirect chain occurs when A redirects to B which redirects to C. Each additional hop dilutes authority and slows crawling. On WordPress, redirects accumulate often after migrations or permalink changes. With a plugin like Redirection, verify that all redirects point directly to the final destination.
On a multilingual site, hreflang tags tell Google which version of the page serves which language and region. Without them, Google may display the wrong version to users. On WordPress, WPML and Polylang handle hreflang automatically. Watch for common mistakes: missing hreflang on the return page, x-default not set, incorrect URLs.
How Orilyt automates this checklist
Of the 25 points in this checklist, Orilyt automatically verifies 18 in its 57-test audit. What normally takes a full day of manual work runs in a few minutes.
One point at a time
Technical SEO can feel overwhelming with 25 points to check. But in practice, most WordPress sites have 5 to 8 recurring issues that account for 80% of their SEO gaps: misconfigured HTTPS, missing or unsubmitted sitemap, TTFB too high, images without alt, and no internal linking.
The recommended approach: start with technical fundamentals (section 1), which are prerequisites for everything else. Then performance (section 3), since Core Web Vitals directly impact rankings. Then mobile (section 4), since mobile-first indexing is the reality.
This checklist is designed to be used regularly — ideally once per quarter. Technical SEO isn't a one-time job: WordPress updates, new plugins and theme changes can reintroduce previously fixed issues.