For WordPress SEO, first establish that important pages are publicly accessible and eligible for indexing, with titles and content that answer the reader's question. Then investigate the actual hosting, plugin, performance and mobile-experience problems. Installing an SEO plugin or obtaining a green speed score addresses only part of the work.
This guide covers ten areas for an existing business site, blog or WooCommerce store, explaining what to inspect and how to verify a change. The instructions draw on public official documentation; test the implementation in your own environment. Hosting arrangements, WordPress versions and plugins affect the available settings, so record the current setup before making changes.
Check the foundation first:
- In Settings → Reading, review search engine visibility. A public production site intended for search should not accidentally discourage indexing. Keep access restrictions appropriate to staging or private environments.
- Inspect the response status, robots directives and canonical URL of important pages. Meeting Google's minimum technical requirements does not guarantee indexing or rankings.
- Identify which theme or plugin generates titles, descriptions, canonicals and structured data. Inspect the actual output for duplication or conflicts instead of assuming that a saved setting has taken effect.
- Record the current URL structure before changing permalinks. Working established URLs should not be replaced simply to make them shorter. A necessary migration needs an old-to-new mapping and corresponding redirects.
- Find the sitemap the site actually serves. WordPress introduced core XML sitemaps in version 5.5, normally with
/wp-sitemap.xmlas the index. An SEO plugin may replace that implementation or use another path; verify the response rather than guessing the address.
1. Choose hosting around access and workload
Use Tools → Site Health to record the application environment, including WordPress, PHP, database, theme and plugin details. Combine that information with hosting metrics to investigate slow responses. An anonymous cached product page, a logged-in dashboard and checkout are different workloads.
The current WordPress recommended environment includes PHP 8.3 or later, MariaDB 10.11 or later or MySQL 8.0 or later, and HTTPS support. Check theme and plugin compatibility before upgrading. A version number does not demonstrate how fast a specific site will run.
Consider the main customer regions and network paths alongside dynamic request processing. A CDN can distribute cacheable resources, but it does not automatically remove slow database queries, third-party API waits or origin capacity constraints. When comparing options, record the URL, region, authentication state, cache state and test time. Do not attach a ranking bonus to a provider name or HTTP/3 support.
Useful questions for a host concern allocated resources, recovery procedures, dynamic-cache exclusions, compatibility support and incident handling. Guangsuan's WordPress hosting and optimization service includes migration, cache and plugin optimization, and continuing technical support, with resources and arrangements defined by the chosen plan. The service description is not a benchmark of your site.
2. Diagnose performance with LCP, INP and CLS
The current Core Web Vitals are LCP, INP and CLS. The good thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1, assessed at the 75th percentile with mobile and desktop segmented. INP replaced FID. Lighthouse's TBT can help investigate main-thread blocking, but it is not a substitute for field INP.
Start with the observed problem. For slow main content, inspect the LCP element, document response, resource discovery, download and rendering. For a slow menu, filter or add-to-cart action, record the actual interaction and investigate the responsible work. For unexpected movement, identify the elements that shift during loading and later use.
Serve images at appropriate display dimensions and compare formats using the actual picture. Image compression for SEO involves visual quality as well as file size; no single compression percentage suits every asset. Reserve the correct space. Apply lazy loading to suitable offscreen images, while avoiding delays to initially visible images, especially the LCP image.
Test representative home, article, product and transaction pages under comparable conditions. If PageSpeed Insights lacks sufficient field data, record that limitation and use lab diagnostics and actual interactions to investigate. Missing field data is not a pass. The page-speed measurement guide explains how to keep these observations separate.
3. Review plugin, code and database dependencies
A plugin count does not establish the site's load. Inventory each component's purpose, affected pages, maintenance status, cost and data dependencies. Look for duplicate responsibilities, errors and unnecessary sitewide resources. WordPress's plugin management instructions distinguish deactivation from uninstalling; an uninstall can remove the plugin's own data.
Query Monitor can expose database queries, PHP errors, enqueued resources and HTTP API requests, with information grouped by responsible components. It is a diagnostic tool, not an automatic optimizer, and collecting diagnostics has overhead. Test a suspected component on a staging copy, change one relevant setting and retest the affected functionality.
Before database cleanup, identify the records and the feature that owns them, and keep a recoverable backup. A broad name match such as “contains plugin” does not prove that an option is disposable. Prefer a documented cleanup or uninstall mechanism for the specific component. Retain revisions according to actual editing and recovery needs.
For example, setting WP_POST_REVISIONS to the integer 3 in the wp-config.php guidance limits the number retained; it does not mean “disable revisions” or perform a general cleanup of historical data. The revision history has a practical recovery purpose.
Apply the same care to delayed JavaScript, removed CSS and caching. A menu, consent choice, translated page, form or payment integration may reveal dependencies only after interaction. For WooCommerce, verify the cart, account, checkout and session exclusions; customer-specific responses must not be reused as public full-page cache entries.
4. Structure the page around a clear question
Establish whether the page serves product selection, a procedure, an explanation or an enquiry. Then make the title, opening and sections deliver that task. Heading structure and JSON-LD structured data are different things; adding a particular number of headings does not establish a ranking increase.
Consider a hypothetical article about blurry WordPress product images. It could first ask the reader to compare the original file, delivered image size, displayed size and compression result, then explain the matching fixes. That is a content-planning example, not a diagnosis of a customer site. Keep essential checks in readable text and use genuine, permitted screenshots when they clarify an operation.
A product page needs accurate specifications, uses, limitations and a usable enquiry or purchase route. A tutorial needs instructions the reader can follow. Plugin readability suggestions are prompts for review; do not delete a model number or an important condition merely to obtain a better score.
Validate applicable markup with Rich Results Test and check Google's structured-data policies. Valid syntax, feature eligibility and actual display are separate checks. Select types appropriate to B2B products, company information and articles, without inventing prices, availability or reviews.
5. Link to the next useful answer
Organize related products, explanations, cases and services into navigable paths. A topic page can introduce more specific questions, and a detailed article can link back when that helps the reader. There is no useful universal quota of internal links per thousand words.
An image-compression tutorial might link to responsive image selection where it becomes relevant. A discussion of LCP could point to diagnosing a slowdown after a CDN change. Use descriptive anchor text and explain why the destination is useful at that point.
Follow Google's crawlable-link guidance, then verify the destination and language. Before deleting, combining or moving a page, identify its incoming links. A permanent move should reach the corresponding replacement; a genuinely unavailable page without a substitute can return an appropriate 404 or 410 instead of sending every visitor to the homepage.
6. Support trust with real sources and authorship
Identify actual authors, responsibilities, relevant experience and contact details. When publishing project records, explain the starting conditions, work, observation period and limitations. Place primary sources close to the claims they support. Stock imagery must not become evidence of your team, and another publisher's case must not become your own experiment.
Google's helpful-content guidance discusses E-E-A-T and explains that it is not a single specific ranking factor. It is not a WordPress setting or a score earned by completing an author-profile form.
Record relevant software and document versions in technical guidance. Preserve model and operating conditions in product advice. Company, contact and privacy information should reflect the actual business; a badge or statement cannot replace the underlying evidence.
7. Review AI-assisted material for accuracy and value
AI can help organize questions, outlines and title options. Review the resulting facts, sources, language, duplication and images before publication. Google's generative-AI content guidance focuses on accuracy, quality and relevance; generating many pages without added value can implicate scaled content abuse.
Compare each consequential claim with its source. Are numbers and units correct? Have exceptions, negations or regulatory conditions disappeared? Does the described software feature actually exist? Without hands-on experience, explain that the account is based on public documentation. A detector score, a rewriting percentage or deliberate conversational mistakes cannot establish reliability.
Check whether an existing page already answers the same question. Update it when appropriate, and keep genuinely different tasks distinct. For a practical drafting method, use the seven-step guide to turning a reader's task into a useful article.
8. Complete a real task on mobile
Walk through representative navigation, long-form reading, product selection and enquiry or checkout tasks. Can the menu be opened and closed? Does enlarged text overlap? Are tables understandable and controls easy to operate? Are validation messages clear, and does the submitted form actually arrive?
Google's mobile-first indexing guidance addresses consistency of important content, metadata and accessible resources. Do not remove necessary content from mobile or make primary material depend on a user action to be fetched.
Also check keyboard focus and operation. Review advertising, chat and notification overlays against the page's real task, then test any adjustment. For a store, use isolated sessions to verify account identity, cart totals and transaction behavior. A faster page is not a successful change if it breaks the purchase.
9. Add useful video and questions where they belong
Video can explain a location, sequence or visible difference. Provide an accurate title, description, accessible thumbnail and appropriate text explanation. Test the embedded player for loading and interaction costs; an autoplaying background is not a substitute for an answer.
When targeting Google video features, distinguish video indexing requirements from VideoObject requirements. A dedicated watch page and an article with an incidental embedded video are different situations. Adding markup does not guarantee display.
Use actual customer questions when a concise answer helps, such as why an updated price is not visible after enabling caching. There is no need to append a generic FAQ to every article or impose a fixed phrase length for spoken queries. Google stopped showing FAQ rich results on May 7, 2026; useful visible questions and answers can still serve readers.
10. Maintain information and compare results consistently
Prioritize broken instructions, outdated products, changed document versions, bad links and substantiated reader feedback. Keep accurate material and verify new facts before editing. Do not simply replace the figures in an old case with current-year figures. The sitemap's lastmod should reflect a significant update rather than cosmetic date changes.
After release, inspect content, metadata, caches and critical functionality, then examine crawling and indexing separately. If a submitted URL remains absent, use the access, indexing and content checks to investigate. Track Search Console clicks, Analytics sessions and valid enquiries separately, with consistent page, date, device and market conditions. Record simultaneous campaigns, seasonal changes and other edits.
| Maintenance record | What to retain |
|---|---|
| Problem | URL, page type, observation and original evidence |
| Change | Specific content or setting, responsible component and version |
| Verification | Test conditions, functional checks and raw results |
| Follow-up | Available field data, unresolved questions and next review trigger |
Address demonstrated faults first, then continue the content work that requires sustained attention. The broader ranking-improvement checklist can help connect these WordPress tasks to keyword selection and ongoing review.