Running a technical SEO audit on a WordPress website is not the same as running one on a custom-built site. WordPress has its own architecture, its own common failure points, and its own set of tools that either help or hinder your SEO depending on how they are configured. This checklist is built specifically for WordPress, covering everything from crawl settings to Core Web Vitals, in the order that makes the most practical sense to work through.
Work through these sections methodically. Some fixes take minutes. Others require developer time. The priority column tells you which to address first.
Section 1: Crawlability and Indexation
Before Google can rank your pages, it needs to be able to find and read them. Crawlability issues are the first thing to check because they can silently block everything else you are trying to achieve.
Check Your robots.txt File
Visit yourdomain.com/robots.txt and verify the file exists and is not accidentally blocking important pages. A common WordPress mistake is a robots.txt that blocks the /wp-content/ folder, which prevents Google from loading CSS and images needed to render your pages properly.
Your robots.txt should disallow: /wp-admin/, /wp-login.php, and any staging or internal paths. It should NOT disallow: /wp-content/uploads/, /wp-content/themes/, or any folder containing publicly viewable assets.
Confirm WordPress Reading Settings
Go to Settings > Reading in your WordPress dashboard. There is a checkbox that reads “Discourage search engines from indexing this site.” On a live site, this must be unchecked. It is commonly left ticked on sites that were built in a staging environment and then pushed live without a final checklist being run.
Review Your XML Sitemap
If you are using Rank Math or Yoast, your sitemap should be available at /sitemap_index.xml. Verify it loads correctly and that it includes all the pages and posts you want indexed. Common issues include:
- Sitemap returning a 404 (usually a WordPress rewrite rules issue, fixed by re-saving permalinks under Settings > Permalinks)
- Sitemap including noindex pages (these should be excluded)
- Pages missing from the sitemap because their SEO plugin has set them to noindex accidentally
- Last modification dates being wrong or missing
Submit your sitemap in Google Search Console under Sitemaps. Verify it shows a “Success” status and that the number of submitted URLs matches your expectations.
Check Crawl Budget and Pagination
For larger WordPress sites, crawl budget matters. Tag archives, category pages, and pagination (page/2/, page/3/) can eat crawl budget without contributing to rankings. Configure Rank Math or Yoast to noindex tag archives if they contain no unique value, and set canonical tags on paginated pages to point to the root category or archive URL.
Section 2: Indexation and Canonical Tags
Audit Noindex Settings
In your SEO plugin settings, check which post types, taxonomies, and archive types are set to noindex. The correct defaults for most WordPress sites are:
- Posts: index
- Pages: index
- Categories: index (if they have sufficient unique content)
- Tags: noindex (usually low-value)
- Author archives: noindex (unless the site has multiple prominent authors)
- Date archives: noindex
- Search results (?s=): noindex
- 404 pages: noindex (handled automatically)
Use Google Search Console’s Coverage report to check whether any pages you want indexed are being blocked or excluded unintentionally.
Review Canonical Tags
Every page on your WordPress site should have exactly one canonical tag pointing to its preferred URL. Common canonical issues on WordPress sites include:
- Pages accessible via both HTTP and HTTPS without a redirect, creating duplicate canonicals
- Pages accessible with and without trailing slashes (yourdomain.com/page/ vs yourdomain.com/page), causing canonical conflicts
- WooCommerce product pages with filter URLs creating thousands of parameter variants, none of which have correct canonicals
- Elementor or page builder preview URLs being indexed
Set your preferred URL format in Rank Math under General Settings and ensure it is enforced by your hosting configuration and redirects.
Handle Query Parameter URLs
WordPress sites often accumulate URLs with query parameters from tracking scripts, AJAX calls, or third-party plugins. These create duplicate content issues. Configure your SEO plugin to output the correct canonical (ignoring parameters) on all query-parameter variant URLs, and add rules in Google Search Console’s URL Parameters tool if you have significant crawl budget waste.
Section 3: On-Page Technical Factors
Audit Title Tags and Meta Descriptions
Every published page and post should have a unique title tag and meta description set explicitly in Rank Math or Yoast. Do not rely on default templates for your most important pages. Check for:
- Title tags over 60 characters (will be truncated in search results)
- Meta descriptions over 160 characters (will be truncated)
- Duplicate title tags across multiple pages
- Missing meta descriptions on key service pages or blog posts
- Title tags that do not contain the primary keyword
Use Rank Math’s Content AI or an external crawler to flag pages with missing or duplicate title tags quickly.
Check Heading Structure
Each page should have exactly one H1 tag, and it should contain the primary keyword. H2 and H3 tags should follow a logical hierarchy without skipping levels. Common WordPress and Elementor errors include:
- The site logo or header widget being wrapped in an H1 tag sitewide (a common theme error)
- Multiple H1 tags on a page because a plugin adds its own heading
- Heading tags being used for styling rather than structure
- Blog post titles not rendering as H1 in certain page builder setups
Audit Image Alt Text
Every image on the site should have descriptive alt text that tells Google what the image shows. Empty alt attributes on meaningful images are a missed opportunity. Decorative images should have empty alt attributes (alt=””) rather than no attribute at all. Check that images uploaded via the WordPress media library have their Alt Text field filled in, not just their title or caption.
Section 4: Core Web Vitals and Page Speed
Core Web Vitals are Google ranking signals. A WordPress site with poor LCP, INP, or CLS scores will underperform in rankings relative to competitors with faster pages, even if the content is better. Use Google PageSpeed Insights and Search Console’s Core Web Vitals report to identify which pages are failing and why.
Largest Contentful Paint (LCP)
LCP measures how long the main content element takes to load. On WordPress sites, the most common causes of poor LCP are:
- Large uncompressed hero images (fix: convert to WebP, compress, set explicit width and height, add fetchpriority=”high”)
- Images loading as base64 encoded data URIs instead of external files (fix: use proper media library uploads)
- Render-blocking JavaScript or CSS delaying the critical path (fix: defer non-critical JS, use LiteSpeed or WP Rocket to manage resource loading)
- Slow hosting server response times (fix: server-side caching, CDN, or hosting upgrade)
Interaction to Next Paint (INP)
INP replaced FID in 2024 and measures responsiveness across all interactions, not just the first one. High INP scores on WordPress are usually caused by heavy JavaScript from plugins running on the main thread. Audit your active plugins and disable any that are not contributing meaningful value on the front end. Third-party chat widgets, pop-up builders, and analytics scripts are common culprits.
Cumulative Layout Shift (CLS)
CLS measures visual instability, elements that jump around as the page loads. Common WordPress CLS causes include images without explicit dimensions, web fonts loading late and causing text to reflow, and ads or embeds that expand after load. Set explicit width and height on all images and use font-display: swap in your theme or via a plugin.
Section 5: Mobile Optimisation
Google indexes the mobile version of your site first. A page that looks correct on desktop but has issues on mobile will underperform in rankings regardless of how well the desktop version is optimised.
Run Google’s Mobile-Friendly Test
Use the Mobile-Friendly Test tool at search.google.com to check your most important pages. Common failures on WordPress sites include text that is too small to read, clickable elements too close together, and content wider than the screen.
Check Elementor and Page Builder Responsiveness
Elementor pages need to be checked at multiple breakpoints. Open the Elementor editor, switch to responsive preview mode, and check each critical page at mobile, tablet, and desktop widths. Common issues include columns stacking incorrectly, hero images displaying at the wrong size, and navigation menus not collapsing properly on small screens.
Verify Touch Target Sizes
Buttons and links should be at least 44×44 pixels to be easily tappable on mobile. Scan your pages with PageSpeed Insights and fix any flagged touch target size issues, particularly on forms and CTAs where a missed tap directly costs you a conversion.
Section 6: Structured Data and Schema Markup
Structured data helps Google understand what your pages are about and can trigger rich results in search, including review stars, FAQ dropdowns, and breadcrumbs. For most WordPress businesses, the minimum schema implementation should include:
- Organization schema on the homepage with your business name, logo, contact details, and social profiles
- LocalBusiness schema if you serve a specific geographic area
- Service schema on each service page
- FAQPage schema on any page with a FAQ section
- BreadcrumbList schema across all pages (Rank Math handles this automatically)
- Article schema on all blog posts
Rank Math handles most of this through its Schema settings. Verify each schema type is active and correctly populated using Google’s Rich Results Test at search.google.com/test/rich-results.
Section 7: Internal Linking and Site Architecture
Good internal linking helps Google discover and understand the relationship between your pages. It also distributes PageRank through your site, which affects how different pages rank relative to each other.
Check for Orphan Pages
An orphan page has no internal links pointing to it. Google may not discover it via crawl, and even if it does, the page will have very low internal authority. Use Rank Math’s Link Report or an external tool like Screaming Frog to identify pages with zero inbound internal links.
Audit Broken Internal Links
Broken internal links waste crawl budget and deliver a poor user experience. Run a crawl of your site and check for any 404 responses triggered by internal links. For each 404, either update the link to the correct URL or create a 301 redirect from the broken URL to the relevant page.
Review Link Depth
Important pages should be reachable within three clicks from the homepage. If a key service page requires four or five clicks to reach, its crawl priority and internal authority are both lower than they should be. Add direct navigation links, include the page in a related posts or services widget, or add contextual internal links from high-traffic blog posts.
Section 8: Security and Technical Housekeeping
Confirm HTTPS Is Enforced
All pages must load over HTTPS, and HTTP requests must redirect to HTTPS automatically. Check that your SSL certificate is valid and not close to expiry. Verify there are no mixed content warnings (HTTPS pages loading HTTP resources) by checking the browser console on your key pages.
Review Redirect Chains
A redirect chain occurs when a URL redirects to a URL that itself redirects. Chains waste crawl budget and dilute link equity. Audit your redirects and ensure each one goes directly from the old URL to the final destination URL without intermediate hops.
Check for Soft 404s
A soft 404 is a page that returns a 200 OK status code but shows content that effectively says nothing was found. Search results and “no products found” pages are common examples on WooCommerce sites. Google Search Console’s Coverage report flags these. Fix them by returning a proper 404 status code or by populating the page with relevant content.
Prioritising What to Fix First
A thorough technical audit will almost always surface more issues than can be fixed in one sprint. Prioritise in this order:
Fix first: anything blocking Google from indexing your key pages (robots.txt errors, noindex on important pages, sitemap 404s). These directly prevent rankings.
Fix second: Core Web Vitals failures on your highest-traffic and highest-value pages. These are ranking signals and directly affect CTR through user experience.
Fix third: canonical and duplicate content issues. These dilute the authority of your best pages and confuse Google about which version to rank.
Fix fourth: structured data gaps and internal linking improvements. These are important for topical authority and rich results but are not blocking your current rankings.
Fix fifth: everything else, in order of expected impact versus effort required.
Running Regular Technical Audits
A technical SEO audit is not a one-time event. WordPress sites change constantly as content is published, plugins are updated, and themes are modified. New issues can be introduced with any update. Running a lightweight technical check monthly and a full audit quarterly keeps problems from accumulating undetected.
Google Search Console provides a continuous view of crawl errors, indexing issues, and Core Web Vitals performance. Monitor it weekly as a minimum. Any spike in crawl errors or drop in indexed pages should trigger an immediate investigation.
If you want a thorough technical SEO audit carried out on your WordPress site by practitioners who do this for client sites every week, or if you want ongoing technical SEO management so you never have to run this checklist yourself again, get in touch with the Beetle Dynamics team. We run technical audits across WordPress, WooCommerce, and Elementor setups across India, the UAE, and global markets, and we fix what we find rather than just reporting it.
You can also explore our full range of SEO services to see how technical SEO fits into a complete organic growth strategy.
