(Actual) WordPress Help for (Actual) Business Owners

WordPress is the software running the machinery behind your website. It gives you a private dashboard for pages, posts, images, users and other site content. Your screen may look different from somebody else's because themes, plugins and editing tools vary. This is normal. The machine has many outfits.

• WordPress is a content management system, usually shortened to CMS.
• The public website is the front end. The area you log into is the back end or Dashboard.
• Themes control presentation and site structure. Plugins add features.
• You do not need to understand every part of WordPress to safely manage ordinary content.

After you log in, the Dashboard is the administrative side of your website. The menu normally runs down the left. What appears there depends on your permissions and the software installed. If an Internet tutorial shows twelve buttons you do not have, this is not necessarily a crisis.

• Use Pages for permanent site pages such as About or Services.
• Use Posts for dated articles, news or blog content.
• Use Media to manage uploaded images and files.
• If a menu item mentioned in an online tutorial is missing, your site may simply be configured differently.

The front end is what visitors see. The back end is where authorized users manage the site. Editing something in the back end does not always mean visitors can see the change immediately.

• Preview changes when that option is available.
• After publishing or updating, open the public page and check your work.
• Caching can occasionally make an old version appear for a short time.

Pages are generally used for long-lived information. Posts are generally used for dated, chronological content such as articles, news and updates.

• Use a Page for About, Contact, Services and other permanent destinations.
• Use a Post for news, articles, announcements and ongoing publishing.
• Do not turn everything into a Post merely because WordPress offers the button.

WordPress sites can use different editors, so your controls may not match every tutorial written by a man shouting at YouTube. The safe principle is universal: locate the correct page or post, edit the content you understand, preview it, then verify the public page.

• Confirm you are editing the correct page before changing anything.
• Make small changes rather than rebuilding a section you do not understand.
• Use Preview when available.
• After Update or Publish, inspect the live page on desktop and mobile.

WordPress lets content exist without being publicly visible. Drafts are useful while work is incomplete, and posts can often be scheduled for a future date and time.

• Draft means the content is saved but not publicly published.
• Publish makes it public, subject to any visibility settings.
• Scheduling is useful for news and blog posts.
• Double-check the date, time and timezone before relying on a scheduled publication.

Deleting a Page or Post usually moves it to Trash first rather than destroying it immediately.

• Use Trash when you are confident content is no longer needed.
• Items can normally be restored from Trash until it is emptied.
• Be careful deleting pages that may be linked from menus, search engines or other pages.

WordPress can keep earlier versions of page and post content. Revisions are useful when an edit goes sideways, although the exact revision controls depend on the site's editor and configuration.

• Look for Revisions or History in the editing interface.
• Compare versions before restoring one.
• Restoring an old revision can also remove newer good changes, so read before clicking.
• If the page is built with a specialized editor, its own history tools may matter more than generic WordPress instructions.

Categories and tags organize posts. They are useful when they reflect a real content structure. Creating seventeen near-identical categories because one article felt lonely is less useful.

• Categories are generally broad groupings of related posts.
• Tags are generally more specific labels, when the site actually uses them.
• Reuse existing terms rather than creating singular/plural duplicates.
• Do not invent taxonomy for one post unless it serves an ongoing organizational purpose.

Many WordPress themes use a Featured Image as the representative image for a post or page in archives, cards, social previews or other layouts. Exactly where it appears depends on the site.

• Use an image that represents the content rather than merely decorating the editing screen.
• Keep featured-image proportions reasonably consistent across similar content.
• Follow the same web-image sizing and compression rules used elsewhere in this guide.
• Check the live archive or listing after changing one.

WordPress can restrict the visibility of individual posts and pages. Password-protected content is not the same thing as a secure client portal.

• Public content is visible normally.
• Private content is limited according to WordPress user permissions.
• Password-protected content can be viewed by anyone who has the content password.
• Do not use a simple page password for genuinely sensitive records, financial information or confidential client data.

Phone numbers, email addresses, hours and addresses often appear in more than one place. Changing one instance does not guarantee you changed all of them.

• Search the site for the old information after making an update.
• Check the header, footer, Contact page and prominent calls to action.
• Check forms and automated confirmation messages when relevant.
• If the business address or phone number changes, remember that listings outside the website may also need updating.

Hours are deceptively easy to update badly because they may appear on the website, maps, directories and search profiles at the same time.

• Keep the site's primary hours accurate.
• Check special or holiday hours when applicable.
• Look for repeated hours in the footer, Contact page or location pages.
• Update major external business listings separately when needed.

Buttons should take people somewhere useful or cause an expected action. A button labeled LEARN MORE that leads to nowhere in particular is mostly decorative optimism.

• Use clear action-oriented labels.
• Test the destination after changing a button.
• Check phone and email buttons on an actual mobile device.
• Keep repeated calls to action reasonably consistent across the site.

Footers often contain contact details, navigation, legal links, copyright information and other site-wide content. Because a footer appears everywhere, one small edit can have impressive geographic reach.

• Confirm whether the footer is controlled globally before editing it.
• Check contact information and legal links carefully.
• Do not remove required privacy or policy links casually.
• Inspect several pages after changing global footer content.

Contact, quote, registration and other forms are often powered by plugins rather than WordPress itself. Editing the words around a form is one thing. Rebuilding its fields, notifications and integrations is another.

• Submit a real test after changing a form.
• Confirm the success message appears.
• Confirm the notification reaches the intended recipient.
• Do not collect information you do not actually need.
• If the form feeds a CRM, payment system or automation, treat structural changes as consequential.

Staff changes tend to touch more places than the obvious biography. Photos, contact information, author profiles and structured team sections may all be involved.

• Replace the name, title, biography and photo where appropriate.
• Check direct email or phone links.
• Remove access for departing staff separately from removing their public profile.
• Keep portrait dimensions and cropping consistent with the existing team.

A new service usually deserves more thought than adding one sentence to a list. Consider whether visitors need a dedicated page, supporting information, navigation and internal links.

• Explain what the service is, who it is for and what happens next.
• Link to it from genuinely related pages.
• Decide whether it belongs in primary navigation or only contextual links.
• Give it a clear page title and useful URL.
• Check whether forms, pricing, FAQs or calls to action also need updating.

Testimonials are most useful when they are specific, believable and connected to the work they support.

• Use the customer's wording accurately.
• Get appropriate permission before publishing identifying details.
• Place relevant testimonials near the service or subject they reinforce when practical.
• Avoid editing a testimonial so heavily that it becomes something the customer did not actually say.

Websites accumulate fossils. Old prices, old staff, old dates and discontinued services can remain perfectly preserved until a customer finds them.

• Periodically review high-traffic and high-value pages.
• Search the site for old names, dates, prices or offers when something changes.
• Update or remove expired promotional content.
• If deleting an established page, consider whether its URL needs a redirect.

For ordinary website photography, Blue Dozen recommends keeping the longest side of an uploaded image at 1920 pixels or less. Bigger is usually just heavier, not visibly better on a normal website.

• Resize oversized camera and phone images before uploading.
• For most photographs, JPEG or WebP is appropriate.
• PNG is useful when transparency or particular graphic characteristics are required, but it can be unnecessarily large for photographs.
• DPI is primarily a print concern. Pixel dimensions and file size matter much more on the web.
• Try to keep similar groups of images at consistent aspect ratios.

Image dimensions and file weight are different things. A 1920-pixel image can still be unnecessarily huge if it is poorly compressed.

• Use the smallest file that still looks good at its intended display size.
• Avoid uploading the original multi-megabyte camera file when a web-sized version will do.
• Large images slow uploads, consume storage and can hurt page performance.

There is no single correct image format for everything.

• JPEG is a dependable choice for photographs.
• WebP can provide excellent quality at smaller file sizes and is widely supported by modern browsers.
• PNG is useful for transparency, logos and certain graphics, but is often wasteful for ordinary photographs.
• SVG can be excellent for vector graphics, but should only be uploaded when your site's configuration safely supports it.

Give image files useful names before uploading them. A descriptive filename is easier for humans to manage and provides more context than IMG_8472.jpg.

• Use simple descriptive words such as custom-kitchen-asheville.jpg.
• Use hyphens rather than a pile of spaces or punctuation.
• Do not cram keywords into filenames.
• Do not rename files inside the server unless you understand how WordPress references media.

Alternative text describes meaningful images for people who cannot see them and helps make websites more accessible.

• Describe the purpose or meaningful content of the image concisely.
• Do not begin every description with 'Image of.'
• Do not stuff SEO keywords into alt text.
• Purely decorative images may appropriately have empty alt text, depending on how they are implemented.

A page looks more deliberate when images serving the same purpose share a consistent shape.

• Keep staff portraits consistent with one another.
• Keep gallery thumbnails or project cards at a common aspect ratio when the design expects it.
• Do not stretch an image to force it into a shape. Crop it instead.
• Check important crops on mobile, where wide images may display differently.

WordPress can store PDFs and other downloadable documents in the Media Library, but that does not mean every document belongs there forever.

• Use clear filenames.
• Replace outdated public documents when appropriate, but be mindful that existing URLs may already be shared or indexed.
• Link text should explain what the visitor is downloading.
• Avoid uploading sensitive or private documents to a public media library.

Replacing an image is usually safer than improvising an entirely new layout around it. Match the role the existing image is already performing.

• Prepare the new image before uploading it.
• Match the existing aspect ratio when practical.
• Use a sensible filename and appropriate alt text.
• Check the crop on desktop and mobile after publishing.
• Do not upload a 6000-pixel phone photo and make the browser negotiate with it.

Logos and simple graphics often need different handling than photographs. Transparency, crisp edges and consistent proportions matter more than photographic compression.

• Use the format already established by the site when replacing a logo.
• PNG or WebP may be appropriate when transparency is required.
• SVG is excellent for vector artwork when the site safely supports it.
• Do not replace a carefully prepared logo with a screenshot of the logo. The ovum committee has standards.

Links connect pages, files and outside resources. A useful link tells the visitor where it goes.

• Prefer descriptive text such as 'View our drainage services' over 'click here.'
• Test links after publishing.
• Use internal links to connect genuinely related pages on your own site.
• Do not create links merely for SEO. Make them useful.

Most normal links can open in the same tab. Opening a new tab is best reserved for cases where preserving the current page is genuinely useful.

• Internal navigation usually belongs in the same tab.
• Downloads or external tools may sometimes make sense in a new tab.
• Do not force every external link into a new window automatically.

Navigation is how visitors move through the important parts of a website. WordPress can manage navigation in different ways depending on the theme and editing setup, so the exact screen may vary even though the job is the same.

• Keep the main navigation focused on destinations visitors actually need.
• Use clear labels. 'Services' is generally more useful than 'Explore Our Synergistic Possibilities.'
• Do not add every page on the website to the main menu.
• After changing navigation, check it on both desktop and mobile.
• If your site uses a specialized menu system or editor, follow that site's established method rather than forcing generic instructions onto it.

Publishing a new Page does not necessarily add it to the site's navigation. Those are separate decisions, which is useful because not every page deserves a seat at the grown-ups' table.

• Publish or confirm the destination page first.
• Open the site's navigation or menu controls.
• Add the page to the appropriate menu and place it intentionally.
• Save the navigation changes.
• Visit the public site and test the new link on desktop and mobile.

Removing something from a menu normally removes the navigation link, not the underlying Page. This distinction has prevented many unnecessary funerals.

• Open the navigation/menu controls and locate the item.
• Remove the menu item rather than deleting the Page itself.
• Save the menu.
• Check whether the destination is linked elsewhere before deciding the Page itself is obsolete.

Most WordPress navigation systems let you change the order of menu items. Order should reflect usefulness and hierarchy rather than the sequence in which somebody remembered the pages existed.

• Keep the most important primary destinations easy to find.
• Group related items logically.
• Avoid very long navigation menus when a simpler structure will do.
• Check mobile navigation after reordering because space and nesting behave differently there.

Dropdowns can organize related pages beneath a broader menu item. They can also become a filing cabinet containing the entire history of the company.

• Use dropdowns for genuinely related destinations.
• Keep labels short enough to scan quickly.
• Avoid excessive nesting, especially on mobile.
• Test every dropdown item after making changes.
• If the menu has become complicated enough to require a map, simplify the information architecture instead.

The words shown in a menu do not always have to match a Page title exactly. A shorter navigation label can make the menu easier to use without changing the actual page.

• Use labels visitors will immediately understand.
• Keep navigation labels concise.
• Changing a menu label normally does not change the page URL or page title.
• Do not rename things so creatively that customers have to decode the navigation.

Search engine optimization is the practice of making your site understandable, useful and technically accessible to search engines and people. It is not a bag of magic words, and Google does not award points for saying Asheville fourteen times before lunch.

• Give each important page a clear purpose.
• Use descriptive page titles and headings.
• Write for the person who actually needs the information.
• Connect related pages with useful internal links.
• Keep important information in readable HTML text rather than only inside graphics.

The SEO title helps describe a page in search results. A meta description can summarize what someone will find there. Your site may use an SEO plugin to manage these fields.

• Write a title that accurately identifies the page.
• Write a concise description that gives a searcher a reason to visit.
• Do not repeat the same title and description across every page.
• Search engines may choose to display different text when they think it better answers a query.

Headings organize a page for readers and help communicate its structure.

• Use one clear primary page heading when your theme/template supports that pattern.
• Use subheadings to divide real sections of content.
• Do not choose heading levels merely because you like their visual size.
• Avoid turning every sentence into a heading.

Internal links help visitors and search engines discover related information on your site.

• Link related services, resources and supporting articles when useful.
• Use descriptive anchor text.
• Do not mechanically link every occurrence of a keyword.
• Periodically check important links after deleting, renaming or reorganizing pages.

Changing the address of an existing page can break old links and create search problems if the old URL is not redirected correctly.

• Do not casually change an established permalink because a plugin suggests a prettier one.
• If a published URL needs to change, plan a redirect from the old address to the new one.
• Check menus, internal links and important external references afterward.
• When in doubt, ask whoever maintains the site.

Your WordPress login gives access to the administrative side of the site. Treat it like the key to the office, not like the Wi-Fi password taped to the refrigerator.

• Use the login address supplied by whoever built or maintains your site.
• Usernames and passwords are case-sensitive.
• Log out on shared or public computers.
• If the login screen suddenly looks unfamiliar, check the website address before entering credentials.

WordPress can normally send a password-reset link to the email address attached to your user account. This is much better than guessing 'Password1!' until morale improves.

• Use the Lost your password? link on the login screen.
• Enter the username or email attached to your account.
• Check spam or junk folders if the reset email does not arrive.
• If you no longer control the account email, contact the site administrator or maintainer rather than creating random replacement accounts.

You can change your own WordPress password from your user profile. WordPress can generate a strong password for you, which is preferable to naming it after the dog and adding 123.

• Go to Users > Profile, or open your own profile from the user menu.
• Find the password/account-management area and generate or enter a new password.
• Use a unique password that you do not reuse on other services.
• Store it in a reputable password manager.
• After changing it, make sure you can log in again before closing every useful browser tab.

Give each person their own account. Sharing one administrator login among the entire staff makes accountability theoretical and password changes unnecessarily theatrical.

• Go to Users > Add New if your role allows it.
• Use an email address the new user actually controls.
• Assign the lowest role that gives them the access they genuinely need.
• Do not automatically make every employee an Administrator.
• Ask the new user to set a strong, unique password.

WordPress roles control what a user is allowed to do. Administrator is not a ceremonial title. It is permission to rearrange the furniture, remove the plumbing and occasionally sell the building.

• Administrator: broad control over the site. Reserve it for people who actually administer the site.
• Editor: can manage and publish content from multiple users.
• Author: can publish and manage their own posts.
• Contributor: can write their own posts but cannot publish them.
• Subscriber: very limited access, generally profile-level.
• Multisite installations may also have a Super Admin role.

If someone's responsibilities change, their WordPress access should change too. Permissions are not a retirement gift.

• Go to Users > All Users if your account has permission.
• Open the user's profile and review the assigned role.
• Choose the least-powerful role that still lets them do their job.
• Be especially deliberate before granting Administrator access.
• If you are unsure what a custom role can do, ask the site maintainer.

When somebody no longer needs access, remove it. Former employees do not need a souvenir key to the website.

• Go to Users > All Users and locate the account.
• Before deleting a user, check whether they own posts or other content.
• When WordPress offers to attribute that content to another user, choose deliberately.
• Do not delete your only working Administrator account.
• If someone left under unusual circumstances, also review passwords, integrations and other account access.

Your WordPress profile can control how your name appears on authored content. It can also contain contact and biographical information depending on the site.

• Review First Name, Last Name, Nickname and Display name publicly as.
• Avoid displaying an ugly login username as your public author name when a proper name is more useful.
• Only add biographical or profile information that the site actually uses.
• Changing a display name is different from changing the underlying username.

Two-factor authentication adds another proof of identity beyond the password. WordPress core installations may not provide the same 2FA controls on every site, so availability depends on configuration.

• If your site offers 2FA, use it for Administrator accounts whenever practical.
• Store recovery codes somewhere secure and separate from the device used for authentication.
• Do not disable 2FA because the extra six seconds have become oppressive.
• If your site does not offer it and you need stronger account security, ask the site maintainer about the appropriate method.

WordPress, themes and plugins receive updates for security, compatibility and features. Updates are important, but blindly pressing every update button on a business website is not a maintenance strategy.

• Backups should exist before consequential updates.
• Plugin and theme compatibility matters.
• Major changes should be tested when the site is business-critical.
• If someone maintains your website for you, let them manage the software layer.

A backup is a recoverable copy of your website. A useful backup strategy includes both site files and the database.

• Know who is responsible for backups.
• A backup is most useful when it can actually be restored.
• Do not assume that downloading a few images is a website backup.
• Before major site work, confirm a recent recoverable backup exists.

Plugins add functionality to WordPress. More plugins do not automatically make a better website. A dashboard containing 73 plugins is not a sign of vigorous health.

• Do not install a plugin merely because an article says you need it.
• Plugins can overlap, conflict or introduce security and performance problems.
• Delete abandoned software only after understanding what it does.
• If your site is professionally maintained, ask before changing the plugin stack.

Your theme and related design tools control much more than the words on one page. This is the part of WordPress where a casual Tuesday can become a very educational Wednesday.

• Changing themes is not comparable to changing a shirt.
• Global typography, colors, templates, headers and footers can affect the entire site.
• Avoid experimenting with site-wide design controls on a live business website unless you know the consequences.

WordPress supports comments on posts, but plenty of business websites do not need them. If comments are enabled, moderation is a job, not a decorative setting.

• Approve legitimate comments intentionally.
• Mark obvious junk as spam rather than proudly preserving it for future generations.
• Review discussion settings before changing site-wide comment behavior.
• If comments serve no business purpose, ask whether they should be enabled at all.

Spam comments often contain generic praise, irrelevant links, suspicious promotions or automated nonsense. Your article about retaining walls did not suddenly inspire a cryptocurrency visionary in Belarus.

• Do not click suspicious links inside comments.
• Use the site's spam controls or moderation tools.
• Delete or mark spam appropriately.
• A sudden flood of spam may warrant reviewing anti-spam and discussion settings with the site maintainer.

WordPress includes tools for assigning a Privacy Policy page, but the legal substance of that policy depends on what your business, website and third-party services actually collect.

• Keep the published privacy policy accessible from the site.
• Review it when adding forms, analytics, advertising, payment tools or other services that collect data.
• Do not assume WordPress-generated starter language automatically satisfies every law or business situation.
• For legal compliance questions, use qualified legal guidance rather than a cheerful WordPress tutorial.

WordPress includes a Site Health area that can flag technical recommendations and critical issues. It is useful diagnostic information, not a video game where every yellow item must be eliminated before dinner.

• Look under Tools > Site Health if your permissions include it.
• Read recommendations before acting on them.
• Some suggestions are server-, theme- or plugin-dependent.
• For a professionally maintained site, send concerning results to the maintainer before making infrastructure changes.

The site administration email can receive important WordPress notices. Changing it may require confirmation and can affect who receives system messages.

• Know which email is currently responsible for the site.
• Do not replace it with a temporary employee address without thinking about continuity.
• Use a monitored business-controlled address where appropriate.
• Confirm changes and test that important notices still reach the right person.

First make sure the change was actually saved. Then check the public page in a fresh tab or private/incognito window.

• Confirm you clicked Update or Publish.
• Hard-refresh the page or check in a private window.
• Caching may temporarily show an older version.
• Make sure you edited the page that actually produces the content you are viewing.

Desktop and mobile layouts have different amounts of space. A change that looks harmless on a large monitor can wrap, crop or stack differently on a phone.

• Check the live page on an actual phone when possible.
• Look for oversized headings, awkward line breaks, image crops and buttons.
• Do not solve a mobile problem by inserting dozens of manual spaces or line breaks.
• If the layout itself needs rebuilding, stop editing content and get help.

Do not turn one small mistake into an archaeological site by making ten more speculative changes.

• Stop and identify the last thing you changed.
• Use revision/history tools if your installation provides them and you understand them.
• If you are unsure, contact the person who maintains the site and explain exactly what changed.
• Screenshots are extremely useful when asking for help.

A broken link may point to a page that moved, a typo in the address, an expired external resource or a file that was removed.

• Open the link and confirm the failure.
• Check the destination URL for obvious errors.
• If an internal page moved, update the link and make sure the old URL is redirected when appropriate.
• If an outside resource disappeared, replace or remove the link.
• Do not leave a knowingly broken link because 'we'll remember later.'

A form that appears to submit successfully can still fail to deliver email. Forms, email delivery and spam filtering are separate pieces of machinery.

• Submit a test using a real email address.
• Check spam and junk folders.
• Confirm the form's notification recipient is still correct.
• Do not repeatedly rewrite the form if the problem may be email delivery.
• If business leads depend on the form, escalate the issue promptly.

A browser security warning can involve SSL certificates, domain configuration or mixed content. This is infrastructure territory, not a good moment to start clicking around WordPress settings.

• Confirm you are visiting the correct domain.
• Take a screenshot of the warning.
• Do not enter passwords or sensitive information through a connection the browser identifies as unsafe.
• Contact the site maintainer or hosting provider.

Some WordPress controls affect the whole website or its infrastructure. They are not inherently forbidden, but they are poor places for casual experimentation on a live business site.

• Theme files and PHP code
• Database tools
• Permalink structure
• DNS, hosting and SSL settings
• Unknown plugin settings
• Global templates and site-wide styles
• User permissions you do not understand