Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To audit WordPress SEO, start by checking whether your important pages are accessible to Google and eligible for indexing. Then verify robots directives, sitemap URLs, canonical signals, Search Console reports, page experience, and the HTML WordPress actually serves. This checklist helps locate technical issues; it cannot guarantee indexing or ranking gains.
1. Set the audit scope and identify priority pages
Choose the pages that matter most to search visitors: for example, key service or product pages, major categories, and important articles. Record their preferred URLs and use them as a representative sample throughout the audit.
Open the site’s Search Console property and review Page indexing for patterns affecting those pages. Google notes that sites with fewer than 500 pages may not need the Page indexing report as their first diagnostic step; for a smaller site, begin with representative searches and URLs, then use reports to investigate specific problems. See Google’s Page indexing report guidance.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsConfirm that each priority page loads publicly and does not require a login or return an access error. A page must be accessible to Googlebot and eligible for indexing before it can appear in Search. Google’s technical SEO guidance explains the distinction between crawling and indexing.
#1 Best Overall
2. Check robots.txt and noindex separately
Inspect robots.txt for rules that block important pages or resources Google needs to render them. Do not block CSS or JavaScript needed to understand a page. A robots.txt rule controls crawling; it is not a dependable way to remove a URL from search results.
If a page should be excluded from Search, use an appropriate noindex directive or restrict access. Google puts it plainly: “Don’t use robots.txt as a mechanism to prevent indexing; use the noindex tag or login requirements for that.” If crawling is blocked, Google may not be able to see a page’s noindex directive.
3. Audit the sitemap
Find the sitemap your WordPress site exposes, if it has one, and open it to confirm it loads. Check that it lists the preferred URLs you want considered for indexing, not obvious noncanonical URLs or pages intentionally excluded from search. WordPress may already provide a sitemap; the important question is whether its contents match the site’s intended URL set.
Recommended Free Tools
In Search Console, use the Sitemaps report to submit or monitor the sitemap and check its processing status. Google’s sitemap documentation describes sitemaps as a discovery aid and a signal of preferred URLs—not a command that forces Google to index them.
4. Compare canonical signals on important URLs
For each sampled page, compare its canonical declaration with its redirects, internal links, and sitemap entry. These signals should point consistently toward the URL you consider preferred. Look for duplicate variants, such as URLs that differ by parameters or trailing slashes, when they represent the same content.
Google treats redirects and rel="canonical" as strong canonicalization signals, while sitemap inclusion is weaker. Google still selects the canonical it considers best, so a canonical tag is not an absolute guarantee. For details, see Google’s canonicalization documentation.
Rank #4
5. Use Search Console to investigate, not just collect warnings
Search Console is the practical place to connect a suspected issue to evidence. Google’s top tasks for Search Console users cover the reports and tools relevant to an audit.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →- Page indexing: Look for repeated patterns that affect priority pages. A reported URL is a clue to investigate, not automatically an error that requires action.
- Sitemaps: Check submission and parsing status for the sitemap you use.
- Performance: Review queries and pages to see which URLs receive search impressions and clicks.
- URL Inspection: Examine an individual URL when its indexing status is unclear. After correcting an issue, you can request a recrawl; the request does not guarantee that Google will include the page.
- Rich result reports: Review relevant reports if the site uses supported structured data.
6. Review Core Web Vitals and page experience
Check the site’s Core Web Vitals in Search Console, then inspect representative URLs to understand which pages or groups may be affected. Treat field evidence about user experience separately from a single lab score: they describe different conditions, and one score alone does not establish how visitors experience every page.
Prioritize problems that make pages difficult to use or interfere with crawling and rendering. After a fix, recheck the affected URLs or groups rather than assuming the change resolved the issue.
7. Verify what WordPress actually outputs
SEO settings may come from a plugin, theme, or custom code. WordPress.org describes plugins as one option for adding metadata, not as a requirement or proof that settings are correct. Whatever the implementation, inspect the rendered page and confirm its title, metadata, robots directives, and canonical output are coherent.
When comparing ways to manage SEO output, focus on whether the implementation produces correct metadata and canonical signals, avoids conflicts between crawling and indexing settings, offers useful diagnostics, and suits the site’s maintenance needs. The tool itself does not replace checking the page output.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →What this checklist can—and cannot—tell you
This workflow is a repeatable way to find technical crawl, indexing, sitemap, canonical, Search Console, and performance issues. It is not a site-specific diagnosis: the right interpretation depends on the site’s size, configuration, priority URLs, and actual Search Console data. It also does not establish whether content quality, backlinks, structured data implementation, security, or hosting are adequate. No checklist can promise ranking gains or compel Google to index a page.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
