WordPress layout or content looks wrong? Find the source before changing the design.

Use the actual editor’s responsive preview where available, then check the front end at representative desktop/mobile widths and widths between presets. Compare the same section and inspect stacking, container width, padding, text wrapping, image crop and any fixed or sticky elements. A mobile preset is a width approximation, not proof of behaviour on every real device.

Inspect whether the missing element is deliberately hidden at that breakpoint or replaced by another mobile element. Page builders can have per-device visibility and inherited styles; native responsive options also vary by theme/version. Keep intentional design choices unless the owner agrees they are wrong. Do not duplicate hidden content across the page or hide essential text simply to remove overflow.

Confirm the preservation and local/shared scope above before editing. Make the smallest approved component-level adjustment using the supported controls. Keep touch targets, menu opening/closing, text readability, keyboard access and anchor clearance usable. Fixed widths, oversized media, negative spacing and overlays can each cause clipping. If a shared style or custom code is responsible, preserve the evidence for the developer rather than add a site-wide overflow rule that hides the inaccessible part.

Read the actual destination and intended purpose of the affected link. Check for a mistyped path, old domain, removed page, wrong anchor or link attached to a different element. Open the intended genuine destination separately without following an unexpected sign-in or supplying private information. A redirect to an unrelated home page is not a meaningful repair for every broken link.

Preserve the existing link and confirm the editing scope first. In the correct content source, use the supported WordPress link control or the actual builder’s link field to select the intended existing page or enter its approved address. For a same-page anchor, confirm the target exists and is unique. Keep the link text meaningful and avoid opening a new tab merely to conceal confusing navigation.

For menus, identify which desktop/mobile navigation instance and shared location are actually displayed. The Navigation block guidance applies to block-based navigation; classic themes and builders use their own menu controls. Preserve intended parent/submenu structure and test opening, focus and destination on both screen sizes. Shared-menu edits need the site owner’s scope and a check of affected pages.

Confirm which approved image the element should use and whether it is a content image, featured image, background or dynamic field. Check the selected media/source and whether the actual public image loads. A missing attachment, old external/temporary URL, denied file request, hidden element and wrong crop can produce different symptoms.

Use the original licensed/approved asset or supported media selection rather than guessing a replacement file path. Check the actual responsive size, aspect ratio, crop/focal point and fit at the affected width. A background can crop differently from a normal image; revealing the whole image may also change the layout. Keep the subject relevant and do not describe generated images as proof of real work.

Write accurate alternative text for meaningful images and review the image title/caption where used. Decorative images may appropriately have empty alt text; a filename or keyword string is not automatically useful alternative text. Do not delete the media library, remove access controls or perform a blind database URL replacement to repair one image. Preserve originals and verify any approved swap in the real page.

If the correct saved content differs from the public page, compare the actual audience, template and relevant style/cache layer. Ask the owner which page, generated style or delivery cache needs attention. Do not clear every user’s data, disable all optimisation or regenerate the whole site repeatedly without identifying the affected layer and preserving current work.

For a suspected theme/plugin conflict or custom CSS/script, arrange a controlled staging investigation with a recoverable position and the developer. Test one relevant change at a time and keep a record of the before/after result. Deactivating all plugins or switching the live theme can alter forms, access, commerce and shared design, so it is not a safe blanket public troubleshooting step.

If an approved scoped regeneration or cache refresh is required, use the actual product’s current supported process and verify the result after it completes. Recheck the original issue and representative affected pages. Avoid hiding failures with broad overrides, making private content public or editing production PHP from the theme editor as a trial.

Use the site owner or responsible developer for shared templates, complex dynamic content, unknown editor behaviour or a fix that affects other pages. Provide the actual URL, affected element, width/browser, expected and observed result, relevant timing and minimal screenshots with private data removed. Do not send admin passwords, secret keys or database exports in a general enquiry.

Our WordPress support and website maintenance pages can start a scoped discussion. Agree access, source preservation, change authority and verification before work. A layout repair does not itself establish site security, every browser’s behaviour or formal accessibility compliance.

If the actual problem is hosting availability or a resource constraint, use the hosting review guide. Unexpected unauthorised content needs incident handling rather than a cosmetic-only replacement. Keep the next action tied to the actual evidence.