Technical SEO Checklist for WordPress (2026)

A technical SEO checklist for WordPress covers five areas: crawl and index settings, one clean XML sitemap, consistent URLs and canonicals, control of the thin archive pages WordPress creates by default, and fast, stable pages that pass Core Web Vitals. Fix them in that order, because a slow page that Google cannot index will never rank.

WordPress is good for SEO out of the box, but it also generates pages you never asked for: tag archives, author archives, date archives, attachment pages and internal search results. Add a page builder, a dozen plugins and a cheap hosting plan, and small problems compound. This checklist is the order we work through on a technical SEO audit within our SEO services, with the WordPress screen where each setting lives. It assumes a typical modern stack: WordPress with a page builder such as Elementor, a caching plugin such as LiteSpeed Cache, and an SEO plugin such as Rank Math or Yoast.

Key takeaways

Check Settings, Reading first. One ticked box (“Discourage search engines”) can keep an entire site out of Google.
Run one sitemap, not two. Your SEO plugin’s sitemap should replace the WordPress core sitemap, and only that one should be in Search Console.
Noindex the thin pages WordPress creates: tag, date and single-author archives, attachment pages and internal search results.
Every page needs one URL. Pick HTTPS, one host version and one trailing-slash pattern, then redirect everything else with a single 301.
Speed work on WordPress is mostly hosting, caching, images and plugin weight. Aim for LCP under 2.5 seconds, INP under 200 ms and CLS under 0.1.

How to prioritise a technical SEO checklist for WordPress

Not every issue matters equally. Use this table to decide what to fix first.

Priority	Area	What breaks if it is wrong	Typical fix time
1	Index settings and robots.txt	Pages missing from Google entirely	Minutes
2	Sitemaps and Search Console	Slow discovery of new pages, confusing signals	Under an hour
3	URLs, redirects and canonicals	Duplicate URLs splitting signals, lost link equity	Hours to days
4	Archive and thin-page bloat	Crawl effort wasted, weak pages competing with strong ones	Hours
5	Speed and Core Web Vitals	Poor user experience, lower conversion, weaker page experience	Days to weeks
6	Structured data	Missed rich results, unclear entity information	Hours
7	Security and maintenance	Spam injections, deindexing, downtime	Ongoing

1. Crawl and index settings

Start here, because a single setting can undo every other piece of work.

Settings, Reading, “Discourage search engines from indexing this site”. This must be unticked on a live site. It is often left on after a staging site is pushed live. The WordPress core team notes that this option also switches off the built-in sitemaps.
robots.txt. View yoursite.com/robots.txt. It should not block /wp-content/ or /wp-includes/ files your theme needs to render, and it should list your sitemap. Google’s introduction to robots.txt is clear that robots.txt manages crawling and is not a way to keep a page out of Google. To keep a page out of results, use noindex.
Per-page robots settings. In Rank Math or Yoast, open your most important pages and confirm none are set to noindex. Page builders and template imports sometimes carry these settings over.
Search Console Page indexing report. Look at “Excluded by noindex tag”, “Blocked by robots.txt” and “Crawled, currently not indexed”. Each tells you something different: a setting, a rule, or a quality problem.
Staging sites. Password-protect staging copies. A noindex alone is fragile because it often gets copied to the live site on the next push.

2. XML sitemaps

Since version 5.5, WordPress produces its own sitemap index at /wp-sitemap.xml. Most SEO plugins replace it with their own; Rank Math, for example, creates a sitemap index at /sitemap_index.xml. The goal is one source of truth.

Open both /wp-sitemap.xml and your plugin’s sitemap. If both return a sitemap, disable one (normally the core one, which most SEO plugins do automatically).
Submit only the remaining sitemap index in Search Console and Bing Webmaster Tools.
Include only canonical, indexable URLs that return a 200 status. No redirects, no noindexed pages, no 404s.
Exclude taxonomies you have noindexed. Rank Math’s sitemap documentation lets you toggle each post type and taxonomy, and recommends against including empty terms unless you are sure.
Keep lastmod honest. Google’s sitemap guidelines say lastmod should reflect the last significant update and is only used when it is consistently accurate. Priority and changefreq are ignored.
Stay within the limits of 50,000 URLs or 50 MB uncompressed per sitemap file. SEO plugins split files for you.

3. URLs, redirects and canonicals

Duplicate URLs are one of the most common technical problems on WordPress sites, usually caused by host, protocol or slash variations rather than duplicate content.

Permalinks. Settings, Permalinks should use “Post name” or a custom structure without dates for evergreen content. Changing this on a live site needs a full redirect map, so plan it carefully.
One host and protocol. http, https, www and non-www should all resolve to one version with a single 301 redirect, not a chain of two or three.
Trailing slash consistency. Choose with or without and redirect the other.
Self-referencing canonicals. Every indexable page should have a canonical tag pointing to its own absolute URL. Google’s guide to consolidating duplicate URLs treats redirects and rel canonical as strong signals and sitemap inclusion as a weak one, and warns against using noindex or robots.txt to choose a canonical.
Parameters. Comment reply links (?replytocom), tracking parameters and filter parameters on WooCommerce shops can create thousands of URLs. Canonicalise them to the clean URL.
404s and broken internal links. Crawl the site with a crawler such as Screaming Frog, fix internal links that point to 404s or redirects, and redirect deleted pages that had traffic or links to the closest relevant page.
Redesigns and migrations. Many sudden traffic drops follow a theme change or rebuild. Our guide to a website redesign without losing SEO covers the redirect map step by step.

4. Thin pages WordPress creates by default

WordPress publishes several page types automatically. Most add nothing for searchers and dilute your site’s quality signals.

Page type	Example URL	Recommended setting
Tag archives	/tag/seo-tips/	Noindex, unless each tag is a curated hub with an introduction
Category archives	/category/guides/	Index if you add a unique description and they act as topic hubs
Author archives	/author/admin/	Noindex on single-author sites; index on multi-author sites with real bios
Date archives	/2026/10/	Noindex or disable
Attachment pages	/image-name/	Redirect to the parent post or the file (Rank Math does this by default)
Internal search results	/?s=keyword	Noindex
Paginated archives	/blog/page/3/	Keep indexable and crawlable with normal links; do not canonicalise all pages to page 1

This is not theory. On a service site we took from around 170 to over 1,200 daily organic visitors in 85 days, noindexing 10+ thin category and tag pages and fixing 50+ 404 errors were among the first jobs. The full case study sets out the order of work.

5. Speed and Core Web Vitals on WordPress

Google’s Core Web Vitals are measured at the 75th percentile of real page loads, separately for mobile and desktop. According to web.dev’s Core Web Vitals overview, a page passes when Largest Contentful Paint (LCP) is 2.5 seconds or less, Interaction to Next Paint (INP) is 200 milliseconds or less, and Cumulative Layout Shift (CLS) is 0.1 or less.

On WordPress the biggest wins usually come from a short list:

Hosting and PHP. WordPress recommends PHP 8.3 or greater, MySQL 8.0 or MariaDB 10.11 or greater, and HTTPS support. Old PHP versions are slower and out of security support.
Server-level page caching. On LiteSpeed servers, LiteSpeed Cache is the natural choice. Use one caching plugin only.
Images. Serve WebP or AVIF, size images to their display dimensions, and lazy-load everything except the main above-the-fold image, which should load immediately.
Plugin weight. Audit plugins that load scripts on every page. Sliders, social feeds, chat widgets and multiple form plugins are common culprits for poor INP.
Page builder output. In Elementor, enable the performance features that load assets only where widgets are used, and avoid deeply nested containers.
Fonts. Host fonts locally, limit weights, and use font-display swap to avoid invisible text.
Layout stability. Set width and height on images and embeds, and reserve space for banners and cookie notices to keep CLS down.

Field data in Search Console’s Core Web Vitals report matters more than a single lab score. If your site needs deeper work, our website speed optimisation service focuses on exactly these fixes.

6. Mobile and rendering

Google crawls with a smartphone user agent, so the mobile version is the version that counts.

Make sure menus, tabs and accordions do not hide important text from the HTML. Content that loads only after a click may not be seen.
Use the URL Inspection tool in Search Console to view the rendered HTML and screenshot of key templates.
Do not block CSS or JavaScript files that are needed to render the page.
Check that mobile and desktop show the same main content, headings and structured data.

7. Structured data

Rank Math and Yoast output Organization or LocalBusiness, WebSite, BreadcrumbList and Article markup automatically. Your job is to make it accurate:

Fill in the business name, logo, address and social profiles once in the plugin settings.
Use the most specific type for service and product pages, and FAQ markup only where the questions and answers are visible on the page.
Remove duplicate schema from themes or other plugins. Two conflicting Organization blocks confuse more than they help.
Validate key templates with the Rich Results Test after any plugin update.

Clear structured data also helps AI tools read your business details correctly. Our AI search optimisation guide explains where schema helps with AI answers and where it does not.

8. Site architecture and internal links

Every important page should be reachable within three clicks of the home page.
Link service pages from related blog posts with descriptive anchor text, not “click here”.
Find orphan pages (indexed but not linked from anywhere) by comparing your sitemap with a crawl.
Use breadcrumbs, which most SEO plugins and themes support.
Avoid mega menus with hundreds of links on every page; they dilute internal link signals and slow pages down.

9. Security and maintenance

A hacked WordPress site can be filled with spam pages, redirected or deindexed. Basic hygiene is part of technical SEO:

Keep WordPress core, themes and plugins updated, and remove plugins you no longer use.
Use strong admin passwords and two-factor authentication.
Run daily off-site backups and test restoring them.
Watch Search Console for “Security issues” and “Manual actions”.
Check the Pages report regularly for unexpected spikes in indexed URLs, which can signal injected spam.

If this list feels like a full-time job, a WordPress development and maintenance partner can own it while you run the business.

The complete technical SEO checklist for WordPress

Use this as your audit sheet.

Check	Where in WordPress	Pass condition
Search engine visibility	Settings, Reading	“Discourage search engines” unticked
robots.txt	yoursite.com/robots.txt	No blocked theme assets; sitemap listed
Key pages indexable	SEO plugin, per page	Index, follow
One sitemap	/sitemap_index.xml or /wp-sitemap.xml	Only one live and submitted
Sitemap contents	SEO plugin, Sitemap settings	Only 200, canonical, indexable URLs
HTTPS and host	Server or .htaccess	One version; single 301 hop
Canonicals	Page source	Self-referencing, absolute URL
Permalinks	Settings, Permalinks	Post name or clean custom structure
Thin archives	SEO plugin, Titles and Meta	Tag, date, search noindexed; attachments redirected
404s and redirects	Crawl tool, Search Console	No internal links to 404s or chains
Core Web Vitals	Search Console, PageSpeed Insights	LCP 2.5 s, INP 200 ms, CLS 0.1 or better
PHP version	Hosting panel, Site Health	8.3 or newer
Structured data	Rich Results Test	Valid; no duplicate Organization blocks
Mobile rendering	URL Inspection	Main content visible in rendered HTML
Security	Search Console, security plugin	No security issues or manual actions

Frequently asked questions

What is technical SEO in WordPress?

Technical SEO in WordPress is the work that lets search engines crawl, render, index and understand your site. It covers index settings, robots.txt, XML sitemaps, canonical tags, redirects, archive pages, page speed, mobile rendering, structured data and security. It does not include writing content or building links, but neither of those works well until the technical base is sound.

Do I need Rank Math or Yoast for technical SEO?

You need one SEO plugin, not both. WordPress handles basic sitemaps and titles on its own, but an SEO plugin gives you per-page noindex controls, canonical settings, archive settings, redirects and structured data in one place. Rank Math and Yoast both do the job. Running two at once creates duplicate tags and conflicting sitemaps.

Should I noindex tag and category pages in WordPress?

Usually noindex tag pages, because they tend to be thin lists of posts with overlapping topics. Keep category pages indexable if you treat them as topic hubs with a unique introduction and a sensible number of posts. On single-author sites, noindex the author archive, and always noindex date archives and internal search results.

Why is my WordPress site not showing on Google?

The most common causes are the “Discourage search engines” setting left ticked, a noindex tag on key pages, a robots.txt rule blocking the site, or a new site that Google has not crawled yet. Check Settings, Reading first, then inspect the home page URL in Search Console to see exactly what Google found.

How often should I run a WordPress technical SEO audit?

Run a full audit once or twice a year and after any redesign, theme change, migration or major plugin change. Between audits, check the Search Console Pages and Core Web Vitals reports monthly, and crawl the site quarterly for broken links and redirect chains. Many serious problems are introduced by a change nobody checked.

If you would rather have someone run this checklist for you, we will crawl your WordPress site, check every item above and send you a prioritised fix list as part of a free SEO audit. Ongoing technical work is included in every business SEO plan, starting at Rs 9,999 per month plus GST.

Technical SEO checklist for WordPress sites in 2026