WordPress powers many sites, and while the platform provides flexibility, common misconfigurations and plugin conflicts create recurring technical SEO issues. This step-by-step checklist covers the platform-specific checks and best practices that help WordPress sites perform well in search engines.
Start with a full site crawl and export of key data: sitemap, robots.txt, page statuses, and sitemap URLs. Verify that you have a complete backup before making changes. Backups prevent accidental data loss when changing plugins, themes, or core settings during remediation.
Check the Reading settings in WordPress and confirm that the 'Search Engine Visibility' box is not checked. Ensure permalinks are set to a clean, SEO-friendly structure (typically post name or a structure appropriate for the site). Confirm that the site has a correct preferred domain and uses HTTPS site-wide with a valid certificate.
Inventory active plugins and the theme. Evaluate SEO plugins (Yoast, Rank Math, All in One SEO) for correct configuration and avoid multiple SEO plugins running simultaneously. Check for deprecated or unsupported plugins and review theme updates. Ensure theme templates output correct canonical tags, meta titles, and meta descriptions and that they do not inject duplicate tags or conflicting structured data.
Verify the XML sitemap generated by the SEO plugin or theme includes only canonical URLs and that it is submitted to search engines. Review robots.txt to ensure no critical paths are blocked. For WooCommerce sites, ensure product and category sitemaps are correctly formed and that search engines can access images referenced in sitemaps.
Confirm canonical tags are present and accurate on post and product pages. Watch for duplicate content generated by tag and category archives; canonicalize them to the primary content where appropriate or use noindex on low-value archive pages. For e-commerce, ensure product variation pages either canonicalize to the parent product or are intentionally indexed if they are unique and valuable.
Use a reliable caching plugin and configure server-level caching where possible. Combine caching with an edge CDN to serve static assets. Minify CSS and JavaScript responsibly and test for conflicts. Lazy load images with a tested approach that preserves SEO-critical content and structured data. Measure Core Web Vitals before and after changes to quantify impact.
Validate structured data output by plugins and theme templates. Use a single source of schema generation when possible to avoid duplicate or conflicting markup. For sites with reviews or products, ensure required properties are present and accurate. Keep schema updated when plugins or templates change their output structure.
Audit the media library for large or duplicated images. Serve responsive images using srcset generated by WordPress or via a plugin that handles image transformation. Ensure alt attributes are descriptive and automated where appropriate. Offload large media to a CDN or cloud storage to reduce server load.
WordPress often creates pagination, tag, and category URLs. Confirm rel="next"/"prev" usage where it makes sense and consider noindex for tag pages that do not provide unique value. For query parameters introduced by plugins or tracking, canonicalize to the base URL and avoid exposure of session IDs or temporary parameters.
Ensure staging sites are blocked from indexing and use basic authentication or robots rules. Remove default debug plugins and ensure file permissions are correct. Update core, plugins, and themes on a predictable schedule and test updates in staging before rolling out to production to avoid SEO-impacting regressions.
Install monitoring for uptime, sitemap health, and structured data errors. Integrate search console verification and set up notifications for coverage issues and manual actions. Use a combination of scheduled crawls and plugin-based audits to detect regressions promptly.
After fixes, re-crawl critical templates and verify changes in search engine tools. Document plugin configurations, theme overrides, and any custom SEO logic for future developers and content teams. Maintain a changelog of SEO-related deployments so any unexpected search performance changes can be traced and resolved quickly.