WordPress SEO Issues: How to Find and Fix Them
By David Roche | Reviewed 19 October 2026
Start a WordPress SEO fix by confirming the problem, finding where it occurs and checking what changed. An error report is a clue; it is not a reason to change every setting or install another plugin.
This guide helps you investigate common problems with access, indexing, redirects, page output, performance and enquiries. Make one controlled change, retest the affected page and keep a way to restore the previous setup. Some faults are straightforward; others need your host or developer.

Triage the problem before editing
| What you notice | Check first | Priority |
| Public site unavailable or showing certificate warnings | Open important URLs while logged out and contact the host with the error and time. | Restore safe public access. |
| Forms or checkout fail | Complete the journey and confirm receipt or the approved test transaction. | Restore the customer function. |
| Important pages unexpectedly excluded | Inspect exact URLs and the current access or indexing instructions. | Correct unintended barriers. |
| Traffic or enquiries decline | Compare search, analytics and business records for the same period. | Establish where the decline occurs. |
| A tool flags a warning | Read the reason and inspect representative pages. | Assess its actual effect. |
Record the exact URL, date and time, device, observed result and expected result. Note whether one page, one template or the whole site is affected. Check recent content edits, updates, redirects, caching changes and security rules.
For a meaningful change, confirm that you have backups of files and the database and know how to restore them. Use a protected staging copy for plugin conflicts, theme changes or server-related work. Do not publish private staging content to make a test pass.
An important page is missing from Google
Check its status rather than guessing from a search
Enter the full URL in Google Search Console’s URL Inspection. The initial information is stored data, so check its crawl date. Use Test live URL to investigate the current page after a change. A successful live test does not mean the page is already indexed or guarantee that it will appear.
A missing result in a site: search is not proof of non-indexing. Inspect the particular page and decide whether it should be public and eligible for search. Duplicate URLs, private areas and genuinely removed pages may be intentionally absent.
Google’s URL Inspection guidance
Trace an accidental exclusion to its source
For a public WordPress site, review Settings → Reading and the “Discourage search engines from indexing this site” option. Also check the page’s SEO settings, template rules and any noindex response header. Removing one setting may not remove another instruction generated elsewhere.
Noindex and robots.txt do different jobs. Google must be able to fetch a page to read its noindex instruction. A robots.txt block controls crawling and is not a reliable way to keep a URL out of results or protect private information.
Correct the unintended restriction on the relevant public page, clear the appropriate cache and retest. Keep necessary privacy and security controls. A sitemap or indexing request does not override an access block or noindex instruction.
Follow the full workflow in Indexing and Sitemaps
Google or an AI search crawler cannot access a page
If you can open a page but a crawler cannot, check whether you are logged in or exempt from a security rule. Look for login screens, challenge pages, denied requests or server failures affecting the public URL.
Ask the host or security administrator to inspect the relevant requests and verify the crawler’s identity. A user-agent label alone is not enough to establish that a request came from Google. Do not disable the firewall globally as a routine fix.
Search crawling and model-training controls serve different purposes. Review the actual bot and rule before changing an “AI” setting. Allowing one search crawler does not establish that every assistant can access or cite your website.
Use Is Your Website Blocking Google or AI Search for detailed access checks
A page returns a 404 or goes to the wrong destination
Decide what the URL should do
Open the exact address and check its response and destination. A visible page is not enough: an error template may look normal, and a redirect can take the visitor somewhere unintended. Use the inspection information or ask your developer to check the HTTP response.
| What should happen | Appropriate action |
| The page still exists at this URL | Investigate an incorrect redirect, removal rule, routing problem or publication setting. |
| The page moved permanently | Redirect the old address to its relevant replacement and update internal links. |
| The page was removed with no suitable replacement | A genuine 404 or 410 can be appropriate. Remove obsolete internal links. |
| The destination redirects again or loops | Trace the rules across WordPress, the host and CDN; remove conflicting or unnecessary hops. |
Do not redirect every missing page to the homepage or return a successful response with no useful content. Check whether the visitor’s original task has a genuine replacement.
Google’s explanation of HTTP status codes
Check rules as well as the post
If an existing post unexpectedly redirects or returns Gone, inspect the redirect systems that can affect it. Removing a mistaken redirect or 410 rule is different from deleting the post. Record the rule and confirm the intended URL before changing it.
If many posts return 404 after a migration or server change, ask your maintainer to check permalink routing and server rewrite configuration. Do not change all slugs or switch the site-wide permalink structure as an unplanned repair.
Google selects a different canonical URL
A canonical declares your preferred version of duplicate or very similar content; it is not a command Google must follow. In URL Inspection, compare the user-declared and Google-selected canonical where available. Then open both pages and examine the actual content.
Check redirects, internal links, sitemap entries and any canonical output from the theme, plugin or server. Correct contradictory signals at their source. If the pages serve genuinely different purposes, assess the content rather than forcing a canonical between unrelated pages.
A canonical field saved in a dashboard does not prove the tag is present on the public page. Inspect the output after clearing relevant caches. Avoid adding a second canonical snippet over an existing one.
Google’s canonical URL guidance
Review archives individually. A useful category page is not automatically an error because it contains article excerpts. Blanket noindex or removal rules can eliminate useful routes without solving the underlying issue.
Titles or structured data look wrong
Separate website output from Google presentation
If a title or description is wrong, compare the SEO field, the public page output and what Google displays. A cache, template or competing plugin may affect output. Google can also generate a different title link or snippet even when your intended information is present.
Correct inaccurate output first, then allow for recrawling and processing. Repeatedly rewriting a correct title to match one search result can create extra work without identifying the cause.
Use Meta Tags and Site Structure for the detailed checks
Check the purpose of a schema warning
Use Google’s Rich Results Test for supported Google features and Schema.org’s validator for broader vocabulary checks. A missing rich result is not proof that a plugin failed. Fix relevant errors and factual conflicts rather than adding another generator.
Keep useful visible FAQs, but do not add FAQ markup expecting to restore Google’s retired FAQ rich result. Valid markup also does not guarantee rankings, clicks or an AI citation.
Follow the WordPress schema implementation guide
Pages load slowly or break on mobile
Reproduce the problem on important page types and on a phone. Note whether the issue is late main content, delayed interactions, layout movement or an element that does not work. A desktop preview or a single lab score is not a complete test.
Use current Core Web Vitals and PageSpeed Insights diagnostics to investigate. Keep lab measurements separate from available real-user data. Check the host and existing optimisation setup before adding a cache plugin, replacing the theme or removing software.
For a broken mobile menu, slider or form, review recent script-delay, minification and caching changes. Restore the last setting if a regression began with it, clear relevant caches and retest. Optimisation should not require a visitor to click twice before an essential control starts working.
Check readable text, keyboard access, overlays and working buttons. Use browser tools and real devices; the retired Google Mobile-Friendly Test is not a current troubleshooting route.
Investigate performance with Speed and Performance
Review layout and accessibility with the theme guide
An update causes errors or missing page elements
Record what changed and which functions are affected. A theme, plugin, builder, PHP version or combination of components may be involved. Capture the error and its time so your host or developer can examine the relevant logs.
Reproduce the issue on a protected copy and isolate likely components there. Do not deactivate every live plugin as a routine experiment: payments, consent controls, security or other business functions may depend on them.
If the public site is down or the dashboard is inaccessible, contact the host or maintainer for recovery. Use a known restoration plan rather than making unfamiliar database or server-file edits. Error logs should help the investigation without being exposed publicly.
WordPress guidance on common errors
Avoid overlapping functions with the Best SEO Plugins guide
People click the enquiry button but no enquiries arrive
Test the whole journey. A click, an opened form, a confirmation message, an email and a completed booking are different observations. Establish the point at which the process fails rather than treating every click as a lead.
Submit a clearly labelled test through the public page and confirm where it is stored or delivered. Check the intended recipient, spam folder, mail service and form logs where available. A successful WordPress mail-function return does not establish that the recipient received the message.
For an external booking service, follow the link, review the available appointments and complete an authorised test through its agreed process. Confirm the booking record and any confirmation rather than relying only on a website click report.
WordPress explains what wp_mail success means
Then check the analytics event. It should represent the action named, such as a successfully submitted enquiry, and avoid duplicate recording. DebugView can help verify events when debug mode is enabled. Test your existing consent behaviour as part of that process.
Google Analytics guidance on DebugView
Traffic falls but the website appears to work
Separate a fall in Google Search clicks from a fall in analytics sessions or recorded enquiries. Compare the same periods, properties and filters. Check tracking changes, collection gaps and business records before attributing the decline to SEO.
In Search Console, compare affected pages, queries, devices and countries. Consider seasonality, demand and search presentation alongside technical changes. An update occurring near a decline is not proof that the update caused it.
A good average position also does not guarantee many visits. Examine the actual queries and impressions, the pages shown and their relevance to customers. Improve a misleading title or an unsuitable page where the evidence supports it, rather than adding schema as a universal click remedy.
Google’s guidance on investigating search traffic drops
Use the traffic-drop investigation guide
Retest and record the result
- Record the URL, original symptom, evidence and setting or component changed.
- Check the public page while logged out and test any affected mobile or customer function.
- Compare the current result with the original problem, not only with a plugin score.
- Recheck relevant inspection or reporting data after processing. A live fix and an older crawl record can describe different moments.
- If a new problem appears, restore the previous setting and retest before attempting another change.
A useful handover includes exact URLs, timestamps and time zone, reproduction steps, recent changes and the last known working setup. Share necessary logs through an appropriate private support route, without publishing credentials or customer information.
A simple troubleshooting record
Fictional example: a cleaning service page returns 410 although the post remains published. The owner records the response and finds a matching removal rule in the redirect manager. They confirm the service should remain public, preserve the rule details and remove only that mistaken rule. After clearing the relevant cache, they verify the expected page response, mobile layout and enquiry form. They inspect the URL again later to review Google’s updated information. The fix restores the intended page behaviour; it does not promise an indexing date or a ranking gain.
For routine setup and maintenance, use the WordPress SEO guide


