Wordpress LCP Issue Diagnostic Playbook

Symptoms

• Wordpress LCP Issue appears in a public page, wp-admin workflow, order, product, email, report, crawl signal, or support ticket.
• The issue may affect revenue, access, search discovery, customer trust, maintenance confidence, or recovery readiness.
• The result may have started after an update, import, migration, provider change, cache rule, SEO setting, or hosting event.

Most Common Causes

• The visible symptom can come from WordPress, WooCommerce, hosting, cache/CDN, payment providers, email providers, crawl directives, product data, or plugin configuration.
• Multiple owners may show the same symptom, so changing every related setting can create duplicate work and unclear evidence.
• Search Console and sitemap signals can help discovery, but Google still decides crawling, indexing, canonical selection, and ranking independently.

How To Confirm The Cause

• Record the exact URL, admin screen, order, product, provider, message, status code, or log entry before applying a fix.
• Compare the current output with the expected workflow and preserve support-safe screenshots, exports, or notes.
• Check sitemap, canonical, noindex, robots, provider, or WooCommerce state only when those layers are relevant to the symptom.

Fixes

• Apply the smallest reversible change that belongs to the confirmed owner.
• Clear only the relevant cache, retry only the affected workflow, and avoid destructive database, payment, DNS, or restore actions unless they are approved.
• Use a WPlura local report, checklist, export, or documentation page to hand off evidence when another owner must act.

How To Verify The Fix

• Repeat the exact workflow that exposed the issue with the same role, device, gateway, product, URL, or crawl context.
• Confirm the page output, status code, order note, email result, product data, sitemap entry, or report now matches the expected result.
• Document the final owner, date, evidence, and next review point.

When To Contact Support

Escalate when the issue involves payment-provider account state, private customer data, malware cleanup, hosting/network controls, destructive restore work, DNS/Search Console ownership, or code-level debugging beyond normal wp-admin review.