Refresh PerformWP site content around 1.6.0 positioning and conversion paths

Context

Authority & Growth audit on 2026-07-07 found that the live PerformWP site has a small content inventory and several high-value pages lag behind current product positioning.

Verified sources:

• PerformWP MCP content inventory: 11 published pages, 3 published posts, 24 published docs.
• Public sitemap review: homepage refreshed in 2026; posts and docs refreshed selectively in 2025.
• Current product listing describes newer 1.6.0 capabilities such as redesigned Assets Manager, full-page cache controls, safer cache writes, scanner interface, validation, and current metadata.
• Public site feature, audit, and docs pages still use older titles, metadata, repeated copy, or sparse content in several places.

Proposed scope

1. Refresh /features/ to reflect current product capabilities.

• Replace repeated placeholder descriptions across feature cards.
• Add current feature clusters: Assets Manager scanner, page cache controls, response validation, stale regeneration and preload scheduling, observability stats, WooCommerce controls, CDN, preconnect, DNS prefetch, and Menu Cache.
• Add contextual links into the most relevant docs.

2. Refresh the introductory product post or replace it with a current evergreen overview.

• Explain what Perform does now, who it is for, and where it fits in a WordPress performance workflow.
• Include current release positioning without unsupported performance claims.
• Link to docs, features, GitHub, the product listing, and the audit page.

3. Rework /web-performance-audit/ as a stronger conversion page.

• Add who should request an audit, what the report includes, expected inputs, deliverables, proof/trust signals, and the next step.
• Fix stale internal links where found.

4. Improve /docs/ as a documentation hub.

• Replace generic archive metadata and thin archive copy.
• Surface feature groups and high-intent docs.
• Add links from feature pages into related docs.

5. Prepare one new educational comparison or solution draft after the refreshes.

• Suggested first draft: WordPress Asset Manager vs Cache Plugin: What Each One Optimizes.
• Keep public copy competitor-neutral and avoid unsupported rankings or Core Web Vitals guarantees.

Acceptance criteria

• Content changes are prepared as WordPress drafts/previews or repo/site PRs before publish.
• No public content is published without owner approval.
• No raw Custom HTML blocks are introduced.
• Rank Math titles and descriptions are updated for affected pages.
• Internal links are added between feature, docs, blog, product listing, GitHub, and audit conversion paths where relevant.
• Screenshots are captured before and after any visible page design changes.
• Performance claims are conservative and tied to supported product behavior.

Validation

• Draft/previews open successfully.
• Block validation passes with registered blocks.
• Metadata is visible in Rank Math or equivalent SEO tooling.
• Internal links resolve to live intended URLs.
• Any design-visible change includes screenshot proof.

Start with the PerformWP content inventory, public sitemap, current 1.6.0 product listing, and the existing features, audit, docs, and introductory post pages. Prepare drafts or a site PR covering the proposed refreshes, then validate registered blocks, Rank Math metadata, internal links, previews, and screenshots. Done means owner approval is still required before publication and all listed acceptance criteria pass.