Ansar Bhatti
Technical SEO decides whether search engines and AI crawlers can find, read and trust your pages in the first place. Strong content on a site that blocks crawlers, loads slowly or splits its authority across duplicate URLs will lose to a weaker page on a clean site. WordPress gives you a solid base, but its flexibility also makes it easy to ship technical problems without noticing. This checklist covers the areas we audit first on every WordPress project, in the order we usually fix them.
Start with crawlability
If a crawler cannot reach a page, nothing else about that page matters. Begin by confirming that the pages you want ranked are reachable and that the pages you do not want crawled are clearly marked.
- robots.txt. Open yourdomain.com/robots.txt and read it line by line. A single stray
Disallow: /left over from staging can hide an entire site. Block only what genuinely has no search value, such as internal search results or cart and checkout paths. - The Search Engine Visibility setting. In Settings, Reading, the box that discourages search engines is often ticked during development and forgotten at launch. Check it before anything else.
- XML sitemap. Your sitemap should list only canonical, indexable, 200-status URLs. Remove redirected pages, noindexed pages and thin archives. Submit the sitemap index in Google Search Console and check the processed count against what you expect.
- Orphan pages. A page with no internal links pointing to it is hard for crawlers to discover and easy for them to undervalue. Compare your sitemap against a crawl of the site and link every orphan from a relevant parent page.
Control what gets indexed
Crawling and indexing are different. A page can be crawled and still be left out of the index, and a page can be indexed even if you blocked crawling. Use the right tool for each job.
- Noindex for pages that should exist but not rank. Thank-you pages, internal search results and login screens are typical examples. Use a meta robots noindex tag rather than a robots.txt block, because a blocked page cannot show crawlers its noindex instruction.
- Canonical tags for duplicates. Parameters, tracking codes, print versions and HTTP versus HTTPS copies can all produce the same content at several URLs. Each indexable page should declare one preferred URL with a self-referencing canonical, and duplicates should point to it.
- Tag, author and date archives. On small sites these archives often add little beyond duplication. Decide deliberately whether each archive type earns a place in the index, and noindex the ones that do not.
- Attachment pages. WordPress can create a standalone page for every uploaded image. Redirect these to the parent post or to the file so they do not appear as thin pages.
Build a clear site architecture
Structure tells search engines which pages matter most. A good rule is that every important page should be reachable within three clicks of the home page, with descriptive internal links doing the pointing.
Keep URLs short, readable and stable. Set permalinks to the post name structure, avoid dates in URLs for evergreen content, and never change a live URL without a 301 redirect. Group related content into clear categories, and use breadcrumbs so both people and crawlers can see where a page sits.
Internal links carry most of the weight here. Link from high-traffic posts to the service pages that convert, and from service pages back to supporting articles. If you are planning the content side of this, our guide to keyword research and topic clusters explains how to map pages to searches so the structure grows in an orderly way.
Secure the site and clean up redirects
HTTPS is the baseline. Make sure every HTTP URL redirects to its HTTPS version in a single hop, that the www and non-www versions resolve to one preferred host, and that no pages load insecure images or scripts.
Then look at redirect chains. A chain of three or four redirects wastes crawl effort and slows users down. Update old redirects so each one goes straight to the final destination. Review 404 errors in Search Console and in your SEO plugin’s monitor, and redirect only those that have a genuinely relevant replacement. Redirecting every dead URL to the home page is treated as a soft 404 and helps no one.
Speed and Core Web Vitals
Page experience is a confirmed ranking input and a conversion factor you can feel directly. The three Core Web Vitals to watch are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. On WordPress the usual causes of poor scores are oversized images, heavy page builders, too many plugins loading scripts on every page, and slow hosting without proper caching.
This topic is large enough to need its own guide, so read our walkthrough of Core Web Vitals and WordPress speed optimization for the specific fixes. For the audit, the key point is to measure with field data from Search Console and PageSpeed Insights, not only with a one-off lab score.
Mobile usability
Google indexes the mobile version of your site first. That means content hidden on mobile, collapsed incorrectly or removed for small screens may not count at all. Test key templates on a real phone. Check that tap targets are comfortably sized, text is readable without zooming, nothing scrolls sideways and that popups do not cover the main content on arrival.
Structured data
Structured data gives search engines an unambiguous description of what a page is. Organization, WebSite, BreadcrumbList and Article markup are a sensible starting set for most business sites, with LocalBusiness added where a physical location or service area applies. Validate everything and make sure the markup matches what visitors can see. Our JSON-LD schema markup guide shows which types are worth the effort and how to avoid the common mistakes.
WordPress-specific problems worth checking
- Plugin overlap. Two SEO plugins, two caching plugins or several that each add their own scripts create conflicts and bloat. Keep one tool per job.
- Theme quality. Themes that output messy markup, skip heading hierarchy or load large libraries on every page cause technical debt that no plugin fully hides. The trade-offs are covered in our comparison of a custom WordPress theme and a page builder.
- Staging copies. A staging site that is publicly reachable and indexable can compete with your live site. Password protect it or noindex it.
- Heading structure. Each page needs one H1 that states its subject, followed by H2 and H3 headings in logical order. Many themes use headings for styling, which breaks the hierarchy.
- Image handling. Upload images at the size they are displayed, add useful alt text, and serve modern formats such as WebP or AVIF where your setup supports them.
A quick reference table
| Area | Where to check | Typical fix |
|---|---|---|
| Crawl blocks | robots.txt, Reading settings | Remove accidental disallow rules |
| Index coverage | Search Console, Pages report | Fix noindex, canonical and redirect issues |
| Duplicate URLs | Site crawl, canonical report | Add self-referencing canonicals |
| Redirect chains | Site crawl | Point each redirect to the final URL |
| Speed | PageSpeed Insights, CWV report | Optimize images, caching and scripts |
| Structured data | Rich Results Test | Correct errors and match visible content |
Monitor, do not just audit once
Technical SEO is not a one-time job. Plugin updates, new templates and content edits can reintroduce problems. Set up Search Console email alerts, review the Pages and Core Web Vitals reports monthly, and re-crawl the site after any significant change such as a redesign, a migration or a theme switch. When you plan a larger rebuild, treat the technical checklist as part of the specification so issues are prevented rather than repaired afterward.
A worked example: auditing a small business site
Imagine a local electrician with a ten-page WordPress site that has not produced an enquiry in months. A structured audit might run like this.
- Check indexation first. Open the Pages report in Search Console. If only four of the ten pages are indexed, the problem is technical or quality-related, not a lack of backlinks.
- Read the reasons. Statuses such as crawled but not indexed usually point to thin or near-duplicate pages. Duplicate without a user-selected canonical often means the HTTP and HTTPS versions, or www and non-www, are both live.
- Consolidate. Redirect the unwanted host and protocol variants to one preferred version with 301 redirects, and add self-referencing canonicals.
- Strengthen the thin pages. Expand service pages with real detail, link to them from the main navigation and from relevant posts so they stop being orphans.
- Check speed. A home page hero image of several megabytes is a classic cause of slow Largest Contentful Paint. Resize, compress and serve it in a modern format.
- Add structured data. Implement LocalBusiness markup with the correct address, phone number and opening hours, then validate it.
- Resubmit and monitor. Submit the cleaned sitemap and watch the Pages report over the following weeks.
This example is illustrative, not a promise of results, but the sequence is realistic: diagnose indexation, remove duplication, strengthen weak pages, fix speed and clarify entity data.
How to prioritise what you find
Audits often produce a long list. Rank every item by how many pages it affects and how hard it is to fix.
| Priority | Typical issue | Why |
|---|---|---|
| Fix immediately | Site-wide noindex, blocked robots.txt, broken HTTPS | Stops the whole site from being found |
| High | Duplicate URLs, redirect chains, key pages not indexed | Splits authority and wastes crawling |
| Medium | Slow templates, missing schema, weak internal linking | Limits how well good pages perform |
| Low | Missing alt text on minor images, unused archives | Worth tidying but rarely decisive |
Once the technical basics are in place, you may also want to read AI-driven visibility services in GEO and AEO and how to choose the best agency for AI visibility services.
Running an online store? Read our WooCommerce SEO guide.
Want the full picture first? Read our guide to the SEO audit: what it covers, free tools and 2026 costs.
Frequently asked questions
How often should I run a technical SEO audit?
Do a full audit at least once a year and after any major change such as a redesign, migration or theme switch. In between, review Search Console’s Pages and Core Web Vitals reports monthly.
Do I need paid tools?
Not to start. Google Search Console and PageSpeed Insights are free and cover indexing and performance well. Paid crawlers become useful on larger sites because they find patterns such as redirect chains and orphan pages quickly.
Does installing an SEO plugin fix technical SEO?
A plugin such as Rank Math handles many settings, including sitemaps, canonicals and basic schema, but it cannot fix slow hosting, poor theme code or thin content. Treat it as a tool, not a solution.
How long before fixes show results?
Indexing fixes can show within days or weeks once pages are recrawled. Speed improvements appear in field data after about a month. Ranking changes depend on competition and are never guaranteed.
Related: WordPress SEO services, Rank Math vs Yoast, what llms.txt is.
Where to go from here
If you want this checklist applied to your own site, our technical SEO and WordPress services include a full audit with a prioritized fix list. You can also read about the broader approach in our guide to building an SEO strategy for a small business, or get in touch and tell us what you are seeing.
