WordPress SEO Problems and Fixes: Feeds, Comment URLs, Staging, Page Builders and More

WordPress is a solid platform for SEO, but its defaults create feeds, archives, attachment pages and parameter URLs, and plugins and builders add their own. Most issues are easy to fix once you know where they come from.

For a full setup list, use the WordPress SEO checklist. This guide is for troubleshooting.

Staging sites and the “Discourage search engines” setting

• WordPress’s Reading setting “Discourage search engines from indexing this site” adds a noindex directive. It’s useful on staging, disastrous if copied to production.
• Protect staging with a password or IP restriction; Google can’t index what it can’t fetch.
• After every launch or migration, check the setting is off and robots.txt isn’t blocking the site.
• If staging got indexed, password-protect it and use Search Console’s Removals tool for a fast temporary removal (removing URLs).

Feeds, comment URLs and the REST API

URL type	What to do
/feed/ URLs	Feeds help discovery; Google rarely shows them in results. If they show in reports, an SEO plugin can noindex them via header; don’t block them in robots.txt if you rely on them.
?replytocom= comment links	Created by threaded comment reply links. Most SEO plugins remove them or canonicalize to the post.
/wp-json/ REST API	JSON responses rarely appear in results. Don’t block the API outright; the block editor and many plugins depend on it. Restrict sensitive endpoints with security settings instead.

Archives, attachments and media

• Single-author sites: noindex or disable the author archive, which duplicates the blog.
• Date archives rarely help; noindex or disable them.
• Redirect attachment pages to the file or parent post.
• Clean the media library: remove unused images, fix file names and alt text on images you use.
• Limit generated image sizes to those your theme uses to save storage and processing.

Shop and search pages in WooCommerce

• The shop page is often a weak duplicate of category pages; give it real intro content or link prominently to categories.
• Noindex internal search results (?s=) and keep them out of sitemaps.
• Cart, checkout and account pages should be noindexed and excluded from sitemaps.

Plugins, page builders and themes

• The number of plugins matters less than what each one loads on the front end. Audit plugins that add scripts or styles sitewide.
• Page builders like Elementor add markup and CSS; use their performance options, limit widgets and test Core Web Vitals.
• Block themes and the block editor generally output leaner markup; migrating from a builder means rebuilding templates, so treat it like a redesign: keep URLs, titles, headings, internal links and structured data.
• Kadence: use its performance options (such as loading Google Fonts locally) and decide whether the theme’s built-in schema or your SEO plugin’s should output structured data, not both.
• Multisite networks need SEO settings, sitemaps and Search Console properties per site.

Redirects: plugin or server?

Server-level redirects (in the web server or host panel) are fastest; plugin redirects are easier to manage. Either works for SEO if they’re 301s and go straight to the final URL. Problems come from mixing several systems, which creates chains and conflicts. Pick one place and document it (redirect types).

Frequently asked questions

Sources

• WordPress.org Documentation: Settings Reading screen
• Google Search Central: Block search indexing with noindex
• Google Search Central: Remove a page hosted on your site from Google
• Google Search Central: Redirects and Google Search
• Google Search Central: Understanding Core Web Vitals and Google search results

Last reviewed October 14, 2026.