Core Web Vitals on WordPress: How to Pass in 2026
Practical fixes for LCP, INP and CLS on WordPress and Elementor sites.
Read articleIn this guide
Key takeaways
- Technical SEO makes sure Google can find, crawl, render and index your important pages.
- Google Search Console is the free tool that shows most technical problems.
- A clear site structure and internal linking help both visitors and search engines.
- Speed matters: aim to pass Core Web Vitals (LCP, INP and CLS) on mobile.
What is technical SEO?
Technical SEO is the work that helps search engines find, understand and show your website. Great content can't rank if Google can't reach it, can't render it or decides it's a duplicate of another page.
It covers four jobs, in this order:
- Crawling: Google can discover and fetch your pages.
- Rendering: Google can load the page, including content added by JavaScript.
- Indexing: Google decides the page is worth storing and showing.
- Ranking signals: speed, mobile usability, security and structured data support how the page performs.
Start with Google Search Console
Google Search Console is free and shows how Google sees your site. If you don't have it set up, do that before anything else and submit your XML sitemap.
| Report | What it tells you |
|---|---|
| Pages (indexing) | Which pages are indexed, which aren't, and why. |
| Sitemaps | Whether Google can read your sitemap and how many URLs it found. |
| Core Web Vitals | Real-user speed data for mobile and desktop, grouped by page type. |
| HTTPS | Pages that aren't served securely. |
| URL inspection | How Google crawled and rendered a single page, and its canonical choice. |
Quick win: open the Pages report and look at "Crawled – currently not indexed" and "Duplicate without user-selected canonical". These two lists often point straight at thin, duplicate or poorly linked pages.
Crawling: help Google find your pages
Google discovers pages by following links and reading your sitemap. Problems here mean important pages are found late, or not at all.
- robots.txt: check you aren't blocking important folders, CSS or JavaScript.
- XML sitemap: include only pages you want indexed, with the correct final URLs.
- Internal links: every important page should be linked from at least one other page, ideally from navigation or related content.
- Broken links: fix links that return 404 errors, and remove redirect chains.
- Crawl waste: stop endless filter, search or calendar URLs from being crawled.
Indexing: tell Google which pages matter
Not every URL on your site should be in Google. Indexing control is about showing Google the one best version of each useful page.
- Canonical tags: point duplicate or near-duplicate URLs (tracking parameters, sorting options, print versions) to the main version.
- Noindex: use it for pages with no search value, such as thank-you pages, internal search results and thin tag archives.
- One URL format: choose https, with or without "www", and with or without a trailing slash, then redirect the rest.
- Thin content: merge or improve pages that say very little, rather than leaving dozens of weak pages indexed.
Don't combine noindex and a robots.txt block on the same page. If Google can't crawl the page, it can't see the noindex tag, and the URL can stay in results.
Site structure and internal linking
A clear structure helps visitors and search engines understand what your business does and which pages matter most.
- Keep important pages within three clicks of the homepage.
- Group content into logical sections, for example services, locations and guides.
- Use descriptive link text ("technical SEO audit", not "click here").
- Add breadcrumbs, which help users and appear in search results.
- Link from blog posts to the related service pages, and back again.
Speed and Core Web Vitals
Core Web Vitals are Google's measures of real-user experience. They're a ranking signal, and more importantly, slow pages lose enquiries.
| Metric | What it measures | Good score |
|---|---|---|
| LCP (Largest Contentful Paint) | How quickly the main content appears. | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How quickly the page responds to taps and clicks. | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much the layout jumps around while loading. | 0.1 or less |
The usual fixes are compressed, correctly sized images (WebP or AVIF), less JavaScript, good hosting with caching, and reserved space for images and embeds. If you're on WordPress, our Core Web Vitals guide for WordPress walks through each fix.
Mobile, HTTPS and accessibility
Google uses the mobile version of your site for indexing and ranking. Check that your mobile pages show the same content, links and structured data as desktop.
- Text is readable without zooming, and buttons are easy to tap.
- No pop-ups cover the main content on mobile.
- Every page loads over HTTPS, with no mixed-content warnings.
- Images have descriptive alt text, and headings follow a logical order.
Structured data
Structured data (schema markup) describes your content in a format machines understand. It can make your listing eligible for rich results and helps search engines, including AI search features, connect your business to the right topics.
- Organization or LocalBusiness for your business details.
- BreadcrumbList for your page hierarchy.
- Article for blog posts and guides.
- Product and Offer for ecommerce.
Only mark up information that's visible on the page, and test it with Google's Rich Results Test.
Not sure where to start?We'll check your crawling, indexing, speed and schema by hand, for free.
Get my free audit Your technical SEO checklist
- Set up Google Search Console and submit your XML sitemap.
- Check robots.txt isn't blocking important pages or files.
- Review the Pages report and fix indexing issues for important pages.
- Choose one URL version and redirect the others.
- Add canonical tags to duplicate and parameter URLs.
- Fix broken internal links and redirect chains.
- Make sure every important page is linked internally.
- Check Core Web Vitals and fix the slowest page templates first.
- Test mobile pages for usability and missing content.
- Add and test structured data.
Common technical SEO mistakes
- Launching a new website with "discourage search engines" still switched on.
- Changing URLs without 301 redirects.
- Indexing thousands of filter, tag or search result pages.
- Huge uncompressed images on every page.
- Content that only appears after a click or a script that Google can't run.
- Ignoring Search Console warnings for months.
Technical SEO FAQs
How often should I do a technical SEO audit?
A full audit once or twice a year is enough for most small and medium websites, plus a check after any redesign, migration or large content change. Keep an eye on Search Console every month in between.
Is technical SEO a one-off job?
The initial clean-up often is, but websites keep changing. New pages, plugins, themes and content can all introduce new issues, so regular monitoring matters.
Do I need a developer to fix technical SEO issues?
Some fixes, such as sitemaps, redirects and meta tags, can be done through your CMS or an SEO plugin. Others, like speed improvements, JavaScript rendering issues and template changes, usually need a developer.
Does page speed really affect rankings?
Core Web Vitals are a ranking signal, but relevance and content quality matter more. The bigger effect of speed is on visitors: faster pages keep more people on the site and turn more of them into enquiries.
The bottom line
Technical SEO is the foundation everything else stands on. Make sure Google can crawl and index your important pages, keep your structure clear, fix speed on the templates that matter most and keep an eye on Search Console. Then your content and links can do their job.