Review a WordPress layout with evidence

---
name: "aboutcodex-wordpress-layout-review"
description: "Review a WordPress page or template for layout, reading hierarchy, and responsive defects using rendered evidence. Use when the user asks to audit or improve an existing WordPress design."
---

# WordPress layout review

Review the actual rendered page and the relevant template or block composition. Follow the user's requested pages, design direction, and authorization.

Establish which layer owns a visible issue before proposing a change: theme shell, archive template, native block attributes, plugin output, or an overriding style rule. A fix for a single article should not constrain every page carrying a shared topic class.

Compare a wide and narrow viewport when a browser is available. When only screenshots are supplied, state that scope and avoid claiming to have tested interactions. Preserve the site's existing editor and theme ownership unless the user requests a migration.

Use references/NOTES.md to inspect hierarchy, reading width, content density, and interaction states. Tie each finding to a page location, observed behavior, user impact, and the smallest reasonable correction. Distinguish content problems from CSS problems.

For authorized fixes, preserve existing URLs and editorial content. Scope selectors to the intended page or component. Recheck the changed view and one other view that shares its template or styles. Inspect narrow layouts for overflow and badly wrapped controls.

Report the material improvements and the checks actually performed. Do not invent photos, testimonials, review outcomes, or product facts to make the design seem complete.