Common Technical SEO Issues on WordPress Websites

1. Index bloat from tag, category, and archive pages

WordPress automatically creates archive pages for categories, tags, authors, and dates. On a site with a handful of posts and dozens of tags, that can produce many thin pages that each list one or two posts. Those pages compete with your real content for crawling attention and rarely help anyone who lands on them.

• Check: search Google Search Console’s page indexing report and your sitemap for /tag/, /author/, and date-based URLs.
• Fix: consolidate tags, keep categories meaningful, and set thin archive types to noindex in your SEO plugin. On single-author sites, author archives usually duplicate the blog page and can be disabled or noindexed.
• Keep: category pages that act as useful topic hubs. Add an introduction and treat them as real pages.

2. Attachment pages

Older WordPress sites often have a separate page for every uploaded image, containing little more than the image itself. WordPress changed this in version 6.4: according to the WordPress core development note, new installs have attachment pages turned off by default, while existing sites keep them enabled on upgrade so nothing breaks.

• Check: visit a URL like /?attachment_id= followed by an image ID, or look for attachment URLs in a crawl.
• Fix: if your site was built before 6.4 and you do not need attachment pages, disable them (the core note describes the wp_attachment_pages_enabled option) or use your SEO plugin’s setting to redirect them to the file or parent post.

3. Duplicate and missing titles and descriptions

Themes and page builders often reuse the same template, so many pages end up with the same title tag, such as just the site name, or with titles generated from the page name alone. Duplicate titles make it harder for searchers to tell pages apart.

• Check: run a crawl and sort by title and meta description to find duplicates and blanks.
• Fix: write a unique, descriptive title for every important page. Set sensible templates in your SEO plugin for posts and archives so new pages are not left blank.
• Watch for: two plugins, or a theme plus a plugin, both outputting title or meta tags. View the page source and confirm each tag appears once.

4. Redirect chains and loops

Every time a page is renamed or a site is migrated, redirects pile up. Over time, an old URL might redirect to another old URL, which redirects again before reaching the final page. Google’s documentation says its crawlers follow up to 10 redirect hops by default (Google Search Central), but long chains still slow users down and waste crawling.

• Check: crawl the site and export redirect chains. Also check http to https and www to non-www behavior together; misconfigured combinations often add a hop.
• Fix: point every old URL directly to its final destination, and update internal links so they link to the final URL rather than relying on redirects.
• Use permanent redirects for permanent moves. Google’s redirect documentation explains that permanent redirects signal that the target should be shown in search results, while temporary redirects keep the source page in results.

5. Plugin conflicts and overlap

Many WordPress SEO problems come from plugins doing the same job twice: two SEO plugins, a theme with built-in SEO settings plus a plugin, or several caching and optimization plugins stepping on each other. Symptoms include duplicate meta tags, two sitemaps, broken layouts after caching, and scripts loading twice.

• Keep one SEO plugin and turn off overlapping SEO features in your theme or page builder.
• Keep one caching and performance plugin, or use your host’s caching if it provides it, but not several stacked together.
• Remove plugins that are inactive or abandoned. Fewer plugins means fewer conflicts and less to update.
• After updates, spot-check key pages and the page source for changes in titles, canonicals, and robots tags.

6. Sitemap problems

Since version 5.5, WordPress core generates a basic XML sitemap at /wp-sitemap.xml. Most SEO plugins replace it with their own. Problems usually come from having both, or from sitemaps listing pages that should not be indexed.

• Confirm there is one sitemap index and that it is submitted in Google Search Console.
• Make sure the sitemap only lists canonical, indexable pages that return a 200 status, not redirects, noindexed pages, or thin archives.
• Reference the sitemap in robots.txt.
• Check that new pages appear in the sitemap after publishing.

7. Canonical tag errors

Canonical tags tell search engines which version of a page you prefer when similar versions exist. In its guidance on consolidating duplicate URLs, Google describes rel=”canonical” as a strong signal, one input among several such as redirects and sitemaps, so conflicting signals can lead Google to choose a different canonical than you intended.

• Common errors: every page canonicalized to the homepage after a misconfiguration, staging URLs left in canonical tags after a launch, canonicals pointing to redirected or noindexed URLs, and paginated pages all canonicalized to page one.
• Check: in a crawl, compare each page’s canonical URL to its own URL, and review Search Console’s page indexing report for pages where Google chose a different canonical.
• Fix: make canonicals self-referencing on unique pages, and align canonicals, internal links, sitemaps, and redirects so they all point to the same preferred URLs.

8. Core Web Vitals and performance

Google’s Core Web Vitals documentation sets targets of Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Google recommends achieving good Core Web Vitals, while noting they are part of a broader page experience picture rather than the only thing that matters.

On WordPress, common causes of poor scores include:

• Heavy page builders and themes loading large amounts of CSS and JavaScript on every page
• Uncompressed or oversized images, especially hero images and sliders
• Too many third-party scripts: chat widgets, tracking pixels, embedded reviews, and fonts
• Slow or overloaded hosting
• Layout shifts from ads, banners, or images without set dimensions

Use the Core Web Vitals report in Search Console for real-user data and PageSpeed Insights to diagnose individual pages. Fix the biggest templates first, since one theme change can improve hundreds of pages.

9. Crawl traps

Crawl traps are URL patterns that generate nearly endless variations of the same content, so crawlers spend time on useless pages. On WordPress sites, the usual suspects are:

• Internal search result pages (?s=) that are linked or indexed
• Calendar and event plugins that create pages for every day, month, and year far into the future
• Faceted filters on WooCommerce shops that combine color, size, price, and sort parameters
• Session IDs or tracking parameters added to internal links
• Reply-to-comment links creating parameter URLs

Fixes depend on the source: noindex internal search results, configure event plugins to limit archive depth, avoid linking to filtered URLs that should not be indexed, and use robots.txt carefully to block crawling of patterns that add no value. Be cautious with robots.txt, since blocking a page from crawling does not by itself remove it from the index.

How to find technical SEO issues on WordPress yourself

1. Start with Search Console

   Review the page indexing, sitemaps, and Core Web Vitals reports for obvious problems.

2. Crawl the site

   Use a crawler to list every URL with its status code, title, canonical, and indexability.

3. Inventory plugins and theme settings

   List every plugin and note which ones affect SEO, caching, or page output.

4. Prioritize by impact

   Fix site-wide template and settings problems first, then individual pages.

5. Recheck after changes

   Recrawl and monitor Search Console over the following weeks.

If you would rather have a specialist handle it, our SEO audit covers each of these areas, and our website maintenance service helps keep them from coming back.